Create a Microsoft System Center Virtual Machine Manager catalog
Create machine catalogsdescribes the wizards that create a machine catalog. The following information covers details specific to Microsoft System Center Virtual Machine Manager (VMM) virtualization environments.
Note:
Before creating a VMM catalog, you need to finish creating a connection to VMM. SeeConnection to Microsoft System Center Virtual Machine Manager.
Create a master VM
- Install a VDA 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.
MCS on SMB 3 file shares
For machine catalogs created with MCS on SMB 3 file shares for VM storage, credentials must meet the following requirements to ensure that calls from the Citrix 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 lifecycle events are performed through the Hyper-V server using the VMM user credentials.
When using VMM 2012 SP1 with Hyper-V on Windows Server 2012: When using SMB as storage, enable the Authentication Credential Security Support Provider (CredSSP) from the Cloud Connector to individual Hyper-V machines. For more information, seeCTX 137465.
使用标准PowerShell V3远程会话HCL in the Cloud Connector 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. The scripts are then sent to the Hyper-V machine to act on the SMB 3.0 storage.
Consolidate Master Image:An 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
Example:
$ims = Get-WmiObject -class $class -namespace "root\\virtualization\\v2"; $result = $ims.ConvertVirtualHardDisk($diskName, $vhdastext) $result Create difference disk: Creates a difference disk from the image generated by consolidating the image. The difference disk is then attached to a new VM.
CreateVirtualHardDisk on the root\virtualization\v2 namespace
Example:
$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 Cloud Connector, 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 deleted to make it available for reuse.
Download identity disks:As with uploads, the identity disks pass through the Hyper-V machine to the HCL. The following process creates a folder that has only 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 using 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.
Where to go next
- If this is the first catalog created, you are guided tocreate a delivery group.
- To review the entire configuration process, seePlan and build a deployment.
- To manage catalogs, seeManage machine catalogsandManage a Microsoft System Center Virtual Machine Manager catalog.