Product Documentation

System requirements

Mar 08, 2017

Database requirements

The following databases are supported: Microsoft SQL Server 2008 SP3 through 2016 (x86, x64, and Express editions).

Database clustering is supported.

Hinweis

Refer to Supported Databases for XenApp and XenDesktop Components in the Knowledge Center for additional information about supported databases and clients.

Licensing requirements

The Citrix Licensing Server download for this release is included with the XenApp/XenDesktop installation media. You should always use the most recent Citrix License server to get the latest features.

Important

Provisioning Services servers must be connected to the license server to operate successfully. You must use the most recent version of the Citrix License server to get the latest features. Citrix recommends that you upgrade the License Server before upgrading PVS to avoid any licensing conflicts related to grace periods. For more information, see Licensing.

Provisioning Server requirements

Operating systems

  • Windows Server 2016
  • Windows Server 2012 and Windows Server 2012 R2; Standard, Essential, and Datacenter editions
  • Windows Server 2008 R2 and Windows Server 2008 R2 SP1; Standard, Enterprise, and Datacenter editions

Provisioning Services English on English, Japanese, German, French, Spanish, Simplified Chinese, Traditional Chinese, Korean, and Russian versions are supported. 

Processors

Intel or AMD x64 compatible; 2 GHz minimum; 3 GHz preferred; 3.5 GHz Dual Core/HT or similar for loads greater than 250 target devices.

Memory

Minimum of 2 GB RAM; 4 GB preferred; 4 GB is required for a larger number of vDisks (greater than 250).

Hard disk and storage

Disk storage management is important because a Provisioning Server can have many vDisks stored on it, and each disk can be several gigabytes in size. Your streaming performance can be improved using a RAID array, SAN, or NAS.

There must be enough space on the hard disk to store the vDisks. For example, if you have a 15 GB hard drive, you can only create a 14 GB vDisk.

Additional requirements depend on several factors such as:

  • Hard disk capacity – the requirements of the operating system and applications running on a target device. Citrix recommends adding 20% to the base size of the final installed image.
  • Private Image Mode – the number of target devices using a vDisk in Private Image mode (vDisks in Private Image mode should be backed up daily).
  • Standard Image Mode – the number of target devices using a vDisk in Standard Image mode. Best practice is to include making a copy of every vDisk created.
  • Minimum common storage sizes
    • 250 MB for the database
    • 5 GB on a clean Windows system
    • 15 GB per vDisk for Vista Class images (estimated)

Network adapter

  • Static IP
  • Minimum 100 MB Ethernet, 1 GB Ethernet preferred; Dual 1 GB Ethernet for more than 250 target devices. Two NICs often perform better than a single dual-ported NIC.

Provisioning Server software

  • The Provisioning Server install program requires Microsoft NET 4.5.2 and Windows PowerShell 3.0

Network requirements

UDP and TCP port requirements
Provisioning Server to Provisioning Server communication
  • Each Provisioning Server must be configured to use the same ports (UDP) in order to communicate with each other using the Messaging Manager. At least five ports must exist in the port range selected. The port range is configured on the Stream Services dialog when the Configuration wizard is run.
    Note: If you are configuring for high availability (HA), all Provisioning Servers selected as failover servers must reside within the same site. HA is not intended to cross between sites.
  • The first port in the default range is UDP 6890 and the last port is 6909.

Provisioning Servers to target device communication

  • Each Provisioning Server must be configured to use the same ports (UDP) in order to communicate with target devices using the StreamProcess.
  • The port range is configured using the Console’s Network tab on the Server Properties dialog.
  • The default ports include: UDP 6910, 6911, 6912, 6913, 6914, 6915, 6916, 6917, 6918, 6919, 6920, 6921, 6922, 6923, 6924, 6925, 6926, 6927, 6928, 6929 and 6930. However, the first 3 ports (6910, 6911, 6912) are reserved for Provisioning Services.

Target device to Provisioning Services communication

Target devices communicate with Provisioning Services using UDP 6901, 6902, 6905 ports. Unlike Provisioning Servers to target device port numbers, target device to Provisioning Services communication cannot be configured.

Login server communication

  • Each Provisioning Server used as a login server must be configured on the Stream Servers Boot List dialog when the Configuration wizard is run.
  • The default port for login servers to use is UDP 6910.

Console communication

The SOAP Server is used when accessing the Console. The ports (TCP) are configured on the Stream Services dialog when the Configuration wizard is run. For Powershell: MCLI-Run SetupConnection. For MCLI: MCLI Run SetupConnection.

TFTP communication

  • The TFTP port value is stored in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNTFTP\Parameters Port
  • The TFTP port defaults to UDP 69

TSB communication

  • The TSB port value is stored in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PVSTSB\Parameters Port
  • The TSB port defaults to UDP 6969

Port Fast

