Help

Clients

The Clients tab shows all registered machines with their connection status (green = online, red = offline), last seen time, and uptime. Click a client name to open its detail page where you can run tasks and view history.

Status dot: A client is considered online if it has sent a heartbeat within the last 3 minutes. If a heartbeat is missed, the dot turns red and an alert may be generated.

Client Detail & Tasks

The client detail page shows server stats from the last Ping result (CPU, memory, disks) and a row of task buttons:

• Ping — Collects current CPU, memory, and disk usage
• Get Logs — Pulls recent Windows Event Log entries (Critical, Error, Warning)
• Check Updates — Scans for pending Windows updates without installing them
• Run Updates (orange) — Installs all pending Windows updates. Prompts for confirmation. May require a reboot.
• Check Backup — Checks status of Windows Backup and IDrive backup jobs
• Reboot (red) — Schedules a server reboot with a 60-second warning. Prompts for confirmation. The agent tracks when the server comes back online and logs the downtime.
• Get Services — Lists all auto-start Windows services and flags any that are stopped

Blue buttons are safe, read-only tasks. Orange (Run Updates) and red (Reboot) buttons perform changes and ask for confirmation before running.

Below the buttons is the Task History table. Click any task row to see its detailed result. Each result includes a human-readable summary and a "Show Raw Data" toggle for the full JSON.

Alerts

The Alerts tab shows unacknowledged alerts. The badge in the nav shows how many are pending. Alerts are generated automatically by the alert engine, which checks every 5 minutes for:

• Offline — Client hasn't sent a heartbeat within the timeout window
• Disk Space — Any drive above the configured usage threshold
• Backup Failure — Last backup check reported a failure
• Pending Updates — Critical or important Windows updates waiting to be installed
• Log Errors — Critical errors found in recent Windows Event Logs

Click Ack to acknowledge and dismiss an alert.

Scheduled Maintenance

The Schedule tab controls automated maintenance windows for each client. Each client can have its own schedule (day, time, enabled/disabled).

During a maintenance window, the system automatically runs: Ping, Get Logs, Check Updates, and Check Backup. If critical or important updates are found, it will install them and reboot if needed.

Schedule options: Monthly (1st Sunday/Saturday/Friday, 1st of month), Biweekly (every other week), or Weekly. All times are in UTC.

Setting Up a New Client Server

1. Configure AV / endpoint security exclusions on the new server before installing
2. Copy LMSRMM.exe to the new server (USB, file share, RDP copy-paste, etc.)
3. Go to the Clients tab in this dashboard and click + Add Client
4. Enter the server name (e.g. OKPRIME-SERVER) and click Create
5. Copy the token that appears — it is only shown once
6. On the new server, double-click LMSRMM.exe — it will prompt for admin elevation (UAC)
7. Press Enter to accept the default Hub URL (wss://rmm.lms-cloud.net/ws)
8. Paste the client token from step 5
9. Press Enter to accept the default client name (or type a custom one)
10. Confirm with y — the installer creates the directory, writes the config, installs the Windows service, and starts it
11. The client should appear as online in the dashboard within a few seconds

Agent

Each monitored server runs the LMSRMM.exe agent as a Windows service. The agent maintains a persistent WebSocket connection to this hub and sends heartbeats every 60 seconds.

Installing: Run LMSRMM.exe setup as administrator. For new installs, it prompts for the hub URL, client token, and machine name. For upgrades, it automatically replaces the binary and restarts the service.

Reboot tracking: When a reboot is triggered (manual or post-update), the agent writes a marker file before shutdown. When the server comes back and the agent reconnects, it reports how long the server was down.

AV / Endpoint Security Exclusions

The RMM agent runs PowerShell commands to collect system data (event logs, update status, service lists, etc.). This can trigger antivirus or endpoint protection alerts. The following exclusions should be configured on each managed machine:

File / Folder Exclusions

• C:\Program Files\LMS RMM\ — Agent install directory
• C:\Program Files\LMS RMM\LMSRMM.exe — Agent executable

Process Exclusions

• LMSRMM.exe — The agent process itself

FortiClient EMS

If using FortiClient EMS, add exclusions in both the AntiVirus and Sandbox profiles:

Endpoint Profiles > AntiVirus > Exclusions:

• File exclusion: C:\Program Files\LMS RMM\LMSRMM.exe
• Folder exclusion: C:\Program Files\LMS RMM\

Endpoint Profiles > Sandbox > Exclusions:

• File exclusion: C:\Program Files\LMS RMM\LMSRMM.exe
• Folder exclusion: C:\Program Files\LMS RMM\

Windows Defender

If using Windows Defender, add exclusions under Windows Security > Virus & threat protection > Manage settings > Exclusions:

• Folder: C:\Program Files\LMS RMM\
• Process: LMSRMM.exe

Without these exclusions, the agent may be quarantined, blocked from executing PowerShell commands, or flagged as a threat.