Important Info

Update 2018/08/03 Since the release of SCCM 1806, this ĥow-to post is done by default. It’s the most requested feature of SCCM! So if you are not using the current version of SCCM, you can use this technique to push the CMTrace tool to your devices

What are you doing when you want to troubleshoot SCCM client locally on a computer? Connect your USB card with the cmtrace.exe on it? Copy the executable file from a network directory? Do you want to be smarter? Create an application with a file detection method that will copy the executable file automatically on any SCCM clients.

Download the file from Configuration Manager Toolkit.

Step 1: Create a script to copy the executable file into the Windows directory

Use this command ‘Xcopy /y cmtrace.exe %windir%’ in a cmd file. Enter the cmd file into the application program.

sccm cmtrace

Step 2: Add a detection method in the application properties

Click on ‘Detection Method’ tab and ‘Add Clause’ to your application.

sccm cmtrace

The idea is to detect if the file is already copied. %Windir% will go automatically in the windows folder depending on the operating version.

sccm cmtrace

Step 3: Deploy the application to all desktop and server clients

sccm cmtrace

Technical supports, administrators and users will benefit from it. You make sure that all clients from anywhere will be able to use CMTrace and see SCCM logs without effort and Notepad.

+5G up to 10G achievement 🙂

sccm cmtrace

Comments (5)


07.01.2015 AT 09:26 AM
Hey, How do to cmtrace became the default program for viewing logs?

Nicolas Pilon

07.01.2015 AT 02:34 PM
The first time you open the tool, you will receive a popup asking for default. Select Yes and it will be the default program for viewing logs.


10.03.2016 AT 12:37 AM
why don't u just add a command in a single TS step instead of going through all the hoops of an app?

Nicolas Pilon

10.06.2016 AT 02:51 PM
You can also do it with a single TS step as well. At that time, there was no OSD in our infrastructure. Thanks