Product: ProfileUnity
Product Version: 6.83R2 and above
Expires on: 365 days from publish date
Updated: Oct, 2020
Problem:
Using ProfileUnity ProfileDisk might cause some AppV applications to fail to launch
Possible Resolution(s):
- Must be on latest Hotfix (dated 10-6-20 or later) for ProfileUnity (see: ProfileUnity HotFix)
- On your master image (Program Files\ProfileUnity\Flexapp\Container Service\x64 and x86) and within the flexapp.zip in your deployment path, edit VirtFsService.exe.config option "HandleUserData" and set it to True.
- To retain App-V Applications personal settings, Create a Custom portability rule and corresponding ruleset for "C:\ProU_UserData\%username%" and then delete .manifest file from portability directory after each logoff:
Create "User Defined Script Rule"
Execute: After ProfileUnity at Logoff (Post-Logoff)
Type: Executable
File: %systemroot%\system32\cmd.exe /c del /f \\server\Profiles\%username%\Portability\nameofportabilityarchiveforappv.manifest
- If the OS is NOT rolled back (ie..is persistent), then on Logoff you must also delete this folder after ProU runs and also make another config file change to force a reboot after logoff:
Create "User Defined Script Rule"
Execute: After ProfileUnity at Logoff (Post-Logoff)
Type: Executable
File: %systemroot%\system32\cmd.exe /c rmdir /s /q C:\ProU_UserData\%username%
On your master image (Program Files\ProfileUnity\Client.NET) and within the client.net.zip in your deployment path, edit the LwL.ProfileUnity.Client.CmdService.exe.config and set open "LogoffRestarts" to True.