This issue occurs when you have installed one of these Microsoft patches, 2482017 or 2467023.
If you have already installed these patches, you can install VMware View Client (build 353760) or uninstall the Microsoft patches.
If you have not installed these patches, delay the installation of the Microsoft patches until you have installed VMware View Client (build 353760).
VMware View Client build 353760 has been tested on:
- Windows 7 Enterprise 32 bit + Internet Explorer 8
- Windows 7 Enterprise 64 bit + Internet Explorer 8
- Windows 7 Home 32 bit + Internet Explorer 8
The View Client patch can be downloaded from here. Enter your credentials, accept the EULA and download the appropriate file:
- If you are using Windows 7 32-bit, use VMware-viewclient-4.5.0-353760.exe.
- If you are using Windows 7 64-bit, use VMware-viewclient-x86_64-4.5.0-353760.exe.
To apply this patch
- Click Start > Settings > Control Panel > Add or Remove Programs.
- Choose the previously installed VMware View Client and click Remove.
- Navigate to where you downloaded VMware-viewclient-xxx-4.5.0-353760.exe and run the executable file.
- Follow the installation installation wizard to complete installation.
- Reboot the computer.
Very Important: VMware View Clients with build number 353760 or later are not affected by this issue.
SCVMM RDV plug-in enables dynamic placement of VDI VMs for both personal and pooled VMs. The key benefit of using this plug-in is that it reduces the number of Hyper-V servers required since VMs are placed on demand rather than statically placed. Dynamic placement is achieved by integrating SCVMM 2008 R2 with the RDS Connection Broker in Windows Server 2008 R2.
Dynamic Placement for Personal VM is available in Windows Server 2008 R2. Pooled VM requires Windows Server 2008 R2 SP1.
Figure below shows the integration:
The bits and content are available at: http://go.microsoft.com/fwlink/?LinkID=195952
For those of you that don’t understand how this works Ill write a little process workflow so you understand.
1. The VDI client tries to connect to the last VM it was using via the Connection Broker.
2. The Broker, knowing where it was in the cluster, in communication with SCVMM, tries to wake the VM from a save state
3. Problem is that the server its trying to start the VM on is already at capacity and it cant start there
4. SCVMM gets involved as part of this and moves the VM to another node in the cluster based on its dynamic placement algorithm, via a SAN move
5. The Connection Broker is then told which host the VM is now on and running
6. The user connects to the VM
Microsoft Desktop Virtualization is going to be a real competitor against VMware View