How To: Enable Debug Logging for the ConfigMgr 2012 Client Agent

Sometimes you need to see a little more detail in the log files. Here’s a quick post for how to enable debug logging on the ConfigMgr 2012 Client:

  1. Launch Regedit.exe as an administrator.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@GLOBAL and modify the following as desired:
    1. LogLevel = 1 (default)  – Set this value to 0 (zero) to enable Debug Logging
    2. LogMaxHistory = 1 (default) – This is the maximum number of rollover log files to keep.  Increase this number to keep additional rollover logs.
    3. LogMaxSize = 250000 (decimal, which is 245 kb) – increase this number to increase the max log size for each log.
  3. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging], and Create a new KEY of the name “DebugLogging”
  4. Cycle the SMS Agent Host service (ccmexec.)

(*Note: In ConfigMgr 2012, we have an x86 and an x64 client, so no need to go through the Wow6432Node registry tree.)

Debug logging is great, but it does add some overhead, so be sure to remove the debug logging settings as soon as possible.



About Greg Ramsey
Greg Ramsey is a Distinguished Engineer for Dell Digital - Services. He has a B.S. in Computer Sciences and Engineering from The Ohio State University and has co-authored many books over the years. Greg is also a board member of the Northwest System Center User Group and the Midwest Management Summit. ​Greg has been a Microsoft Endpoint Manager (ConfigMgr, Intune) MVP for over 14 years.

One Response to How To: Enable Debug Logging for the ConfigMgr 2012 Client Agent

  1. Pingback: How To: Enable Debug Logging for an OS Deployment Task Sequence « Greg's Systems Management Blog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: