You can use a diagnostic tool to monitor the changes made by users to both parts of their Personal vDisks (the user data and the application parts). These changes include applications that users have installed and files they have modified. The changes are stored in a set of reports.
Software hive report: This report generates two files: Software.Dat.Report.txt and Software.Dat.delta.txt.
The Software.Dat.Report.txt file records the changes made by the user to the HKEY_LOCAL_MACHINE\Software hive. It contains the following sections:
See the hive delta report for information about the Software.Dat.delta.txt.
System hive report: The generated SYSTEM.CurrentControlSet.DAT.Report.txt file records changes the user made to the HKEY_LOCAL_MACHINE\System hive. It contains the following sections:
Security hive report: The generated SECURITY.DAT.Report.txt file monitors all changes that the user makes in the HKEY_LOCAL_MACHINE\Security hive.
Security Account Manager (SAM) hive report: The generated SAM.DAT.Report.txt file monitors all changes that the user makes in the HKEY_LOCAL_MACHINE\SAM hive.
Hive delta report: The generated Software.Dat.delta.txt file records all registry keys and values added or removed, and all values the user modified in the HKEY_LOCAL_MACHINE\Software hive.
Personal vDisk logs: The log files Pud-IvmSupervisor.log, PvDActivation.log, PvDSvc.log, PvDWMI.log, SysVol-IvmSupervisor.log, and vDeskService-<#>.log are generated by default in P:\Users\<user account>\AppData\Local\Temp\PVDLOGS, but are moved to the selected location.
Windows operating system logs:
File system report: The generated FileSystemReport.txt file records changes the user made to the file system in the following sections:
In Studio, when you choose a PvD-enabled machine in a machine catalog, the "PvD" tab provides monitoring status during image updates, plus estimated completion time and progress. The possible state displays during an image update are: Ready, Preparing, Waiting, Failed, and Requested.
An image update can fail for different reasons, including lack of space or a desktop not finding the PvD in sufficient time. When Studio indicates that an image update failed, an error code with descriptive text is provided to help troubleshooting. Use the Personal vDisk Image Update Monitoring Tool or the personal-vdisk-poolstats.ps1 script to monitor image update progress and obtain error codes associated with the failure.
The most recent content is at the end of the log file.
Error code 2. The rule file contains syntax errors. The Personal vDisk log file contains the name of the rule file and line number where the syntax error was found. Fix the syntax error in the rule file and retry the operation.
Error code 3. The last inventory is stored in “UserData.V2.vhd” in “\ProgramData\CitrixPvD\Settings\Inventory\VER-LAST”. Restore the inventory corresponding to the last version of the master image by importing the ‘VER-LAST’ folder from a known working PvD machine associated with the previous version of the master image.
Error code 4. This is caused by personal vDisk version incompatibility between the last master image and the current master image. Retry updating the catalog after installing the latest version of personal vDisk in the master image.
Error code 5. A USN journal overflow was caused by a large number of changes made to the master image while creating the inventory. If this continues to occur after multiple attempts, use procmon to determine if third party software is creating/deleting a large number of files during inventory creation.
Error code 6. First, verify that the PvD disk is attached to the VM through the hypervisor console. This error typically happens due to “Data Leak Prevention” software preventing access to the PvD disk. If the PvD disk is attached to the VM, try adding an exception for “attached disk” in the “Data Leak Prevention” software configuration.
Error code 7. Restart the desktop and retry the operation.
Error code 8. Install personal vDisk and try again.
Error code 9. The personal vDisk inventory was not updated in the master image before shutting down the desktop. Restart the master image and shut down the desktop through the “Update personal vDisk” option, and then create a new snapshot; use that snapshot to update the catalog.
Error code 10. This could be caused by the PvD driver failing to start a virtualization session due to an internal error or personal vDisk corruption. Try restarting the desktop through the Controller. If the problem persists, collect the logs and contact Citrix Support.
Error code 11. This error occurs when the PvD driver fails to find the PvD disk within 30 seconds after restart. This is usually caused by an unsupported SCSI controller type or storage latency. If this occurs with all desktops in the catalog, change the SCSI controller type associated with the “Template VM” / “Master VM” to a type supported by personal vDisk technology. If this occurs with only some desktops in the catalog, it might be due to spikes in storage latency due to a large number of desktops starting at the same time. Try limiting the maximum active power actions setting associated with the host connection.
Error code 12. This could be due to a desktop failing to complete the boot process with PvD enabled. Try restarting the desktop. If the problem persists, watch the desktop startup through the hypervisor console and check if the desktop is crashing. If a desktop crashes during startup, restore the PvD from backup (if you maintain one) or reset the PvD.
Error code 13. This could be caused by PvD failing to mount the PvD disk at the mount specified by the administrator. The PvD disk will fail to mount if the drive letter is already used by other hardware. Select a different letter as the mount point for the personal vDisk.
Error code 14. Personal vDisk installs drivers during the first inventory update after installation. Some antivirus products prevent installation of the driver when attempted outside the context of an installer. Temporarily disable the antivirus real time scan or add exceptions in the antivirus for PvD drivers during the first time inventory creation.
Error code 15. This could occur because the Volume Shadow Copy service is disabled. Enable the Volume Shadow Copy service and retry taking an inventory.
Error code 16. Personal vDisk uses change journal for tracking changes made to master image. During an inventory update, if PvD detects that the change journal is disabled, it attempts to enable it; this error occurs when that attempt fails. Wait for few minutes and retry.
Error code 17. There is not enough free space available on the C drive of the desktop for the image update operation. Expand the system volume or remove unused files to free space in the system volume. The image update should begin again after the next restart.
Error code 18. There is not enough free space available on the personal vDisk drive when performing an image update operation. Expand personal vDisk storage or remove unused files to free space in the personal vDisk storage. The image update should restart after next reboot.
Error code 19. There is not enough free space available on the personal vDisk drive to fully accommodate thick provisioned “UserData.V2.vhd”. Expand the personal vDisk storage or remove unused files to free space in the personal vDisk storage.
Error code 20. The system registry is corrupt, damaged, missing, or unreadable. Reset the personal vDisk or restore it from an earlier backup.
Error code 21. This is a catch-all for all the errors encountered during a personal vDisk reset. Collect the logs and contact Citrix Support.
Error code 22. There is not enough free space available on the Personal vDisk drive when performing a reset operation. Expand the personal vDisk storage or remove unused files to free space in the personal vDisk storage.
|0x20000001||Failed to save the diff package, most likely due to lack of free disk space inside the VHD.|
|0x20000004||Failed to acquire required privileges for updating the PvD.|
|0x20000006||Failed to load hive from the PvD image or from PvD inventory, most likely due to corrupt PvD image or inventory.|
|0x20000007||Failed to load the file system inventory, most likely due to a corrupt PvD image or inventory.|
|0x20000009||Failed to open the file containing file system inventory, most likely due to a corrupt PvD image or inventory.|
|0x2000000B||Failed to save the diff package, most likely due to lack of free disk space inside the VHD.|
|0x20000010||Failed to load the diff package.|
|0x20000011||Missing rule files.|
|0x20000021||Corrupt PvD inventory.|
|0x20000027||The catalog "MojoControl.dat" is corrupt.|
|0x2000002B||Corrupt or missing PvD inventory.|
|0x2000002F||Failed to register user installed MOF on image update, upgrade to 5.6.12 to fix the issue.|
|0x20000032||Check the PvDactivation.log.txt for the last log entry with a Win32 error code.|
|0x20||Failed to mount application container for image update, upgrade to 5.6.12 to fix the issue.|
|0x70||There is not enough space on the disk.|
The personal vDisk was found but a PvD session could not be created.
The administrator selected an incorrect snapshot while creating or updating the PvD catalog (that is, the master image was not shut down using Update Personal vDisk when creating the snapshot).
If Personal vDisk is not enabled, you can view the following events in Windows Event Viewer. Select the Applications node in the left pane; the Source of the events in the right pane is Citrix Personal vDisk. If Personal vDisk is enabled, none of these events are displayed.
|1||Personal vDisk Status: Update Inventory Started.|
|1||Personal vDisk Status: Update Inventory completed. GUID: %s.|
|1||Personal vDisk Status: Image Update Started.|
|1||Personal vDisk Status: Image Update completed.|
|1||Reset in progress.|
|2||Personal vDisk Status: Update Inventory Failed with: %s.|
|2||Personal vDisk Status: Image Update Failed with: %s.|
|2||Personal vDisk Status: Image Update Failed with Internal Error.|
|2||Personal vDisk Status: Update Inventory Failed with: Internal Error.|
|2||Personal vDisk has been disabled because of an improper shutdown.|
|2||Image update failed. Error code %d.|
|2||Personal vDisk encountered an internal error. Status code[%d] Error code[0x%X].|
|2||Personal vDisk reset failed.|
|2||Unable to find disk for storing user personalization settings.|
|2||There is not enough space available on the storage disk to create a Personal vDisk container.|