System Center Universe Next Week!

I just wanted to give a BIG THANKS to Catapult Systems for organizing System Center Universe! I recognize there’s a lot of time and effort that goes into the planning of this kind of event.  I’m thankful that I get to attend in person – so if you’re there, let’s be sure to meet up.

It’s also great how Catapult has reached out to the user groups around the world – take a look at the list of user groups on this page:  http://www.systemcenteruniverse.com/UserGroupViewings. The simulcast is free, so find your nearest user group and register. Also, if you haven’t yet joined a user group, please do! You will be amazed at the amount of knowledge transfer, personal friendships and professional networking that occurs through user groups.

And if you’re reading this blog, you probably already know about myITforum, but just in case you haven’t, link over there now and start drinking from the fire hose.

One final note, be sure to keep an eye on www.ctsmug.org next week – you may find a link for watching additional deep dives into ConfigMgr 2012 from our user group meetings on Jan 18th and 20th.

Greg

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