On Technet Edge there is a couple of videos for Virtualization admins to learn more about how Microsoft Virtualization solution works.

It is a very good way to get up to speed what Microsoft has to offer and that it is a competitive solution!

from the jumpstart site:

About this Jump Start series:

The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging “team teaching” approach which makes the class as entertaining as it is educational.

Click here to watch the complete video series

• Virtualization Jump Start (01): Virtualization Overview
• Virtualization Jump Start (02): Differentiating Microsoft & VMware
• Virtualization Jump Start (03a): Hyper-V Deployment Options & Architecture | Part 1
• Virtualization Jump Start (03b): Hyper-V Deployment Options & Architecture | Part 2
• Virtualization Jump Start (04): High-Availability & Clustering
• Virtualization Jump Start (05): System Center Suite Overview with focus on DPM
• Virtualization Jump Start (06): Automation with Opalis, Service Manager & PowerShell
• Virtualization Jump Start (07): System Center Virtual Machine Manager 2012
• Virtualization Jump Start (08): Private Cloud Solutions, Architecture & VMM Self-Service Portal 2.0
• Virtualization Jump Start (09): Virtual Desktop Infrastructure (VDI) Architecture | Part 1
• Virtualization Jump Start (10): Virtual Desktop Infrastructure (VDI) Architecture | Part 2
• Virtualization Jump Start (11): v-Alliance Solution Overview
• Virtualization Jump Start (12): Application Delivery for VDI

Hi

on one of the blogs i am following, Adian Finn, he has a post about a new hotfix from Microsoft that has come out regarding a problem with Hyper-V clusters and CSV volumes in redirected mode, read more at this link and get the hotfix

Consider the following scenario:

• You enable the cluster shared volume (CSV) feature on a Windows Server 2008 R2-based failover cluster.
• You create a virtual machine on the CSV on a cluster node.
• You start the virtual machine on the cluster node.
• You move the CSV owner to another cluster node, and you change the state of CSV to redirected access.
• The connection that is used for redirected access is switched to another connection when one of the following scenarios occurs:
  • The cable for local area network (LAN) is disconnected.
  • The related network adapter is disabled.
  • The connection is switched by using Failover Cluster Manager.

In this scenario, you receive a Stop error message that resembles the following in the virtual machine:

Note

• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all “0x0000007a” Stop error messages are caused by this issue.
• You may also receive other Stop error messages when this issue occurs. For example, you may receive a “0x0000004F” Stop error message.

Hi

Have been playing a little with powershell and SCVMM2012 and with these simple lines i add 64 SCSI vhd drives á 4 GB each and then delete them all while the VM is running

$VM = Get-VM -Name "VMc2test"

for ($i=0;$i -le 63;$i++){

$vhdfilename = "vhdtest" + $i
New-VirtualDiskDrive -VM $VM -Dynamic -Filename $vhdfilename -sCSI -Size 4000 -Bus 0 -LUN $i
}

and to delete them

$vhds = @(Get-VirtualDiskDrive -VM vmc2test | where {$_.BusType -match "SCSI"})

foreach ($vhd in $vhds){

Remove-VirtualDiskDrive -VirtualDiskDrive $vhd

}

and why did i select the ones that had SCSI in the remove part, well the system vhd where the OS resides is on the IDE controller so i can safely assume that the OS will still be accessible, as some of you already know in Hyper-V the boot volume must reside on a IDE controller for the VM to boot.