Add cmtrace to the Windows\System32 directory during client installation
It's time
Brian Knackstedt
shared this idea
Admindjam
(Product Director, or Executive, Microsoft Endpoint Configuration Manager)
responded
This is fixed in #SCCM 1806
12 comments
-
Chris Kinchen
commented
This would be perfect! We have to do this manually right now.
-
Paul
commented
I believe this was added to the 1805 TP, however it is copied to %windir%\ccm. Would be nice if it was placed in %windir%\system32 as indicated in the uservoice request. %windir%\ccm is not part of the path, whereas system32 is. So unless you know where cmtrace is located it will not load from the command-line or run prompt.
From the 1805TP documentation - The CMTrace log viewing tool is now automatically installed along with the Configuration Manager client. It's added to the client installation directory, which by default is %WinDir%\ccm\cmtrace.exe.
-
Marc-André Chartrand commented
Should be built-in to Windows 10 as the default log reader app IMO, regardless if you have sccm or not, this log reader is a must
-
Itzik Tamar
commented
Yep, I always throw it in there before closing an image, would be nice if it happened automatically.
-
Raphael Jülich
commented
Its something almost everyone does, wouldn't be a big thing for Microsoft to implement this!
-
Mark ter Weele
commented
That would be a lot more easier and useful for troubleshooting
-
Nash Pherson (MVP)
commented
Putting it in windows\system32 is important so that it is already in the PATH statement on all systems. Would love it if this happened on existing systems during client install and on future systems during the "Setup Windows and ConfigMgr" step.
-
Jon Warnken
commented
This is a standard step for me in OSD Task Sequences
-
Anonymous
commented
Excellenct idea - we do this manually this time.
-
CS
commented
Would be very convenient.
-
Reto Gloor
commented
would make life much easier....
-
Tonito Dux
commented
Excellent idea, I always do this manually.