Collect SCCM Client Logs Using ConfigMgr Console

Using the ConfigMgr console, you can collect SCCM client logs. You can remotely collect the SCCM logs from the client machines by sending a client notification action from Configuration Manager console.

The client log collection feature was first introduced in Configuration Manager technical preview 1912. However this popular feature was also added to current branch 2002 release as well.

This feature is really useful for admins who normally require the log files to troubleshoot the ConfigMgr agent related issues. If you haven’t explored this feature yet, this post should help you in understanding about the client log collection feature.

What is Client Log Collection In ConfigMgr ?

Client log collection is a SCCM feature that lets you trigger a client device to upload its client logs. The log files are sent to the site server by sending a client notification action from the Configuration Manager console.

Imagine a situation where you as an IT admin would require SCCM client logs for troubleshooting from a remote device. Prior to log collection feature, you may have done of these to grab the log files.

  • Go the user desk and collect SCCM client logs.
  • Guide the user the location of Configuration Manager log files and ask user to mail it to you.
  • Launch CMTrace and connect to admin$ of the remote computer and monitor the issue.
  • Use a PowerShell script to copy the entire SCCM client log directory (C:\Windows\CCM\Logs).

Prerequisites for Client Log Collection

To collect client logs, listed below are prerequisites.

  • User account must have notify resource permission on the Collection.
  • The Full Administrator and Operations Administrator built-in roles have this permission by default.
  • SCCM current branch 2002 and above.
  • Ensure the client agent version is updated after you install Configuration Manager current branch update.

Client Log Collection Log files

The log file associated with client log collection feature is Diagnostics.log. This log file should confirm if the client logs were sent to site server or not.

How to Collect SCCM Client Logs

So now that know about client log collection feature, let’s see how to collect SCCM client logs.

  • In the Configuration Manager console, click Assets and Compliance workspace.
  • Find the device from which you want to collect the log files.
  • Ensure the device is online (Green tick on computer icon signifies it’s online).
  • Right-click on a device and select Client Diagnostics. Now click Collect Client Logs.
Collect SCCM client logs
Collect SCCM Client Logs Using ConfigMgr Console

As mentioned earlier, the client device must be online. Only then the client will be notified to collect the client logs which are further sent to site server. Click OK on the information box.

Collect SCCM Client Logs Using ConfigMgr Console
Collect SCCM Client Logs Using ConfigMgr Console

When you trigger the client log file collection, a client notification message is sent to the selected clients to collect SCCM client logs. Furthermore the logs are returned using software inventory file collection.

You can review diagnostics.log on the client computer. This log file is located along with other client log files in default location – C:\Windows\CCM\Logs folder.

This log file should tell you if the log files were sent to site server successfully or not. The line FileCollection: Successfully sent report confirms the log files were sent successfully to the site server.

Collecting log files ... DiagnosticsEndpoint 
PowerShell path: C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell.exe DiagnosticsEndpoint
FileCollection: Successfully sent report. Destination:mp:MP_SinvCollFileEndpoint, ID: {FDED4A8B-0D9C-4577-9E69-7B9A485AD5B9}, Timeout: 10080 minutes MsgMode: Signed, Not Encrypted DiagnosticsEndpoint

View the Client Logs

In the above step we successfully gathered the log files from remote client computer. In order to view the log files, you must again use the Configuration Manager console.

To view the collected log files from ConfigMgr console.

  • In the console, go to Devices node, right-click on the device you want to view logs for.
  • Select Start, then select Resource Explorer.
  • From Resource Explorer, click on Diagnostic Files.
  • From the list of options, click View File and open the log files from CcmLogDataCollector\Logs folder.
View client logs
View client logs

On the Resource Explorer window, click Diagnostic Files and in the right pane you will see some fields.

  • Collection Date
  • File Name
  • File Path
  • Client Logs File Size (Bytes)
  • Last Date Modified

When you right click the collected log file info, you get set of options.

  • Open Support Center
  • Copy
  • View file
  • Save
  • Export
  • Refresh
  • Properties
View client logs
View client logs

When you click Open Support Center, the Configuration Manager Support Center viewer opens. It loads all the log files along with full path and name. To view a log file, simply double-click any file and you can view the log file in Log Viewer tool.

View the log files in Support Center
View the log files in Support Center

The next two options include Copy and View File. The Copy option copies the row information from Resource Explorer. While the View file opens the folder where the zip file is located with File Explorer.

View Extracted Client Logs
View Extracted Client Logs

Finally the last two options are Save and Export. Save option opens a Save File dialog for the selected file.

Save Client Logs
Save Client Logs

Clicking Export saves the Resource Explorer columns shown in Diagnostic Files.

Export Client Logs
Export Client Logs

Need Assistance?

Send us a message or post your question in forums.

9 thoughts on “Collect SCCM Client Logs Using ConfigMgr Console”

  1. Hi, is there an option to collect an additional Custom Logfile with this function? Or I have to use the origin Software Inventory Collection feature. Thanks.


  2. I’m receiving a similar error any solution? Any assistance is much appreciated.

    PowerShell path: C:\WINDOWS\system32\WindowsPowerShell\v1.0\PowerShell.exe
    GetAllCcmLogs: Non-zero exit code. 5.
    GetAllCcmLogs: Failed. 0x80004005.

    • Also, I have confirm the following:
      Client Version: 5.00.9040.1044
      Client online and shows as active in console
      Client Check result Passed

  3. Great Article! Thank you. When I open an individual log file, there is a Live Update button but the flyout message that not all files support this feature. Would you know which Files support the Live Update feature?


  4. Hello, Prajwal!

    I tried to get the logs of my client and this error was showed for me.

    ” GetAllCcmLogs: Failed. 0x80004005. DiagnosticsEndpoint 16/10/2020 16:16:17 1860 (0x0744) ”

    Is There any recommendation?

    Thanks in advance.


Leave a Comment