When creating a desktop pool in VMware View using View Composer, you may receive an error similar to the below.
What it is generally saying is View Composer has a fault, it was a no permission fault and the problem was with a specific permission which will be listed in the error.
When you installed View and configured to access your vCenter Server you created an Active Directory user (e.g. svc_view) and created a role on the vCenter with the specific permissions only for View (e.g. View Administrator).
If you missed a permission when creating this rule (even I've missed a permission out at least once), just add it to the vCenter role.
As you can see below we are missing the "Virtual Machine.Inventory.CreateFromExisting" and "Global.DisableMethods" permissions...
One of the features of vCloud Networking and Security is the ability to provide load balancing.
This is a great benefit if you do not have a hardware load balancer, do not want to or cannot use Windows NLB, but need to load balance traffic.
It can provide load balancing for the following:
Load balancing methods available are:
In View 5.1 the task of changing the default self-signed certificate on the View Connection Server is much easier than previous versions.
Now a certificate can be requested using the standard Windows MMC based certificates console.
In the case of below we will be using an internal Microsoft AD based certificate authority (CA).
The keyboard combination CTRL+ALT+DEL has been a long known shortcut on Linux systems to immediatley shutdown the server.
In most recent Linux distributions this has been disabled for obvious reasons.
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.