Search

Enable Verbose and Debug Logging - SCCM/MECM

In this post, we will how to enable the verbose and debug logging for components that helps you in detailed logs analysis for SCCM.


CCM Logs

ConfigurationMgr Client, Management Point, and roles that rely on ccmexec services.


Verbose Logging:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global

LogLevel = 0 (Default Value = 1)

Debug Logging:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\DebugLogging (Does not exist by default)


CCM Log Size can be increased to 5MB by changing the LogMaxSize registry value.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\Logging\@Global

LogMaxSize = 5242880 (Default Value = 250000)


REQUIREMENT: Restart of CcmExec service is required. On Site System Roles, restart of IIS Services as well as CcmExec is required.



SQL Tracing (Site server Logs)

Verbose Logging:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing

SqlEnabled = 1 (Default Value = 0)

REQUIREMENT: Service/Component restart is NOT required.


CloudMgr.log (SMS_Cloud_Services_manager)

Verbose Logging:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SMS_CLOUD_SERVICES_MANAGER

LoggingLevel = 0 (Default Value = 1)

DDM.log (Discovery_Data_Manager)

Verbose Logging:-

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISCOVERY_DATA_MANAGER

Verbose logging = 1 (Default Value = 0)


REQUIREMENT: Restart of SMS_Executive service or Component is required.



PkgXferMgr.log (SMS_PACKAGE_TRANSFER_MANAGER)

Verbose Logging: Provides more information in the log about the content copy process, file hashes, and job scheduling.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SMS_PACKAGE_TRANSFER_MANAGER

LoggingLevel = 0 (Default Value = 1)


Debug Logging: Provides more information about the content copy process.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SMS_PACKAGE_TRANSFER_MANAGER

DebugLogging = 1 (Default Value = 0)


REQUIREMENT: Service/Component restart is NOT required.


Logging: Provides information about the content copy process for Cloud DP.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_CLOUD_SERVICES_MANAGER

Logging Level = 2 (Default Value = 1)


RcmCtrl.log (SMS_REPLICATION_CONFIGURATION_MONITOR)

Verbose Logging:-


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_REPLICATION_CONFIGURATION_MONITOR

Verbose Logging = 2 (Default Value = 0)


Debug Logging: This is used for advanced DRS Troubleshooting to track DRS messages. note that this enables advanced output in the Database within vLogs.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_REPLICATION_CONFIGURATION_MONITOR

DRS Logging Level = 2 (Default Value = 1)


REQUIREMENT: Service/Component restart is NOT required.



SCClient_<User>.log (Software Center)


Verbose Logging: Verbose Logging for Software Center can be enabled by modifying the .config file for the Software Center executable, which is SCClient.exe.config. This can generate excessive amount of logging in the SCClient.log, and the logging change should be reverted after you no longer need it.


Edit <ClientInstallDirectory>\ClientUX\SCClient.exe.config via notepad, and locate and modify the following section;


From:

<source name="SCClient" switchValue="Information">


To:

<source name="SCClient" switchValue="Verbose">



REQUIREMENT: You need to exit and relaunch Software Center for the changes to take effect.



SmsAdminUI.log (Admin Console)

Verbose Logging: Verbose Logging for the console can be enabled by modifying the .config file for the console executable, which is Microsoft.ConfigurationManagement.exe.config. This generates excessive amount of logging in the SmsAdminUI.log, and the logging change should be reverted after you no longer need it.


Edit <ConsoleInstallDirectory>\AdminConsole\bin\Microsoft.ConfigurationManagement.exe.config via notepad, and locate and modify the following section;


From:

<source name="SmsAdminUISnapIn" switchValue="Error" >


To:

<source name="SmsAdminUISnapIn" switchValue="Verbose" >


REQUIREMENT: You need to exit and relaunch the console for the changes to take effect.



StateSys.log (SMS_STATE_SYSTEM)

Verbose Logging HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_STATE_SYSTEM

Verbose logging = 1 (Default Value = 0)



swmproc.log (SMS_SOFTWARE_METERING_PROCESSOR)

Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_SOFTWARE_METERING_PROCESSOR

Verbose logging = 1 (Default Value = 0)


REQUIREMENT: Restart of SMS_Executive service or Component is required.


WSyncMgr.log (SMS_WSUS_SYNC_MANAGER)

Debug Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SMS_WSUS_SYNC_MANAGER

LogLevel = 4 (Does NOT exist by default)


Debug/Verbose logging is controlled by same key. SUMMARY = 1; DETAIL = 2; VERBOSE = 3; DEBUG = 4; Default LogLevel is DETAIL.


REQUIREMENT: Restart of SMS_Executive service or Component is required.



EPCtrlMgr.log (SMS_ENDPOINT_PROTECTION_CONTROL_MANAGER)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_ENDPOINT_PROTECTION_CONTROL_MANAGER

Verbose logging = 1 (Default Value = 0)


EPMgr.log (SMS_ENDPOINT_PROTECTION_MANAGER)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_ENDPOINT_PROTECTION_MANAGER

Verbose logging = 1 (Default Value = 0)


dmpdownloader.log (SMS_DMPDOWNLOADER)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DMPDOWNLOADER

Verbose Logging = 0 (Does NOT exist by default)



dmpuploader.log (SMS_DMPUPLOADER)

Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DMPUPLOADER

Verbose Logging = 0 (Does NOT exist by default)


WSFBSyncWorker.log (SMS_CLOUDCONNECTION)

Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SMS_CLOUDCONNECTION

LoggingLevel = 0 (Default Value = 1)


SMS_MESSAGE_PROCESSING_ENGINE.log (SMS_MESSAGE_PROCESSING_ENGINE)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_MESSAGE_PROCESSING_ENGINE

VerboseLogging = 1 (Default Value = 0)



SMS_CLOUD_PROXYCONNECTOR.log (SMS_CLOUD_PROXYCONNECTOR)

Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMS_CLOUD_PROXYCONNECTOR

VerboseLogging = 1 (Default Value = 0)


SMS_AZUREAD_DISCOVERY_AGENT.log (SMS_AZUREAD_DISCOVERY_AGENT)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_AZUREAD_DISCOVERY_AGENT

VerboseLogging = 1 (Default Value = 0)



ADForestDisc.log (SMS_AD_FOREST_DISCOVERY_MANAGER)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_AD_FOREST_DISCOVERY_MANAGER

Verbose Logs = 1 (Default Value = 0)


Adsgdis.log (SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT

Verbose Logs = 1 (Default Value = 0)

Adsysdis.log (SMS_AD_SYSTEM_DISCOVERY_AGENT)


Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_AD_SYSTEM_DISCOVERY_AGENT

Verbose Logs = 1 (Default Value = 0)



Adusrdis.log (SMS_AD_USER_DISCOVERY_AGENT)

Verbose Logging:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\COMPONENTS\SMS_AD_USER_DISCOVERY_AGENT

Verbose Logs = 1 (Default Value = 0)



22 views0 comments

Recent Posts

See All