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.

 

Greg

 

ramseyg@hotmail.com

How To: Enable Debug Logging for ConfigMgr 2012 Admin Console

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

  1. From an administrator command prompt, open the following with Notepad: “C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe.config”
  2. Search for switchValue=”Error”, and change to switchValue=”Verbose” (as shown below), and save changes.
  3. Restart the admin console for debug logging to take effect.

image