First of all you have to be log on with an account that can start all published apps
Open the registry editor of that machine.Select “Run as administrator” = enter the password provided
Locate and document the App-v Staging Computer Cache File Location The value can be found at
32bit Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS: FileName
64bit Systems:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\AppFS: FileName
Note the File Location:
C:\ProgramData\Microsoft\Application Virtualization Client\SoftGrid Client\sftfs.fsd
start “Application Virtualization Client”
Click on “Applications” tab In the right pane do CTRL+A Select all the applications Right Click- select “Load” from the drop down menu
Be sure all application are with a status of: Idle (100%)
Check the size of the cache file.The size should reflect the amount of published applications with the app-v server.
In order to be able to copy the current Staging Cache File to another location, the App-V Service must not be running before the App-V Driver gets initialized Click Start Right in the search box services.mscRight click and run as administrator
Locate the following services. “Application Virtualization Client” and “Application Virtualization Service Agent”
Right click on the first service chose start-up type – disabled.Do the same operation for the second service
“Rebooting the Staging Client VM is necessary, because it is not the App-V Client Service that locks the file. Instead, it is the driver that still is active after the Service has been stopped. After the reboot, the driver can’t be initialized because the Service has been disabled. Therefore the App-V Driver will not lock the fsdfs.fsd file – and then, the App-V Cache File can be copied to a different location.”
After the Staging Client machine has been rebooted, you can copy the Staging Cache File to a central location, like on a file server. Locate the file in:
C:\ProgramData\Microsoft\Application Virtualization Client\SoftGrid Client\ sftfs.fsd
Copy and paste on the network share.
I use the MS DFS for managing sharedcache modifications to migrate from one version to another
NOTE: You never should directly try to overwrite the Cache File that currently is used by the VDI VMs in Read Only Mode! Always use an intermediate copy.
After this operation of creation the shared cache. Clean up the staging client and revert back to the previous state
