Where Them
Logs App
WTLA-01

Configuration Manager (SCCM)

3 log locations · Windows, macOS

Microsoft Corporation · Vendor documentation (opens in a new tab)

Where Configuration Manager (SCCM) keeps its logs

Configuration Manager (SCCM) logs to <ConfigMgr install dir>\Logs\ on Windows. 1 other Windows log location is recorded below.

Configuration Manager (SCCM) logs to /Library/Application Support/Microsoft/CCM/Logs/ on macOS.

Paths are printed exactly as Configuration Manager (SCCM) writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.

Finding your way around Windows and macOS.

WIN

Configuration Manager (SCCM) - Windows

Microsoft Corporation
site server, e.g. SMS_Executive.log, distmgr.log<ConfigMgr install dir>\Logs\
client; AppIntentEval.log and AppEnforce.log for app deployments%WINDIR%\CCM\Logs\

How to turn on debug logging for Configuration Manager (SCCM)

  1. Windows client: in Registry Editor, open HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global.
  2. Windows client: set REG_DWORD LogLevel to 0 for verbose. 1 is the default.
  3. Windows client: optionally raise LogMaxSize (default 250000 bytes) and LogMaxHistory (default 1).
  4. Windows client: for debug logging, set REG_SZ Enabled to True under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\DebugLogging.
  5. Windows client: restart the SMS Agent Host service (CcmExec).
  6. At install time, pass CCMENABLELOGGING, CCMDEBUGLOGGING and CCMLOGLEVEL to ccmsetup instead.
  7. Site server: set LoggingLevel, LogMaxHistory, MaxFileSize or DebugLogging under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\<ComponentName>, then restart SMS Executive.
  8. Console: set switchValue="Verbose" on SmsAdminUISnapIn in Microsoft.ConfigurationManagement.exe.config.

How to collect Configuration Manager (SCCM) logs

  1. In the Configuration Manager console, go to Devices, select the device and choose Client Diagnostics.
  2. Windows client: copy %WINDIR%\CCM\Logs\ and %windir%\ccmsetup\logs\.
  3. Task sequences: find smsts.log in X:\Windows\temp\smstslog\, C:\_SMSTaskSequence\Logs\smstslog\ or C:\Windows\CCM\Logs\, depending on the phase.
  4. macOS client: copy /Library/Application Support/Microsoft/CCM/Logs and the CCMAgent-, CCMNotifications- and CCMPrefPane- logs in ~/Library/Logs.
  5. Co-managed devices: Intune Collect diagnostics also picks up both Windows client log folders.
  6. Open the logs with CMTrace, OneTrace or Support Center.