# Endpoint Manager

See every company computer's health, run fixes and updates, and take over a screen from the browser.

Endpoint Manager shows the health of every company computer connected to your workspace, and lets IT fix common problems on them from one screen. At Acme Precision, the IT lead sees that the file server ACME-FS01 is online and that a shop-floor PC has a disk alert, runs a health check on it, and cleans up its disk without walking out to the plant.

[Add it from the Marketplace](/tenant/?open=settings/marketplace)

## What it does

**Endpoint Manager** in the sidebar opens one page:

- **Across the top**: the **Endpoints**, **Online** and **With Alerts** counts, **Add Endpoint** and **Help**.
- **On the left**: one card per computer, with a green dot when it is online, its alert count, its location or operating system, and its latest **CPU**, **MEM** and **DISK** use. The first list shows **All endpoints**, **Online only**, **Offline only** or **With alerts**; the second sorts by **Sort: name**, **Sort: status** or **Sort: alerts**. The list refreshes by itself every 15 seconds.
- **The icons on each card**: the **gear** icon (Support Actions), the **screen** icon (Remote Desktop), the **wrench** icon (Sync Tools) and **↻** (Collect metrics now). They are greyed out while the computer is offline.
- **On the right**, after you click a card: gauges for CPU, Memory, Disk (and GPU where there is one), **Trend — Last Hour**, **Top Processes**, **Active Alerts** when there are any, and **Recent Activity**.

Each computer runs the Data Visions Bridge, which sends a reading every minute. A computer shows as offline when it has not checked in for 90 seconds.

## Set it up

A Workspace Admin does this first.

1. Open **Module Settings** from the ⋮ on the **Endpoint Manager** sidebar row. On **Preferences**, check the CPU, memory and disk limits that raise an alert (85, 90 and 95% by default), how many days history is kept (**retention_days**, 30), when a computer counts as offline (90 seconds), whether remote desktop is allowed, and whether the assistant is on. See [Module settings and versions](article:fb7c92e4-6dcc-4ef4-80bc-1b6e7482e540).
2. Give the permissions to your roles (see **Who can do what** below). Keep the high-risk ones with the few people who need them. See [Users and roles: create and edit roles](article:88d4e232-d5b8-4909-b452-cfe96d3d550f).
3. Add your computers (next section).
4. If you also want computers in your asset register, add the **Assets** module from the Marketplace.

## Add a computer

1. Click **Add Endpoint** at the top of the page.
2. Under **1. Download**, click **Download installer (.msix)** and **Trust certificate (.cer)**. Both are needed the first time on each computer.
3. Follow **2. Install (run as Administrator)** on the computer: install the certificate to **Local Machine** (Trusted People, then Trusted Root), then double-click the .msix. The bridge installs as a service that starts with Windows.
4. To enroll many computers, fill in **Name**, **Max uses** and **Expires (days)** under **3. Enroll — unattended**, and click **Generate token**. Copy the command it shows (it is shown only once) and run it in an elevated PowerShell on each computer. Only a Workspace Admin can generate a token.
5. Or, on one computer, open `http://127.0.0.1:8765/ui/`, set the platform address and sign in. A Workspace Admin then approves it in **Bridge Registry**.

The computer appears in the list once its bridge connects.

## Check how a computer is doing

1. Click the computer's card.
2. Read the gauges and the **Trend — Last Hour** chart. A gauge turns amber, then red, as it gets high.
3. **Top Processes** lists the programs using the most CPU and memory.
4. **Active Alerts** lists anything over its limit. **Recent Activity** lists each action run on the computer, and whether it came from a **button**, the **agent** or a **schedule**.
5. For a reading from right now, click **↻** on the card. You see **Metrics collected** when it is done.

## Run a support action

1. Click the **gear** icon on the computer's card. **Support Actions** opens in the side panel.
2. Under **Choose an action**, pick one. A short description says what it does. Actions that change the computer are marked with a warning sign and their button reads **Run action (confirm)**.
3. If it asks for a value (a host to ping, a service name, a message), type it.
4. Click **Run action**. The result appears underneath; long actions show how long they have been running. Every run is added to **Recent Activity**.

The actions:

