- Microsoft System Center Virtual Machine Manager and virtual machine management
- XenDesktop properties for Microsoft System Center Configuration Manager
- VMware and virtual machine management
Configure your system as described in this document if you use Hyper-V with Microsoft System Center Virtual Machine Manager (SCVMM) to provide virtual machines in your environment.
Before creating virtual machines (VMs), make sure that your environment meets the requirements described in Host requirements section of System requirements for XenDesktop 7.
Upgrade from SCVMM 2012 to SCVMM 2012 SP1
When upgrading from SCVMM 2012 to SCVMM 2012 SP1 consider the following component operating system versions combinations:
Upgrade from SCVMM 2008 R2 to SCVMM 2012 SP1
If you are starting from XenDesktop 5.6 on SCVMM 2008 R2, it is important to follow this sequence so that XenDesktop can continue to operate without any downtime.
The recommend component upgrade sequence is:
Verify the following account information:
You create a master VM to provide user desktops.
If you are using Citrix Studio to create VMs, rather than selecting an existing Machine Catalog, run the Studio Deployment wizard and create virtual desktops as follows:
This feature provides performance improvements for Machine Creation Services ( MCS) when using SMB 3.0 on file servers with clustered shared volumes and Storage Area Networks (SANs). These file shares provide low cost caching and reduced IO on the SAN storage improving the performance.
Machine Creation Services (MCS) on SMB 3 file shares
For Machine Catalogs created through MCS on SMB 3 file shares for VM storage, make sure that credentials are set up as follows so that calls from a Delivery Controller's Hypervisor Communications Library (HCL) can successfully connect to SMB storage:
Storage virtual disk operations during VM life cycle events are performed through
the Hyper-V server using the VMM user credentials.
Using a standard PowerShell V3 Remote session, the HCL opens a connection to the to Hyper-V machine using the Authentication Credential Security Support Provider (CredSSP) feature. This feature passes users' credentials across to the Hyper-V Machine (Kerberos encrypted) and the PowerShell commands in this session on the remote Hyper-V machine run with the credentials provided (in this case, those of the SCVMM User), so that communication commands to storage correctly work.
The following tasks use PowerShell scripts that originate in the Delivery Controller 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).
PowerShell script operation
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 Hypervisor Communications Library (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 Delivery Controller, HCL must first copy the identity disk through the Hyper-V machine as follows.
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 SCVMM user permissions on the Hyper-V server if it does not exist.
Personal vDisk creation
If the administrator creates the VM in a Personal vDisk Machine Catalog, you must create an empty disk (Personal vDisk).
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 disk 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 SCVMM command failure.
From the Hyper-V machine, perform a mkdir on the storage.
For more information about using the XenDesktop SDK, see About the XenDesktop SDK.