57 matches found
PVS Server: Windows Event logging for UEFI target Devices Boot Time inaccurate
The customer had built a new UEFI based vdisk and deployed it to production. The customer subsequently observed that the PVS Servers were recording a clearly inaccurate boot time, of millions of minutes, in Windows Event logs when target devices were booting. Example inaccurate boot time logged i...
Provisioning Services with multiple non routable streaming networks
Using Provisioning Services with multiple non routable streaming networks may result in target devices failing to fully boot.A simple example is described below, how customers may have multiple PVS servers added to each network. Example single PVS server farm, the PVS server has three network...
BITS performance counters not working after publishing App Layering image to PVS
When you published an image from App Layering to PVS, Target Devices may not show BITS performance counters...
PVS 2407 BIOS target devices crash on PVS reconnect
PVS 2407 BIOS based Target Devices crash on PVS reconnect. Customers would typically encounter a requirement for a PVS reconnect when performing load balancing operations, for example when patching and rebooting PVS servers. PVS reconnect would also occur during normal operation if sufficient PVS...
Citrix PVS rebalancing leaves target devices unresponsive with CheckPoint agent installed
Rebalancing PVS targets devices ends up with the target devices in an unresponsive frozen state. The only method to recover target devices is to force restart the target devices on the hypervisor. Customer validated all PVS servers are configured as PVS login servers. Target devices fail to...
PVS Target Devices boot statistics very high bytes read
The customer had observed very slow PVS target boot time. Boot statistics on vDisk shows a long time to boot, over 600 seconds, and boot time bytes read of over 2.5 GB...
PVS SOAP Service Crashes After Running the Auto Update
Provisioning Services Simple Object Access Protocol service crashes after running the Auto Update. The Auto Update feature in Provisioning Services PVS allows a master target to receive an update and roll it out to the target devices. The completion is signaled to the Windows Application log by a...
Provisioning Services Target Devices Start with MAC Address as the Computer Name
When booting, VMware ESX target devices replace computer name with MAC Address...
Error: "Max Number of DHCP Retries Exceeded" when Provisioning Services Target Devices are Unable to Boot from PXE
Provisioning Services PVS target devices are unable to boot from PXE with an error: "Max number of DHCP retries exceeded" This failure occurs very early in the boot process when the PXE client sends a Discover packet to the broadcast domain to find a DHCP server...
Target Device Performance and Freezing Issues While Patched into a Cisco Catalyst Line of Switches
Target devices experience intermittent freezing behavior and poor performance while patched into a Cisco Catalyst line of switches...
How to Export Target Devices into a .CSV File
This article details how to export Target Devices from a Provisioning Services PVS database in a formatted Comma Separated Values CSV file. Requirements SQL Server Management Studio or bcp.exe, both of which are components of a full SQL Server or SQL Server Express install...
Understanding Subnet Affinity and Auto Rebalance
This article details the Subnet Affinity and Auto Rebalance features and also provides the best practices for their use. Subnet Affinity When assigning the server and NIC combination to provide a vDisk to target devices, select from the following subnet settings: None: Ignore subnets; use least...
Provisioning Services Server Target Devices BSOD with KERNEL_SECURITY_CHECK_FAILURE When Cache is Set on RAM
Provisioning Services PVS Server target devices streamed to a vSphere Virtual Machine displays a blue screen withKERNELSECURITYCHECKFAILURE when cache is set on RAM...
Error: "A duplicate IP address was assigned" on Provisioning Server Target Devices
Two IP addresses are assigned to individual PVS target devices streaming network adapters. The behavior can occur on every boot, or intermittently. Background This can occur in environments with DHCP solutions which may assign different IP addresses to individual target devices, at pxe dhcp reque...
Target Device Fails to Boot on Hyper-V V2
Provisioning Service Target Devices fails to boot when launched from a HyperV v2 host other than the host where the Provisioning Service Server is located...
Provisioned Target Devices are Acquiring Multiple IP Addresses During Boot Process
Provisioned Target Devices acquiring multiple IP addresses on a same NIC while booting up, thus leading to IP address exhaustion on a DHCP server. The following error message might appear: "A duplicate IP address was assigned to this machine while attempting to boot from the network. Stop code:...
Copied vDisk Fails to Start in Private Mode
Provisioning Services Server target devices fail to boot in private mode with the following error: “vDisk file access permission denied ” The error does not occur when the target devices boot is in standard mode...
PVS Configuration Wizard does not display dialogues to configure DHCP or PXE services
Citrix Provisioning Configuration wizard does not display dialogues to configure DHCP servers and PXE Services. The configuration wizard begins by directly showing the Farm Configuration dialogue. If DHCP servers and PXE Services are not configured, PVS target devices which rely on those services...
Citrix Provisioning Target Poor Performance And Slow Boot
Target Devices appear to boot slowly and hang or remain stuck at a black screen shortly after power on. Other devices that are up and running can be found frozen. These machines might be found "unregistered" in Studio and you cannot RDP or console into them. PVS servers may be reporting DB Offlin...
PVS target devices will not HA failover to another PVS server.
PVS target devices will not HA failover to another PVS server. Targets devices will freeze until the original server they were streaming from is available again. HA related configurations can be checked: The vdisk should beconfigured to use cache in ram with overflow to local device hard disk, an...