SCCM 2012 Log Parser: cmtrace.exe

Written by Tao Yang

In my opinion, THE most used utility (other than SCCM console) for any SCCM administrators / engineers would have to be trace32.exe. Back in SMS and SCCM 2007 days, trace32.exe comes with the SCCM Toolkit, which contains a bunch of other tools.

Speaking of my own experience, out of all the tools provided by the toolkit, trace32.exe is the one I used the most.

Now with SCCM 2012, trace32.exe has been replaced by a new tool called cmtrace.exe.

Unlike trace32.exe, cmtrace.exe is actually built-in in SCCM, there is no need to download separate toolkits for it. cmtrace.32 can be found on the SCCM site server, under “<SCCM Install Dir>\tools\” folder. Same as it’s predecessor trace32.exe, cmtrace.exe can be copied / redistributed to other locations / computers alone and use as a log parser.

I have also found that trace32.exe actually does not correct parse SCCM 2012 logs. For example, I’m using both trace32.exe and cmtrace.exe to open execmgr.log from a SCCM 2012 client:

trace32.exe:

image

cmtrace.exe:

image

So, if you are working with SCCM 2012, make sure you use cmtrace.exe rather than the good old trace32.exe. And maybe like me, copy cmtrace32.exe to your local machine and use it from there rather than using it on the server.

5 comments on “SCCM 2012 Log Parser: cmtrace.exe

  1. Pingback: SCCM / ConfigMgr 2012 – How to read log files: – cmtrace.exe Vs trace32.exe « Anoop's

  2. Nice information …

  3. Thanks for the heads up that trace32 doesn’t parse 2012 correctly. We are a few months away from migrating to 2012, but I think I’ll go ahead and update our image with CMTrace. I highly recommend any SCCM shop include this in their image. It saves time versus launching it remotely or having to copy it locally when you need it.

  4. Pingback: SCCM / ConfigMgr 2012 – How to : read log files: – cmtrace.exe Vs trace32.exe « Anoop's

  5. Excellent Info.

Leave a Reply