A list containing the majority of Citrix Provisioning (formerly Provisioning Services) support articles collated to make this page a one stop place for you to search for and find information regarding any issues you have with the product and its related dependencies.
The page is updated daily with new support articles and information. Articles will change from time and if information here is outdated or incorrect please let me know using the comments. Links may also expire or change so if you find broken links, please again let me know. For each issue, known product versions affected are recorded however that does not mean product versions that aren’t listed are not affected.
There is a search box that you can use if looking for a specific fault. For example if you have an error code or error message, use that to perform a search. You can also use your browsers search feature which will perform a search against the whole page based on the words you enter.
Provisioning Services / Citrix Provisioning:
| wdt_ID | Brief Description of Issue | Brief Description of Fix | Applicable Product Versions Affected (if known) | Link to supplemental Support Article(s) |
|---|---|---|---|---|
| 1 | Target Devices become stuck at "virtual disk found" or "Starting Windows". | This may be caused by software loading drivers into memory during NT-loading. As a workaround, a script has been included in the CTX article which checks for machines that have likely stuck and restarts them. | https://support.citrix.com/article/CTX224259 | |
| 2 | On VMware image conversion fails and the machine becomes stuck at the Windows splash screen. | This can be caused by the master Target Device having both a SATA and SCSI controller attached to it. The SATA controller is normally used for the CD/DVD drive in hardware versions 10 and 11. Change the SATA controller to an IDE controller or remove the CD/DVD component if not needed. | Provisioning Services 7.12. | https://support.citrix.com/article/CTX226954 |
| 3 | PVS servers are showing as offline within the PVS console and the Event Log is showing Event ID 11 "Undefined Database Error". | This is due to the SQL server being configured for TLS 1.2 which SQL native client version 11.0.2100.60 does not support. Install the latest version of the SQL native client on all PVS servers and then restart each server. | Provisioning Services 7.11 to 7.12. | https://support.citrix.com/article/CTX226526 |
| 4 | Linux VDA Target Devices fall out of domain after automatic password change duration. | Within the Linux vDisk properties, select "Enable Active Directory machne account password management". | Provisioning Services 7.13 to 7.14. | https://support.citrix.com/article/CTX226607 |
| 5 | When using the XenDesktop Setup Wizard with System Center Virtual Machine Manager as your Hypervisor broker, you receive error "Error - Has no available templates defined that are fully accessible by all hosts". | From the machine that you are converting in to a VM Template (the master template machine), edit the properties and under "Hardware Configuration" make sure there is a blank formatted cache disk attached. Set the "Guest OS profile" to "None" and make sure your storage names have no special characters. | Citrix Provisioning Services 7.12. | https://support.citrix.com/article/CTX221203 |
| 6 | After upgrading to Provisioning Services 7.8 your Target Devices no longer boot and stick on the Windows boot screen. | Try setting the Telemetry Service to Delayed Startup or Disabled. Otherwise make sure Group Policy is not set to delete profiles on the PVS Servers after a number of days. | Citrix Provisioning Services 7.8. | https://support.citrix.com/article/CTX215724 |
| 7 | After running a batch of updates, the Write Cache is not filling up quickly. | This could be due to Microsoft Updates not having properly installed before the image was promoted to production. Revert the image back and make sure update installs are complete, also run a defragmentation against the vDisk. | https://support.citrix.com/article/CTX224523 | |
| 8 | Target Devices perform slowly when a copy and paste vDisk operation in on-going and the vDisk store resides on CIFS storage. | It is a better practice to use DFS-R for vDisk replication on SMB3 storage. | https://support.citrix.com/article/CTX226170 | |
| 9 | Target Device stuck at "Login to Provisioning Services disk services". | If the vDisk is load balanced then change the settings to make it only available from one of the PVS Servers. Next reboot the VDA and test to see if it moves past the sticking point. Keep doing this for each PVS server to see which one is causing the issue. Once you have found the culprit, restart that server. | ||
| 10 | The vDisk auto-update schedule does not take effect or even reconfigure after rebooting the environment. | Reconfigure auto-update from the PVS Server or else manually start the auto-update virtual machine. | https://support.citrix.com/article/CTX205019 | |
| 11 | Target Devices fail to boot and become stuck at the "Starting Windows" screen. | This is due to ESXi VM Hardware versions 10 and 11 including by default a SATA controller for the CD/DVD Media device. Edit the Target Device hardware properties and change the CD/DVD Media device from a SATA controller to IDE. | https://support.citrix.com/article/CTX221534 | |
| 12 | When adding a store via the PVS Console the console hangs and then throws error "An error occured communicating with the Server". | Disable the Auditing feature via Farm -> Options -> Auditing. This feature is off by default, so must have been enabled manually. | Citrix Provisioning Services 7.14. | https://support.citrix.com/article/CTX226300 |
| 13 | From a remote server you cannot promote a vDisk version and get error "DeviceIoControl error: A device attached to the system is not functioning". | Promoting a vDisk remotely is not supported, so you must manage the vDisk from the PVS Server that is set to provide it. | https://support.citrix.com/article/CTX225580 | |
| 14 | When you promote a vDisk you receive error "XenDesktop Site is not reachable, check that the Citrix PVS Soap Server service user has XenDesktop permissions and network connectivity". | Change the login account for the PVS Stream and SOAP services on the PVS server to a domain service account rather than the "Network Service" account. Also add the account as a XenDesktop Full Administrator. | https://support.citrix.com/article/CTX214692 | |
| 15 | Target Device stuck at "Starting Windows". | Change the NIC from E1000 which is no longer supported on ESX 5.x+ to VMXNET3. | https://support.citrix.com/article/CTX224825 | |
| 16 | When running through the XenDesktop Setup Wizard you receive error "Cannot connect to the Hypervisor, object reference not set as an Instance". | Remove commands from any storage name associated with the Hypervisors you use in your Hosting Connection. | https://support.citrix.com/article/CTX223609 | |
| 17 | When running through the XenDesktop Setup Wizard you receive error "Cannot connect to the Hypervisor at #vCenterURL# object referece not set to an instance of an object". | This can be caused by the Datacentre name in vCenter having a comma which needs to be removed. | Citrix Provisioning Services 7.6. | https://support.citrix.com/article/CTX223662 |
| 18 | vDisk write cache is set to "Cache in device RAM with overflow to hard disk" however it is falling back to "Cache on server" after booting. | 1. The Write Cache disk needs to be "Volume 0". Confirm this is true using diskpart -> list volume. The PVS wizards normally get the volume numbers in the right order so use these wizards to deploy Target Device VMs. 2. This can also happen to VMs provisioned by the XenDesktop Setup Wizard as first boot is required to initialise the write cache disk and subsequent boots will use the correct write cache mode as normal. | ||
| 19 | You might notice that the Target Device time is not consistent with the system time of the PVS server after Daylight Saving Time (DST) has passed. This can cause a variety of issues such as Kerberos authentication and GPO processing. | You may have to place the vDisk in maintenance mode, run "w32tm /resync /nowait" and then promote to production. | https://support.citrix.com/article/CTX200058 | |
| 20 | When exporting a vDisk you receive IPC error "No response receive to successful sent. Error number 0xA0070002". The PVS SoapServer log contains error "The Disk Version specified is not valid". | Navigate to the affected vDisk versions and remove comments from the description. | Citrix Provisioning Services 7.6. | https://support.citrix.com/article/CTX140009 |
| 21 | When using Boot Device Manager, the Target Device(s) fall back to server side cache after booting. The same is not experienced when using PXE to boot the Target Device(s). | This can be caused by the XenDesktop Setup Wizards chosen template machine hardware and master image Virtual Machine hardware being different. Make sure they are the same before running through vDisk imaging. | https://support.citrix.com/article/CTX220534 | |
| 22 | When using the XenDesktop Setup Wizard, you reach the VM Templates stage but do not see any VM Templates. | Make sure you have a VM Template added to one of the storage locations defined withn Citrix Studio under "Hosting". You'll not have a VM Template to pick from until one exists within the storage location. | ||
| 23 | Whilst uninstalling the PVS Target Device software you receive error "TargetDir entry was not found in registry". | Create the following REG_SZ string on the machine: HKLM\SOFTWARE\Citrix\ProvisioningServices\TargetDir = REG_SZ and value = Path to Target Device software installation directory. | Citrix Provisioning Services 7.0, 7.1 and 7.6. | https://support.citrix.com/article/CTX215931 |
| 24 | You receive a BSOD "BNIStack failed, network stack could not be initialized. Error code 0x00007E". when capturing a new vDisk using the imaging wizard. This occurs after the first reboot when you switch the Virtual Machine to boot from the network. | Check the NIC settings for any extra settings outside of the norm. In this case SCCM client software had installed the Wake On LAN feature which was interfering with BNIStack. Microsoft does not support the Wake on LAN feature running on Virtual Machines. | Citrix Provisioning Services 7.6. | https://support.citrix.com/article/CTX216891 |
| 25 | When adding new PVS provisioned machines to a Machine Catalog you receive error "The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter..Invalid enum value 'RegistrationStateMismatch'..". | This can happen if you move machines from one Device Collection to another but do not perform the same operation within Citrix Studio. This results in a mismatch between the Device Collection and Machine Catalog. You need to move the machines back to their original Device Collection. | Citrix Provisioning Services 7.6. | https://support.citrix.com/article/CTX209209 |
| 26 | Target Device blue screens with error "0x000000BC" which means duplicate network address. | This can be caused by a duplicate IP on the network or by ProxyArp sending GARP responses to Target Devices. After verifying there is no IP conflict, boot the vDisk into private mode or create a maintenance version, create a new DWORD with name "ArpRetryCout" and value of 0. | https://support.citrix.com/article/CTX218232 | |
| 27 | You cannot shutdown or restart Target Machines from the PVS Console. | Upgrade to Provisioning Services 7.13. | Citrix Provisioning Services 7.12. | |
| 28 | You experience slow connections to the PVS farm and may receive server communication timeouts. | Upgrade to Provisioning Services 7.13 or if that does not resolve, upgrade to 7.17 | Citrix Provisioning Services 7.12. | |
| 29 | You notice sluggish performance within the PVS Console. | This can be caused by ongoing vDisk replication or other operations that cause high CPU utilisation. It can also be caused by multiple people using the same PVS console from the same machine. | ||
| 30 | When setting "Cache in Device RAM" to 4096 or 4097MB Hyper-V Generation 2 VMs will BSOD. | Upgrade to Provisioning Services 7.13. | ||
| 31 | When using the Streamed VM Setup Wizard to deploy VMs to XenServer, if you specify 1vCPU the VM is created with 1vCPU and a topology of 2 cores per socket which prevents the VM from booting. | Specify 2vCPU during the wizard or manually change the deployed VMs to 1 core per socket. | Citrix Provisioning Services 7.15, Provisioning Services 7.18, Citrix Provisioning 7 1808, Citrix Provisioning 7 1811. | |
| 32 | Provisioning Services fails to delete PVP file due to the file being open by Steamprocess.exe. | Restart the Citrix PVS Stream Service. | https://support.citrix.com/article/CTX227243 | |
| 33 | After a XenDesktop and PVS upgrade, the XenDesktop Setup Wizard in PVS does not list existing catalogs that were created before the upgrade. | Upgrade existing Machine Catalogs to the latest functional level or else run the PVS XenDesktop Setup Wizard choosing a lower functional level when asked. | Citrix XenApp and XenDesktop 7.6/7.8. | https://support.citrix.com/article/CTX223899 |
| 34 | After upgrading PVS you receive error "The wrong database version is being used. Found version: 40. Expected version number: 60". | Take a back up of the PVS database and perform a SQL database failover and run the Configuration Wizard again. If you have a single database server then re-run the Configuration Wizard. | https://support.citrix.com/article/CTX217967 | |
| 35 | When using a Private Mode or Maintenance version vDisk, you receive a high amount of retries. | Upgrade to Provisioning Services 7.7. | Citrix Provisioning Services 7.6. | https://support.citrix.com/article/CTX200952 |
| 36 | When running through the XenDesktop Setup Wizard to create devices that use BDM to boot, you receive error "vsan cannot complete file creation operation". | Citrix are aware of this limitation with PVS and VMware vSAN storage and are currently investigating the issue. In the meantime, use an alternative boot method to BDM. | Citrix Provisioning Services, VMware vSAN and Boot Device Manager. | https://support.citrix.com/article/CTX228215 |
| 37 | "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CVhdMP.sys" message when booting images created by App Layering via Citrix Provisioning Services. | Check that there are no ghost network adapters in the image. Check the NIC slot number if using VMware ESX. Make sure the Target Devices hardware is not too different from the Packaging Machine. Check the publishing Platform Layer Hypervisor version is set correctly for the Hypervisor you are using. Make sure E1000 NICs are not being used. | https://support.citrix.com/article/CTX222191 | |
| 38 | After installing PVS on a Ciscos UCS Server, a reboot fails potentially presenting a blue screen with error code "0x7B INACCESSIBLE_BOOT_DEVICE". | Before installing PVS: Uninstall EMC PowerPath, install PVS and then reinstall EMC PowerPath. | https://support.citrix.com/article/CTX229180 | |
| 39 | When booting machines you receive BSOD "CtxMcsWbc.sys". | Mount the vDisk to a management computer, open the HKLM Registry hive and add value "PvsVmBoot" to the "BootExecute" Multi-String Value. | https://support.citrix.com/article/CTX223789 | |
| 40 | Target Devices fail to PXE boot with error "Could not start download: operation not supported" when using an Infoblox Appliance to hand out DHCP information. | Follow the link included in the CTX article from Infobox, which explains the steps needed to configure PXE booting. | Infoblox. | https://support.citrix.com/article/CTX229698 |
| 41 | If you have multiple domains, creation of a new PVS farm using the PVS Configuration Wizard hangs. | A domain blacklist file needs to be created to prevent long delays that may occur when PVS tried to access unreachable domains. The CTX article shows steps on how to create a blacklist JSON file. | Citrix Provisioning Services 7.15. | https://support.citrix.com/article/CTX229670 |
| 42 | In a large Active Directory environment that has multiple domains, the PVS console may timeout and throw error "Server communication timeout". | This happens as the PVS console tries to enumerate all groups the user connecting to the PVS console is a member of by quering both child and parent domains. If the user is part of many different groups and/or certain domains are unreachable, timeouts can occur. Contact Citrix for a private fix. | https://support.citrix.com/article/CTX230426 | |
| 43 | When deleting vDisk files you receive error "The action cannot be completed because the file is open in MgmtDaemon.exe". | Restart the "Citrix PVS Stream Service" on the Provisioning Servers. You could also kill the "MgmtDaemon.exe" process itself. using "taskkill". | https://support.citrix.com/article/CTX231203 | |
| 44 | When you right-click a vDisk, select "Copy vDisk Properties" and then try to paste those properties to another vDisk, it fails to complete. | Contact Citrix to obtain private fix "LC8767" or upgrade to PVS 7.17. | Citrix Provisioning Services 7.15. | https://support.citrix.com/article/CTX231487 |
| 45 | The "vdiskdif.vhdx" file increases rapidly when copying a file to the C:\ drive. | Uninstall AppSense from the affected vDisk. | https://support.citrix.com/article/CTX231641 | |
| 46 | When running through the PVS Configuration Wizard you receive error "Errors have occurred during the configuration process" and the server is not joined to the farm. | If using SQL Mirroring, fix the database Mirroring configuration or else if not using Mirroring, do not select it when running through the PVS Configuration Wizard. | https://support.citrix.com/article/CTX231918 | |
| 47 | Target Devices fail to boot with error "PXE-E32: TFTP open timeout". | In this case the PVS server has multiple NICs and the TFTP configuration file was pointed to the wrong NIC. Use "tftpcpl.cpl" to reconfigure the TFTP service with the correct PVS NIC. | Citrix Provisioning Services 7.15. | https://support.citrix.com/article/CTX232228 |
| 48 | Windows 10 Target Devices encounter slow performance and high CPU at the same time. | Try to stop the "Network Location Awareness" service before vDisk creation to see if this resolves the issue. | Microsoft Windows 10. | https://support.citrix.com/article/CTX232313 |
| 49 | The XenDesktop Setup Wizard attempts to connect to a Hyper-V host in the wrong cluster. This issue happens if there are multiple clusters managed by the same SCVMM server. | Upgrade to Citrix Provisioning Services PVS 7.15.3 or 7.16. | https://support.citrix.com/article/CTX232501 | |
| 50 | When using the XenDesktop Setup Wizard to generate "Generation 2" Target Devices, the amount of CPUs configured during the wizard is ignored and the VMs CPU count match the specified VM Template. | This is a known issue when creating Generation 2 VMs using the XenDesktop Setup Wizard. As a workaround, edit the CPU configuration on the VM Template before using the wizard to deploy machines. | https://support.citrix.com/article/CTX232572 | |
| 51 | Provisioning Servers show as offline and Event Log shows Event ID "Undefined database error". | Install the latest version of SQL native client on all PVS servers. The version installed with PVS did not support TLS 1.2 which was enabled on SQL. | Citrix Provisioning Services 7.12. | https://support.citrix.com/article/CTX232573 |
| 52 | A Target Device running on Hyper-V may fail to boot when in Read/Write mode and when vDisk streaming switches from Legacy NIC to Synthetic NIC during boot. | This issue is related to RES ONE Workspace and will be resolved in a future release of this software. As workarounds, contact RES Workspace support for a newer "RES ONE Netguard" driver or disable the RES Netguard driver via registry on the VDA. | RES ONE Workspace. | https://support.citrix.com/article/CTX232604 |
| 53 | On your master Target Device the PVS Imaging wizard fails to run either with error "The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer" or "imagingwizard.exe crashed when calling the following method". | The first error occurs when Visual C++ is not installed on your master Target Device. The second error is resolved by upgrading .NET Framework to 4.6. Both these components are required by the imaging wizard. | https://support.citrix.com/article/CTX232698 | |
| 54 | vDisk properties are lost after a move of the vDisk to a Microsoft DFS server occurs. | Grant the PVS server computer account with full control permissions on the new store directory. | https://support.citrix.com/article/CTX232887 | |
| 55 | When trying to promote a vDisk you receive an unexpected MAPI error. | The "Catalog UID" on the Delivery Controller was different than the "xdCatalogID" entry in SQL. Either recreate the catalog and VDAs or run a SQL query on the PVS database to correct the IDs. | https://support.citrix.com/article/CTX215890 | |
| 56 | The XenDesktop Setup Wizard fails with error "The xsPvsSiteUuid field does not exist". | Make sure the PVS Console you are using matches the PVS Server software and all its components. Also make sure the Database Schema version is consistent with the version of your PVS server. | https://support.citrix.com/article/CTX233289 | |
| 57 | When importing a new vDisk version on top of an existing vDisk you receive message "The scan did not find any new vDisks". | Make sure there are no XML manifest files in the Store path where the vDisk version is being imported. | https://support.citrix.com/article/CTX233655 | |
| 58 | After a PVS upgrade Target Devices experience slow boots when configured to use BDM using an ISO. | Create a new ISO using BDM from the updated PVS servers. | https://support.citrix.com/article/CTX233881 | |
| 59 | After an upgrade to PVS 7.17 you are unable to open the PVS Console. | Install .NET 4.6.1 on the PVS servers, reboot then attempt to open the Console. | Citrix Provisioning Services 7.17. | https://support.citrix.com/article/CTX234351 |
| 60 | After enabling PVS Accelerator your Target Devices receive a "Login request time out" error during boot. | A MAC address change during Target Device boot up caused this issue. A gateway then blocked this behaviour, which is normal when using PVS Accelerator. Configure your gateway to allow this MAC change without blocking the boot. | https://support.citrix.com/article/CTX234863 | |
| 61 | When a Target Device boots you receive message "Login request timed out!". | Check the Streaming IP and Management IP addresses are set correctly under "Server Properties" and "Configure Bootstrap" configuration menus. | https://support.citrix.com/article/CTX234922 | |
| 62 | When trying to run the Imaging Wizard on a newly upgraded 7.17 Target Device and when connecting to a newly upgraded PVS 7.17 server, you see error "Cannot connect to Server version prior to 7.17". | Make the PVS Service Account a db_owner on the PVS database. | Citrix Provisioning Services 7.17. | |
| 63 | When connecting Provisioning Server 7.15 CU2 to ESX 6.7 you receive error "Cannot connect to the hypervisor". | This will be resolved in Provisioning Services 7.18 and a future 7.15 LTSR. | https://discussions.citrix.com/topic/395445-supporting-vcenter-67-for-pvs-715/ | |
| 64 | The "Active Directory" menu option is missing when you right-click on a Target Device. | Borwse to your PVS database, right-click the table "dbo.farm" and select the top 1000 rows. Confirm if "adGroupsEnabled" is set to "1". If not, set it. | https://support.citrix.com/article/CTX235577 | |
| 65 | PVS Accelerator fails to initialise caching and the status shows "Incompatible protocol version". | If there are multiple sites in a PVS farm, a target that belongs to Site-A for example must aquire a bootstrap from a PVS server in Site-A, login to a PVS server in Site-A and be assigned a vDisk served from a PVS server in Site-A. | https://support.citrix.com/article/CTX235616 | |
| 66 | When installing or upgrading the Provisioning Services Console to 7.18, you may see warning "A newer version of Citrix Diagnostics Facility is already installed". | This message can be ignored. | ||
| 67 | When running the Imaging Wizard you receive error "Could not load file or assembly "Citrix Diagnostics Version=7.1.3.0". | Install the 7.13 GPMC kit and rerun the Imaging Wizard. | https://support.citrix.com/article/CTX235814 | |
| 68 | When you attempt to join a PVS server to the farm you receive error "A database error occured. The target principal name is incorrect". | This could be due to SQL database corruption, SPN corruption or an issue with the PVS SOAP service account. | https://support.citrix.com/article/CTX235972 | |
| 69 | Target Devices may fail to shutdown when creating PVS targets with a local write cache such as "Cache in device RAM with overflow on hard disk". | Set DWORD "RebootDelaySec" to "2" under "HKLM\SOFTWARE\Citrix\ProvisioningServices". | https://support.citrix.com/article/CTX235960 | |
| 70 | Upgrades to new Windows 10 versions may fail. | It may not be possible to perform an upgrade from say Windows 10 1703 to 1709 without performing a reverse image. | ||
| 71 | Office 2016 licensing activation is lost when placing a vDisk in Standard mode. It works when in Private mode. | Follow the steps outlined in CTX article which involves setting the vDisk "Microsoft Volume Licensing" setting to "None" and running OSPP.VBS/OSPPREARM.EXE commands. | https://support.citrix.com/article/CTX231040 | |
| 72 | When booting a Target Device it does not boot and you receive error "No ARP reply". | Reconfigure the BDM.iso or BDM disk. | https://support.citrix.com/article/CTX221584 | |
| 73 | The XenDesktop Setup Wizard fails with error "Failed to connect with the requested server. (UUID_INVALID)". | If thereis a mismatch of the UUID between PVS and XenServer, the currently supported solution is to recreate the Target Devices including deleting and recreating the "Hosts" entry on PVS. | https://support.citrix.com/article/CTX236636 | |
| 74 | While booting a Target Device, the wrong MAC address is shown. | Remove the NIC, add a new one and then the correct MAC will appear. | https://support.citrix.com/article/CTX237139 | |
| 75 | If you reboot a VDA using PVS Accelerator via Studio or power off and on the VDA from the XenCenter console, the PVS status reports "Incompatible Protocol Version". If you reboot the VM the status shows correctly as "caching". | Recreate the ARDBP32.BIN bootstrap file. | https://support.citrix.com/article/CTX237338 | |
| 76 | Windows 10 1803 cannot boot when the vDisk cache mode is set to "Cache in Device RAM". | Citrix are investigating this issue. As a workaround, "Cache in device RAM with overflow on hard disk" can be used. Citrix also report that "Cache in device RAM" for Windows 10 1808 is not supported on Citrix Provisioning 7 1808. | https://support.citrix.com/article/CTX231942 | |
| 77 | KMS activation takes too long to complete after configuring KMS as documented in CTX128276. | As per the CTX article, follow the steps from CTX128276 and add a startup script to Windows that performs KMS activation when Windows is started. | https://support.citrix.com/article/CTX237691 | |
| 78 | Target Device fails to boot and no errors are shown. | Make sure the "Datacenter" property for the Host connection you are using matches the datacenter name in vCenter. | https://support.citrix.com/article/CTX238141 | |
| 79 | After running through the Imaging Wizard and rebooting, after log on an "Imaging Wizard did not restart" error appears. | DHCP option 67 should be configured with "pvsnbpx64.efi" and not "ARDBP32.BIN" when using Generation 2 Target Devices. | https://discussions.citrix.com/topic/398326-pvs-718-imaging-wizard-did-not-start-error/ | |
| 80 | When upgrading Provisioning Services from 7.17 to 7.18, you receive error "A newer Version of Citrix Diagnostics Facility is already installed". | Before upgrading, you must manually uninstall CDF from the PVS server, servers that host the console, and any Target Devices. | Citrix Provisioning Services 7.18. | https://support.citrix.com/article/CTX238399 |
| 81 | Booting Target Device fails with error "No servers available for disk". You also see database access errors in Event Viewer. | In this case, the PVS service account had restricted permissions to the SQL database. | https://support.citrix.com/article/CTX238396 | |
| 82 | Session Printers configured through Group Policy do not appear on a streamed desktop until "gpupdate /force" is run on the VDA. | The printer management option in PVS was interfering with the GPO printer policies. From within the PVS console, uncheck "Enable printer management" on the affected vDisk properties, restart the "Citrix PVS Soap Server" and "Citrix PVS Stream Service" services, and then restart the Target Device. | https://support.citrix.com/article/CTX238512 | |
| 83 | Citrix Provisioning servers may stop responding or Target Devices may freeze due to large SQL transaction logs. | Backups of the SQL database and transaction log should be taken regularly to avoid this file increasing in size. | https://support.citrix.com/article/CTX238582 | |
| 84 | When running the XenDesktop Setup Wizard or the Streamed VM Wizard, the PVS Console may report an error such as "Cannot connect to the hypervisor" or "The underlying connection was closed: an unexpected error occurred on a send" if you are connecting to a vCenter server that has been configured to only accept TLS 1.1 or higher connections. | Use the registry to configure .NET to communicate using higher versions of TLS, as explained in the CTX article. | https://support.citrix.com/article/CTX238947 | |
| 85 | VDAs randomly freeze. | Extend the Write Cache drive, as it is running out of space. | https://support.citrix.com/article/CTX239343 | |
| 86 | Windows 10 boots and hangs at the Windows splash screen. | This can happen if you have both a Boot Device Manager (BDM) ISO file and a BDM partition attached to the Target Device. Remove the ISO. | ||
| 87 | 10GB Write Cache disks are being fully consumed and Process Monitor is showing that the majority of writes are from web browsers, specifically Firefox. | Running a defragmentation against the vDisk and setting Firefox option "browser.cache.disk.enable" to "false" solved the problem. | https://discussions.citrix.com/topic/399672-win10-write-cache-with-browsers/ | |
| 88 | When Target Device boots you receive a BSOD with error "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (CVhdMp.sys)". | Follow the CTX article steps to clone a working VM, convert it to a template, deploy a new VM from the template and edit a few properties. | https://support.citrix.com/article/CTX239608 | |
| 89 | When booting a Target Device you receive error "PXE-E32: TFTP open timeout". | Re-running the PVS Configuration Wizard on all PVS servers and checking "Use the Provisioning Services TFTP service" resolved the issue. | https://support.citrix.com/article/CTX220799 | |
| 90 | When doing a rebalance of Target Devices, they stop responding. | The vDisk these devices were using was set up with a "Cache on server" cache type. | Citrix Provisioning Services 7.13. | https://support.citrix.com/article/CTX229243 |
| 91 | Target Devices boot and stick at "virtual disk found". | The gold image was built using a machine with EFI boot firmware, but the Target Devices are using set to use BIOS boot firmware. Changing the Target Devices to EFI fixed the issue. | ||
| 92 | When booting a Target Device using BDM, the machine gets stuck in a reboot loop whilst constantly displaying message "Downloading tsbbdm.bin from server". | Boot Device Manager cannot work with any MTU lower than 1500. The WireShark trace taken when diagnosing this issue shows an MTU of 1410. Using PXE instead, the Target Device will auto-negotiate with different MTU sizes. | https://discussions.citrix.com/topic/399751-downloading-tsbbdmbin-over-and-over-again/ | |
| 93 | After applying patches to Windows 10 that have been released after November 2018, no pagefile is set or created on the non-OS volume. | Install KB4476976 for Windows 10 1809 which fixes this issue. For 1803, install the 2019-02 Cumulative Update. | Microsoft Windows 10 1709, 1803, 1809. | https://discussions.citrix.com/topic/400750-windows-update-kb4480976-causes-pagefile-problems/ |
| 94 | When running the Imaging Wizard which is on version 1811, you cannot connect to a Provisioning Server that runs 7.15 LTSR. You receive error "Cannot connect to Server version prior to 7.20". | The Target Device and Provisioning Server should be on the same version. | https://discussions.citrix.com/topic/401146-cannot-connect-to-server-version-prior-to-720/ | |
| 95 | Target Device does not boot unless "Interrupt Safe Mode" is enabled. | A SATA Controller was attached to the virtual machine. Removing it allowed the machine to boot normally. | ||
| 96 | When performing an in-place upgrade of Citrix Provisioning Server from 1808 to 1903, you receive message "Please uninstall PVS Server 1808 and then install PVS Server 1903". | This is caused by a CDF version issue. | Citrix Provisioning 1808. | |
| 97 | Creating machines on vSphere fails with error "DVPortGroup cannot be found" as seen on the vCenter console. | VMware recommends creating a new temporary DVPortgroup pointing to the same network as the DVPortgroup that has the problem with Citrix Provisioning. Existing working Machine Catalogs could have information about the old DVPortgroup in the Virtual Apps and Desktops database, which cannot be modified. If the DVPortgroup no longer exists in the Host connection, you may need to recreate existing Machine Catalogs and VDAs. | https://support.citrix.com/article/CTX250028 | |
| 98 | When using "Cache in RAM", Windows 10 1809 VDAs blue screen with error "SYSTEM THREAD EXCEPTION NOT HANDLED". | Citrix is investigating. As a workaround, use "Cache in device RAM with overflow on hard disk". | Microsoft Windows 10 1809. | https://support.citrix.com/article/CTX250105 |
| 99 | After an upgrade to Citrix Provisioning 1903, Target Devices do not boot in standard mode. | Reinstalling the VDA without the MCSIO option resolved the issue. The original install script used had the "/install_mcsio_driver" switch included. | https://discussions.citrix.com/topic/402355-unable-to-boot-vdisk-in-standard-mode/ | |
| 100 | Target Devices during boot blue screen with error "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (CVhdMp.sys)". | Downgrading the PVS Target Device software from 1811 to 1808 resolved the problem. | https://discussions.citrix.com/topic/402142-pvs-target-getting-blue-screen-on-nutanix-acropolis-hypervisor/ | |
| 101 | Target Device fails to boot with BSOD "BNIStack failed, network stack could not be initialized". | Install Microsoft KB2550978. | Microsoft Windows Server 2008 R2. | https://support.citrix.com/article/CTX202087 |
| 102 | During vDisk version promotion, you may see error "0x00000057 - Invalid Parameter". | Citrix Provisioning does not support VHD vDisks on 4K storage. A VHD disk was not initially designed for 4K based storage. Merge all vDisk versions to the base, and then change the disk to VHDX. | https://support.citrix.com/article/CTX250229 | |
| 103 | "No servers available for disk" appears for a device booting to a private mode vDisk. | Set "SkipRIMSForPrivate" DWORD to "0x1" under "HKLM\SOFTWARE\Citrix\ProvisioningServices\StreamProcess" and restart the Citrix PVS Stream Service. | https://support.citrix.com/article/CTX200233 | |
| 104 | Updating the Target Device software to 1903 results in a black screen during boot. | A reinstall of the VDA resolved this issue, making sure that the MCS I/O driver was not included. | https://discussions.citrix.com/topic/402888-target-device-driver-721021001-1903/ | |
| 105 | After an in-place upgrade of the Target Device software, the Target Device boots in Maintenance mode, but not in Test or Production mode. This problem only occurs when the vDisk is configured for KMS. | Boot the Target Device in Maintenance mode, export the "HKLM\SOFTWARE\Citrix\ProvisioningServices\KMS" key. Upgrade the Target Device software and then re-import the previously exported key. | https://support.citrix.com/article/CTX255898 | |
| 106 | When booting Target Devices from XenServer, the Target Devices blue screen with error "BNIStack failed". | The customer ended up upgrading to Citrix Hypervisor 8.0 and creating a new vDisk with XenTools freshly installed. | https://discussions.citrix.com/topic/403251-pvs-715-cu3-bnistack-failed-bsod-cvhdmpsys-xenserver/ | |
| 107 | When Target Devices boot the "Getting device ready" message appears each time. | This is expected behaviour and should not be treated as an issue. | https://support.citrix.com/article/CTX203575 | |
| 108 | After installing or upgrading the Target Device software to 7.15 CU4, Target Devices lose trust with the domain and some Target Devices fail to register with a Delivery Controller. | This might only be an issue with CU4. | Citrix Provisioning 7.15 LTSR CU4. | https://discussions.citrix.com/topic/403465-windows-10-1903-and-pvs/ |
| 109 | After silently running the Provisioning Services Configuration Wizard and then attempting to open the Provisioning Services Console, you receive error "An error occurred communicating with the Server". | Add the PVS service account to the Local Administrators group on the machine. | https://support.citrix.com/article/CTX256785 | |
| 110 | After upgrading PVS from 7.15 LTSR CU3 to CU4, PowerShell snapins are not upgraded and from "Programs and Features" you can see CU3 in the names. | This will be resolved in Citrix Provisioning 7.15 LTSR CU5. For now, mount the PVS 7.15 LTSR CU4 media and install the snapins manually as per the CTX article instructions. | Citrix Provisioning 7.15 LTSR CU4. | https://support.citrix.com/article/CTX256773 |
| 111 | If using ReFS storage for your vDisks, you may encounter vDisk corruption after merging or promoting a vDisk. | Contact Citrix for a private fix. | Citrix Provisioning 7.15 LTSR CU4 and 1903. | |
| 112 | When attempting to boot a vDisk from a PVS server other than the one it was created on, error "vDisk cannot be accessed" is displayed. | The ".pvp" files on each PVS server had a different time stamp. | https://discussions.citrix.com/topic/401448-vdisk-cannot-be-accessed-a/ | |
| 113 | Upgrading the VDA to version 1906 automatically installs the new MCS I/O driver if it was not previously installed. As a result, target devices fail to boot in read only mode. | Citrix recommends that you do not install updated MCS I/O functionality and Citrix Provisioning in the same Windows environment. | Citrix Virtual Apps and Desktops 7 1903 & 1906. | |
| 114 | After creating a vDisk and trying to log on to a Target Device that is using the new vDisk, you receive error "The trust relationship between this workstation and the primary domain failed". Resetting, deleting and recreating the machine account from the PVS console does not resolve the issue. | Boot the gold image machine and run command "Test-ComputerSecureChannel". If the response is "false", run command "$Creds = Get-Credential" followed by "Test-ComputerSecureChannel -Repair -Credential $Creds". Once the machine account password is reset, capture a new vDisk. | https://support.citrix.com/article/CTX257591 | |
| 115 | During the XenDesktop Setup Wizard process, when creating a BDM partition, you may receive error "Cannot create BDM partition for device". This happens on a VMware environment. | A datastore permission was blocking upload of the BDM when trying to create a device with the XenDesktop Setup Wizard. For the account running the wizard, grant access to "Administration -> Access Control -> Roles -> %CitrixRoleName% -> Privileges -> All Privileges -> Cryptographic operations -> Direct Access" | https://support.citrix.com/article/CTX258291 | |
| 116 | When using Device CALs, the RDS Licensing Manager shows multiple Device CALs consumed by the same Target Device. | This is expected. The RDS CAL that is issued is stored in "HKLM\SOFTWARE\Microsoft\MSLicensing\Store" on each Target Device. When a Target Device reboots, that registry information is lost. It is advised to use Per User CALs. | https://support.citrix.com/article/CTX130004 | |
| 117 | When attempting to create a new vDisk and booting the gold machine using Boot Device Manager, you receive error "BOOTMGR is missing". | Detach the second hard disk from the machine being captured. | https://support.citrix.com/article/CTX214751 | |
| 118 | After deploying Target Devices on VMware, the mouse cursor when connected to the virtual machine's console does not work and sticks to the side of the console window. | Downgrading the virtual machine template's compatibility to "ESXi 5.1 and later" and redeploying the Target Devices using the new template resolved the problem. | ||
| 119 | Virtual Machines were configured with old statically assigned DNS IP addresses, even after removing them. This only happens to PVS provisioned machines with App Layering images. | It turns out that Citrix Provisioning was being used to deploy the machines and the Boot Device Manager ISO has static DNS entries configured, which was then applying to the machines. | https://discussions.citrix.com/topic/404273-app-layering-image-being-assigned-static-dns-ips/ | |
| 120 | Servers hang during the day, and a reboot is needed to bring them back online. | Disabling Asynchronous I/O has solved the problem. | https://discussions.citrix.com/topic/404730-vms-losing-connection-to-vdisk-async-io/ | |
| 121 | When booting a Target Device you receive error "PXE-E32: TFTP open timeout". | "Tftpcpl.cpl" under "C:\Program Files\Citrix\Provisioning Services" was showing the network interface unchecked under the "TFTP Network" tab. Checking the interface did not stick. Re-running the Configuration Wizard resolved the issue and the interface remained checked. | ||
| 122 | The "Reset Machine Account Password" option is missing from the console when righ-clicking on a Target Device. | The Target Device must be powered off before this option is made available. | ||
| 123 | Target Devices fail to boot with error "PXE-E99: Unexpected network error". | For UEFI Target Devices the DHCP option "066 Boot Server Host Name" was pointing to a VIP that was DOWN. Repointing to an individual Provisioning server resolved the problem. | ||
| 124 | During failover from one Provisioning server to another, Target Devices that have the Palo Alto Terminal Services agent installed do not reconnect. | Install version 10.0.1.32 of the Palo Alto Terminal Service agent, and then set DWORD values as per CTX article. | https://support.citrix.com/article/CTX292848 | |
| 125 | When exporting a vDisk, no XML file is generated. | Within the properties of each vDisk Version, remove any multiple lines. | ||
| 126 | Target Devices boot slowly with the SentinelOne agent installed. | SentinelOne was running a disk certificate scan. Allow this to run and complete in a read-write version of the vDisk. The 'sentinelctl.exe read_fdcs_status' command and 'ScanCompleted = 2' result confirms the scan is complete. | https://support.citrix.com/article/CTX370621/citrix-provisioning-services-slow-target-boot-with-sentinel-one-client | |
| 127 | After logging into a Target Device you receive a popup from Citrix License Management stating "No device license is currently available for this computer. A system shutdown will be initiated in 720 hours. To avoid loss of data, save your work now and close all applications". | The provisioning license applied on the Citrix License Server had expired. On the Provisioning Servers Event ID 107 "Licensing grace period expired" was being logged every hour. Redownloading the renewed "Citrix Provisioning for Apps and Desktops" license and placing on the license server resolved the problem. | https://docs.citrix.com/en-us/licensing/licensing-guide-for-citrix-provisioning.html#renew-a-license |
Keith Wills
July 13, 2018may see warning “A newer version of Citrix Diagnostics Facility is already installed” – “This message can be ignored” – not true, or at least for me it would cancel the install. Was trying to upgrade console first and got the error. Fix was to uninstall the CDF (Citrix Diagnostics Facility) and then run console install. Gave a new error (installation failed), but actually went through and completed.