5 Best Ways to Repair SCCM Client Agent

This detailed guide explores various methods to repair SCCM client agent, including using PowerShell script, command line, Right-Click Tools, and Advanced Insights.

I frequently receive emails inquiring about the proper steps to repair the SCCM client. While I usually respond with the repair instructions, I’ve decided to write a blog post on the topic. Now, I can direct users to this article for reference, and it may even become a helpful resource through search engines like Google.

Configuration Manager client is a small software agent installed on devices that communicates with SCCM to perform different actions. These include deploying software updates, enforcing security policies, and gathering inventory information from those devices.

When should you repair the client?

In an ideal scenario, client agents should function as expected. However, in certain environments, issues may arise. For example, clients might stop sending data to management points, the software center could crash upon launch, or agent upgrades might fail. In such cases, it is advisable to repair or reinstall the client on the affected computer.

Note that repairing a client is much faster than reinstalling it. Hence, the methods that I have outlined in this guide are useful.

Repair SCCM Client using Command Line

The recommended way to repair a Configuration Manager client is by using CCMRepair. Sign in to a Windows device and launch the Command Prompt as Administrator. Change the path to C:\Windows\CCM. To begin the SCCM client agent repair, run the command ccmrepair.exe.

Repairing the ConfigMgr client agent typically takes only a few minutes. In this context, “repair” essentially involves reinstalling the client agent. If the status displays “Done,” it indicates that the client agent repair has been successfully completed.

C:\Windows\CCM>ccmrepair.exe
Repairing product {88B420C9-C484-4E20-8D02-C25243A36B80}…
Done.

C:\Windows\CCM>ccmrepair.exe
Repairing product {88B420C9-C484-4E20-8D02-C25243A36B80}…
Done.

Repair ConfigMgr Client using Right Click Tools

Using the Right Click Tools, you can repair the SCCM client using the below mentioned steps.

• Launch the Configuration Manager console.
• Navigate to Assets and Compliance\Overview\Devices. Select a device for which you want to repair the SCCM agent.
• Right-click the device and select Right Click Tools > Client Tools > Repair Client.
• You get a dialog box asking, “Are you sure you want to repair the client?“. Click Yes to proceed with repair.

Repair Configuration Manager Client via Run Script

The Run Script feature in Configuration Manager provides an efficient solution for resolving client agent issues. This method is particularly advantageous as it enables the repair of the Configuration Manager client across multiple remote computers simultaneously.

In the Configuration Manager console, go to Software Library\Overview\Scripts. Right-click Scripts and click Create Script. In the Script Details window, specify a script name such as Repair SCCM Client Agent and select the script language as PowerShell. Enter the below command in the Script Editor window and click Next.

C:\windows\ccm\ccmrepair.exe

C:\windows\ccm\ccmrepair.exe

On the Completion window, click Close.

When you create a new script in Configuration Manager, you must approve the script. Occasionally the approve or deny button may be disabled. Here is a solution to fix approve deny button disabled in SCCM. Right-click the client repair script and select Approve.

Once the client repair script is approved, go to devices. Select a device, right-click and Run Script. As I mentioned earlier, you can also run the client repair script on device collections as well.

Select the repair SCCM client agent script and click Next.

Running this script will repair the Configuration Manager client agent on the device(s). On the client computer, review the ccmsetup.log to monitor the client agent repair process.

Repair SCCM Client using PowerShell Script

The following PowerShell script allows you to remotely repair the SCCM client. It is particularly helpful for repairing the agent on a computer that is situated at a remote location. To use this script, copy it to a notepad and rename it to SCCMAgentRepair.ps1. Open the PowerShell and execute this script.

# Usage: SCCM-RepairClient <TargetName>
function SCCM-RepairClient([String] $strTargetName)
{
$SCCMClient = [wmiclass] "\\$strTargetName\root\ccm:sms_client"
$SCCMClient.RepairClient()
}

# Usage: SCCM-RepairClient <TargetName>
function SCCM-RepairClient([String] $strTargetName)
{
$SCCMClient = [wmiclass] "\\$strTargetName\root\ccm:sms_client"
$SCCMClient.RepairClient()
}

Repair SCCM Client using Advanced Insights

Advanced Insights by Patch My PC offers an easy way to repair client agents on remote computers. To begin, launch Advanced Insights (desktop shortcut or via the browser) and sign in with your credentials. In the dashboard, go to Devices > Managed Devices. Select the Windows device and click on Patch My PC Actions and select Repair Client.

Monitoring the Client Repair Process

You can monitor the SCCM client repair process by reviewing the ccmsetup.log on the client computer. The ccmsetup file is located in the C:\Windows\ccmsetup\Logs folder on the client computer. You can open this log file with CMTrace or other compatible log viewers. In addition, for other client logs, take a look at the SCCM log files.

The line CcmSetup is exiting with return code 0 confirms that SCCM client agent repair is completed successfully. You don’t have to restart your computer after you repair the ConfigMgr client, but I highly recommend doing that before installing a new one.

You might be concerned that repairing the SCCM client agent could delete all the folders in the CCMCache folder. However, upon verification, running the ccmrepair command via the command line retains all the folders in the CCMCache folder, which is reassuring.