A monitoring gap most fleets don't notice
Intune tells you a lot about a device — compliance state, last check-in, installed apps. It doesn't tell you how long it's been since it actually restarted.
On a personal device, that gap doesn't matter much: the owner reboots it eventually, because they notice it slowing down. On a shared device, nobody feels that ownership, so the gap can run for months without anyone in IT ever seeing it.
This page is about closing that specific gap. For step-by-step deployment instructions, see our full Intune deployment guide.
Visible on the device
Anyone picking up the device sees its current status and uptime immediately, no admin console required.
A configurable nudge
A notification and in-app popup appear once a device has gone too long without a restart — 7 days by default, adjustable to 3 or 14 days, or off. A battery optimization shortcut is built in for the rare device where a reminder doesn't come through. Administrators can also set the reminder centrally with an Intune app configuration policy.
Per-device history
Every device keeps its own 12-month reboot history and monthly heatmap, viewable on that device.
Fits Managed Home Screen
Works as one more tile in a locked-down, single-purpose or multi-app kiosk configuration.
A decentralized monitoring model, on purpose
RebootMonitor does not send reboot data to a server, so there is no central "which devices haven't rebooted" report to check from your desk.
That is a deliberate trade-off, not a missing feature. The person best placed to act on a low-uptime warning is whoever is using the device at that moment — not an administrator reading a report days later. Putting the signal directly on the device turns monitoring into action immediately, without building or maintaining a separate reporting pipeline.
Pairs well with what Intune already reports
- Intune already shows last check-in and compliance state per device.
- RebootMonitor adds the one number Intune doesn't track: time since the last actual restart.
- Support staff can ask the current user to check the app instead of chasing device logs remotely.
Private by default
- No reboot data leaves the device, so there's nothing extra to secure or govern centrally.
- Deploys as a normal Managed Google Play app, assigned Required to your device group.
- Only
RECEIVE_BOOT_COMPLETEDandPOST_NOTIFICATIONSpermissions are used.
Frequently asked questions
Does RebootMonitor give admins a fleet-wide reboot dashboard in Intune?
No, and that is deliberate. RebootMonitor reports reboot status on the device itself rather than to a central server, so there is no cross-device dashboard to view from the Intune admin center.
Why monitor on the device instead of centrally?
On a shared device, the person most able to act on a low-uptime warning is whoever is holding it right now, not an admin browsing a report days later. On-device monitoring turns the signal into an action immediately.
Can this be combined with Intune's own compliance reporting?
Yes. Intune already reports last check-in and compliance state per device. RebootMonitor adds the one signal Intune does not track: how long it has actually been since the device restarted.
Does this replace a device compliance policy?
No. It is a lightweight nudge for users, not an enforcement mechanism. Devices are not blocked or marked non-compliant for a missed reboot.
What about battery optimization blocking the reminder?
Most devices deliver the reminder fine on default battery settings. If a particular device doesn't seem to receive it, users can check the shortcut to battery optimization settings built into the app (our step-by-step guide shows what to tap), or, on Samsung devices, an admin can manage that setting fleet-wide through Intune using the Samsung Knox Service Plugin (OEMConfig).
Does RebootMonitor need a connection to Intune?
No. It is a normal Android app that tracks restarts on its own and needs no connection to Intune. It can be deployed through your existing Android management setup and also works outside enterprise environments.
Will restarting the device fix every Android problem?
No. A restart can clear temporary processes and memory and can help with certain transient issues, but persistent problems should still go through your normal IT support and device-management processes.
Is RebootMonitor only for companies?
No. Individual Android users can use it too. The shared-device case is where it matters most, because nobody feels like the owner.
Give your shared devices a reboot habit
Deploy RebootMonitor as a Managed Google Play app and let every device monitor its own reboot health.