SCCM logging by default do not provide you with detailed information for you to do advanced analysis. To do so, you will need to enable Verbose / Debug or NAL. This logging will give you much more detailed information, and it will help you location the root of the problem.
Server verbose logging:
1 – open means
0 – off means
SCCM and components:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ ENABLED = 1 – (REG_DWORD – General SCCM turn on Logging)
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ xxxxxxx \ Enabled = 1 – (REG_DWORD – The Role SCCM’de If you change the compositions according to him)
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ xxxxxxx \ MaxFileSize = 3000000 – (REG_DWORD – 3 MB large – NAL and Debug Logging for growth with more than it is worth)
Important components to be linked to SQL for SQL logging, open the key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ Sqlenabled = 1 – (REG_DWORD)
Component of SQL and SCCM logs, including:
ciamgr.log – SMS_CI_ASSIGNMENT_MANAGER
Colleval.log – SMS_COLLECTION_EVALUATOR
compsumm.log – SMS_COMPONENT_STATUS_SUMMARIZER
Dataldr.log – SMS_INVENTORY_DATA_LOADER
ddm.log – SMS_DISCOVERY_DATA_MANAGER
Distmgr.log – SMS_DISTRIBUTION_MANAGER
Hman.log – SMS_HIERARCHY_MANAGER
objreplmgr.log – SMS_OBJECT_REPLICATION_MANAGER
offermgr.log – SMS_OFFER_MANAGER
Offersum.log – SMS_OFFER_STATUS_SUMMARIZER
policypv.log – SMS_POLICY_PROVIDER
sinvproc.log – SMS_SOFTWARE_INVENTORY_PROCESSOR
Sitestat.log – SMS_SITE_SYSTEM_STATUS_SUMMARIZER
smsdbmon.log – SMS_DATABASE_NOTIFICATION_MONITOR
statesys.log – SMS_STATE_SYSTEM
Statmgr.log – SMS_STATUS_MANAGER
swmproc.log – SMS_SOFTWARE_METERING_PROCESSOR
wcm.log – SMS_WSUS_CONFIGURATION_MANAGER
wsyncmgr.log – SMS_WSUS_SYNC_MANAGER
SMS Provider
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ SMS \ Providers \ Logging Level = 1 – (REG_DWORD)
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ SMS \ Providers \ SQL Cache Logging Level = 1 – (REG_DWORD)
HKEY_LOCAL_MACHINE \ Software \ Microsoft \ SMS \ Providers \ Log Size MB = 1 – (REG_DWORD)
SCCM logumuz with logging provider are as follows:
Smsprov.log
NAL logging:
Sometimes it may be enough, and NAL logging verbose logging information in the pop-up. Caution: NAL logging Log file too big for him, keeping detailed logs have benefits.
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ NAL \ Logging
– DataType: REG_DWORD – Log To = 3
– DataType: REG_DWORD – Verbosity = 7
NAL logging, set the values:
NAL_LOG_VERBOSITY_LEVEL_1 = Errors
NAL_LOG_VERBOSITY_LEVEL_2 = Warnings
NAL_LOG_VERBOSITY_LEVEL_4 = Information
NAL_LOG_VERBOSITY_LEVEL_7 = Errors, Warnings, Information
SCCM loglarımız with NAL logging are as follows:
compsumm.log – SMS_COMPONENT_STATUS_SUMMARIZER
Distmgr.log – SMS_DISTRIBUTION_MANAGER
inboxmgr.log – SMS_INBOX_MANAGER
ntsvrdis.log – SMS_WINNT_SERVER_DISCOVERY_AGENT
sitecomp.log – SMS_SITE_COMPONENT_MANAGER
Sitestat.log – SMS_SITE_SYSTEM_STATUS_SUMMARIZER
smsexec.log – SMS_EXECUTIVE
IMPORTANT:Registry changes to work:
Stop the SMS_SITE_COMPONENT_MANAGER
Stop the SMS_EXECUTIVE
Start the SMS_EXECUTIVE
Start SMS_SITE_COMPONENT_MANAGER
SCCM Agent (Workstation):
CCM for the verbose logging:
For Administrator Key, “full rights” to provide the necessary – there is no default.
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ CCM \ Logging \ @ GLOBAL
Set of the following values:
LogEnabled = 1
LogLevel = 0
LogMaxSize = 40000000
LogDirectory = c: \ windows \ system32 \ ccm \ logs (If you want to print the logs to a different location)
LogMaxHistory = 1 (Although the size of the logs filled with incense,> here is one: will be holding an old log. Example: Execmgr.log and will execmgr.lo_.
Verbose logging is not enough DebugLogging CCM:
This is necessary to create the reg KEYI:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ CCM \ Logging \ DebugLogging
– DataType: REG_SZ – Enabled = TRUE
WMI:
SCCM agent is based entirely WMI WMI is useful to turn verbose logging:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ WBEM \ CIMOM \ Logging = 0 – (REG_SZ – Disabled)
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ WBEM \ CIMOM \ Logging = 1 – (REG_SZ – Error only)
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ WBEM \ CIMOM \ Logging = 2 – (REG_SZ – Verbose)
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ WBEM \ CIMOM \ Log File Max Size = 4000000 – (REG_DWORD – If you need to WMI 2)
IMPORTANT: To study the changes of registry and WMI:
Restart the Computer
Other important components are: WSUS + SCCM component:
Set HKLM \ SOFTWARE \ Microsoft \ SMS \ Components \ SMS_WSUS_SYNC_MANAGER
– DataType: REG_DWORD – LogLevel = 3
LOG_SUMMARY = 1;
LOG_DETAIL = 2; default
LOG_VERBOSE = 3;
LOG_DEBUG = 4;