Port Fast must be enabled

Network card

PXE 0.99j, PXE 2.1 or later

Network addressing

DHCP

Target device requirements

In most implementations, there is a single vDisk providing a standard image for multiple target devices. To simplify vDisk and target device maintenance, create and maintain fewer vDisks and assign more target devices to each vDisk.

In order to have a single vDisk, all target devices must have certain similarities to ensure that the OS has all of the drivers it requires to run properly. The three key components that should be consistent are the motherboard, network card, or video card.

If NIC teaming is desired, the Microsoft NIC teaming driver or OEM NIC teaming software should be installed and configured before you install the target device software.

The Unified Extensible Firmware Interface (UEFI) is supported, but note that:

  • Secure boot is only supported using a Hyper-V 2016's Secure Boot VM that uses the Microsoft UEFI Certificate Authority template.

Target device operating systems

Target devices are identified by the operating system that runs on the device. The following operating systems are supported for target devices.

Note: Dual boot vDisk images are not supported.
  • Operating systems supported by Provisioning Services target devices:
    • Windows 10 (32 or 64-bit); all editions
    • Windows 8 (32 or 64-bit) and Windows 8.1 (32 or 64-bit); all editions
    • Windows 7 SP1 (32 or 64-bit); Enterprise, Professional, Ultimate.
      Note: The Ultimate edition of Windows 7 is supported only in Private Image mode.
    • Windows Server 2016
    • Windows Server 2012 and Windows Server 2012 R2; Standard, Essential, and Datacenter editions
    • Windows Server 2008 R2 and Windows Server 2008 R2 SP1; Standard, Datacenter, and Enterprise editions
  • For Provisioning Services support of Gen 2 VMs in a XenDesktop environment, the following operating systems are supported:
    • Windows 2016
    • Windows Server 2012 and Windows Server 2012 R2; Standard, Essential, and Datacenter editions
  • For Linux streaming, the following operating systems are supported:
    • RedHat Enterprise Linux 7.2
    • CentOS 7.2

Provisioning Services English on English, Japanese, German, French, Spanish, Simplified Chinese, Traditional Chinese, Korean, and Russian versions of operating systems are supported.

Target device software requirements

.NET 4.5.2 (default).  

Microsoft licensing key considerations

  • Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Server 2012, and Windows Server 2008R2 are deployed using either Key Management Server (KMS) or with Microsoft Multiple Activation Key (MAK) volume licensing keys.
  • Windows Office 2010, Office 2013 and Office 2016 are deployed using KMS licensing.
    Note: In order for MAK licensing to work, the Volume Activation Management Tool (VAMT) for that client OS must be installed on all login servers within a farm.
    Note: Both Private and Standard Image Modes support MAK and KMS.
    Volume licensing is configured within the vDisk image when the Imaging wizard is run on the Master target device. Volume licensing is configured for the vDisk file on the Microsoft Volume Licensing tab, which is available from the Console vDisk File Properties dialog.

Supported file system types

NTFS

Console requirements

  • Processor – Minimum 1 GHz, 2 GHz preferred
  • Memory – Minimum 1 GB, 2 GB preferred
  • Hard Disk – Minimum 500 MB
  • Supported Operating Systems:
    • Windows Server 2012; Standard, Essential, and Datacenter editions
    • Windows Server 2012 R2; Standard, Essential, and Datacenter editions
    • Windows Server 2008 R2 and Windows Server 2008 R2 SP1; Standard, Datacenter, and Enterprise editions
    • Windows 10
    • Windows 8.1 (64-bit); all editions
    • Windows 8 (32- or 64-bit); all editions
    • Windows 7 (32- or 64-bit)
  • Software:
    • MMC 3.0, Microsoft .NET 4.5.2, Windows PowerShell 3.0

Store requirements

The store must be able to communicate with the Provisioning Services database.

XenDesktop Setup wizard requirements

