NavigationThis article applies to all 7.x versions of Citrix Provisioning, including 2206, LTSR 2203, LTSR 1912 CU5, LTSR 7.15.45 (aka 7.15 LTSR CU9), and LTSR 7.6.9 (aka 7.6 LTSR CU8). Show
💡 = Recently Updated Change Log
Planning and VersionsCTX220651 Best Practices for deploying PVS in multi-geo environments: ensure that Provisioning farms do not span data centers with a network latency that can affect communications between the Provisioning Servers and the SQL database SQL 2019 is supported with Citrix Provisioning 2003 and newer. Citrix Provisioning Firewall Rules The most recent Current Release version of Citrix Provisioning is 2206. For LTSR CVAD, deploy the Citrix Provisioning version that matches your CVAD version: Citrix License Server VersionUpgrade the Citrix Licensing server to the latest version. UpgradeWindows Server 2022 is supported with Citrix Provisioning 2206 and newer. SCVMM 2022 is supported with Citrix Provisioning 2206 and newer. If you are upgrading from an older version of Citrix Provisioning, do the following:
vDisk StorageDo the following on both Provisioning Servers. The vDisks will be stored locally on both servers. You must synchronize the files on the two servers: either manually (e.g. Robocopy), or automatically (e.g. DFS Replication). Create D: Drive
vDisk FoldersOn the new D: partition, create one folder per Delivery Group. For example, create one called Win10Common, and create another folder called Win10SAP. Each vDisk is composed of several files, so its best to place each vDisk
in a separate folder. Each Delivery Group is usually a different vDisk. Robocopy ScriptHere is a sample robocopy statement to copy vDisk files from one Provisioning server to another. It excludes .lok files and excludes the WriteCache folders. REM Robocopy from PVS01 to PVS02 REM Deletes files from other server if not present on local server Robocopy D:\vDisks \\pvs02\d$\vDisks *.vhd *.vhdx *.avhd *.avhdx *.pvp /b /mir /xf *.lok /xd WriteCache /xoCitrix Blog Post vDisk Replicator Utility has a GUI utility script that can replicate vDisks between Provisioning Sites and between Provisioning Farms. Service AccountProvisioning Services should run as a domain account that is in the local administrators group on both Provisioning servers. This is required for KMS Licensing. Provisioning Console Install/UpgradeThe installation and administration of Citrix Provisioning 2206 and older (including LTSR versions 2203, 1912 CU5, 7.15.45 and 7.6.9) are essentially identical. Windows Server 2022 is supported with Citrix Provisioning 2206 and newer. SCVMM 2022 is supported with Citrix Provisioning 2206 and newer. If you want to automate the installation and configuration of Citrix Provisioning, see Dennis Span Citrix Provisioning Server unattended installation. To manually install Provisioning Console, or in-place upgrade the Provisioning Console:
After upgrading the Console, re-register the PowerShell snap-in. This is required for the Citrix App Layering Agent. "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe" "c:\program files\citrix\provisioning services console\Citrix.PVS.snapin.dll"Provisioning Server – Install/UpgradeThe installation and administration of Citrix Provisioning 2206, 1912 LTSR CU5, 7.15.45, 7.6.9 and other 7.x versions are essentially identical. Windows Server 2022 is supported with Citrix Provisioning 2206 and newer. SCVMM 2022 is supported with Citrix Provisioning 2206 and newer. You can in-place upgrade Provisioning Server. The Provisioning Servers must be upgraded before the vDisks’ Target Device Software are upgraded. While upgrading one Provisioning Server, all Target Devices are moved to the other Provisioning Server assuming that vDisk High Availability is properly configured. To install/upgrade Provisioning server:
Database ScriptBy default, the Citrix Provisioning Configuration Wizard will try to create the database using the credentials of the person that is running the Wizard. This isn’t always feasible. An alternative is to create a script that a DBA can run on the SQL server.
Configuration Wizard – New Farm
From Running the Configuration Wizard silently at Citrix Docs: Now that you have a configured server, you can run "C:\Program Files\Citrix\Provisioning Services\ConfigWizard.exe" /s to produce an .ans file at "C:\ProgramData\Citrix\Provisioning Services\ConfigWizard.ans". This .ans file can be modified and copied to additional Provisioning servers. "C:\Program Files\Citrix\Provisioning Services\ConfigWizard.exe" /a reads the .ans file and applies the configuration silently. Configuration Wizard – Join Farm
Troubleshooting – Networking Services Don’t Work After RebootIf your PXE service or TFTP service does not work after a reboot of the Provisioning server, do the following:
Disable FirewallDisable the Windows Firewall to allow communication to all Citrix Provisioning Server ports. Or, see Citrix Provisioning Firewall Rules and manually open all required ports. If you change the ports in the Citrix Provisioning Console, then you’ll need to adjust the Windows Firewall rules accordingly.
The versioning process in Citrix Provisioning will present a boot menu when booting any version except Production.
Private Mode vDisk – No Servers Available for vDiskCitrix CTX200233 – Error: “No servers available for disk”: When you set a vDisk to Private Image mode (or new Maintenance version), if the Target Device is not connected to the server that contains the vDisk then you might see a message saying “No Servers Available for vDisk”.
Multi-Homed Provisioning ServerFrom slide 20 of http://www.slideshare.net/davidmcg/implementing-and-troubleshooting-pvs:, Multi-homed Provisioning server is not recommended but if you insist, and if running Provisioning 6.1 or older, configure the following. Provisioning 7.7 configuration wizard should have asked you for the management NIC.
Citrix 133877 Timeout Error 4002 in Provisioning Server Console after Clicking “Show Connected Devices“: when there are multiple streaming NICs assigned to the Provisioning Server, when Show Connected Devices was clicked in the Provisioning console, the following symptoms might be experienced: Server timeout error 4002, unusual delay of 3 to 4 minutes to list the connected devices, or Provisioning console stops responding. Complete the following to resolve the issue:
Antivirus ExclusionsCitrix’s Recommended Antivirus ExclusionsEndpoint Security, Antivirus, and Antimalware Best Practices at Citrix Docs TechZone contains a list of recommended exclusions for Citrix Provisioning. Citrix Blog Post Citrix Recommended Antivirus Exclusions: the goal here is to provide you with a consolidated list of recommended antivirus exclusions for your Citrix virtualization environment focused on the key processes, folders, and files that we have seen cause issues in the field:
See the Blog Post for exclusions for each Citrix component/product including: StoreFront, VDA, Controller, and Provisioning. The Blog Post also has links to additional KB articles on antivirus. Microsoft’s virus scanning recommendations(e.g. exclude group policy files) – http://support.microsoft.com/kb/822158. TFTP High AvailabilityBIOS machines have multiple methods of booting into PVS:
EFI/UEFI machines have two methods of booting into PVS:
If PXE booting on same subnet as Provisioning Servers, then make sure the PXE service is running on the Citrix Provisioning Servers. When your target device boots, it will broadcast a PXE Request message to the entire subnet. One of the Provisioning Servers PXE services will reply with the IP address of the TFTP service on the local Provisioning Server.
If your Target Devices are not on the same VLAN/subnet as the Provisioning Servers, then for EFI/UEFI devices, you will need to configure DHCP Scope Options 66, 67, and 11. BIOS machines can instead use Boot ISO or Boot Partition, but these options are not available for EFI/UEFI.
DHCP FailoverThe DHCP infrastructure must be highly available. And session hosts should be configured with DHCP Reservations. With multiple DHCP servers, any reservation should be created on all DHCP servers hosting the same DHCP scope. The easiest way to accomplish this is with the DHCP Failover feature in Windows Server 2012 and newer.
Health CheckCTP Sacha Thomet’s PowerShell script to view the health/status of the Provisioning environment. Emails an HTML Report. For Provisioning 7.7 and newer, see
https://blog.sachathomet.ch/2015/12/29/happy-new-script-pvs-7-7-healthcheck/. Related Pages
How do you fix the security database on the server does not have a computer account?Security database on the server does not have a computer account for this workstation trust relationship. First unjoin the computer from the domain and make sure you set a local administrator password on machine or set an user account password which is a member of local administrators group.. Reboot the machine.. How do you fix the security database on the server does not have a computer account for this workstation trust?Win 10 The Security Database on the Server does not have a Computer Account for this Workstation Trust Relationship after update 20H2. Run an nslookup on each of the problem machines. ... . Reset the computer accounts for the problem machines in ADUC.. Verified replication is taking place on both DCs.. |