- **Diagnostics** (read-only): **Health Check**, **System Errors (last 24h)**, **Startup Programs**, **Network Info**, **Ping a Host** and **List Processes**.
- **Patching**: **Scan Patches** and **Apply All Patches**.
- **Inventory**: **Collect Inventory** (hardware and installed software).
- **Maintenance**: **Disk Cleanup** (temporary files and the Recycle Bin, never documents), **Optimize Drive**, **Restart a Service** (for example *Spooler* to fix printing) and **Reboot Endpoint** (restarts in 60 seconds; the person signed in gets a warning).
- **Support**: **Message User** pops a message box on the screen of whoever is signed in.

What asks before it runs, from this panel:

- **Apply All Patches**, **Disk Cleanup**, **Optimize Drive** and **Reboot Endpoint** show an OK / Cancel box in your browser first.
- **Restart a Service** is marked with a warning sign but runs as soon as you click **Run action (confirm)**. No box appears, so check the service name first.
- **Message User** and the read-only checks run straight away.
- Nothing you start from this panel waits for anyone else's approval. Your role's permission is the only check.

## Install updates

1. Click the **gear** icon, choose **Scan Patches** and click **Run action**. The pending updates are listed with the current and new version.
2. Tick the ones you want and click **Apply Selected**, or click **Apply All (n)**. Click **OK** in the box that asks you to confirm.
3. Each update then shows updated, no update, needs a user, or failed, and whether a restart is needed.
4. Click **Re-scan** after a few minutes, because some installers finish in the background.

Updates marked **needs user** open the vendor's own updater, so they cannot install unattended. Finish them over Remote Desktop. Every online computer is also scanned for updates once a day.

## Take over a computer's screen

1. Click the **screen** icon on the computer's card. **Remote Desktop** opens in a wide side panel and connects.
2. Use **Fit** to switch between fitting the screen and full size (**100%**), and **Ctrl+Alt+Del** to send that key combination.
3. Click **Disconnect** when you are done.

If the panel says **Remote desktop isn't set up on this endpoint**, it offers **Enable RDP** or **Install VNC server**. These run as soon as you click, with no OK / Cancel box, and need both **Connect remotely** and **Deploy software**. **Enable RDP** leaves remote desktop on. **Install VNC server** installs the free TightVNC program after checking it is signed by its publisher, and can replace a VNC server already on the computer.

A session signs in with a temporary account that is removed when it ends, and never opens the computer's firewall. If the session had to turn remote desktop on, it turns it back off once no session is left.

## Add a computer to the asset register

This shows only when the workspace also has the **Assets** module.

1. Click the computer's card.
2. If it is already an asset, click **Asset: …** at the top of its detail to open it.
3. Otherwise click **＋ Register Asset**. A **New Asset** form opens, filled in with the computer's name, maker, model and serial number. Check it and save it. Saving needs the Assets module's permission to add assets.

A computer whose name matches a different asset does not overwrite that asset; you are asked to rename one of them.

## Who can do what

Each action in the module needs a permission. A Workspace Admin gives permissions to roles; see [Users and roles: create and edit roles](article:88d4e232-d5b8-4909-b452-cfe96d3d550f). **High risk** marks permissions that can change a computer or take it over. Give them only to the people who need them.

