What’s New in Personal vDisk 5.6.10
The following issues have been fixed in this release:
-
In some cases, upgrading personal vDisk from 5.6.0 to 5.6.5 or 5.6.7 may fail
because some registry keys on the virtual desktop cannot be deleted. [#0353652] -
Configuration changes made by Internet Information Services (IIS) are not persisted
after restarts. [#0353639] -
In some scenarios, if an application installed by a user on a personal vDisk registers
a Managed Object Format (MOF) file, the image update process fails due to MOF
registration issue 0x2000002F. [0353655] -
An administrator who creates a master image with a personal vDisk catalog cannot
log on to one of the virtual desktops created from the image, and a temporary
profile is created. [0353656] - Users are unable to access mount points and junctions on a virtual desktop. [0353920]
- AppSense Environment Manager 8.3 is not compatible with personal vDisk. [0353936]
-
Downgrading from Version 5.6.5 or later to Version 5.6.0 might damage the personal
vDisk volume and prevent it from attaching. From then on, regardless of the version
of personal vDisk that is used, the error message “Cannot load Personal vDisk –
Status Code 7, Error Code 0x20000006” is displayed.
