Learn How to Collect SCCM Client Logs Using ConfigMgr Console

9
Collect SCCM Client Logs ConfigMgr

Let’s learn how to collect SCCM client logs using the ConfigMgr Console. This log collection feature got introduced in the Configuration Manager version 2002.

Client logs feature is part of Client Diagnostics features of Configuration Manager. Client diagnostic feature helps SCCM admins to enable and disable verbose logging.

So, you don’t need to have admin access right on client devices to collect ConfigMgr client logs. Also, no registry hacks to enable and disable verbose logs.

Requirements to Collect SCCM Client Logs

  • ConfigMgr Server and Console version should be 2002 or later version.
  • Update the target client to the 2002 version (minimum version 5.00.8968.1008) or later version.
  • Your Configuration Manager administrative user needs the Notify resource permission.
  • The client should be ONLINE.
Collect SCCM Client Logs - Configuration Manager Client Diagnostics
Collect SCCM Client Logs – Configuration Manager Client Diagnostics

How this Works?

  • A client notification message via the fast channel is sent to the selected clients to gather the ConfigMgr Client logs.
  • The logs are returned using software inventory file collection.
  • Get Logs Files from Resource Explorer (more details in the below section).
  • The maximum size limit for the compressed client logs is 100 MB.
Altaro Office 365 Backup
Advertisement Altaro Office 365 Backup

Client Diagnostics – Collect Client Logs

Let’s see how to collect logs from SCCM clients using Console.

  • Right click on the device collection (or a particular device record).
  • Select Client Diagnostics and then click on Collect Client Logs.
Collect SCCM Client Logs - Configuration Manager Client Diagnostics
Collect SCCM Client Logs – Configuration Manager Client Diagnostics
  • Click on the OK button to continue.
There is 1 resource in this collection. Clients that are online will be notified to collect client logs as soon as possible.
There is 1 resource in this collection. Clients that are online will be notified to collect client logs as soon as possible.

Process

  • Client Side – Check the client logs to understand process via Diagnostics.log.
LOG[Collecting log files …]LOG
LOG[PowerShell path: C:\windows\system32\WindowsPowerShell\v1.0\PowerShell.exe]LOG]!> component="DiagnosticsEndpoint" context="" type="1" thread="7736" file="DiagnosticsEndpoint.cpp:363"
FileCollection: Successfully sent report. Destination:mp:MP_SinvCollFileEndpoint, ID: {AF9598A4-B17E-4BF5-928C-15DA70F2B0F8}, Timeout: 10080 minutes MsgMode: Signed, Not Encrypted
  • MP Server – Check the MP server log MP_SinvCollFile.log.
Inv-SinvCollFile Task: Processing message body
Full report from client PROD-WIN20, action description = File Collection
Sinv CollFile: There are 1 CollectedFile nodes and 1 attachments
Sinv CollFile: 1 of 1 CollectedFile records processed
Sinv CollFile Task: Report translation created "F:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\8JQWBXCU.SIC" successfully
Collect SCCM Client Logs - Configuration Manager Client Diagnostics
Collect SCCM Client Logs – Configuration Manager Client Diagnostics
  • Site Server – Check the site server log sinvproc.log.
Processing file: F:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\8JQWBXCU.SIC
Processing Inventory for Machine: PROD-WIN20 ResId: 16777219 [OpCode=8 Sinv=0 FC=1 Resync=0] 
Transactions: Total FC=1
Report for Machine PROD-WIN20 took 0 secs. for 1 recs, FP=0, P=0, F=0, FC=1
Successfully Processed file F:\Program Files\Microsoft Configuration Manager\inboxes\auth\sinv.box\8JQWBXCU.SIC !!!
Cycle Completed. 1 files out of 1 processed. 1 secs for 1 threads.
Scan Completed.

Results

  • Right-Click on Device.
  • Select StartResource Explorer.
Collect SCCM Client Logs - Configuration Manager Client Diagnostics
Resource ExplorerCollect SCCM Client Logs – Configuration Manager Client Diagnostics
  • Click on Diagnostic Files.
  • Right-click Support<>.Zip file.
  • Select Open Support Center to open the log file.
Collect SCCM Client Logs - Configuration Manager Client Diagnostics
Collect SCCM Client Logs – Configuration Manager Client Diagnostics
  • Verify the client details from Configuration Manager Support Center
Collect SCCM Client Logs - Configuration Manager Client Diagnostics
Collect SCCM Client Logs – Configuration Manager Client Diagnostics
  • You can also SAVE the log files to local drive.
SAVE - Collect SCCM Client Logs - Configuration Manager Client Diagnostics
SAVE – Collect SCCM Client Logs – Configuration Manager Client Diagnostics

Resources

9 COMMENTS

  1. I just used it few minutes ago and worked perfectly. I think it’s new feature and very good one. I don’t have access to Workstations and was running behind engineers to collect logs for troubleshooting but now i am the king and my word is law 🙂

  2. HI Anoop. Where is the zip file actually stored? I see a file path of c:\windows\system32\config\systemprofile\AppData\Local\Microsoft\ConfigMgrSupportCenter.Common\Temporary\ and that’s on the client. Does it actually get copied to one of the CM servers? Just trying to figure out if there is any cleanup that needs to be done when using this feature.

    • Hello Scott – I don’t know where it’s stored. I didn’t check that piece. I assume that it is stored in the same inbox where software inventory data is stored. But I could be wrong.

  3. I never got any prompt when trying to collect files. And when opening resource explorer i do not have anything under Diagnostic files.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.