← CMTrace Open

Known Log Sources: Stop Hunting for File Paths

If you’ve ever Googled “where is the Intune log file” more than once, this feature is for you. CMTrace Open ships with 24 preset log sources across Windows and macOS. Each one knows the exact file path. You click it, the log opens. No typing paths, no digging through folders.

How to Open a Known Source

Go to File > Known Log Sources. You’ll see a menu grouped by family and category.

[Screenshot: File > Known Log Sources menu expanded showing the full hierarchy]

Click any source and CMTrace Open opens it. If the source is a folder, all the files inside show up in the sidebar and open as tabs. If it’s a single file, it opens directly.

Windows Sources

Windows Intune

Intune IME (5 sources)

SourcePathWhat It Contains
Intune IME Logs FolderC:\ProgramData\Microsoft\IntuneManagementExtension\LogsAll IME logs as a folder. App installs, scripts, health checks.
IntuneManagementExtension.logSame folder, single filePrimary IME log. App lifecycle, policy evaluation, sync events.
AppWorkload.logSame folder, single fileWin32/WinGet download, staging, install details.
AgentExecutor.logSame folder, single filePowerShell script execution with exit codes.
HealthScripts.logSame folder, single fileProactive Remediation detection and remediation results.

[Screenshot: Known Sources > Windows Intune > Intune IME submenu]

MDM and Enrollment (1 source)

SourcePathWhat It Contains
DMClient Local LogsC:\Windows\System32\config\systemprofile\AppData\Local\mdmMDM sync, enrollment, and policy delivery logs.

Windows Setup

Panther (2 sources)

SourcePathWhat It Contains
setupact.logC:\Windows\Panther\setupact.logWindows Setup and Autopilot actions. Everything that happened during OOBE, upgrade, or provisioning.
setuperr.logC:\Windows\Panther\setuperr.logErrors only from Windows Setup. Same events as setupact.log but filtered to just failures.

Windows Servicing

CBS and DISM (2 sources)

SourcePathWhat It Contains
CBS.logC:\Windows\Logs\CBS\CBS.logComponent-Based Servicing. Update installs, component adds/removes, servicing stack operations.
DISM.logC:\Windows\Logs\DISM\dism.logDISM operations. Image servicing, driver injection, feature management.

Windows Update (1 source)

SourcePathWhat It Contains
ReportingEvents.logC:\Windows\SoftwareDistribution\ReportingEvents.logWindows Update transaction history. Every update attempt with HRESULT and status.

Software Deployment

Deployment Logs (2 sources)

SourcePathWhat It Contains
Deployment Logs FolderC:\Windows\Logs\SoftwareAll deployment logs. PSADT, SCCM, and custom installer output.
ccmcacheC:\Windows\ccmcacheConfigMgr package staging folder.

PSADT (1 source)

SourcePathWhat It Contains
PSADT LogsC:\Windows\Logs\SoftwarePowerShell App Deployment Toolkit logs.

MSI Logs (1 source)

SourcePathWhat It Contains
MSI LogsC:\Windows\Temp\MSI*.LOGMSI verbose install logs. These are the logs you need when an MSI fails with exit code 1603.

PatchMyPC (2 sources)

SourcePathWhat It Contains
PatchMyPC Logs FolderC:\ProgramData\PatchMyPC\LogsPatchMyPC client logs.
PatchMyPC Install LogsC:\ProgramData\PatchMyPCInstallLogsPatchMyPC MSI and Burn installer logs.

[Screenshot: folder opened via Known Sources, sidebar showing all files in the folder]

macOS Sources

CMTrace Open runs on macOS too, and the Known Log Sources menu adjusts based on your platform.

[Screenshot: macOS Known Log Sources menu if available]

macOS Intune

Intune Logs (3 sources)

SourcePathWhat It Contains
Intune System Logs/Library/Logs/Microsoft/Intune/MDM daemon logs. Enrollment, policy sync, compliance.
Intune User Logs~/Library/Logs/Microsoft/Intune/User-context Intune agent logs.
Intune Script Logs/Library/Logs/Microsoft/Intune/Scripts/Shell script execution output.

Company Portal (1 source)

SourcePathWhat It Contains
Company Portal~/Library/Containers/.../CompanyPortal/Enrollment, registration, and app install logs.

macOS System

System Logs (4 sources)

SourcePathWhat It Contains
install.log/var/log/install.logPKG installs from Intune and Software Update.
system.log/var/log/system.logSystem events. MDM profile installs, daemon crashes.
wifi.log/var/log/wifi.logWi-Fi diagnostics.
appfirewall.log/var/log/appfirewall.logApp firewall events.

macOS Defender

Defender Logs (1 source)

SourcePathWhat It Contains
Defender Logs/Library/Logs/Microsoft/mdatp/Microsoft Defender installation and error logs.

The Point

Every one of these paths is something you’d otherwise have to remember, Google, or dig through a docs article to find. Now it’s one click.

Open the source, find the problem.

What’s Next

The last post in the Getting Started series covers Real-Time Tailing. Watch logs as they happen, filter on the fly, and catch problems the moment they occur.