Overview

Troubleshooting client health, policy processing, and management point communication.

Reading Logs

Support Center - Configuration Manager is another great tool for troubleshooting clients.
Here’s the quickstart guide for that Support Center quickstart - Configuration Manager

The installer is found in the same folder as the client installer.
\\aus-dp.austin.utexas.edu\sccmclient\SupportCenterInstaller.msi

The CMTrace log viewing tool is automatically installed along with the Configuration Manager client and makes it easier to read .log files. It's added to the client installation directory, which by default is %WinDir%\ccm\cmtrace.exe. Simply run the executable, there's no need to "install" it and if desired you can associate it with .log files.

Remotely reading logs

This is helpful when you are physically unable to access the client.

What Is Included

The collected bundle typically contains:

• Client service and policy logs (e.g., PolicyAgent.log, CcmExec.log)

• Software update logs (e.g., UpdatesDeployment.log, WUAHandler.log)

• Content transfer logs (e.g., ContentTransferManager.log, DataTransferService.log)

• Application deployment logs (e.g., AppDiscovery.log, AppEnforce.log)

What Is Not Included

• Site server logs (MP, DP, SUP, etc.)

• Windows Event Logs

• Windows Update logs (outside ConfigMgr context)

Right click on a device in the console, then navigate to Client Diagnostics and click on Collect Client Logs

If the client is online, it may take a few minutes for the logs to be gathered. The logs will not be gathered until the client is online and responds to the request.

Open Resource Explorer to access the collected logs.

Find Diagnostic Files and on the right side you should see what you just collected. Double click on it to open them.

You will then be able to view all the CM related logs.

CMTrace Tips:

• Error Code lookup:
  Click on Tools | Error Lookup (or use CTRL-L). Type in an error code and then click Lookup to display more information about the error.

  Open

  

   

• Merge Logs:
  You can view multiple logs in the same window. This is useful when troubleshooting with multiple logs that have overlapping time frames. Click on File | Open and select multiple logs, then check the box for "Merge selected files" before you click Open.

  Open

  

   

• Highlighting:
  Click on Tools | Highlight. This will highlight lines that contain the specified text. By default, any line that contains "error" or "fail" will already be highlighted in red.

  Open

  

Client Installation

• If the client was pushed out (installed) but you can't find the applet in the control panel or policies do not appear to be assigned, review the installation logs to search for errors that might help determine the issue.

  Installation logs location:

  C:\Windows\CCMSetup\Logs

General Operation

• Review operational logs

  Operational logs location:

  C:\Windows\CCM\Logs

  For log description information see the Log file reference - Configuration Manager

• Review Windows Event logs
  log=Application log, source=Configuration Manager Agent

Removal

Uninstall an existing Configuration Manager client:
 

• Run this command from an elevated prompt:

  c:\Windows\CCMSetup\ccmsetup.exe /uninstall

• Ensure the following registry keys no longer exist following the uninstall. Manually remove them if necessary:

  Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS

• Ensure the following directories no longer exist following the uninstall. Manually remove them if necessary:

  C:\Windows\CCMSetup C:\Windows\CCMcache C:\Windows\CCM

Log File Reference

Client Core / Policy

Content Distribution / Download

Software Updates

Application Deployment

State and Compliance

Inventory / General Client Activity

Log Collection / Diagnostics

Related Information