Remote monitoring & management
RMM: agent inventory, patch, and discovery in one feed
Ingest endpoint inventory, patch state, and network discovery from a lightweight agent, with Microsoft 365 sync — remote monitoring and management for the fleets you run.
Backed by app modules
- Agent reports
- Agent inventory ingest
- Discovery
- Patch and discovery data
- Sync
- Microsoft 365 sync
- Isolation
- Tenant-scoped endpoint feed
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
How it works
Deploy the agent
A lightweight agent on each managed device posts to the RMM ingest endpoints. Devices are the same records used by device management, so inventory, patch state and discovery all attach to one endpoint identity rather than a parallel list.
Ingest software inventory
The agent reports installed software with name, version, publisher, install date and its source, whether that is the Windows registry, pkgutil, dpkg or brew. Inventory items can be matched to a software licence so ownership and entitlement stay connected.
Ingest patch and discovery data
Missing patches arrive with an identifier such as a KB number or package id, a severity, a status and whether a reboot is required. Network discovery reports found devices by IP, MAC, hostname, guessed OS, open ports and vendor, ready to convert into assets.
Deploy patches and run commands
Group devices into a patch deployment with a severity filter, a schedule and an optional automatic reboot. For ad hoc work, queue a remote command in PowerShell or a shell; the agent runs it and reports back the exit code and output.
Sync Microsoft 365
With Azure credentials configured, a Microsoft Graph client-credentials sync pulls Intune managed devices into the discovery list and reports the directory user count. When no credentials are set it returns a clear error rather than a fake success.
Already live in the product
Running in production today: agent-fed inventory, patch, and discovery data, plus Microsoft 365 sync. Protected app route: /rmm
A worked example
A typical 250-seat accounting firm rolls the agent to every workstation. Inventory comes back showing 38 distinct applications, two of which match existing licence records. The patch feed lists 120 missing updates across the fleet, 17 of them critical; the admin builds a deployment targeting the workstation group, filtered to critical and important severities, scheduled for Saturday night with automatic reboot allowed. A discovery sweep also surfaces an unmanaged NAS by IP, MAC and vendor — converted into a tracked asset on the spot — and the Microsoft 365 sync reconciles the Intune device list into the same console: one endpoint picture instead of four spreadsheets.
What teams can do here
- Step 1
- Deploy the agent
- Step 2
- Ingest inventory and patch state
- Step 3
- Sync Microsoft 365
- Step 4
- Act from a unified feed
Frequently asked questions
See also: Guide: what is RMM and how it works · Guide: comparing RMM tools · Guide: remote desktop software options · Patch management · Remote access
One agent feeding one honest endpoint picture
Software inventory, missing patches, discovery and remote commands attach to the same device record — with scheduled ring deployments to close what they find.
