Ved at bruge denne side, du accepterer Privatlivspolitik.
Acceptere
EnterineEnterineEnterine
  • HJEM
  • Det pro
  • Teknik
  • Microsoft
    • Azurblå
    • Configmgr/SCCM
    • DPM
    • Orkester
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Kontor 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Hold
  • Windows
    • Windows Admin Center
    • Windows klient
    • Windows Server
  • SCCM-forespørgselsindsamlingsliste
Læsning: Configuration Manager Client Status for Effective Device Management
Font ResizerAa
EnterineEnterine
Font ResizerAa
  • HJEM
  • Det pro
  • Teknik
  • Microsoft
  • Windows
  • SCCM-forespørgselsindsamlingsliste
Søge
  • HJEM
  • Det pro
  • Teknik
  • Microsoft
    • Azurblå
    • Configmgr/SCCM
    • DPM
    • Orkester
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Kontor 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Hold
  • Windows
    • Windows Admin Center
    • Windows klient
    • Windows Server
  • SCCM-forespørgselsindsamlingsliste
Configmgr

Configuration Manager Client Status for Effective Device Management

Offentliggjort: februar 11, 2024
4 Min læst
DELE

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.

Indhold
Configure client statusConfigure alerts for client statusRun Client Status Report

Configure client status

1. Start the SCCM console. Naviger til Monitoring\Client Status. Klik 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. Klik OK;

4. Klik Schedule Client Status Update in the upper menu. Som standard, 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. Klik OK;

Configure alerts for client status

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

2. Click on the Alerts tab and click Tilføje;

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. Klik 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. Naviger til Monitoring\Reporting\Reports\Client Status, run the report for client status, Client status summary;

2. Vælge Collection, Klientversion og klik View Report;

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

4. This is from my non-test deployment:

TAGGET:SystemcenterSystem Center Configuration ManagerWindows
Forrige artikel Configuration Manager Forespørgselsindsamlingsliste Troubleshooting Configuration Manager IIS WSUSPool Crashing During Sync Error
Næste artikel Configuration Manager Forespørgselsindsamlingsliste Customize RamDisk TFTP Block and Window Sizes for PXE Boot in SCCM
Efterlad en kommentar Efterlad en kommentar

Efterlad et svar Annuller svar

Din e-mailadresse vil ikke blive offentliggjort. Påkrævede felter er markeret *

Denne side bruger Akismet til at reducere spam. Lær, hvordan dine kommentardata behandles.

Oversættelse

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

Populære indlæg

Systemkrav til Windows Server 2016
Windows Server
Configuration Manager Forespørgselsindsamlingsliste
Configuration Manager Forespørgselsindsamlingsliste
Configmgr
Struktureret/administreret navigation aktiveret på moderne sider i klassiske teamwebsteder
Teknik
SCCM Kunne ikke hente DP-placeringer som den forventede version fra MP
Configmgr

Seneste indlæg

Configuration Manager Forespørgselsindsamlingsliste
System Center Configuration Manager Technical Preview Update 1611
Configmgr
Installation og konfiguration af Fail2ban til SSH-beskyttelse på Ubuntu 24.04
Linux
How to Check Timezone in Linux
Linux
Aktivering og konfiguration af FirewallD på AlmaLinux
Linux

© 2023 Enterine

Gå til mobil version
Velkommen tilbage!

Log ind på din konto

Brugernavn eller e-mail-adresse
Adgangskode

Mistet din adgangskode?