How to Install Splashtop Business on Multiple Computers

Splashtop Business is a remote desktop solution used by IT teams, managed service providers, and businesses that need reliable access to computers across multiple locations. Installing it across several machines isn't complicated, but the process involves a few moving parts — and how smoothly it goes depends on your plan type, the number of endpoints, and how your network environment is set up.

What You're Actually Installing (and Where)

Splashtop Business has two distinct components, and understanding the difference matters when deploying across multiple machines:

• Splashtop Business App — installed on the device you're accessing from (your laptop, tablet, or phone). This is the client-side interface.
• Splashtop Streamer — installed on the computers you want to access remotely. This runs as a background service on each target machine.

For a multi-computer deployment, you'll primarily be installing the Streamer on every endpoint you want to reach. The Business App only needs to be on the devices belonging to the people doing the remote accessing.

Step-by-Step: Installing the Streamer on Multiple Machines

1. Log In to the Splashtop Web Console

Start at the Splashtop web portal (web.splashtop.com or your team's assigned portal). This is where you manage computers, users, and deployment settings centrally. You'll need admin-level access to your Splashtop Business account.

2. Generate a Deployment Package or Use the Direct Download Link

Splashtop provides a deployment package from within the admin console. This pre-configured installer already contains your account credentials embedded, which means each machine that runs it will automatically register to your team's account — no manual login required on every endpoint.

This is the key feature that makes multi-machine deployment practical. Without it, you'd need to manually authenticate every single install.

3. Choose Your Deployment Method

How you actually push the installer to each machine depends on your environment:

For larger deployments, the silent install method is widely used. Splashtop's Streamer supports command-line flags that suppress the installation interface, making it suitable for batch scripting or inclusion in software deployment pipelines.

4. Confirm Each Machine Appears in Your Console

After the Streamer installs and the machine connects to the internet, it should appear in your computer list inside the web console or Business App. If a machine doesn't show up, common causes include:

• Firewall rules blocking Splashtop's outbound ports
• The Streamer running under a limited user account without sufficient permissions
• The machine not yet connected to the internet at time of install

🖥️ Each computer is listed by name and shows its online/offline status in real time.

Licensing and Seat Limits Across Multiple Machines

This is where deployments vary significantly. Splashtop Business plans are structured around the number of concurrent users or managed computers, depending on the plan tier:

• Splashtop Business Access plans typically limit concurrent remote sessions
• Splashtop Remote Support and Enterprise plans are designed for managing large numbers of unattended endpoints

You can install the Streamer on more machines than your plan's seat count covers, but your ability to actively connect to those machines at any given time is gated by your license. Understanding the distinction between installed endpoints and licensed concurrent connections is important before a large rollout.

Cross-Platform Considerations

Splashtop supports Windows, macOS, Linux, iOS, and Android, but the deployment experience isn't identical across all platforms:

• Windows offers the most robust deployment options, including GPO and MSI-based silent installs
• macOS requires additional permissions (Screen Recording, Accessibility access) that must be granted manually or pushed via MDM (Mobile Device Management) — this step is easy to miss during bulk deployments
• Linux support varies by distribution and is more limited in terms of automated deployment tooling

🔧 macOS deployments in particular often catch teams off guard. Granting the necessary system permissions is a per-machine step that can't always be scripted without an MDM solution like Jamf or Kandji.

Variables That Shape Your Deployment Experience

No two rollouts look exactly the same. The factors that most affect how your installation goes include:

• Number of machines — a handful of computers versus hundreds changes the right approach entirely
• Operating systems in your environment — mixed OS environments add complexity
• Whether endpoints are on-site or remote — remote machines require users to initiate or assist with install unless you already have another remote tool in place
• Your existing IT infrastructure — Active Directory, RMM tools, or MDM platforms unlock deployment options that aren't available in simpler setups
• Your Splashtop plan — not all plans support the same deployment features or endpoint quantities

Some teams complete a 10-machine rollout in under an hour. Others managing 200+ mixed-OS endpoints across distributed locations build a multi-day deployment plan. The technical steps are the same — the scale and environment are what determine how involved the process actually gets.