VMWare VVOL Support With Citrix MCS and PVS

Use of VMware vSphere Virtual Volumes VMware vVOLs with CVAD MCS and PVS environments...

PVS XDSW retain template disks

AllowXendesktop Setup Wizard XDSW created targets, to be created with disks as configured in the template. Background: PVS 7.x XDSW introduced new functionality to allow setting write cache size for the new target devices about to be created. XDSW will create the cache disk, and it will be...

High CPU Utilization on PVS 7.6 Servers

PVS 7.6: High CPU Utilization...

XenDesktop Setup Wizard fails with error (UUID_INVALID)

When running the XenDesktop Setup Wizard XDSW you might receive the following error when selecting the PVS Accelerator Configuration. The error might also be shown when attempting to change the Accelerator Status of a Target Device or Enabling/Disabling the Accelerator setting on a Host Entry...

PVS config wizard failed with error " Service Start for Citrix PVS Soap Service failed. The service did not respond to start or control request in a timely fashion. (0x41d)"

While running the Configuration wizard it fails to start the network service. Event viewer shows that the soap service has terminated. Soap service is in stopped state and is not able to start the service. PVS config wizard failed with error " Service Start for Citrix PVS Soap Service failed. The...

How to re-create missing .pvp file from vDisk versions

This article explains how to recreate a .pvp file for a PVS vDisk version in case that is deleted by accidentally...

PVS configuration wizard failed to add domain\users service account into database automatically:<The EXECUTE permission was denied on the object 'uspGetServerSettings

PVS configuration wizard fails to add domain\users service account into database automatically.The EXECUTE permission was denied on the object 'uspGetServerSettings' or System.Data.SqlClient.SqlException 0x80131904: Windows NT user or group 'domain\username' not found in CDF trace. No error is...

PVS Accelerator fails to cache and shows status: "Incompatible protocol version"

When PVS Target Devices that have been configured for PVS Accelerator caching boot, the XenServer PVS Accelerator fails to initialize the caching correctly. The caching status of the target will change from Stopped to Initialized and then eventually to"Incompatible Protocol version"...

The Soap service is not running on the PVS server

The Soap Server service isn't running.This service is needed to allow logging in to the Provisioning Services Console...

The Tftp service is not running on the PVS server

The TFTP Service isn't running. This service is required for target devices that use the network boot process. Note: If you are using the Boot Device Manager boot partition, this service is not required. If you are not using the network boot process, you can hide this alert...

The Stream service is not running on the PVS server

The Stream Service is not running. This service is responsible for keeping all critical PVS services up and running...

The Stream process is not running on the PVS server

Smart Check has detected that the StreamProcess.exe isn't running. This process is responsible for allowing target devices to acquire images from the vDisks contained in the vDisk store...

After upgrading Windows on a PVS server, PowerShell snapins are no longer shown

After upgrading a PVS server from Windows Server 2008 R2 to Windows Server 2019, it was observed that none of the PVS PowerShell snapins were registered. Tools like the App Layering Agent that attempted to use those those PowerShell cmdlets failed, though they had worked before the upgrade...

TRIM and PVS: vDisks may Reduce in Size after a Merged Base

After performing a Merged Base operation on a vDisk that is utilizing the VHDX file format, the resultant merged base VHDX file may be smaller than the original base VHDX file. For example, this behavior might occur in situations where files are deleted in a particular vDisk version, and these...

PVS targets using MAK Licensing intermittently fail to reactivate

PVS targets using a vdisk that has the radio button set to MAK licensing will intermittently fail to reactivate after rebooting. PVS CDF traces may also show an error that the device does not exist in the VAMT database. "Device: 10.10.10.10 not found in Vamt database."...

Unable to open PVS Console after upgrade to 7.17

Unable to open PVS Console after upgrade to PVS 7.17 with error An unhandled exception occurred and the application will exit. Please report the information below. Press Ctrl-C to copy the data to the clipboard. Method not found: '!!0 System.Array.Empty'. Stack Trace: at...

What are Hung Threads and why is the StreamProcess terminating?

On PVS Servers StreamProcess Hung Threads can lead to poor performance, constant target re-connections and even full outages. These Hung Threads are usually detected by looking at the Windows Application Event logs. The following Events will be recorded: Level| Source| Id| Text ---|---|---|---...

How to Sysprep PVS images before they are streamed to Target Devices.

Question: Is needed to run Sysprep on PVS images? Answer: It is not needed to run Sysprep on PVS/MCS images since they both have their own version/method built-in to Sysprep the images. Also, it is not recommended to run Sysprep on PVS or MCS machines since it is not needed...

PVS image published from App Layering gives a BSOD with inaccessible boot device error

When booting an image in PVS that was published via App Layering, you may receive a BSOD with theINACCESSIBLE BOOT DEVICE error...

App Layering - PVS Blue Screen SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (CVhdMp.sys)

The BSOD SYSTEMTHREADEXCEPTIONNOTHANDLED CVhdMp.sys is seen when booting up a VM in PVS using an App Layering image. It is also possible to just simply get a BSOD with a Stop Code of 0x0000007B. However, this is fairly generic. If you see this stop code and "ERROR: BNIStack failed, network stack...