RITIS · Devices
Every machine you own, accounted for
You see health, patch state, agent coverage and backup status for every server and workstation you own, with memory, uptime and last contact per device. In this 115-machine sample environment, agent coverage at 93% means eight machines are not fully managed, and RITIS names them for you.
Health and standards
90%
Patch compliance
90%
Agent coverage
93%
Backup success
100%
Your fleet, one row per machine
Every server and workstation you own appears as a row: health, patch state, which agents are installed, memory pressure, uptime and last contact. The tiles are those rows rolled up. When one of your devices drops out of patching or stops checking in, your number moves, and the Find action names the machine.
What gets fixed for you
Each of these is a finding with a Find action behind it, so you see the exact records involved.
-
5 devices without a patching agent
Five machines named. The Automox agent deploys from the finding, not from a follow-up ticket.
-
18 devices needing patches
The exact machines behind the 90%, sorted by how far behind they are.
-
Devices over 90% memory
Flagged from telemetry before your people start calling about a slow machine.
Your questions about devices
- Which agents does coverage count?
- Remote management, patching, endpoint security and backup where the device warrants it. A machine missing any expected agent counts as a gap, which is why coverage reads 93% rather than a friendlier number.
- What makes a device unhealthy?
- Falling below the device standard: sustained memory over 90%, excessive uptime without a restart, missed check-ins, failed patch runs or a security agent that has stopped reporting. Each unhealthy device shows the specific reason.
- Are BYOD devices included?
- Devices enrolled in management are scored. Unmanaged personal devices do not appear, which is exactly why agent coverage is the first number to watch: it marks the edge of what can be managed for you.