Repair Application from Software Center using SCCM 1810+

Beginning with SCCM 1810, you can now repair an application directly from software center on an SCCM client. A small but useful new feature! Before 1810, you would have to go through Control Panel (not useful if a user didn’t have admin rights) or by uninstalling and reinstalling the application using 2 distinct software center actions.

Now, you can directly initiate a Repair action in Software Center. The good news, is that’s really simple to do ! The only thing that you need to do is :

Upgrade to SCCM 1810
Add a repair command line to your application
Check the Repair option in your application deployments

If you haven’t upgrade to SCCM 1810 yet, we have a complete post for it. As the time of this writing SCCM 1810 is in slow ring, so you may see it in your console in a couple of days. If you don’t have it yet, follow our post to see how to switch your SCCM server in the Fast Ring.

Add SCCM repair command line

The first thing you need to do to have the SCCM application repair option is to add your repair command line in your application.

In the SCCM Console
Select the desired application, select the deployment type and go to the Properties
In the Program tab, specify the command to repair the application in the new box

You’ll have to find the silent switch for repairing your application as for the installation switches.

If you have an MSI, it will look like this :

https://www.advancedinstaller.com/user-guide/msiexec.html

Add the repair option in the SCCM Deployment

Once the application has a repair command line, we can add the option in the deployment

In the SCCM Console
Create a new deployment for your application
In the General tab, select your software and collection

In the content tab, ensure that your application is distributed, click Next

In the Deployment Settings tab, select Allow end users to attempt to repair this application

In the Scheduling tab, select the desired schedule

In the User Experience tab, select the desired options

In the Alerts tab, select the Alerts options

In the Completion tab, you can see the repair option has been enabled

Test SCCM Repair Application on Client

Let’s see the results on an SCCM client

Launch the Software Center
On our test client, 7zip has already been installed
Click on the application, a new Repair button is available
Once initiated, the repair command line is launched.

You can see the repair results in the AppEnforce log file.

A small but awesome new feature !

[share title=”Share this Post” facebook=”true” twitter=”true” reddit=”true” linkedin=”true”]

Benoit Lecours

Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. Working in the industry since 1999. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.

11 Comments on “Repair Application from Software Center using SCCM 1810+”

Yale.Rebecca

04.15.2020 at 4:02 PM

Don’t make excuses for failure, just find a way for success

sunroof tamiri

09.07.2019 at 8:40 AM

Dolu Hasar tamiri sistemleri ve Sunroof tamiri

mini onarım

09.07.2019 at 8:39 AM

A Yelp study shows that if someone had a good customer service experience

Damo

07.08.2019 at 2:10 AM

Will the app still repair for users who have limited (no) rights to the local ccmcache folder?

So if an .MSI needs to write files to the user profile %AppData%\Roaming\appname will they repair achieve this function?

Jonny M

06.03.2019 at 10:36 AM

Is it possible to remotely run the repair command on behalf of the user? for example – I do not want to ability for users to repair their own applications, however want to give this permission to 1st Line Support who have limited access to SCCM.

Jakub

05.13.2019 at 5:11 AM

I don ‘t seem to be able to create new deployments with powershell to include this feature. Anyone knows how to create/modify an app deployment that includes this parameter?
Start-CMApplicationDeployment or Set-CMApplicationDeployment or New-CMApplicationDeployment don’t seem to have this parameter…

Ben Allsup

04.11.2019 at 3:59 AM

Discovered a bit of a bug with the repair. If you run a batch file script, then the end user (non-admin) has the ability to Ctrl+C out of it and end up with an elevated command prompt. Surely MS could have included the option to run REPAIR as hidden as well as the installation/uninstall?