When things go wrong...
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.
You can right click on a device, then go to Client Notification 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.
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.
C:\Windows\CCMSetup\Logs |
Review operational logs
C:\Windows\CCM\Logs |
For more information visit: Log file reference - Configuration Manager | Microsoft Docs
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 |
Submit a ServiceNow request to the Core EPM Team by sending email to epm-requests@its.utexas.edu |
Caution: The Excerpt Include sometimes disappears when editing this template. If it does, copy it from another template or page and paste it here as the last thing you do before saving this template.