Feature Matrix

This appendix is a single-page index of what NetLock RMM does. It groups every feature into Console, server, and agent areas, records platform support where it varies, and links to the chapter that documents the feature in full. Use it to answer "does the product do X, and where do I read about it?" — not as a configuration reference. For mechanics, follow the cross-links.

Three conventions apply throughout:

• Yes / No in a platform column means the feature is or is not available on that operating system.
• A dash (—) means the feature does not apply to that platform.
• Where a column names a tool or shell instead of Yes (for example PowerShell), that is the platform-specific implementation.

Note: This matrix summarises shipped behaviour. When a feature area carries deployment-specific or licensing-specific limits, the linked chapter is authoritative.

X.7.1 Console features

The web Console is the single operator surface. The features below are available regardless of agent platform; they are properties of the Console itself.

Optional module: The Ticket System applies only when it is enabled in Settings → Ticket System. See Chapter 10.

The AI features are optional and require an LLM provider to be configured (see A.11). Two kinds exist: the general-purpose AI Chat page, and targeted per-feature assistants. The targeted integrations are the AI Assistant in the Scripts editor (which writes directly into a script), the AI Assistant on the Automations dialogs, the AI SQL Assistant in the Widget Editor, and the Analyze with AI action on event and audit details (which opens AI Chat with the entry pre-filled). See Chapter 13.

Whitelabeling options

Whitelabeling is broad enough to list separately. Each option below is configured under Settings → Whitelabeling and documented in A.6.

X.7.2 Server features

The server is the central service the Console reads from and agents report to. Self-hosted operators run it themselves; cloud operators do not.

Self-hosted only: Server architecture and role splitting apply to self-hosted deployments. Cloud deployments delegate server operation to the hosted operations team.

X.7.3 Device management and remote access

These features act on managed devices through the agent. Platform columns record where each is available.

Remote Screen Control delivers H.264 video over the relay when available and falls back to JPEG frames over SignalR when it cannot. The product does not use VNC or RDP. Full detail, including session switching, recording, and unattended access, is in Chapter 3 and A.7. Linux support is experimental and depends on the device's display server (X11 or Wayland); its prerequisites, the desktop/display-server support matrix, and how unattended access works on Wayland are covered in X.8.5.

The Relay Server provides end-to-end-encrypted TCP tunnels and jump-host access for network devices without an agent. See Chapter 9.

X.7.4 Security and control

Antivirus management covers Microsoft Defender only; third-party antivirus products are not managed. Application Control and Device Control are library features under Collections — see Chapter 8.6 and Chapter 8.7. A ruleset or whitelist reaches devices only through a policy; see Chapter 6.

X.7.5 Software and patching

The App Hub is a catalogue you pick from; installation runs through Software Deployment. See Chapter 8.5 and Chapter 8.8.

Patch Management is split across two surfaces. The /patch-management page is a global approval queue with a vulnerability view and SLA tracking; per-policy rollout rules — schedule, deployment rings, reboot, retry, notifications — live inside the policy editor. See Chapter 7 for the page and Chapter 6 for per-policy rollout.

X.7.6 Automation and monitoring

An automation is a condition → policy rule, not a workflow engine: there are no event triggers, no schedules, and no actions other than assigning one policy. Automations are evaluated in a fixed condition-type order — Device Name, then Internal IP, External IP, Domain, Group, Location, and Tenant — and the first matching condition type assigns its policy. Automations cannot run scripts, send notifications, or compose Sensors and Jobs. See Chapter 5 for the resolution model and Chapter 6 for what a policy contains.

Note: A device is assigned at most one policy at a time. Policies do not attach to tenants, locations, groups, or devices directly — attachment is routed exclusively through Automations.

Sensors not only alert but can run an action script on a threshold breach. Sensor and Job mechanics live in Chapter 8.2 and Chapter 8.3. Website uptime monitoring and the Port Scanner are documented in Chapter 9.

Tray icon

The agent exposes an optional tray application to end users on all three platforms. Its branding, button set, and App Hub window labels are configured per policy.

See Chapter 6 for tray-icon policy settings.

X.7.7 Platform support

The supported operating systems and architectures — together with additional community-confirmed platforms and the Linux prerequisites for Remote Screen Control under X11 and Wayland — are documented on their own page: Platform Support.

Related chapters

• Chapter 3 — Devices — device inventory and remote access.
• Chapter 5 — Automations — policy routing.
• Chapter 6 — Policies — what a policy configures.
• Chapter 7 — Patch Management — the approval queue.
• Chapter 8 — Collections — the reusable libraries.
• Chapter 9 — File Server & Monitoring — relay, uptime, port scanning.
• X.5 — Integration endpoints — external systems the product talks to.
• X.8 — Platform Support — supported operating systems and Linux Remote Screen Control prerequisites.