This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Create a Microsoft System Center Virtual Machine Manager catalog
Create machine catalogs describes the wizards that create a machine catalog. The following information covers details specific to Microsoft System Center Virtual Machine Manager (VMM) virtualization environments.
Before creating a VMM catalog, you need to finish creating a connection to VMM. See Connection to Microsoft System Center Virtual Machine Manager.
- Install a VDA on the master VM, and select the option to optimize the desktop to improve performance.
- Take a snapshot of the master VM to use as a backup.
- Create virtual desktops.
For machine catalogs created with MCS on SMB 3 file shares for VM storage, ensure that credentials meet the following requirements. These requirements ensure 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 storage, enable the Authentication Credential Security Support Provider (CredSSP) from the Controller to individual Hyper-V machines. Use this process for VMM 2012 SP1 with Hyper-V on Windows Server 2012. For more information, see CTX137465.
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. The PowerShell commands in the session on the remote Hyper-V machine run with the credentials provided. In this case, the credentials 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 an MCS provisioning scheme (machine catalog). It clones and flattens the master VM ready for creating 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)
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);
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 finishes uploading the identity disk to the Hyper-V machine, the remote PowerShell session copies the identity disks to SMB storage. It 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 Hyper-V machine copies the disk from the SMB storage to the local Hyper-V storage through a PowerShell script. This script runs 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.
You can use a machine profile to create and update an MCS machine catalog in System Center Virtual Machine Manager (SCVMM) environments. You can also enable nested virtualization and vTPM.
- Master image can only be a snapshot and not a VM.
- You can only use VM as the machine profile source.
- You can configure VTPM from the Hyper-V console and not from the SCVMM console.
- If the master image has vTPM enabled, then you must enable the vTPM on the machine profile source.
- vTPM is only supported on Generation 2 machines.
The following parameters overwrite the values captured in a machine profile if provided separately:
- Disk storage
- You can update an existing catalog using the
Create a VM to be a machine profile source. For more information, see Provision virtual machines in the VMM fabric. You cannot change the Generation once selected.
- If you want to enable nested virtualization, select the Enable Nested Virtualization checkbox on the Select Source page.
- If you want to enable vTPM, then after you create the VM, log in to the Hyper-V host and find your VM under the Hyper-V Manager. Right-click the VM, then go to Settings. Under Security, select the Enable Trusted Platform Module checkbox.
- Open a PowerShell window.
asnp citrix*to load the Citrix-specific PowerShell modules.
- Create a Broker catalog. This catalog is populated with machines which are about to be created.
- Create an identity pool. This becomes a container for AD accounts created for the machines that are to be created.
Create a provisioning scheme with the machine profile. For example:
New-ProvScheme -HostingUnitName "<hostingunit name>" -IdentityPoolName "ID1" -MasterImageVM "XDHyp:\HostingUnits\HU1\<path to the checkpoint/snapshot>" -ProvisioningSchemeName "<catalogname>" -MachineProfile "XDHyp:\<path to the machine profile VM>" <!--NeedCopy-->
- Updates the Broker catalog with the unique Id of the provisioning scheme.
- Create and add VMs to the catalog.
You can update an existing catalog using the Set-ProvScheme command. For example:
Set-ProvScheme -ProvisioningSchemeName "<catalogname>" -MachineProfile "XDHyp:\<path to the machine profile VM>"
- If this is the first catalog created, Web Studio guides you to create a delivery group
- To review the entire configuration process, see Install and configure
- To manage catalogs, see Manage machine catalogs and Manage a Microsoft System Center Virtual Machine Manager catalog
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.