New Remote Control Is Coming – Powered by Splashtop
This update applies to customers who currently have access to Remote Control via Automox Assist.
Launch date: January 14
What’s changing: Automox is launching a new Remote Control (RC) experience powered by Splashtop. Our current Remote Control feature will be deprecated.
What to Expect on January 14
- Splashtop becomes Automox’s Remote Control solution.
- Legacy Remote Control will be deprecated.
- Rollout will occur in batches throughout the day.
- All customers will be enabled by end of day (EOD).
Once enabled, you’ll see a new Settings → Remote Control section in the Automox console.
What You Can Do Before January 14
1. Confirm your Automox Agent version
Remote Control requires Agent version 2.4.33 or later.
2. Install the Splashtop RMM App app (Admin machine)
Admins who initiate remote sessions must install the Splashtop RMM App ahead of time.
(Links available in the console and Quick Start Guide - Using Remote Control with Splashtop.)
What Happens After RC Is Live
Streamer installation is required
To use Remote Control, the Splashtop Streamer must be installed on your endpoints.
You control when and how this happens:
- Org-wide install (recommended)
- Per-device install from the Device Details page
Platform Behavior (Important)
Windows
- Streamer installs silently
- No end-user interaction required
macOS
- Streamer installs silently
- End users will be prompted to grant required permissions:
- Accessibility
- Screen Recording / Remote Desktop
- Microphone (optional)
- Full Disk Access (optional)
- Until permissions are granted, Remote Control will not work
For step-by-step instructions, see macOS Permissions – What’s Required and Why.
Installing the Streamer (Org-Wide)
- Go to Settings → Remote Control
- Click Install Streamer
- Confirm the action
What happens next:
- Online devices begin installing immediately
- Offline devices install when they next check in
- Device status updates appear under Device Details → Remote Control
Org-wide Streamer install can be initiated once every 24 hours. This allows time for online and offline devices to complete installation and prevents repeated retries.
