Recently I had the need to do a quick and dirty fix of a couple of virtual applications that had been deployed to users in an environment that uses App-V with SCCM integration. Applications are advertised to users based upon AD Security Group membership and are configured to download and execute, rather than stream from a DP.
Without going into the reasons behind why this can happen (that’s another post) – I’ll demonstrate how to quickly resolve the error and get the user back up and running. Before proceeding make sure you have got SCCM Client Center 🙂
A error of this kind would be seen by the user when attempting to launch the broken application, e.g. ;
- Find the package ID of the affected virtual application
- Connect to the users SCCM cache (%windir%system32CCMcache) and see if the source files for the affected application are still there (use the package ID to find the folder)
- If the cached package is still there, load SCCM client center, navigate to Agent Actions > Cache and delete the package from here (this will ensure it is not orphaned)
- From within Client Center > Client Actions run a Download & Apply User (or machine) policy
- On the affected machine, restart the SMS Agent Host Service (or reboot)
- From within Client Center > Advertisements, re-run the advertisement for the failed virtual application
You should now see the application begin to download into the SCCM cache, and once complete the package should register itself with the App-V client and once again be functional.
If this fails your App-V cache may be corrupt. To resolve this you can use SFTMIME which is a tool contained within the App-V client installation directory. The following command can be used to clear all applications from within the cache;
- sftmime.exe remove obj:app /global /complete
Please note, this command will remove all applications from the App-V client, and the user running the command must have administrative permissions.
A full reference for SFTMIME can be found here;