The Provisioning Services XenDesktop Setup wizard operates only with the equivalent version of the XenDesktop controller, that is, the version levels must be the same.

  • One or more configured XenDesktop hosts with identical templates must exist.
  • A Device Collection must have been created in the Provisioning Services Site.
  • The vDisk that will be assigned to each VM must be in standard image mode.
  • Permissions:
    • A XenDesktop controller must exist with permissions for the current user.
    • vCenter, SCVMM, and XenServer minimum permissions must be configured.
    • A Provisioning Services Console user account must be configured as a XenDesktop administrator and must have been added to a PVS SiteAdmin group or higher.
    • If you are using Provisioning Services with XenDesktop, the SOAP Server user account must have XenDesktop Full administrator privileges.
    • When creating new accounts in the Console, the user needs the Active Directory Create Accounts permission. To use existing accounts, Active Directory accounts have to already exist in a known OU for selection.
    • When creating a machine catalog in XenDesktop, the boot device file is created automatically (eliminating the need to boot using PXE) and an unformatted write cache disk is automatically attached and formatted on first boot.
    • When updating the Virtual Desktop Agent (VDA) on the vDisk image, you must also set the appropriate functional level for the XenDesktop catalog using the XenDesktop Console. See the XenDesktop upgrade topics for more information.
    • If you are importing an Active Directory .csv file, use the following format: <name>,<type>,<description> . The CSV file must contain the column header. For example, the csv file contents are as follows:

      Name,Type,Description,

      PVSPC01,Computer,,

      The trailing comma must be present to signify three values, even if there is no description. This is the same formatting used by Active Directory Users and Computers MMC when exporting the contents of an organizational unit.

    • If you are using Personal vDisks with XenDesktop, the SOAP Server user account must have XenDesktop full administrator privileges.
  • Template virtual machine (VM) requirements:
    • A template virtual machine must be created from a working virtual machine (connected to the network and boots successfully)
    • Boot order: Network/PXE first in list (as with physical machines)
    • Network: Static MAC addresses. If using XenServer, address cannot be 00-00-00-00-00-00
    Note: If using hard disks, the wizard automatically creates and formats the disk (NTFS) with a write cache partition large enough for the cache. No hard disks are required.
  • System Center Virtual Machine Management (SCVMM) requirements:
    • SCVMM servers require that PowerShell 2.0 is installed and configured for the number of connections. The number of required connections for an SCVMM server should be greater than or equal to the number of hosted hypervisors used by the setup wizard for virtual machine cloning. For example: to set connections to 25 from a Powershell prompt, run: winrm set winrm/config/winrs @{MaxShellsPerUser="25"}winrm set winrm/config/winrs @{MaxConcurrentUsers="25"}.
    • For Microsoft SCVMM to work with XenDesktop, the user must run the following PowerShell command; set-ExecutionPolicy unrestricted on SCVMM.
    • For Microsoft SCVMM, please verify that the MAC address for the template is not 00-00-00-00-00-00 before attempting to clone the template. If necessary, use the template properties dialog to assign a MAC address.
  • If running a vCenter server on alternate ports, the following registry modifications must be made in order to connect to it from Provisioning Services:
    • Create a new key HKLM\Software\Citrix\ProvisioningServices\PlatformEsx
    • Create a new string in the PlatformEsx key named ServerConnectionString and set it to http://{0}:PORT#/sdk
      Note: If using port 300, ServerConnectionString= http://{0}:300/sdk
  • If using multiple NICs, the XenDesktop wizard assumes that the first NIC is the Provisioning Services NIC, and therefore changes it in accordance with the virtual machine network in the Domain Controller. This is the first NIC listed in the virtual machines properties.
  • To use the Synthetic switch-over feature, both the first legacy NIC and the synthetic NIC must be on the same network. If the Provisioning Services XenDesktop Set Up Wizard is used with SCVMM, both the first legacy and the synthetic NICs' network will change according to the network resource set by XenDesktop, or by the user if SCVMM host has multiple network resources.
  • Multi-NIC support for XenDesktop private virtual machine desktops.
  • Legacy XenDesktop Virtual Desktop Agents are supported on VMs. For details, refer to VDA requirements in the XenDesktop documentation.

Streamed VM Setup wizard requirements

  • One or more hypervisor hosts must exist with a configured template.
  • A Device Collection must exist in the Provisioning Services Site.
  • A vDisk in Standard Image mode must exist, to be associated with the selected VM template.
  • Template VM requirements:
    • Boot order: Network/PXE must be first in list (as with physical machines).
    • Hard disks: If you are using local write cache, an NTFS formatted disk large enough for the cache must exist. Otherwise, no hard disks are required.
    • Network: Static MAC addresses. If you are using XenServer, the address cannot be 00-00-00-00-00-00
    • Before attempting to create a template from a VM, ensure that the VM is fully operational.
  • Permissions:
    • The Provisioning Services Console user account must have been added to a PVS SiteAdmin group or above.
    • If you are using Active Directory, when creating new accounts in the Console, the user needs the Active Directory Create Accounts permission. To use existing accounts, Active Directory accounts have to already exist in a known OU for selection.

ESD server requirements for vDisk Update Management

  • WSUS Server – 3.0 SP2
  • Microsoft System Center Configuration Management (SCCM):
    • SSCM 2016
    • SCCM 2012 R2
    • SCCM 2012 SP1
    • SCCM 2012

Hypervisor requirements

For a list of supported hypervisors, refer to XenDesktop and Provisioning Services Hypervisor support.

Hypervisor considerations

XenServer 5.6 and newer
  • The template’s MAC address cannot be 00-00-00-00-00-00-00.
