You might have came across below four client check categories during application or software update deployments - Unknown in Configuration Manager:
- Client check failed/Active
- Client check failed/Inactive
- Client check passed/Active
- Client check passed/Inactive
In this post, we'll see what these categories really implies. The distinction between Active and Inactive machines are an arbitrary date limit (by default, 7 days) for when it talked to Configuration Manager final. So the machines falls beneath "Client check passed/Inactive" implies the final commination with ConfigMgr, the client check was great, but haven't listened anything in at least 7 days.
Active implies the client has communicated with Configuration Manager since the limit. For case, in the event that the limit is set at the default of 7 days and a client communicated with the server 5 days prior, it would appear up as "Active" within the console.
You can change the limit in the Monitoring workspace by right clicking on Client Activity:
Client Status Settings window looks like below screenshot:
Client status update can be scheduled by right clicking on Client Activity:
Statistics of Click Status:
Statistics dashboard in the client status will give you the detailed view of clients which are active/inactive:
Below are few examples of client check failures:
No comments:
Post a Comment