The Microsoft App-V Team Blog

The official blog for Microsoft Application Virtualization

How to quickly repair published App-V packages

How to quickly repair published App-V packages

  • Comments 6
  • Likes

Ryan Cobb | Senior Premier Field Engineer

GearsHi all, Ryan Cobb here with a little insight on repairing App-V packages. A question I’ve received more than a couple times from App-V administrators is “What’s the easiest way to retrieve a shortcut that was accidently deleted by a user?”

The background is usually a situation where the administrator deploys a virtual application to an end user and the app is added and the extensions are published. Everything works fine, but then the user accidently deletes a shortcut from the published application and calls the help desk looking for support.

The help desk then instructs the user to open the App-V Client Console, select the Virtual Apps tab, Select the Package and click the Repair button.  This resets the extensions to their original published locations.  One other task this command performs is that it cleans the user state of this package for this user.  There’s a lot more information on what user state is all about here and Thamim explains it perfectly!  While this process will work, the end result is that when using the repair option from within the console the extensions and the user state are reset to the ‘gold image’ of the package. This means that if the user customized their application then those customizations are reset as well.

So what if you wanted a better way? Enter PowerShell. If the admin simply wants to repair the applications extensions they can execute the following command:

Get-AppVClientPackage *Office* | Repair-AppVClientPackage –Extensions

Note the use of wildcards.  This will simply ‘republish’ the shortcuts and not reset the user’s state.

On the flip side, if all you wanted to repair was the user state, then simply remove the –Extensions switch and add –UserState instead!

Hope this helps!

Ryan Cobb | Senior Premier Field Engineer | Microsoft

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Comments
  • Thanks for sharing

  • And what about an "un-publish" "publish" except script triggers

  • I am not sure what the ask is here? Repairing upon publish?

  • How to quickly repair published App-V packages
    thank you

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment