Citrix Provisioning

Setting the target device as the template for this collection

March 2, 2022

Contributed by:

C B

A target device can be set as the template for new target devices that are added to a collection. A new target device inherits the properties from the template target device, which allows you to quickly add new devices to a collection.

Tip

Target devices that use personal vDisks are created and added to a collection when the XenDesktop Setup Wizard is run. If a target device template exists, it is ignored when the target device that uses a Personal vDisk is added to the collection.

To set a target device as the template device for a collection, in the Console, right-click on the target device, then select Set device as template.

Consider the following when using templates:

Disable the target device that serves as the template to permit all target devices using this template to be added to the database, but not permit the target device to boot.
Target devices receive a message requesting that they first contact the administrator before being allowed to boot.
‘T’ appears in light blue on the device serving as the template. New target devices automatically have a name generated and all other properties are taken from the default template target device. No user interaction is required.

Creating a VM with nested virtualization

Sometimes, you might want to create a nested virtualization paradigm for a VM. If your environment uses Device Guard and you want to create a template from the VM running Device Guard, PVS has no means to know if this functionality was set up for that particular VM. To resolve this issue, you can manually enable Device Guard on the Hyper-V host using a PowerShell command after the VM has been created using the XenDesktop Setup Wizard.

Note:

Citrix Provisioning only supports Device Guard using Hyper-V 2016 and newer.

To configure a VM to use Device Guard:

Create the VM using the XenDesktop Setup Wizard.
After creating the VM, run the following command for each VM on the physical Hyper-V host to enable nested virtualization:

Set-VMProcessor -VMName <Target VM's Name> -ExposeVirtualizationExtensions $true

Tip

Refer to the Microsoft site for more information about nested virtualization.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Setting the target device as the template for this collection

March 2, 2022

Contributed by:

C B

March 2, 2022

Contributed by:

C B

Setting the target device as the template for this collection

Creating a VM with nested virtualization

In this article