For System Center Configuration Manager (SCCM) admins, troubleshooting Operating System Deployments (OSD) can sometimes be a painful process. Traditionally, the process to troubleshoot OSD logs would be to copy the SMSTS log file to an external drive and then review it on another system that has CMTrace installed.
Using the helpful CMTrace.exe utility to scour through SCCM logs is not a new process, but I’ve encountered many SCCM administrators that are not aware that the CMTrace is available to use during OSD.
Before beginning, first ensure that the boot image has the checkbox filled in to Enable command support. Without this enabled, none of the following troubleshooting steps will be possible.[image_with_animation image_url=”24332″ animation=”None” hover_animation=”none” alignment=”center” border_radius=”none” box_shadow=”none” image_loading=”lazy-load” max_width=”100%” max_width_mobile=”default”]With that enabled, we can start using CMTrace.
First, open a Command Prompt by pressing F8. I prefer to navigate to the location of the SMSTSLogs:
- cd x:WindowstempSMSTSLog
[image_with_animation image_url=”24335″ animation=”None” hover_animation=”none” alignment=”center” border_radius=”none” box_shadow=”none” image_loading=”lazy-load” max_width=”100%” max_width_mobile=”default”]Now, you can simply open CMTrace by typing it out and pressing Enter.[image_with_animation image_url=”24338″ animation=”None” hover_animation=”none” alignment=”center” border_radius=”none” box_shadow=”none” image_loading=”lazy-load” max_width=”100%” max_width_mobile=”default”]Since we started out in the SMSTSLog folder, we can quickly open the SMSTS.log file and start analyzing it for troubleshooting.[image_with_animation image_url=”24340″ animation=”None” hover_animation=”none” alignment=”center” border_radius=”none” box_shadow=”none” image_loading=”lazy-load” max_width=”100%” max_width_mobile=”default”]Good luck in troubleshooting!
Lucas | PEI
