PvD enabled targets are failing to register with the broker. Additionally, within Citrix Studio the targets return agent error code 6:
The Personal vDisk could not find a disk attached to the system for storing user data.

1. Verify that a PvD disk is attached to the VM through the Hypervisor console.

2. Ensure that the GUID marker file ({9E9023A4-7674-41be-8D71-B6C9158313EF}.VDESK.VOL.GUID) exists at the root of the PvD Disk.

• Browse to the root of the PvD disk through Windows File Explorer.
• Under 'Folder Options', select 'Show hidden files, folders, and drives' and uncheck 'Hide protected operating system files'.
• If the GUID marker file is not present at the root of the PvD Disk, insert the GUID marker file into the PvD from a working PvD where the file is present.

3. If the GUID marker file exists, ensure that it can be read

• This condition typically occurs due to “Data Leak Prevention” software preventing access to the PvD disk. In this case, try adding an exception for “attached disk” in the “Data Leak Prevention” software configuration.

 

---

Problem Cause

The Personal vDisk service prevents the registration of the VDA with the broker until the PvD successfully initializes. This is done in an effort to ensure that users are not connected to a desktop before the PvD state is fully functional. For the machines to register the PvD agent error will need to be resolved, error code 6 specifically indicates that a viable PvD disk was not found. The Personal vDisk technology locates the PvD disk by iterating through the root of each of the disks on the system attempting to locate the GUID marker file. If a PvD disk is not attached to the VM, or if the GUID marker file does not exist at the root of the drive, or if the read attempt fails then PvD will return error code 6.

PvD enabled targets are failing to register with the broker. Additionally, within Citrix Studio the targets return agent error code 6