Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

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.

783 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    22 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Brian commented  ·   ·  Flag as inappropriate

        This used to be the option before it was 'fixed.' Why was it removed?

      • Andrew Felber commented  ·   ·  Flag as inappropriate

        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.

      • HoustonAU commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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.

      • Matthias commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Bryan commented  ·   ·  Flag as inappropriate

        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.

      • Dominik commented  ·   ·  Flag as inappropriate

        Would be a very great feature for user self service. Many problems get just fixed by a clean uninstall and reinstall.

      • muecom commented  ·   ·  Flag as inappropriate

        The object model of deployment types already have
        - RepairCommandLine
        - RepairFolder
        But this are not exposed to admin UI and I have not tested if the Client recognize these

      • C. Lessard commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Agree. Having options to repair or modify an existing installed application would be very useful.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        This would be a nice feature but would really depend on the internal companies packaging standards as to whether a feature like this was a benefit. In some instances it may cause more harm than good.

        Nice Idea though!

      • Marco Cibis (MS) commented  ·   ·  Flag as inappropriate

        A functionality for repair of an application (uninstall followed by an install) of a required application out of the software center would be highly appreciated and would take of load from the helpdesk.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Honestly having "repair" or "reinstall" options probably would be a better more useful option. Apps behave differently with just a re-run of the installation. Having something a bit more customizable (cmd like install/uninstall) could be used by anything. Heck fi you wanted you can even have a "reinstall" check box in the dependency area.

        One improvement to the application model would be to use the TS methodology but for Application objects!

        You could have multiple... install, repair, and uninstall sequences with as many steps as you wish in the order that you wish.

        I currently find the Deployment Type +requirements + priority to be limiting and not nearly as straight forward as it could be.

      ← Previous 1

      Feedback and Knowledge Base