Force Reinstall of Application
Many customers want to be able to force a reinstallation of an application. this deployment should ignore all detection rules and just install the application again.
At the moment this is not possible.
First slice of this feature is now available in 1807 Technical Preview so updating status to started.
@TonyK,@RobO,@CMProdGrp, exactly what we're looking for and we're hopeful that it will support APP-V 5 deployments. With a similar setup, unpublish (for user in our case but should support both user and global publishing), removepkg, addpkg, and publish (support for user or global/computer)...that would allow for break/fix for APP-V 5 packages also.
Tony Klassen commented
Rob Ostry hit the nail on the head in his comment below; that's the exact rationale and implementation I had in mind as well.
So how do we go about using this feature in 1807? Is there a powershell function / cmdlet that can do this as well? Please this feature is much need by our company
This used to be the option before it was 'fixed.' Why was it removed?
Andrew Felber commented
What would happen in a scenario where, in the instance of implementing this as uninstall/install as opposed to repair, the uninstall requires a reboot to before the application can be reinstalled?
Would need to account for that and ensure that the application either starts the install automatically upon return from reboot, in cases of required deployments, or leaves the application in software center, in cases where the application is not deployed as required, so it can be triggered to install again.
If this is implemented I would also like to see the button made available in Software Center, where allowed by the Admin.
The repair setting can either be a custom command (like Install and Uninstall) or a checkbox to say 'This application requires and uninstall/reinstall to repair' and the 'Repair' button in SC does just that, a full uninstall and reinstall.
Rob Ostry commented
We leverage Software Center for break/fix scenarios. If an application is not working, users can go to Software Center, run the uninstall and then install the app again. Required apps gray out the uninstall and that is a problem. It would be great if required app that have both a defined install and uninstall could show a reinstall button instead of a grayed out uninstall. This could simply run the uninstall and then run the install.
Dustin Hedges commented
In some instances the "repair" could, in fact, necessitate an Uninstall/Install which could be configured as a "condition" of the repair. Possibly like stacking Dependency rules in App Model. With this configuration, the "repair" could call the uninstall of one or more applications (and/or their dependencies if necessary), and reinstall (in a specified order if necessary). Or it could be as simple as calling a repair switch or custom script.
When you troubleshoot issues with application which have been deployed by ConfigMgr, you often want to repair that application. For example by setup.exe /repair in case of Office, or using the msiexec repair options. If you could add a repair program, the end user can repair their applications with the Software Center, rather than just uninstall and install it again.
Would be nice to have the option in Software Center to simply Reinstall/Repair an application that is deployed as Required. There is no easy way for users to repair applications, even those that are deployed as Available only as the Uninstall-option which obviously uninstalls the application but then the user needs to wait for the application to re-appear in Software Center and trigger the installation again.
My thought is that this should be an option in the Deployment-wizard so you can choose which applications this should be available on since you might have applications that the user should not be able to touch at all.
I'd really like to see this. One few things I still use the Silverlight-based Application Catalog for is to reinstall an application after removing it for troubleshooting purposes -- the App Catalog always runs a fresh evaluation, so it's faster than opening up the control panel applet to start an application deployment evaluation. Since App Catalog is being removed, it would great to have this option. Ideally, users use be able to initiate a remove/reinstall, since this would reduce the need for desktop support staff to to manually remove and reinstall.
ethel strang commented
reinstall configuration application
Would be a very great feature for user self service. Many problems get just fixed by a clean uninstall and reinstall.
The object model of deployment types already have
But this are not exposed to admin UI and I have not tested if the Client recognize these
Loïc SÉBAS commented
This is not built-in but we are able to do this using native WMI method
C. Lessard commented
Right now, end-users can only install or uninstall applications from the Software Center. It's missing either a "repair", "reinstall" or "verify" option. For me this would be a good addition as most of the time you do not need to uninstall and reinstall the application but simply run a MSI repair (or other relevant actions).
Being new to SCCM, the reason I propose this is I've been using Zenworks Configuration Management for the last 10 years and we've always had the "verify" option available. Also the nice thing about this is that you can either re-run the same install sequence, or specify a different one that is used only if the products is already installed so you can really customize what happens.
Making this an available option either on the Application or Deployment setup would be great, especially for Required Applications. Right now end users having an issue have to contact the helpdesk to remove the application, check the machine back in, and let it reinstall. Just make it an optional check box that is not checked by default.
Agree. Having options to repair or modify an existing installed application would be very useful.
Jonathan Weinberg commented
This would be great to have, plus the option to repair as mentioned.
This would be best implemented as a tick box option in the required deployment. That way if the reinstall isn't useful for a particular application or a particular company it doesn't need to be used. The behavior should be to perform an uninstall if one is defined and then re-install. If no uninstall is defined then simply run the install again.