The device page at a glance

1. 1

   Device header

   The machine's name, the client it belongs to, whether it is Online or Offline, when it was last seen, and how many tools are linked to it.

2. 2

   The tabs

   Overview, Monitoring, Activity, Policy, Tickets, Integrations, Inventory, Files and Alerts. Files is only there for someone who has been granted the file browser permission.

3. 3

   Live tiles

   The agent's most recent telemetry sample: CPU, Memory, one tile for each disk volume, and Network, each with a Last 24h sparkline. Every tile opens the Monitoring tab for the history, and a machine with no agent enrolled gets a line saying so instead of empty tiles.

4. 4

   Drives

   One row per volume with how full it is, the filesystem, whether it is encrypted, and the recovery key when there is one to show.

5. 5

   Device Information

   Hostname, operating system, processor, device type, location, who it is assigned to, the agent version, and the warranty line, which reads that warranty lookup is not connected until you connect Dell, Lenovo or HP under Integrations. The switches, the approval and the policy at the bottom of the same card are called out next.

The switches, the policy in force, the owner, and what has run

1. 6

   Switches, approval and policy

   Remote control, Quarantine and Telemetry each show their state and the one button that changes it. Approval names who approved the device, Policy names the policy that governs it, Armed actions lists the command types armed for it, and View full policy opens the Policy tab.

2. 7

   Owner

   Who the machine belongs to and how that was decided, with Change owner, Remove owner, and a tick for a shared device that has no owner.

3. 8

   Running actions

   Every remote action queued against the machine with its result and who asked for it, newest first. Rows marked Automated are the ones a rule or a schedule started.

Health, Elise, and the section that holds notes and files

1. 9

   Health issues

   What the agent has flagged about the machine itself. It reads that there are no health issues when nothing is wrong.

2. 10

   Troubleshoot with Elise

   Opens a chat about this device. The card says plainly that it is read only: Elise takes a fresh read from the machine and never runs anything on it.

3. 11

   Recent activity

   The last few events on this record. The Activity tab holds the full log, with filters by type, severity, actor and source, and an Export CSV button.

4. 12

   Notes, tags, lifecycle and files

   A collapsed section holding free notes, tags, replacement history and files kept against the record. Open it with the chevron on the right.

Monitoring: the history behind the tiles

1. 13

   Time window

   24 hours, 7 days or 30 days. Every chart on the tab follows the choice you make here.

2. 14

   CPU & Memory Trend

   Both percentages over the window, captioned with how current the samples are.

3. 15

   Disk Trend

   Disk usage over the same window, from the samples the agent reports.

4. 16

   Network Trend

   Download and upload over the window, with the peak rate in the caption underneath.

5. 17

   Agent & Enrollment

   Last check-in, agent version, update ring and approval, plus when the machine enrolled. A machine with no agent, or one that has not sent enough telemetry yet, gets a line saying so instead of an empty chart.

Policy: every setting, and where its value came from

1. 18

   What this tab is

   Every RMM setting this device receives, and where each value comes from. The line points you at RMM > Policies to change one.

2. 19

   A settings group and its source chips

   Each setting shows the value the device is running and a chip naming where it came from. Default is the shipped default; a chip naming a policy is a link into that policy's editor.

3. 20

   What installs automatically

   The patching grid this machine is running: one row per update type, one column per severity, and what happens for each pair.

Inventory: the hardware the agent reported

1. 21

   Hardware

   Secure Boot, graphics cards with their VRAM and driver, memory modules with slot, size, speed and part number, and the monitors plugged in. Battery tiles show up only where the agent reports a battery, so a desktop has none, and anything the agent has not collected reads as not reported rather than being left blank.

Inventory: installed software

1. 22

   Installed Software

   Every application the agent found, with version, publisher and install date, searchable and sortable.

Inventory: updating an app on this machine

1. 23

   Third-Party Patching

   Check for updates scans this machine for updates to managed applications, then they are updated one at a time.

2. 24

   Install an app

   Search the catalog by name, publisher or package id, pick the application and click Install. The install runs as the system account through the same signed, audited path a script uses, so nobody has to be at the desk, and only an entry that is turned on in the catalog can be installed.

Inventory: local accounts and installed patches

1. 25

   Local Accounts

   Every local account on the machine, whether it is enabled, whether it is an administrator, and when it last signed in.

2. 26

   Patches / Hotfixes

   The Windows patches the agent found installed, with the KB number, what kind of update it was, and the date it went on.

Files: browsing the machine itself

1. 27

   Folder bar

   The folder you are in, with controls to go up a level, refresh, and Upload here.

2. 28

   File list

   Names, sizes and modified dates for the folder, over the same secure channel every other remote action uses. Every browse, download and upload is logged with the path, the machine and who did it, and a download or an upload asks for a fresh code first while browsing a folder does not.

Alerts raised on this machine

1. 29

   Status

   One dropdown: Open, Acknowledged, Resolved, or All. The count of matching alerts sits on the right.

2. 30

   An alert

   Severity, the condition that tripped, the observed value against the threshold, the status, how long it has been open and how many times it has repeated.

The policy behind the device: LAPS

1. 31

   The policy's own sections

   General, Monitoring, Patching, Maintenance, Agent, Permissions, LAPS and Security Baseline. The header carries the policy's state, its priority, and what it applies to.

2. 32

   Rotate local-admin password

   Off, On, or the shipped default. Turned on, the account below is rotated to a fresh random password on the schedule set here, and the rotate action also has to be armed on the Permissions tab before it will run.

3. 33

   Local-admin account

   The local admin username to rotate on devices under this policy. It is created if it does not already exist.

4. 34

   Rotation interval (days)

   How often the password rotates. A blank field falls through to the shipped default, which is shown as the placeholder.

The policy behind the device: Security Baseline

1. 35

   Screen lock

   One setting watches whether the screen locks after inactivity, and the field beside it holds the longest timeout you will accept. A machine over that shows as drift.

2. 36

   The rest of the baseline

   Host firewall, real-time antivirus, automatic updates, the account lockout threshold with its own maximum, and the built-in guest account. Each one watches and reports the control's real state, so you see the machines that do not match without a change being pushed at them.

The menu those devices show in their tray

1. 37

   Scope

   Default for all devices, or a company, a tag, or a single device. A machine uses the most specific menu that applies to it: device, then tag, then company, then default, and the line above the form says so.

2. 38

   Support door wording

   Support door name replaces Get Support on the desktop shortcut, the tray row and the installer checkbox for every device this menu covers. Form heading replaces the question at the top of the support form those devices open. Leave either blank and the default wording is used.

The About panel, your details, and the rest of the menu

1. 39

   The About entry

   Its label, its icon, two rows of tokens you can drop into the text, and the panel's own content. "Insert a placeholder token" is filled in by the device itself. "Insert a server token" is a second row underneath it, filled in by the portal from your company's brand and support details when it delivers the menu, not by the device. The shipped text puts your company and support line above the machine's name, the signed-in user, the agent version and the last check-in.

2. 40

   Support email, phone and logo

   Left blank, the portal fills the company name, support email and support phone from your company settings and your helpdesk mailbox before the menu is delivered, and sends your logo with it. Fill them in here and this menu uses these instead. An edit to the company name, phone, or logo reaches a device on its next check-in (src/app/api/agent/v1/poll/route.ts at 4b5e59a2f, resolveTrayMenuForDelivery runs on every poll).

3. 41

   Add item

   Run a script, Open an app, Open a link, Send an email, a submenu, a text label, a divider, Create a ticket, About this device, or Exit. Add one here once and every device this menu covers renders it.

Why it works this way

Questions this page answers