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.
- Mouse and keyboard input. The operator can move the cursor and type on the device.
- File transfer. Up to 500 MB per file in either direction, up to 5 concurrent transfers.
- Clipboard synchronization. Text and image content can be shared between the device and the operator's browser.
- Print redirection. Print jobs originating on the device during a session can be routed to the operator's local printer.
- 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.
What the Agent will not do. Run arbitrary commands, edit Windows services or the registry remotely, browse files outside an explicit transfer, capture audio or webcam, or record sessions. Cross-device "fleet commands" are not part of the product today.
You can switch any device between Automatic mode (no per-session approval needed) and User-Approved mode (a prompt appears on the device before each session) at any time from the portal or the on-device Agent.
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.
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.