CM Troubleshooting
- Katelyn Russell
- Daniel Vega
When things go wrong...
Reading Logs
Use CMTrace to more efficiently read your logs.
The CMTrace log viewing tool is now automatically installed along with the Configuration Manager client. 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 associate it with .log files.
CMTrace Tips:
- Lookup up error codes:
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. - 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. - 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.
Remotely reading logs
You can right click on a device, then go to Client Diagnostics and Collect Client Logs
Assuming the client is online, after a few minutes you will be able to view the logs. 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'll then have access to all the CM related logs.
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 more information visit: Log file reference - Configuration Manager | Microsoft Docs
- 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
Need Help?
Submit a ServiceNow request to the Core EPM Team by sending email to epm-requests@its.utexas.edu
Be sure to include your department code and any relevant information such as what step you are on and what issue or help you need.
EPM is available to IT Support Organizations (ITSOs) with any endpoint management questions. If you have a question about a specific endpoint client, please reach out to your local endpoint client support organization.
- ConfigMgr: Every Tuesday, from 6 a.m. – 10 a.m.
- Jamf: Every Tuesday, from 8 a.m. – 12 p.m.
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.