PNT-RMMS Specific Terms
4.1 What the Agent Does
By installing the PNT-RMMS Agent on a device, you acknowledge that the Agent:
- Installs and runs a Windows Service that starts automatically at boot.
- Collects hardware inventory (CPU, RAM, drives, system make/model/serial), Windows version and build, current resource utilization, and the device's most-recently-observed public IP, and reports these to the portal periodically.
- Authenticates to the portal using an encrypted device token issued at activation; the token is bound to your subscription's seat count.
- Forwards Warning-and-above application logs to the portal for centralized troubleshooting.
- Submits a brief summary at the end of each remote-control session containing the path that connected (LAN-direct / direct over WAN / relay), per-session bytes, and timestamps. Screen content is not stored.
4.2 Remote Access Consent
The Agent allows authorized operators in your company to initiate remote-control sessions. By installing it, you consent to the following capabilities being available during a session:
- Screen viewing. Real-time forwarding of the device's display to the operator's browser, including all attached monitors.
- Mouse and keyboard input. The operator can move the cursor and type on the device, including key combinations reserved by Windows such as Ctrl+Alt+Del.
- Command execution with SYSTEM privilege. An operator can run arbitrary PowerShell commands on the device at the highest privilege level Windows provides. This is broader than the access held by a signed-in administrator: it can read, modify or delete any file, install or remove software, and change Windows configuration and security settings. This capability is available only for companies where an owner has enabled it, and every command executed is recorded in the audit trail described in section 4.7.
- File browsing and transfer. The operator can browse the device's file system and view directory listings, and transfer files in either direction — up to 500 MB per file, up to 5 concurrent transfers.
- Clipboard synchronization. Text and image content can be read from and written to the device's clipboard.
- Print redirection. Print jobs originating on the device during a session can be routed to the operator's local printer.
- Power control. The operator can restart or shut down the device, including while work is unsaved.
- In-session chat. A chat window for ad-hoc messaging during the session.
- Cross-session input (optional). Forwarding of input to the Windows login screen, locked workstation, and UAC consent prompts. This requires the two installer-time toggles to be enabled and is off by default. Enabling either one disables a Windows protection machine-wide, for every account on that device, and for as long as the setting remains on — see the End User License Agreement presented during installation.
What the Agent will not do. Capture audio — neither microphone input nor the sound the device is playing — capture the webcam, or act on more than one device at a time, since cross-device "fleet commands" are not part of the product today. The Agent has no dedicated feature for editing Windows services or the registry, although the command-execution capability above is general enough to do so where a company has enabled it.
Approval mode. Every device operates in one of two modes: Automatic (an authorised operator connects without asking) or User-Approved (a prompt appears on the device and must be accepted before each session). Automatic is the default. The mode is set on the device itself, through the PNT RMMS Agent installed on it, by someone with administrative rights to that device; the portal displays the mode each device reports but does not currently set it. Note also that User-Approved mode cannot obtain approval when nobody is signed in, so a connection to the sign-in screen may proceed without a prompt.
While a session is active, the Agent displays an on-screen indicator naming the connected operator. That indicator is a notification, not a consent mechanism: in Automatic mode the session proceeds whether or not anyone acknowledges it.
4.3 Connection Paths
The Agent attempts a direct connection first using WebRTC. When the operator's browser and the device are on the same local network, the connection runs LAN-direct (no internet bandwidth used by RMMS). When direct over the public internet succeeds, traffic flows peer-to-peer with no detour through our servers. When neither is possible, the session falls back to our PNT-operated relay servers (TLS over WSS). All paths are encrypted in transit. We do not operate or use third-party TURN servers.
What the relay path means for confidentiality. On the relay path the encrypted connection terminates at our relay server rather than passing through it opaquely. Session content — including screen images and keystrokes — is therefore present in unencrypted form in that server's memory while it is being relayed between the device and the operator. It is not written to disk there and is not retained after the session ends, and the relay is operated by us rather than by a third party. This is a property of how relaying works, and it applies whenever a direct connection cannot be established. If your use case requires that no intermediary can technically observe session content, use devices and networks where the direct path succeeds.
4.4 RMMS Portal & Company Roles
Subscribers create a company in the portal and invite team members at one of three roles:
- CustomerOwner — manages subscriptions, members, and devices for the company. Can activate, reactivate, move, and deactivate devices.
- CustomerMember — can connect to devices and activate new ones, but cannot change billing or membership.
- CustomerViewer — read-only access to the device list and status; cannot connect or activate.
4.5 Automatic Updates
The Agent periodically checks the portal for new releases and can install them automatically. Each release is checked against the portal's hash manifest before it runs, and only Authenticode-signed installers issued by Pro Nova Technologies Inc. will execute. You can review available versions at any time from the on-device Agent.
4.6 Subscription Resilience
If your subscription lapses (cancellation, payment failure, or temporary suspension), the Agent stops accepting connections and the portal blocks new sessions. Device tokens are preserved for 90 days from the lapse — if you renew within that window, your fleet automatically reactivates up to your seat cap with no per-device action required. After 90 days, tokens are wiped and devices must be re-activated. Manually-deactivated devices retain their tokens for 180 days.
4.7 Audit Trail
The portal logs authentication events (sign-ins, MFA enrollment, role changes), subscription changes, device activations and deactivations, and per-session summaries (path used, bytes, timestamps). These logs are visible to company owners and to PNT support staff, and are retained for 12 months by default.