Product Version: 6.8.0 and earlier.
Expires on: 365 days from publish date
Updated: May, 3 2019
With the previous versions of ProfileUnity the only path "ProfileDisk" was mounted was "C:\users\ProfileDisk\username" This path made it occasionally incompatible with various 3rd party applications which were coded to see c:\users\user_name path in the local profile.
Sometimes this could case also multiple user profiles to be created inside profile disk. This is not exclusive problem to ProfileUnity as windows default profile issues can cause same effect but if its happening because of "ProfileDisk" path this KB will address this problem.
- The user ProfileDisk path format "c:\Users\Profiledisk\user_name" is causing issues
- Multiple profiles created in profiledisk. Example:
1. Upgrade to ProfileUnity 6.8.1 or later!
Test and most likely the problem will go away. In case it does not follow these steps:
- Create GPO registry key:
- Key: HKLM\SOFTWARE\Liquidware Labs\ProfileUnity
- Value name: Pdusecontainerservice
- Value type: REG_DWORD
- Value data: 1
- Base: Hexadecimal
- Upgrade ProfileUnity tools to 6.8.1 or later
- Recompose your pool.
Note: Update also your userinit.exe on the network share where you have extracted client tools.
Example of GPO registry key that needs to be created:
After refreshing the pool and restarting the VM's profiledisk will be mounted to this path:
For internal compatibility reasons this path will remain available :
this is expected Example:
ProfileDisk is mounting in this directory:
Note: If this is happening after making above changes and upgrading, it is possible to use the new ProfileUnity client without the registry key entry.