The device page

Open any device from the device list, a ticket, an alert or search (Cmd+K) to reach its page. It brings together what the agent reports, what monitoring sees, patches, software, scripts, alerts, tickets and documentation for that one machine.

You can also look a device up, run a script or restart it from the Tenvara app.

The header#

The title is the device's name: the one you gave it in Edit (for example Main server), else its hostname. Then come its status, any criticality and warning badges, its tags and Follow. Under it you see the customer, site, Used by, who is Signed in and whether they are there (or Last user and when, while nobody is), criticality, the Hostname with Rename the computer too beside it, operating system, model, serial number, when it was last seen and its IP address. A computer with no screen attached says Display: No monitor connected, and the viewers say why the picture is black rather than showing a silent black screen.

Edit (E) changes the name, customer, site, type and the other details. The hostname is the computer's own name, as its agent reports it, and is read-only once anything reports the device: nothing the device reports ever overwrites the name you gave it. Rename the computer too asks the agent to rename the machine itself, after an approval. See Device names, hostnames and renaming the computer and Who is signed in and whether they are there.

The buttons along the top:

The More actions menu holds:

• Raise ticket, Run diagnostics (see Diagnostics), Page on-call, Message the user and Show a message to users.
• Ask AI... and Investigate with AI, see AI, and Search security events for this device.
• Refresh inventory, Agent modules and Troubleshoot agent (below).
• Registry (below). The other background tools are in the Toolbox and on the Tools tab.
• Run script and Run a command (see Running and scheduling scripts), Install software, Check for updates, Install updates and Reconcile printers.
• Open in Infrastructure for a server that is also a hypervisor host or another Infrastructure record.
• Open web page and Forward a port, to reach the device's own web interface or a port on it through an agent on its network. See Opening device web pages and forwarding ports.
• Copy hostname, Copy IP address, Copy serial and Revoke agent.
• Power, Maintenance mode..., Planned state..., Add warning..., Set who uses it..., Merge into another device... and Retire device..., see Device lifecycle, retire, replace and stale devices.
• Criticality, History, Print, Print labels (see Print labels and unique asset tags), Pin a note and Delete device, which removes the agent too (see Deleting a device removes its agent).

The tabs#

Power actions#

Power in the ... menu offers Restart..., Shut down..., Sign out the user... and Lock....

1. Choose the action.
2. Under When, choose Now, Ask the user (restart only) or At a time. With Ask the user, set Restart by: the signed-in user can put the restart off until then, and with nobody signed in it restarts straight away. A device that is offline acts when it is next online.
3. Change the Message to the user if you like, and give a Reason, which is kept on the device's timeline with your name.
4. Confirm. A server, or more than 10 devices at once, asks you to type the hostname or the count first.

Sign out and lock act on everyone signed in to the device. The same actions are in the device list's bulk bar, on an open alert about the device, on a ticket's device and in Cmd+K (Restart ..., Lock ...).

Registry editor#

Registry in the ... menu of a Windows device opens the registry as an editor, without taking the screen. Browse the hives, search under the open key (key names, value names and data), create, edit, rename and delete keys and values of every type, export a key to a .reg file and import one, with a preview of what it will write.

Every change keeps the values before and after, on the action and on the device's timeline. Roles decide separately who may browse the registry and who may change it. See Roles and permissions.

Troubleshooting the agent#

When the agent itself misbehaves, Troubleshoot agent in the ... menu offers:

• Show agent health: the agent's work waiting to send, its clock compared with the server's, modules that are failing, errors today, free disk and the last error.
• Collect agent logs: the agent zips its logs and uploads them, ready to download from the device page for 7 days.
• Restart the agent: the service stops and starts again, and the device comes back online in a few seconds.

Show agent health also lists the script modules on the device. A Windows device carries only the agent's core scripts, plus those of the modules it uses (device hardening, web hosting, Hyper-V, printers and so on), which arrive when it starts using a module and go when it stops. Any it should not have are flagged.

The agent also looks after itself: it retries every step of connecting, reconnects at once after a network change, and restarts itself when it has not reached your server for a while although its network works (Restart an agent that cannot connect after in Settings > Devices and agent).

Warnings and who uses it#

Add warning... puts a short note in front of everyone who opens the device, remotes in, runs a script, installs updates or restarts it, for example Runs payroll: never restart before 18:00. Choose a Level: Information, Caution or Stop. A Stop warning must be ticked as read (I have read the warning and still want to go ahead) before any of those actions goes ahead. Warnings show as a banner on the device, an icon in lists and Cmd+K, and on tickets and visits about the device; their history is kept.

Used by names the contact who uses the device. Set it with Set who uses it..., or accept a suggestion: Tenvara suggests the person who has signed in on most of the last 14 days, and can set it by itself each night (Settings > Device lifecycle). Who uses a device shows on the contact's page, on tickets from that person (with one click to link the device) and in the steps when someone leaves.

