The following databases are supported: Microsoft SQL Server 2008 SP3 through 2014 (x86, x84, and Express editions).
Database clustering is supported.
SQL Server 2012 supports always on tracing, but does not support multi-subnet failover.
The Citrix Licensing Server download for this release is included with
the installation media. Refer to Citrix License Server documentation for
licensing details and requirements. You should always use the most recent
Citrix License server to get the latest features.
Provisioning Server requirements
- 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.
Intel or AMD x86 or x64 compatible; 2 GHz minimum; 3 GHz preferred; 3.5 GHz Dual Core/HT or similar for loads greater than 250 target devices.
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)
- 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
UDP and TCP port requirements
Provisioning Server to Provisioning Server communication
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.
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.
- 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
- 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 must be enabled
PXE 0.99j, PXE 2.1 or later
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.
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:
- The Boot Device Manager (BDM) and Boot menu are not available for UEFI environments.
- The Provisioning Services Network Boot Program (NBP) supports UEFI SecureBoot. Citrix recommends that you turn on SecureBoot when firmware supports it. The exception is Hyper-V Generation 2 VMs. Hyper-V does not contain Microsoft Windows Production CA 2011 and Microsoft Corporation UEFI CA 2011 root certificates. UEFI- certified Provisioning Services NBP is not authenticated correctly by Hyper-V, therefore you must disable Hyper-V SecureBoot.
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.
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.0 (default).
Microsoft licensing key considerations
- Windows 10, 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 and Office 2013 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
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.