Workflow: Device restart enforcement

Many employees rely on sleep mode rather than shutting down their devices, which can cause system instability over time. This workflow identifies devices that haven’t been restarted in over a week and guides users to restart in a respectful, user-centric way.

Problem

Devices that are left on for extended periods without a proper restart often fail to install patches, suffer from degraded performance, and generate more support tickets.

Forcing restarts without user involvement can harm employee sentiment and strain the relationship between IT and end users.

Solution

With the Device restart enforcement workflow, you can detect devices that haven’t been restarted for over seven days and initiate targeted Campaigns to request a restart or offer a delay option.

The workflow uses real-time device restart status and user interaction to balance operational needs with employee flexibility.

Benefits and outcome

By implementing the "Device restart enforcement "workflow you:

• Improve compliance with operating system patching policies.

• Prevent long-running device sessions that degrade performance.

• Reduce service desk tickets related to unresponsive or slow devices.

• Strike a balance between operational enforcement and respectful user engagement.

• Use repeatable logic that checks the restart status and user responses.

Get started

Configure and start using your packs by following these links:

• Usage guide: Device restart enforcement for standard users.

• Configuration guide: Device restart enforcement only accessible to users with an administrator role.