The main column#

From top to bottom on Overview:

• Health: CPU, memory, swap and every disk, who is signed in, uptime, when data last came in and how often it is sampled, followed by charts for CPU, memory, each disk and the network. See Device health.
• Network: how the device is connected, "Plugged into SW01 port 12 (VLAN 20)" on a cable or "Connected to Wi-Fi Staff through WAP01 (5 GHz, signal good)" on Wi-Fi, once a switch, controller or the agent has reported it. See Network discovery and topology.
• Diagnostics: the latest diagnostics run and what stood out.
• Patches: who updates the device (Updates handled by, with Change), compliance, missing updates, the next maintenance window and recent installs. See Who updates a device. A server in a server set shows its set, its partners and its next turn. See Patching and Server sets.
• Software: deployments that apply to the device, what is installed, updates available and history. See Software deployment.
• Remote access tools: remote access and remote management tools found on the device, with Allow and Remove now. See Remote access and RMM tool finder.
• Vulnerabilities: the known vulnerabilities in the device's software, with the fix for each. See Vulnerability management.
• Scripts: recent script runs on this device, with Run script and All runs.
• Printers: printers deployed to the device and whether they are in sync, and the printers on it that Tenvara did not add, with Take over. See Deploying printers to devices.
• Security: security events, detections and the protection report (antivirus, EDR, firewall, encryption, local admins). On Windows the encryption part lists each BitLocker recovery key Tenvara holds for the device. See BitLocker recovery keys.
• Open alerts, Checks, Backup (with Recovery points and Recent jobs), Recovery, Automation, Tickets and Documentation (credentials, records and articles linked to the device).
• Lifecycle and warranty: purchase, warranty and support, and when the device is due for replacement, with What we know about the hardware. See Asset lifecycle and warranty.
• Services: every service with its state and start type, filterable to those not running.
• Hardware and OS: processor, memory, BIOS, build, domain, time zone, Network interfaces and Disks. External drives and network shares are listed apart under External and network, see Sleeping devices and volumes.
• Changes: what changed between inventories this week: software installed, removed or updated, operating system upgrades, hardware, network adapters, serial, model or domain, and local administrators. All changes opens the full list.

A device that Microsoft Intune also manages has an Intune card, once the customer's Microsoft 365 tenant is connected. Tenvara links the two records by the Entra device ID, then the serial number, then the name, and you can link or unlink them by hand. The device list has a Managed by Intune column and filter to match.

A device on older Windows runs the Lite agent: the page says Lite agent beside the status, names when that version of Windows went out of support, and greys out what the Lite agent does not do, with the reason. See Older Windows and the Lite agent.

The side column#

• Agent: the version, when it enrolled, the platform and when inventory last came in, then every module with its state. Manage switches modules for this device (below).
• Signed in: everyone signed in to the device, at the console or over Remote Desktop, with whether each is active, idle, locked or disconnected and since when.
• At a glance: open alerts, the last backup, patches and recent activity.
• Remote Ctrl+Alt+Del on Windows: whether the Ctrl+Alt+Del button works in a remote session on this device and, when it does not, which policy blocks it. See Ctrl+Alt+Del in a remote session.
• Used by, with Set, and any suggestion waiting.
• From the tray and Record a problem: what the person at the device sent from the tray. See The tray app and Record a problem.
• Roles: what the device does, such as domain controller or file server.
• Updates: the agent's version, channel, pins and maintenance windows. See Agent updates and release channels.
• macOS permissions on a Mac: each permission the agent needs, shown as granted, missing or not needed, with what needs it and where to switch it on. A missing one shows a quiet notice at the top of the page rather than an alert. See Installing the agent.
• Remote sessions: the latest sessions on this device, with History.
• Portal access: the customer's contacts who may remote into this computer themselves from the portal. See Remote control.
• Remote access policy: whether sessions on this device need approval, and what set it.
• Availability: the share of the last 30 days the device was reporting, with a strip by day, and this month's uptime against its target.
• Monitoring: the policies that reach the device, its groups, maintenance windows and mutes.
• Top processes: the busiest processes by CPU and memory.
• Where it is: the customer, site address and the people at that site.
• Details and Notes, files and history.

Switching agent modules for one device#

Open Agent modules from the ... menu (or Manage on the Agent card). Each module has three choices:

• Default follows the workspace setting in Settings > Devices and agent (shown in brackets, for example Default (on)).
• On runs the module on this device whatever the default says.
• Off stops it on this device.

The state badge beside each module shows what the agent says: Running, a short status such as 4 checks, 1 failing, or Not reported yet.

Note: Switching Monitoring off for a device stops its metrics and checks, and resolves its open monitoring alerts. Switching Remote control off stops anyone remoting in to it.