To deliver desktops and applications for machines in Server OS or Desktop OS machine catalogs, you must prepare the master image that creates the user desktops and applications.
The master image is a template that you use to deploy your environment. In addition to desktops and applications, creating a master image includes installing and configuring the operating system and any software you want to include on your image.
Microsoft KMS activation with Machine Creation Services
If you are using a XenDesktop 7 VDA with either XenServer 6.1 or XenServer 6.2, or vSphere, or SCVMM, you do not need to manually re-arm Microsoft Window or Microsoft Office when using Machine Creation Services (MCS).
If you are a XenDesktop 5.x VDA with XenServer 6.0.2, follow the procedure documented in CTX128580 when using Machine Creation Services (MCS).
Windows Desktop Experience with Server OS machines
You must add the Windows Desktop Experience Feature Pack to a master image for Server OS machines running on:
Without this Feature Pack, Windows Media Player does not properly play video in a session. Follow the procedure documented in CTX133429.
GPU capable master images
For GPU capable machines and machine catalogs, you must use a GPU-dedicated master image. GPU virtual machines require specific video card drivers, and the VM configuration must be setup in a specific way for the VM to operate with software that uses GPU for operations. You create the master image using the XenServer's XenCenter console. See the XenServer documentation for specific details.
The following procedure describes the high-level steps to create a GPU master image that Studio detects when you select a GPU capable resources as described in Connections and resources.
You are prompted to use RDP.
To prepare a master image
If they are sufficient to allow the master image to run, the number of vCPUs and the amount of memory you assign to the master image are not critical at this stage because you can change these settings when you create the machine catalog.
Make sure that the hard disk for the master image is attached at device location 0. Most standard master image templates configure this location by default, but some custom templates may not do so.
For machines provisioned through Provisioning Services (PVS), you can either use a master image or a physical computer as your master target device. For more information about preparing a master target device, see Installing and Configuring Provisioning Services.
Citrix recommends that you create a snapshot of your master image and name the snapshot so that you can identify the master image in the future. If you specify a master image rather than a snapshot when creating a Server OS or Desktop OS machine catalog, Studio creates a snapshot for you but you cannot name it.
For machine catalogs created through Provisioning Services, create a VHD file for the vDisk from your master target device before you join the master target device to a domain. For more information about imaging a vDisk, see Installing and Configuring Provisioning Services.