This poster provides a visual reference for understanding key Hyper-V technologies in Windows Server 2008 R2 Service Pack 1. It focuses on architecture, snapshots, live migration, virtual networking, storage, RemoteFX and Dynamic Memory.
To download the poster click on the picture 
System Center Virtual Machine Manager 2012 delivers industry leading fabric managment, virtual machine management and services deployment in private cloud environments. Virtual Machine Manager 2012 offers key new features that include hypervisor creation and management, network management, storage management, private cloud creation, self-service usage and service creation. It features deep investments in server application virtualization, service design and service modeling all of which can be used to efficiently offer an on-premises private cloud.
Feature Summary
System Requirements
Download System Center Virtual Machine Manager 2012 Beta Evaluation HERE
Just click on the picture 
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
Nice huh 
Microsoft Desktop Virtualization is going to be a real competitor against VMware View
HyperV_Mon is my free tool for monitoring and diagnosing performance issues with Hyper-V.
After prompting from a user with a lot more processors then the test systems here, I updated the HyperV_Mon tool to handle resizing in general, and to adjust the root partition processor display. This new version is a minor release (1.8.0).
In the works will be a version 2.0 that will look at 2008 R2 with SP1 changes. This should come out in Q1 of next year.
Download it HERE
Jonathan has created a nice script. This script checks witch updates are missing from Hyper-V hosts and SCVMM Server.
What updates?
Updates are regularly released for SCVMM Server, Hosts, and the Admin Console. These updates must be applied to all Hosts no matter how many you have. Updates are also released for technologies SCVMM leverages:
As well as components SCVMM cannot function without:
The difficulty is in making sure all systems are fully updated. This is a time-consuming task.
WSUS takes care of this for me…
Not necessarily. There are certain Hotfixes that need to be downloaded manually, but for the most part Windows Update is the key. WSUS is Microsoft’s solution to distributing Windows Updates within an enterprise, and this pulls from Windows Update as well. Unfortunately, rules in WSUS are sometimes set up such that all updates required do not find their way to SCVMM systems. So, there are layers of complexity in keeping systems up to date.
Prevent problems with VMMUpdate
With this script you now or that your Hyper-V hosts & SCVMM Server are up to date.
To download the latest follow the link HERE
Just like any other operating system, over time, a disk will become fragmented. Virtual machines are no different. The time that it takes for a disk to become fragmented depends on what data is being added to and removed from the virtual machine hard drive.
Why use MyDefrag instead of the standard Windows defragger?
When you run MyDeFrag.exe with /verysilent it detect automatically the OS and then install x86 or x64 version from MyDefrag. It’s always installed at c:\program files. You can deploy it with MDT 2010 automatically when installing the OS. Or run it from a network share.
You can use Group Policy Preferences to schedule it. 