In this post I will show you how to enable Debug and Verbose logging for SCCM client. Benefit of enabling these logging is to capture additional details for troubleshooting as default logging didn’t contain in-depth steps which are executing in the background while running any Configuration Manager related process.

Before enabling Debug and verbose Logging, let’s understand what it is.

What is Debug Logging ?

When we enable Debug Logging through registry key settings, log files will register low-level information which helps in troubleshooting the issues. Advance Debugging comes very handy when we wanted to deep dive into the issue as default logging in log files does not contain detailed information.

How to enable Debug Logging ?

To enable Debug logging for SCCM client log files, open registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\

  1. Create New key with the name DebugLogging
  2. Under DebugLogging key, create New > String Value with:

Name: Enabled
Value: True

Enable Debug Logging

It is not recommended to enable this in production. It should only be used to troubleshoot the issue. Once done, the advance debugging should be disabled by changing the value to False or by deleting Key DebugLogging.

What is Verbose Logging ?

To get the additional details from configuration manager to write into log files, verbose logging is required.

Default value of verbose logging is 1. The registry key with the name LogLevel can be found under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global

LogLevel has following acceptable values:

  • 0 : Verbose
  • 1: Default
  • 2: Warnings and erros
  • 3: Errors only
Enable Verbose Logging

As we wanted to apply verbose logging, change the value of LogLevel from 1 (Default) to 0 (Verbose)

You need to start SMS Agent Host service for these changes to apply.

Once done, you will see additional details getting captured in ccm logs located under c:\windows\ccm\logs.

Enable Debug and Verbose Logging using Configuration Manager

We can enable Debug and Verbose Logging using Configuration Manager console. Navigate to Assets and Compliance, navigate to Collections or devices.

Right click any device (or collection), select Client Diagnostics > Enable Verbose Logging.

Client Diagnostics Enable Verbose Logging

Collect Configuration Manager logs

Starting onwards configuration manager version 2107, we can enable “collect client log file settings” through hardware inventory.

Open Configuration Manager Console and navigate to \Administration\Overview\Client Settings, open existing Client Settings or create new one.

Under Hardware Inventory, click on Set Classes.

Under Hardware Inventory Classes, We have to enable the Class Client_Diagnostics, select following under it:

  • Debug Logging Enabled
  • Logging Enabled
  • Log Level
  • History File Count
  • Max Log File Size

Click on Ok twice.

That’s it. In SCCM database we will have additional table which contains the information of workstation about log file status, whether logging is enabled, what is the log file level, max log file size etc.

Location of SCCM log files

About log files – Configuration Manager | Microsoft Docs