Prolonged loss of contact
A check of the time of the last contact. It does not prove that the device is turned off, lost, or that the client has been removed.
Condition and parameters
The loss-of-contact threshold is set in days, hours, and minutes and must be positive. outOfContactThreshold is saved in the request. The form’s default value is 7 days. Compare it with the current time of the last contact.
In the current build, the additional parameters below are visible in the form, but these values are not sent to the server on save. Their purposes are described based on the form hints. Do not rely on the selected values being applied until the save fix is confirmed and verified on a device.
| Parameter | Purpose and values | Verification and dependencies |
|---|---|---|
| Count calendar days | Otherwise only working time can be counted. | Toggle. Not sent as a setting when saving the current form. |
| Repeat notifications | Remind administrators until contact is restored. | Toggle. Not sent as a setting when saving the current form. |
| Auto-retire from management after | After how much time to mark the device as a retirement candidate. | Duration. Not sent as a setting when saving the current form. |
Response and assignment
Select a response and assign the policy. Use the administrator notification first. Locking requires a separate check of the command on a test device.
How to verify
Check the assignment, the freshness of the server data, the result of the check run, and the entry in “Violations”. Verify the response in the history, and the lock on the device. Do not treat the absence of a violation with unknown or stale telemetry as confirmation of security.