Those who have worked with VMware View are probably aware that VMware provides the following optimization guide for Windows 7 virtual desktop deployments: VMware View Optimization Guide for Windows 7 While the optimization settings are
As most administrators who have deployed VMware View would know, a service account is used by the View Connection server to connect to the vCenter server to create, manage and delete the virtual desktops. The
Problem You’ve completed the install of a VMware View 5.1 Connection server and began to configure the vCenter Server settings for the environment but receiving the following error when enabling View Composer in the View
Problem You attempt to install VMware View Composer on your Windows server but the process fails with the following error: The exception unknown software exception (0xc0000409) occurred in the application at location 0x6d3afe35. Click on
Administrators of VMware View 4.x and 5.x would know that View Manager would from time to time fail to complete operations with virtual desktops in pools and eventually leave orphaned or stale virtual desktops in
To follow up on my previous post: Deploying VMware vSphere 5.1 Single Sign On, Inventory Service and vCenter Server https://blog.terenceluk.com/deploying-vsphere-51-single-sign-on/ … this post serves to continue the deployment by installing an additional vCenter and configuring
As I had to deploy 2 new instances of vCenter over the weekend in Linked Mode, I took the opportunity to document all the steps so I could write a blog post demonstrating the steps
I have to say that I wasn’t too satisfied with the documentation available setting up the database for installing the VMware vSphere 5.1 Single Sign On component independently: … rather than using the VMware vCenter
As with my previous posts for creating vCenter 4.1 and 5.0 databases, this post serves to demonstrate how to set up the database for vCenter 5.1. Before I begin, it’s important to note that the
While I’m sure not everyone is going to run into the same issue as I did here but because this issue almost got me to pick up the phone to call VMware support until I
