A very effective way to expose more detailed information within the SCCM agent logs on both clients or site servers is to modify the below registry keys. As a bonus if you do this on an SCCM site server with the MP role installed then you will also see verbose logging within management point logs. This is due to the MP being integrated with the SCCM agent so this is why verbose agent logging also affects the MP logs. This can be extremely useful for when troubleshooting management point errors. As a real world example I used this technique to monitor when exactly client registrations were occurring on a management point in the mp_registrationmanger.log as by default it will only show errors. Setting the following registry keys will only enable verbose logging for the SCCM agent and not affect other site server logs when performed on an SCCM site server.
Steps to enable verbose logging for the SCCM Agent:a) Modify the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\CCM\LOGGING\@GLOBAL\LogLevel value from 1 to 0, LogMaxSize to 5000000 (decimal, 5MB) and LogMaxHistory to 4.
By default, Administrators have no permission to modify this value. You may need to grant you admin account full control rights first.
b) Create HKLM\Software\Microsoft\CCM\Logging\DebugLogging as a key. Don’t need to create any values under the key.
c)Restart 'SMS Agent Host' service (CCMExec).
Note: Only leave the verbose logging enabled for the duration of your troubleshooting.
Fig 1. Changing registry permissions before editing keys:
The above log settings will only affect SCCM Agent logs contained within the following paths:
- x86 C:\Windows\System32\CCM\Logs\
- x64 C:\Windows\SysWow64\CCM\Logs\