From the desk of Vishwa Kumbalimutt:
We’re pleased to announce RTW of SCVMM RDV plug-in that 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 dont understand how this works Ill write a little process workflow so you undertand.
1. The VDI client tries to connect to the last VM it was usign via the Connection Broker.
2. The Broker, knowing where it was in the cluster, in commuication 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
You mentionned "SAN move" for VM reallocation, but, is it really a SAN move or a cold Migration process via VMM migration algorithms (Quick or Live ones)?
Thanks for your article, :)
High Availability for VDI is possible without SCVMM?