How Can You Tell If SCCM Client Is Installed On A Workstation

To check if SCCM client is installed on a workstation, use one of five direct verification methods depending on your access and need for detail. The most immediate way is to look for the Configuration Manager applet in Control Panel, while PowerShell, the registry, the SMS Agent Host service, and the SCCM console each serve specific scenarios like remote checks, troubleshooting, or bulk verification. Before running remote queries, you may first need to find workstation id to target the correct machine.

Check the Control Panel for Configuration Manager

This method is best when you are physically at the workstation or connected remotely and want a quick visual confirmation. A common misconception is that the Control Panel applet for the SCCM client is named "Systems Management"; the correct and current name is "Configuration Manager".

1. Open the Control Panel on the workstation.
2. Locate the applet named "Configuration Manager".
3. If the applet is present, the SCCM client is installed. Double-clicking it opens the client properties, where you can verify site assignment and client actions.

Use PowerShell to query the SCCM client status

PowerShell is ideal for remote or scripted checks across multiple workstations. The correct namespace is root\CCM, not root\ccm\clientsdk as sometimes misstated. Run the following command as an administrator:

Get-WmiObject -Namespace "root\CCM" -Class "CCM_Client" | Select-Object -Property ClientActiveStatus

The ClientActiveStatus property returns values such as "Active" or "Inactive". A value of "Active" confirms the client is installed and communicating with the site. "Inactive" indicates the client is installed but not currently connected, while "Uninstalled" or an empty result means the client is not present.

Query the Windows Registry for SCCM client keys

Registry checks are useful when Control Panel or PowerShell are unavailable or when you need to verify installation on a system that cannot run scripts. Key registry entries for the SCCM client are located under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CCM.

1. Open Registry Editor (regedit.exe).
2. Navigate to HKLM\SOFTWARE\Microsoft\CCM. On 64-bit systems, also check HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM for the 32-bit client components.
3. Look for keys such as Client and ClientComponents under the CCM key. Their presence confirms the SCCM client is installed.

Check the SMS Agent Host service

This method verifies not only installation but also that the client is running. The presence and running state of the SCCM client are indicated by the "SMS Agent Host" service, which has the executable CcmExec.exe. For proper client operation, the "SMS Agent Host" service's startup type should be set to "Automatic".

1. Open the Services console (services.msc).
2. Find the service named "SMS Agent Host".
3. Verify its status is "Running" and its startup type is "Automatic". If the service is missing or not running, the SCCM client is either not installed or has a problem.

Verify installation via the SCCM console

When you have access to the central management server, the SCCM console provides a single pane of glass for checking client status across many devices. Navigate to Assets and Compliance > Devices, locate the workstation, and review its "Client Activity" column. A green checkmark or "Active" status indicates the client is installed and reporting. This method is efficient for bulk verification without touching each machine.

Check the ccmsetup folder and log files

Log files are essential when troubleshooting a client that appears installed but is not functioning correctly. The C:\Windows\ccmsetup folder contains the client setup files used during the installation process. Key log files include:

• ccmsetup.log, Records detailed information during the client installation process and can be used for troubleshooting.
• ClientIDManagerStartup.log, Helps confirm if the client has successfully registered with its assigned Configuration Manager site.
• PolicyAgent.log, Indicates whether the client is successfully retrieving policies from the management point.

Review these logs when the client appears installed but fails to check in, apply policy, or receive software. The Configuration Manager client regularly performs health checks, which include verifying its correct installation, the presence of prerequisites, sufficient disk space, and the running status of the SMS Agent Host service. Log files are the primary source for diagnosing why a health check might fail.