Client

Try out Client diagnostic at different level feature released in Microsoft Endpoint Configuration Manager Version 2002

Author Nawaz and Mamata

 

Hi Everyone,

Starting in version 1910, there are new device actions for Client Diagnostics in the Configuration Manager console. The following actions have been added:

Enable verbose logging: Change the global log level for the CCM component to verbose, and enable debug logging.

Disable verbose logging: Change the global log level to default, and disable debug logging.

Collect Client Logs (starting in 2002): A client notification message is sent to the selected clients to gather the CCM logs. The logs are returned using software inventory file collection.

  • The size limit for the compressed client logs is 100 MB.
  • Use Resource Explorer to manage and view these files.
In this blog, we will try to check out how things work in the background
  • Machine Named:- W10PEER-0001
  • SCCM server name:- CM01

Log Files to be verified:

  • diagnostics.log on Client Machines  C:\windows\CCM
  • MP_SinvCollFile.log on Siteserver SMS_CCM\Logs Folder
  • sinvproc.log on site server Installation logs folder
Any pre-requisites, Yes

Your Configuration Manager administrative user needs the Notify resource permission.

The following built-in roles have this permission by default:

  • Full Administrator
  • Infrastructure Administrator
Add this permission to any custom roles that need to use client notification actions.

The whole process is listed in the video, the reason because things happening so quickly it was difficult for me to capture the snaps of it, when logfiles were zipped and uploaded.

  1. Command has been sent to collect Logfile, confirmation has been asked job to be run
  2. Diagnostic.log generates the command
  3. log files are zipped at location C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\ConfigMgrSupportCenter.Common\Temporary\Guid.zip
  4. MP_SinvCollFile.log: Management point receives and validates
  5. Job is successfully processed and changes are been observed in sinvproc.log

Where are those log files and how can we use it to validate it. Resource Explorer plays a role here. Further steps again in youtube link, its time to watch another video,

    1. From the Devices node, right-click on the device you want to view logs for.
    2. Select Start, then Resource Explorer.
    3. From Resource Explorer, click on Diagnostic Files.
    4. In the Diagnostic Files list, you can see the collection date for the files. The name format of the client logs is Support_<guid>.zip.
    5. Right-click on the zip file and select one of the following options:
      • Open Support Center: Launches Support Center.
      • Copy: Copies the row information from Resource Explorer.
      • View file: Opens the folder where the zip file is located with File Explorer.
      • Save: Opens a Save File dialog for the selected file.
      • Export: Saves the Resource Explorer columns shown in Diagnostic Files.
      • Refresh: Refreshes the file list.
      • Properties: Returns the properties on the selected file.
    6.  and Many more watch out below video.

Can we upload more than one machine client logs for diagnostics? i don’t have count how many clients can we select but whenever you do, Just remember you are trying to upload some files from clients to Site server in MB’s

Happy Sharing!

Leave a Comment

Your email address will not be published. Required fields are marked *