The concept of a shared, or read-only cache was introduced in version 4.6 of the Microsoft Application Virtualization client. When using App-V in a Shared Cache environment, it is recommended to use a UNC path to a symbolic link (see http://technet.microsoft.com/en-us/library/ee956915.aspx for more information).
That way, when you change or adjust the shared/read-only cache, you do not have to change the FileName registry value in all of the client’s registries or the master VDI image. There is a possibility that random startup failures may exist for some App-V clients on VDI virtual machines during a App-V FSD (file system device) upgrade or modification (e.g. when applications are being provisioned and added to the read-only cache). This is caused by the App-V client attempting to start during the window where the symbolic link is being updated (a process that involves removal and re-adding the link to initiate the new location). During this window the App-V client engine find that the FSD does not exist and the client will fail to start. You will see the following error in the Windows System Event Log.
Could not start the Application Virtualization Client service on Local Computer.
Error 1068: The dependency service or group failed to start.
In addition, additional dependency errors calling out “sftfs” specifically will also be referenced.
Also note that this is only a problem during the App-V client startup. Restarting the AppV client a few minutes after initial failure will resolve the issue. If the issue persists, there is likely a problem with accessing the shared cache access.
App-V, shared cache, read-only cache
Microsoft Application Virtualization 4.6 for Terminal Services, Microsoft Application Virtualization 4.6 for Terminal Services Service Pack 1, Microsoft Application Virtualization 4.6 for Windows Desktops, Microsoft Application Virtualization 4.6 for Windows Desktops Service Pack 1