By using this site, you agree to the Privacy Policy.
Accept
EnterinITEnterinITEnterinIT
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
Reading: Configuration Manager Client Status for Effective Device Management
Font ResizerAa
EnterinITEnterinIT
Font ResizerAa
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
  • WINDOWS
  • SCCM Query Collection List
Search
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
ConfigMgr

Configuration Manager Client Status for Effective Device Management

Published: February 11, 2024
4 Min Read
SHARE

How to Configure and Monitor Configuration Manager Client Status for Effective Device Management. Before you can monitor Configuration Manager client status and remediate problems that are found, you must configure your site to specify the parameters that are used to mark clients as inactive and configure options to alert you if client activity falls below a specified threshold.

Contents
Configure client statusConfigure alerts for client statusRun Client Status Report

Configure client status

1. Start the SCCM console. Navigate to Monitoring\Client Status. Click Client Status Settings in the upper menu;

2. In the Client Status Settings Properties, you can configure next parameters:

  • Client Policy requests during the following days – This setting specifies the number of days since a client requested a policy. The value is set to 7 days by default.
  • Heartbeat discovery during the following days – This setting specifies the number of days since the client sent a heartbeat record to the site database. The value is set to 7 days by default.
  • Hardware inventory during the following days – This setting specifies the number of days since the client sent a hardware inventory record to the site database. The value is set to 7 days by default.
  • Software inventory during the following days – This setting specifies the number of days since the client sent a software inventory record to the site database. The value is set to 7 days by default.
  • Status messages during the following days – This setting specifies the number of days since the client sent status messages to the site database. The value is set to 7 days by default.
  • Retain client status history for the following number of days – This setting specifies for how long the client status history should remain in the site database. It is set to 31 days by default.

3. Click OK;

4. Click Schedule Client Status Update in the upper menu. By default, the client status update is set to 1 Day. You can set it to 1 Hour. This means that every 1 hour the client status is updated.

5. Click OK;

Configure alerts for client status

1. Navigate to Assets and Compliance\Device Collections. Select the collection for which you want to enable the alerts. Click Properties in the upper menu;

2. Click on the Alerts tab and click Add;

Note: Alerts are supported only for Device Collections

3. Under the Client status select all options. Configure Endpoint protection when Endpoint clients are deployed to a device collection. Click OK;

4. We see there are 3 conditions for which alerts can be raised. An Alert severity can be Critical, Warning, or Information. Leave by default and click Apply, then OK;

Run Client Status Report

1. Navigate to Monitoring\Reporting\Reports\Client Status, run the report for client status, Client status summary;

2. Select Collection, Client Version and click View Report;

3. In my case, it’s empty (because it’s LAB deployment);

4. This is from my non-test deployment:

TAGGED:System CenterSystem Center Configuration ManagerWindows
Previous Article Configuration Manager Query Collection List Troubleshooting Configuration Manager IIS WSUSPool Crashing During Sync Error
Next Article Configuration Manager Query Collection List Customize RamDisk TFTP Block and Window Sizes for PXE Boot in SCCM
Leave a Comment Leave a Comment

Leave a Reply Cancel reply

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

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

Translation

English中文(简体)DanskNederlandsFrançaisDeutschItaliano한국어PolskiPortuguêsRomânăEspañolУкраїнська
by Transposh - translation plugin for wordpress

Popular Posts

System Requirements for Windows Server 2016
Windows Server
Configuration Manager Query Collection List
Configuration Manager Query Collection List
ConfigMgr
Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Tech
SCCM Failed to get DP locations as the expected version from MP
ConfigMgr

Recent Posts

Installing and Configuring Fail2ban for SSH Protection on Ubuntu 24.04
Linux
Enabling and Configuring FirewallD on AlmaLinux
Linux
User Creation and SSH Key Setup in AlmaLinux
Linux
How to reset password on AlmaLinux
Linux

© 2023 EnterinIT

Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?