System Center Virtual Machine Manager (SCVMM) VMM 2012 and newer
  • VMM 2012, 2012 SP1, and 2012 R2 are significantly different from each other.
  • When creating a machine template for VMM 2012 only, ensure that it has a similar hard disk drive structure and that it can boot from a vDisk in Private Image mode. Examples:
    • To PXE boot a VM with write cache, create a VM with one hard disk drive.
    • To use Boot Device Manager (BDM) to boot a VM with write cache, create a VM with two hard disk drives.
    • To use BDM to boot a VM that uses a personal vDisk and write cache, create a VM with three hard disk drives.
  • To do the Synthetic NIC Switch Over (boot using legacy NIC and then stream using synthetic NIC), both the legacy and the synthetic NICs must be in the same vlan in the template VMs. The Provisioning Services XenDesktop Set Up Wizard changes the vlan of both NICs to the vlan selected during the XenDesktop Set Up Wizard run. This uses two IP addresses
  • When running the imaging wizard, make sure you select the legacy NIC’s MAC address.
  • Provisioning Services does not support multiple legacy NICs in the VMM’s VM. This is because VMM uses the last legacy NIC and XenDesktop Set Up Wizard always uses the first NIC, regardless of whether it is legacy or synthetic.
  • When creating a VMM template, make sure you select None – customization not required as the Guest OS profile in Configure Operating System menu.
  • When using the XenDesktop Set Up Wizard, you may find that the targets are created but are not bootable with the error Device not found in PVS dB. This usual reason is that the template has the legacy and synthetic NICs in reverse order: synthetic is NIC 1 and legacy is NIC 2. To fix this, delete the NICs in the template. Make a legacy NIC 1 and synthetic NIC 2.
VMware vSphere ESX 4.1 and newer
  • Supported Provisioning Services PXE NIC
    • ESX 4.x – E1000
    • ESX 5.0 and newer – VMXNET3
  • Template VM and the master VM
    • Both must have the same guest operating system, configuration, and virtual machine version. Mismatches cause the process to stop unexpectedly.
  • Provisioning Services and ESX virtual machine version
    • vCenter 5.5 defaults to virtual machine version 8, which is for ESX 5.0.
    • The virtual machine version must be changed before OS installation.
    • The template and the master VM must have the same virtual machine version.
  • Windows 7 and Windows 2008 R2 with VMXNET3 NICs
    • Windows 7 and Windows 2008 R2 without service packs — Install Microsoft iSCSI hotfix http://support.microsoft.com/kb/2344941 and restart the VM before installing Provisioning Services target device software.
    • Windows 7 and Windows 2008 R2 with Service Pack 1 – Install Microsoft iSCSI hotfix http://support.microsoft.com/kb/2550978 and restart the VM before installing Provisioning Services target device software.
  • For ESX 5.0 only, the Interrupt Safe Mode must be enabled on the Provisioning Services bootstrap. Otherwise, the VM displays a partial MAC address during reboot.
  • With ESX 5.5, a VM created using the Web client defaults to virtual hardware version 10 (ESX 5.5) and a VM created using the vSphere client defaults to version 8 (ESX 5.0).
  • When creating a new ESXi 5.5 template using the vSphere web client, you can only create hardware version 10 templates. Be sure to modify the template's CD/DVD drive's virtual mode from SATA to IDE. Remove the SATA controller if you are planning to use the VMXNet3 driver. This will ensure that the template is compatible with the XenDesktop Setup izard, which requires the drives that are created for the target to be attached using the SCSI driver.
  • When using multiple NICs in ESX VM, be aware that the order of the NICs in the VM’s properties, BIOS, and OS may differ. Keep this in mind when making your choices for the streaming NIC. This should be the first NIC in the VM’s properties. You can choose the PXE NIC in the BIOS.
  • Host record – Regardless of the ESX version, the host’s address for the XenDesktop host will be that of the vCenter system. Do not enter the address used by the web client.

Linux streaming requirements

Important

The Linux VDA streaming feature is provided as a technical preview at this release of Provisioning Services. Citrix recommends that use of this feature be limited to non-production environments.

The following distributions are supported at this release:

  • RedHat Enterprise Linux Server 7.2
  • CentOS 7.2

Hinweis

For more information related to Linux streaming, refer to the installation article.

The following Hypervisors are supported:

  • XenServer
  • ESX

The following image management options are included with this feature:

  • Versioning

Hinweis

Reverse imaging is not necessary with Linux.

Caching:

  • All cache modes supported. Refer to the Managing vDisks article for more information on supported cache types.

Tipp

Once the write cache disk has been formatted, the Linux client will not shutdown. Instead, it automatically begins using the cache disk.

Hinweis

Cache on device hard disk and Cache in device RAM with overflow on hard disk both use the Linux file system caching mode.

Important

Linux streaming functionality works with the latest version of Provisioning Services in conjunction with corresponding versions of XenApp/XenDesktop.