View

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

I’ve been calling one of my recent VMware View 5.x upgrades bad luck because of all the issues I’ve had with version 5.1.1 (799444): The first issue I had was with the 5.1.1 View Agent

——————————————————————————————————————————————————————– Update December 17, 2012 I received an update from the engineer I was working with on this case today to inform me that the new 5.1.2 agent was out and to try it and

I’ve recently been asked a few times over the last 2 months as to whether it is possible to update the VMware View Agent to 5.1 if the View Connection server was still at version

To follow up one of my previous posts: Extracting the msi file from VMware View Client installation executable and installing it via Active Directory Group Policy https://blog.terenceluk.com/2012/02/extracting-msi-file-from-vmware-view.html … a few of my colleagues asked me

Problem You attempt to recompose virtual desktops in a VMware View 5.x pool from within VMware View Administrator but receive the following error message: Internal View Composer error. Contact your administrator. You’ve verified that the

For those who may have come across my previous posts: Disappearing network adapter with VMware View 5.0 and vSphere 5.0 https://blog.terenceluk.com/2012/10/disappearing-network-adapter-with.html … would know that I recently ran into a strange incident where a user

Update There is a way to prevent users from accidentally ejecting their network adapter but I haven’t figured out a way to configure VMs in bulk.  See the following post for more information: Preventing VMware

Problem I was recently asked by an ex-colleague of mine about how I dealt with a printer mapping issue he was currently dealing with.  The issue he had was that users in his organization who