Microsoft System Center Virtual Machine Manager virtualization environments
Follow this guidance if you use Hyper-V with Microsoft System Center Virtual Machine Manager (VMM) to provide virtual machines.
This release supports the VMM versions listed in the System requirements article.
You can use Provisioning Services and Machine Creation Services to provision:
- Generation 1 Desktop or Server OS VMs
- Generation 2 Windows Server 2012 R2, Windows Server 2016, and Windows 10 VMs (with or without Secure Boot)
Upgrade from VMM 2012 to VMM 2012 SP1 or VMM 2012 R2
For VMM and Hyper-V Hosts requirements, see https://technet.microsoft.com/en-us/library/gg610649.aspx. For VMM Console requirements, see https://technet.microsoft.com/en-us/library/gg610640.aspx.
A mixed Hyper-V cluster is not supported. An example of a mixed cluster is one in which half the cluster is running Hyper-V 2008 and the other is running Hyper-V 2012.
Upgrade from VMM 2008 R2 to VMM 2012 SP1
If you are upgrading from XenDesktop 5.6 on VMM 2008 R2, follow this sequence to avoid XenDesktop downtime.
- Upgrade VMM to 2012 (now running XenDesktop 5.6 and VMM 2012)
- Upgrade XenDesktop to the latest version (now running the latest XenDesktop and VMM 2012)
- Upgrade VMM from 2012 to 2012 SP1 (now running the latest XenDesktop and VMM 2012 SP1)
Upgrade from VMM 2012 SP1 to VMM 2012 R2
If you are starting from XenDesktop or XenApp 7.x on VMM 2012 SP1, follow this sequence to avoid XenDesktop downtime.
- Upgrade XenDesktop or XenApp to the latest version (now running the latest XenDesktop or XenApp, and VMM 2012 SP1)
- Upgrade VMM 2012 SP1 to 2012 R2 (now running the latest XenDesktop or XenApp, and VMM 2012 R2)
Installation and configuration summary
- Install and configure a hypervisor.
- Install Microsoft Hyper-V server and VMM on your servers. All Delivery Controllers must be in the same forest as the VMM servers.
- Install the System Center Virtual Machine Manager console on all Controllers. The console version must match the management server version. Although an earlier console can connect to the management server, provisioning VDAs fails if the versions differ.
- Verify the following account information:
The account you use to specify hosts in Studio is a VMM administrator or VMM delegated administrator for the relevant Hyper-V machines. If this account only has the delegated administrator role in VMM, the storage data is not listed in Studio during the host creation process.
The user account used for Studio integration must also be a member of the administrators local security group on each Hyper-V server to support VM life cycle management (such as VM creation, update, and deletion). Note: Installing a Controller on a server running Hyper-V is not supported.
- Create a master VM.
- Install a Virtual Delivery Agent on the master VM, and select the option to optimize the desktop. This improves performance.
- Take a snapshot of the master VM to use as a backup.
- Create virtual desktops. If you are using MCS to create VMs, when creating a Site or a connection,
- Select the Microsoft virtualization host type.
- Enter the address as the fully qualified domain name of the host server.
- Enter the credentials for the administrator account you set up earlier that has permissions to create new VMs.
- In the Host Details dialog box, select the cluster or standalone host to use when creating new VMs. Important: Browse for and select a cluster or standalone host even if you are using a single Hyper-V host deployment.
MCS on SMB 3 file shares
For Machine Catalogs created with MCS on SMB 3 file shares for VM storage, make sure that credentials meet the following requirements so that calls from the Controller’s Hypervisor Communications Library (HCL) connect successfully to SMB storage:
- VMM user credentials must include full read write access to the SMB storage.
- Storage virtual disk operations during VM life cycle events are performed through the Hyper-V server using the VMM user credentials.
When you use SMB as storage, enable the Authentication Credential Security Support Provider (CredSSP) from the Controller to individual Hyper-V machines when using VMM 2012 SP1 with Hyper-V on Windows Server 2012. For more information, see CTX137465.
Using a standard PowerShell V3 remote session, the HCL uses CredSSP to open a connection to the Hyper-V machine. This feature passes Kerberos-encrypted user credentials to the Hyper-V machine, and the PowerShell commands in the session on the remote Hyper-V machine run with the credentials provided (in this case, those of the VMM user), so that communication commands to storage work correctly.
The following tasks use PowerShell scripts that originate in the HCL and are then sent to the Hyper-V machine to act on the SMB 3.0 storage.
Consolidate Master Image—A master image creates a new MCS provisioning scheme (machine catalog). It clones and flattens the master VM ready for creating new VMs from the new disk created (and removes dependency on the original master VM).
ConvertVirtualHardDisk on the root\virtualization\v2 namespace
$ims = Get-WmiObject -class $class -namespace "root\virtualization\v2"; $result = $ims.ConvertVirtualHardDisk($diskName, $vhdastext) $result
Create difference disk—Creates a difference disk from the master image generated by consolidating the master image. The difference disk is then attached to a new VM.
CreateVirtualHardDisk on the root\virtualization\v2 namespace
$ims = Get-WmiObject -class $class -namespace "root\virtualization\v2"; $result = $ims.CreateVirtualHardDisk($vhdastext); $result
Upload identity disks—The HCL cannot directly upload the identity disk to SMB storage. Therefore, the Hyper-V machine must upload and copy the identity disk to the storage. Because the Hyper-V machine cannot read the disk from the Controller, the HCL must first copy the identity disk through the Hyper-V machine as follows.
The HCL uploads the Identity to the Hyper-V machine through the administrator share.
The Hyper-V machine copies the disk to the SMB storage through a PowerShell script running in the PowerShell remote session. A folder is created on the Hyper-V machine and the permissions on that folder are locked for the VMM user only (through the remote PowerShell connection).
The HCL deletes the file from the administrator share.
When the HCL completes the identity disk upload to the Hyper-V machine, the remote PowerShell session copies the identity disks to SMB storage and then deletes it from the Hyper-V machine.
The identity disk folder is recreated if it is deleted so that it is available for reuse.
Download identity disks—As with uploads, the identity disks pass though the Hyper-V machine to the HCL. The following process creates a folder that only has VMM user permissions on the Hyper-V server if it does not exist.
- The HyperV machine copies the disk from the SMB storage to local Hyper-V storage through a PowerShell script running in the PowerShell V3 remote session.
- HCL reads the disk from the Hyper-V machine’s administrator share into memory.
- HCL deletes the file from the administrator share.
Personal vDisk creation—If the administrator creates the VM in a Personal vDisk machine catalog, you must create an empty disk (PvD).
The call to create an empty disk does not require direct access to the storage. If you have PvD disks that reside on different storage than the main or operating system disk, then the use remote PowerShell to create the PvD in a directory folder that has the same name of the VM from which it was created. For CSV or LocalStorage, do not use remote PowerShell. Creating the directory before creating an empty disk avoids VMM command failure.
From the Hyper-V machine, perform a mkdir on the storage.