6 min read

ConfigMgr - Support Center - Client Tools Part 1 - Client Information

ConfigMgr - Support Center - Client Tools Part 1 - Client Information

So, this is the next part in the "Support Center" series and in this one we'll cover the "Client Tools" and "Client Information" tab.

I will split the Client Tools into some smaller parts for readability and not cramming to much information into one long post.

Support Center - Configuration Manager
Troubleshoot Configuration Manager clients with the Support Center.

  1. Installing Support Center
  2. Getting started
  3. Client Information
  4. Maintenance Windows
  5. Control Client Agent Service

Installing Support Center

As with my previous post
has an excellent post about how to deploy it

How To Deploy Support Center Using SCCM | Troubleshooting Tool | ConfigMgr HTMD Blog
Let’s check how to deploy Support Center Using SCCM (a.k.a Configuration Manager). Support Center aims to reduce the SCCMIT Admin challenges for

Getting Started

As with the rest of the Support Center tools, Client Tools can either be run remote or locally on a device. When you start it just click the blue button in the upper left, and choose either "Local machine Connection" or "Remote Connection" depending on your use-case. If its run locally on a device with ConfigMgr Client installed it usually auto-connects as local.

Client Tools, connect to ConfigMgr Client

OBS When using remote connection:
Remote connections must include computer name or domain as part of the user name

If you connect to a remote client from Support Center, you must provide the machine name or domain name for the user account when establishing the connection. If you use a shorthand computer name or domain name (such as .\administrator), the connection succeeds, but Support Center doesn't collect data from the client.

To avoid this issue, use the following user name formats to connect to a remote client:

  • ComputerName\UserName
  • DomainName\UserName

When your connected to a device you will probably start at the "Client" tab (at least thats what were a going to do, and work or way left -> right").

Just click "Load" to have Client Tools load in the information about the device's ConfigMgr Client

Client Tools, Client Information Tab

Client Information

Here we get some quick and useful information about the configmgr client state at the moment and some of the info i look at first is

Client information loaded using "Support Center Client Tools"
  • Approved - Has the client registration been approved at the site or not? If its not approved further functionality of the CMClient wont work, the only thing the client could do is to ask the MP to be part/register of/with the site.
    Usually clients in a trusted AD forest are automatically Approved when installed, but if you install the CM client in lets say a workgroup and it register with you site, you will have to manually approve the client.

    As with client registration after installation, you can check the client-side log "ClientIDManagerStartup.log"
client-side log ClientIDManagerStartup.log

Settings for you client approval method is under "\Administration\Overview\Site Configuration\Sites" -> Hierarchy Settings

Client Approval settings under Hierarchy Settings
  • Assigned MP - This is what management point the client has set as assigned MP.
    For troubleshooting if its the wrong MP or if its empty, i would start to check the clients logs, and start with the client-side logs "LocationServices.log"  and "ClientLocation.log" found in "C:\Windows\CCM\Logs\".
client-side log ClientLocation.log
client-side log LocationServices.log
  • Client ID - The Unique Identifier of the configmgr client and is not the same as the SMBIOS UUID.
    It can be found using eg. Powershell
    Get-WmiObject Win32_ComputerSystemProduct | Select-Object ExpandProperty UUID

    And you can also view it in eg. ConfigMgr Console selecting a device and checking under "General information"

    I've seen some cases dealing with VDI's where the teams which handles the Master Image etc has missed some things and all VDIs generated after that have the same GUID and a lot of confusion begins, CM wont be able to handle it and clients wont work.
From device general information, selecting a device in configmgr console
  • Hardware ID - This is just a copy+paste from Jason Sandys:
    Hardware ID. It is a hash value generated based on the hardware contained in a system to identify the system regardless of the OS or ConfigMgr client status and version.
  • Internet-Facing - If you are using IBCM (Internet Based Client Management) to manage eg. Workgroup computers or private devices, they would show as Internet-Facing True.
  • Proxy MP - If the client is part of a secondary site with an MP, then that MP would be a "Proxy MP".
  • Proxy Site Code - As with MP, if it's part of a secodary site, this site code would be "Proxy Site Code".
  • Proxy State
  • Registration State - This tells if the client has successfully registered with the site/MP after client installation, if it hasn't successfully registered with the MP it wont be able to get an site assignment.
    It can be "Pending", "Registered", "unregistered".

    For troubleshooting, eg. the MP log "MP_RegistrationManager.log" and client-side log "ClientIDManagerStartup.log"
Client-side log ClientIDManagerStartup.log
Management Point-Side log, MP_RegistrationManager.log
  • Resident MP - This is the MP currently assigned to a roaming client. I'm going to link to an really good article where you can read up on this, instead of trying to do it better.
    Roaming and Roaming Boundaries
  • Site Code - What site code is assigned to the client.
  • Version - What ConfigMgr Client version is installed.

Maintenance Windows

At the Client tab you can also view the clients past and coming Maintenance Windows, their start/stop time, its ID and how the MW type of Window.

Hovering over the icon will tell you more info about the icon, the green arrow here meaning that this is the next MW coming up. The other icon meaning its a future MW.

These would be your (if defined) business hour MW's

User defined Business Hour MW's

And this is a MW defined on a collection for eg. software updates on servers.
I've asked why its an hour diff in the Client Tools vs ConfigMgr Console, don't know if its a bug or some TimeZone setting programmed in the Client Tools. No answer yet... Will update post when i get one!

Collection defined MW

Control Client Agent Service

This one is pretty self explanatory, you get three actions which can control the ConfigMgr Client Agent Service, restart, start or stop.