Windows - Software - Install Splashtop Business (32-Bit)

What the Splashtop Business Installer does

This Automox Worklet™ installs Splashtop Business on Windows endpoints using the 32-bit MSI installer. Splashtop Business provides remote desktop access and support capabilities, enabling IT teams to remotely connect to and troubleshoot endpoints from any location.

The Worklet checks for existing Splashtop Business installations in both 64-bit and 32-bit registry paths before proceeding. This detection identifies existing installations regardless of their architecture, preventing duplicate deployments.

During remediation, the Worklet downloads the 32-bit MSI installer from the Automox API cache, executes msiexec with /qn and /norestart flags, logs the installation to C:\ProgramData\amagent\Splashtop_Business_x86_install.log, and removes the installer after completion. A five-minute timeout prevents installations from hanging.

Why deploy Splashtop Business through Automox

Splashtop Business enables IT support teams to provide remote assistance to users regardless of their location. Manual deployment of remote access tools across distributed endpoints requires significant IT resources and delays support readiness.

Automating Splashtop deployment through this Worklet standardizes your remote support infrastructure. You can deploy the latest version from a verified Automox cache URL to all targeted endpoints, preparing your organization for remote support scenarios before issues arise.

The Worklet provides visibility into which endpoints have Splashtop Business installed, helping you track remote support coverage and identify endpoints that may need the client for upcoming support engagements.

How Splashtop Business installation works

1. Evaluation phase: The Worklet searches Windows registry uninstall keys for "Splashtop Business" in both 64-bit and 32-bit registry paths. If found, the endpoint is marked compliant. If not found, the endpoint proceeds to remediation.

2. Remediation phase: The Worklet downloads Splashtop_Business_x86.msi from the Automox API cache, executes msiexec with /qn, /norestart, and logging arguments, waits up to five minutes for completion, and removes the installer file after installation.

Splashtop Business installation requirements

• Windows workstation or server endpoint

• Network connectivity to download from api.automox.com

• Administrative privileges for MSI installation

• Splashtop Business license for production use

• No user configuration required - all parameters are predefined

Expected state after Splashtop Business installation

After successful remediation, Splashtop Business appears in the Windows Programs list and registry uninstall keys. The Splashtop streamer service starts automatically, making the endpoint available for remote connections from authorized support personnel.

Installation logs are saved to C:\ProgramData\amagent\Splashtop_Business_x86_install.log for troubleshooting. The installer file is automatically removed after installation. Subsequent Worklet runs will detect the existing installation and exit without action.

How to validate install splashtop business (32-bit) changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install splashtop business (32-bit).

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as Get-ChildItem, Get-ItemProperty, Where-Object, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install splashtop business (32-bit). This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Write-Output, Get-ChildItem, Get-ItemProperty and remediation operations such as Get-ChildItem, Get-ItemProperty, Where-Object. Use these indicators to verify that endpoint changes match intended policy outcomes.