Wohoo! – CMTrace included in ConfigMgr 2012 Toolkit SP1

Today is a good day for all MDT 2010/2012 admins. CMTrace.exe is included in ConfigMgr 2012 SP1 Toolkit.

You don't need to get the full ConfigMgr 2012 software to find a new log viewer for the MDT log files (of course good old Trace32.exe still works, but does not exist publicly in x64 version).

Note: Even though CMTrace is available for download publicly at the Microsoft website, it is licensed to ConfigMgr clients only. However, note that with a ConfigMgr evaluation, you also get rights to use the tool (but technically/legally still bound by that evaluation license).

After installing ConfigMgr 2012 SP1 Toolkit, CMTrace.exe is found in the C:\Program Files (x86)\Configmgr 2012 Toolkit SP1\ClientTools folder.

Download link to ConfigMgr 2012 SP1 Toolkit

The ConfigMgr 2012 SP1 Toolkit installation folder.

However

For some odd reason, Microsoft only included the x86 executable (which extracts the x64 version when running on full Windows).

This will of course fail in x64 WinPE, in which cannot start the x86 extractor, and CMTrace.exe fails to start. This is not a problem if you have full ConfigMgr 2012, because ConfigMgr also includes a core x64 version which the ConfigMgr 2012 SP1 Toolkit does not. However, you can get it anyway. By copying the file that is extracted, and you can use Process Explorer to find it.

This is the CMTrace.exe process viewed in Process Explorer. Note the TRA1887.tmp file (may be named different on your system).

Here are the properties of the TRA1887.tmp file

Get a copy of the TRA184B.tmp file, rename it to CMTrace64.exe and add it to your WinPE Image, and voila, it works in x64 WinPE

/ Johan

About the author

Johan Arwidmark

0 0 vote
Article Rating
Subscribe
Notify of
guest
6 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
ramg1967
ramg1967
6 years ago

ConfigMgr 2012 toolkit worked out perfectly since it was an MSI. The only issue is it installed all the tools including CMTrace. I will have to find a way to just install CMTrace and ignore other tools.

Admin
Admin
6 years ago

The ConfigMgr 2012 R2 toolkit setup (the MSI) supports the normal /q switch, or you simply copy the cmtrace file over.

As far as registering the log files, you need to create a script for that.

/ Johan

ramg1967
ramg1967
6 years ago

How can, I deploy CMTrace as an application to all Windows 7 x64 systems? What silent switches to use with the application?

The reason why, I want to deploy CMTrace to all Windows 7 machine is to open the logs (SCCM) with Trace to troubleshoot issue relating to application and other stuff.

Searched the NET for solution – NONE found. Hence made the request here. Appreciate your help.

Admin
Admin
8 years ago

Use the Extra directory to add feature of the MDT boot image (Deployment Share Properties)

/ Johan

Bavo
Bavo
8 years ago

sorry for my ignorance but how exactly do you add CMTrace64.exe to the WinPE image? I copied it to the tools directory in MDT2012 U1 (the x64 one), in the hope that it would be picked up automatically each time boot media are regenerated, but so far no luck.

Grtz
bavo

TimNilimaa
TimNilimaa
8 years ago

You can get the very same (well almost) info that you get with Process Explorer with the native program Resource Monitor in Windows Server 2012 with the command/feature "Analyze Wait Chain". Good to know for the one time when you do not have a connection to Internet or for some other reason 'is stuck' with only whats on the installation dvd (I mean ISO) 🙂


>