Before
An administrator likely had to review the roaming-computer list, identify unique devices, and check each device's status and last synchronization time. They then had to compile matching device details into a report and email the agent manually.
How it works
- Retrieve the roaming-computer inventory and identify unique devices.
- Check each device for an offline status and a last synchronization time greater than seven days.
- Compile matching devices and email their names, statuses, and versions to the configured agent.
Workflow details
- Collection: The workflow retrieves the current list of roaming computers and maps their device identifiers so each unique device can be evaluated.
- Deduplication: It iterates through the returned computers and filters the records to focus on unique devices for downstream processing.
- Exception checking: Each device is evaluated against two conditions: its status must be off, and its last synchronization must be more than seven days old.
- Reporting: Devices that meet both conditions are included in a report showing the device name, status, and version.
- Delivery: The completed list is sent by email to the configured agent as a report of roaming computers that have not recently checked in.
What changed
The device inventory is now evaluated automatically against the offline and seven-day synchronization criteria. Matching devices are assembled into a consistent email report, so the agent receives the exception list without manually checking each computer or preparing the report.
Work removed
Manually reviewing roaming computers one by one, identifying duplicate or unique devices, checking offline status, comparing last synchronization dates against the seven-day threshold, copying device details into a report, and emailing the agent.
Expected outcome
One consolidated exception report per run, with manual device-by-device review and report preparation removed for devices meeting the defined criteria.
