Follow

What exclusions need to be in place in AppVolumes for ProfileUnity to work and coexist.

Product: ProfileUnity

Product Version: 6.5.8+

Expires on: 365 days from publish date

Updated: February 22, 2017

 

Problem: 

What exclusions need to be in place in App Volumes for ProfileUnity to work and coexist.

Possible Resolution(s)

Before starting for ProfileUnity and AppVolumes to co-exist the container service in the parent vm would need to be off.  This is due to incompatibility in filter drivers co-existing at same time.

To turn off use the following article then proceed.

https://liquidwarelabs.zendesk.com/hc/en-us/articles/210637903-ProfileUnity-6-5-App-V-apps-crash-when-launched

-----------------------------------------------------------------------------------------------------------------------

1. The following file "snapvol.cfg” is located on each writable volume and appstack and needs to be modified

exclude_path=%systemroot%\system32\drivers\etc (This may not be necessary unless writing to this location).

exclude_process_path=\temp

exclude_path=\temp

exclude_process_path=\Windows\Temp\ProfileUnity

exclude_process_path=\Program Files\ProfileUnity

exclude_process_name=client.exe

exclude_process_name=ctxinit.exe

exclude_process_name=rdpinit.exe

exclude_process_name=userinit.exe

exclude_process_name=Elevation\lwl_elevation_service.exe

exclude_process_name=lwl_process_watcher.exe

exclude_process_name=lwl_process_watcher64.exe

exclude_process_name=lwl_userapp_player.exe

exclude_process_name=lwl_userapp_player64.exe

exclude_process_name=lwl_userapp_service.exe

exclude_process_name=lwl_userapp_service64.exe

exclude_process_name=lwl_userapp_trigger.exe

exclude_process_name=lwl_userapp_trigger64.exe

exclude_process_name=msiexec_monitor.exe

exclude_process_name=msiexec_monitor64.exe

exclude_process_name=symlink_creator.exe

exclude_process_name=symlink_creator64.exe

exclude_process_name=vhd.exe

exclude_process_name=LwL.ProfileUnity.Client.exe

exclude_process_name=LwL.ProfileUnity.Client.ServiceManager.exe

exclude_process_name=tntgrd.exe

If the above list doesn't seem to help with a specific issue you're having, you can take these a step further and try this list of exclusions:

exclude_path=\Program Files\ProfileUnity
exclude_path=\Program Files\ProfileUnity\Client.NET
exclude_path=\Program Files\ProfileUnity\Elevation
exclude_path=\Program Files\ProfileUnity\FlexApp
exclude_path=\Program Files\ProfileUnity\Profile
exclude_path=\Program Files\ProfileUnity\Temp
exclude_path=%temp%\ProfileUnity
exclude_path=%temp%\unttmp2
exclude_path=\Program Files\ProfileUnity\FlexApp\lwl_proc_info.sys
exclude_path=\Program Files\ProfileUnity\FlexApp\lwl_proc_info64.sys
exclude_path=\Program Files\ProfileUnity\FlexApp\ContainerService\x64
exclude_path=\Program Files\ProfileUnity\FlexApp\ContainerService\x64\drivers\fs\cbfltfs3.sys
exclude_path=\Program Files\ProfileUnity\FlexApp\ContainerService\x64\drivers\fs\cbfltfs4.sys
exclude_path=\Program Files\ProfileUnity\FlexApp\ContainerService\x86
exclude_path=\Program Files\ProfileUnity\FlexApp\ContainerService\x86\drivers\fs\cbfltfs3.sys
exclude_path=\Program Files\ProfileUnity\FlexApp\ContainerService\x86\drivers\fs\cbfltfs4.sys
exclude_path=%SystemRoot%\System32\spool
exclude_path=%userprofile%
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Liquidware Labs
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Liquidware Labs\ProfileUnity
exclude_registry=\REGISTRY\USER\SOFTWARE\Liquidware Labs
exclude_registry=\REGISTRY\USER\SOFTWARE\Liquidware Labs\LWLStartMenu
exclude_registry=\REGISTRY\USER\SOFTWARE\Liquidware Labs\ProfileUnity
exclude_process_path=\Program Files\ProfileUnity
exclude_process_path=\Program Files\ProfileUnity\Client.NET
exclude_process_path=\Program Files\ProfileUnity\Elevation
exclude_process_path=\Program Files\ProfileUnity\FlexApp
exclude_process_path=\Program Files\ProfileUnity\Profile
exclude_process_path=\Program Files\ProfileUnity\Temp
exclude_process_path=%temp%\ProfileUnity
exclude_process_path=%temp%\unttmp2
exclude_process_name=spoolsv.exe
exclude_process_name=client.exe
exclude_process_name=curl.exe
exclude_process_name=ctxinit.exe
exclude_process_name=dllhost.exe
exclude_process_name=gpscript.exe
exclude_process_name=iconv.exe
exclude_process_name=LwL.ProfileUnity.Client.Logoff.exe
exclude_process_name=lwl_tray.exe
exclude_process_name=msiexec_monitor.exe
exclude_process_name=refresh.exe
exclude_process_name=rsync.exe
exclude_process_name=script.exe
exclude_process_name=sqlite3.exe
exclude_process_name=userinit.exe
exclude_process_name=wkix32.exe
exclude_process_name=wscript.exe
exclude_process_name=vhd.exe
exclude_process_name=flusher.exe

 

2. Apply the registry change (see the attached AppVolumes-Pu Fix.reg)

3. Apply the attached Hot Fix (See the attached Windows6.1-KB2614892-x64.msu):

If the App Volumes Manager indicates the volume is still attached, but you
do not see the attachment in the VM properties:


1. Identify the VM that AVM believes to still have an attachment in place.
2. Log in to the VM as the same user indicated, allowing AVM to actually
attach the volume
3. Log out of the VM, allowing AVM to properly detach the volume(s).
4. Reboot the VM

 

NOTE: If the VM still indicates it has a volume attached and App Volumes Manager
does not indicate the volume is attached:


1. Locate the VM in vSphere
2. Right-click the VM and select "Edit settings..."
3. Remove any HDD entries pointing to your 'cloudvolumes' share mounts
4. Reboot the VM (if it is powered on).

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.