| Permission | What it lets someone do | Out of the box |
|---|---|---|
| **View the computer list** | See every computer, whether it is online, and open its detail. | Admin, Operator, Viewer |
| **View computer performance** | See CPU, memory, disk and GPU readings and the last-hour trend. | Admin, Operator, Viewer |
| **Refresh performance data** | Take a reading now (**↻**) and use **Sync Tools** (the **wrench** icon). | Admin, Operator |
| **View alerts** | See alerts raised when a computer goes over a limit. | Admin, Operator, Viewer |
| **Acknowledge alerts** | Mark an alert as being worked on (through the assistant; there is no button). | Admin, Operator |
| **View hardware and software** | See a computer's hardware and installed software, its asset link, and open **＋ Register Asset**. | Admin, Operator, Viewer |
| **Refresh the inventory** | Run **Collect Inventory** and **Scan Patches**. | Admin, Operator |
| **View patch status** | See the pending updates found by the last scan. | Admin, Operator, Viewer |
| **Run read-only checks** | Run **Health Check**, **System Errors (last 24h)**, **Startup Programs**, **Network Info** and **Ping a Host**. | Admin, Operator, Viewer |
| **See running programs** | Run **List Processes**. | Admin, Operator |
| **Read files on computers** | Read a file on a computer, such as a log, through the assistant. | Admin, Operator |
| **Save performance reports** | Save a performance report into the computer's Data Visions reports folder. | Admin, Operator |
| **View action history** | See what was run on each computer, when and by whom (not the output of commands, file changes or scripts). | Admin, Operator, Viewer |
| **Run maintenance** | **High risk.** **Disk Cleanup**, **Optimize Drive**, **Restart a Service** and clearing the DNS cache. | Admin, Operator |
| **Install updates** | **High risk.** **Apply All Patches**, **Apply Selected** and **Apply All**. | Admin |
| **Restart computers** | **High risk.** **Reboot Endpoint**. | Admin |
| **Connect remotely** | **High risk.** Take over a computer's screen and use **Message User**. | Admin |
| **Deploy software** | **High risk.** Set a computer up for remote desktop (**Enable RDP**, **Install VNC server**), and send updates to a group of computers (with **Install updates**). | Admin |
| **Stop running programs** | **High risk.** Force a program to close, through the assistant. | Admin |
| **Change files on computers** | **High risk.** Create or overwrite a file on a computer, through the assistant. | Admin |
| **Run commands on computers** | **High risk.** Run any command on a computer, through the assistant, and see command output in the activity lists. | Admin |
| **Run scripts on computers** | **High risk.** Run a library script or a written script, through the assistant, and see script output. | Admin |
| **Manage the script library** | **High risk.** Add and remove saved scripts. | Admin |
| **Set up automatic responses** | **High risk.** Decide what runs on its own when an alert fires. A command rule also needs **Run commands on computers**, a script rule **Run scripts on computers**. | Admin |
| **Manage computer groups** | Organize computers into groups. | Admin |
| **Set alert and patch policies** | Set CPU, memory and disk alert limits (1 to 100%) for a group or the whole fleet. | Admin |

- Groups, the script library, alert policies, automatic responses and software rollouts have no screen in this version.
- An automatic response runs without anyone approving it. It stops once the person who saved it loses the permission it needs, and a script rule runs only the version of the script it was saved with.

## Ask its agent

The **Endpoint Agent** answers questions and runs the same actions by chat. With a computer selected, it works on that computer; with none selected, name the computer. It has your permissions and no more. Try:

- "Run a health check on ACME-FS01."
- "Show me the top 5 processes by memory on ACME-ENG-WS02."
- "Generate a fleet health report."

Before it does anything that changes a computer, it says in one sentence what it will do and waits for you to click approve or decline. That covers running a command or script, changing a file, stopping a program, installing updates, restarting the computer, **Disk Cleanup**, **Optimize Drive**, starting, stopping or restarting a service, clearing the DNS cache, and showing a message on the user's screen. Readings, scans, inventory, read-only checks, reading a file and saving a report run without asking. See [Agent chat](article:073c6465-d85c-4364-8768-acf42a3a6a48).

## Good to know

- The card icons and support actions work only while the computer is online.
- Some actions are for Windows only, such as the Recycle Bin, Windows services and the .msix installer.
- Every action, whether from a button, the assistant or a schedule, is recorded in **Recent Activity**.
- An alert closes on its own when the reading drops back under its limit, or after a week with no readings from that computer.
- Readings, logs and history older than **retention_days** are removed once a day. Open alerts are kept until they close.
- An administrator can turn remote desktop off, or the assistant off, for the whole workspace in **Module Settings**.
- The module also gives you datasets for reports and dashboards (readings, alerts, patch status, action history, update jobs and remote sessions). See [Dashboard](article:1d8a33a4-3a13-4874-b8e5-5ef9da22df95).

## More help

Click **Help** at the top of the Endpoint Manager page for the full reference: every support action, alerts, remote desktop, setup and who can do what. The module has no runbooks yet.


Source: https://datavisions.ai/docs/module-guides/endpoint-manager
