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

What the Splashtop Business 32-bit installer does

This Automox Worklet™ installs the Splashtop Business 32-bit Streamer on Windows endpoints. Splashtop Business is the attended and unattended remote support client that lets help-desk and support engineers connect into a workstation or server from any location. The Worklet pairs an idempotent evaluation phase with a silent MSI remediation, so the policy is safe to run on a recurring schedule across the Windows fleet.

Detection runs against both 64-bit and 32-bit registry uninstall hives. On a 64-bit OS, the Worklet opens the Registry64 view of HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and then enumerates HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall, matching any DisplayName that contains "Splashtop Business." On a 32-bit OS, it walks the native HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall hive. Covering both views matters because the 32-bit MSI registers under Wow6432Node on 64-bit Windows, while a legacy 32-bit-only host registers under the native hive.

Remediation pulls Splashtop_Business_x86.msi from the Automox file cache and hands it to msiexec.exe with /norestart, /qn, /i, and /l*v arguments. The installer writes a verbose log to C:\ProgramData\amagent\Splashtop_Business_x86_install.log and the Worklet waits up to 300 seconds for the process to exit. After completion, the MSI payload is removed from the working directory and the Worklet reports the installer exit code back to Automox.

Why deploy Splashtop Business through Automox

Remote support coverage is binary at the endpoint level. Either the Streamer is installed and reachable when the user calls in, or the help-desk spends the first part of every ticket walking a user through an install on a machine they cannot remote into. Coverage gaps tend to appear in inconvenient places: a remote employee on a fresh image, a contractor laptop that skipped the onboarding policy, or a kiosk that was reset over the weekend. The operational cost shows up as inflated handle time and missed SLAs.

Apply this Worklet to the help-desk-managed Windows device group on a weekly cadence. The dual-hive registry check confirms the 32-bit Streamer is present on every evaluation, and a freshly imaged or rebuilt host is brought back into support coverage on the next policy run rather than after the next ticket.

How Splashtop Business 32-bit installation works

1. Evaluation phase: The Worklet detects whether the OS is 64-bit, then enumerates DisplayName values under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall (Registry64 view) and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall. On a 32-bit OS it inspects HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall directly. A DisplayName match on "Splashtop Business" in any hive exits 0 and marks the endpoint compliant. No match exits 1, which queues the endpoint for remediation.

2. Remediation phase: The Worklet downloads Splashtop_Business_x86.msi from the Automox file cache endpoint (api.automox.com/api/cache, downloadLatestVersion for the Splashtop_Business 32-bit Windows package) into the script working directory, then runs msiexec.exe with the arguments /norestart /qn /i <path>\Splashtop_Business_x86.msi /l*v C:\ProgramData\amagent\Splashtop_Business_x86_install.log. The Worklet waits 300 seconds for the process to complete, deletes the MSI from disk, and exits 0 on success or 1 on timeout or a non-zero installer exit code other than 3010 (reboot pending).

Splashtop Business deployment requirements

• Windows 10, Windows 11, or Windows Server endpoint with the Automox agent installed and online (workstation or server device type)

• SYSTEM-level execution context, which the Automox agent provides by default

• Outbound HTTPS reachability to api.automox.com so the agent can download the cached Splashtop_Business_x86.msi payload

• Write access to C:\ProgramData\amagent\ for the msiexec verbose log (the Automox agent already owns this directory)

• A valid Splashtop Business deployment code or team license bound to the cached installer if you replace the default Automox-cached binary with a tenant-specific one

• No interactive user prompt is required; the /qn switch suppresses installer UI and /norestart suppresses automatic reboots

Expected state after Splashtop Business installation

After remediation, msiexec.exe has finished installing the Splashtop Business Streamer, a DisplayName entry for "Splashtop Business" appears under HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall on 64-bit Windows (or under the native HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall hive on 32-bit Windows), and the MSI verbose log is available at C:\ProgramData\amagent\Splashtop_Business_x86_install.log for review.

Validate by running Get-ItemProperty 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object DisplayName -like 'Splashtop Business*' and confirming a single entry returns. Review the verbose log for any non-zero return values from custom actions if the install reports failure. On the next Automox sync, the policy reports the endpoint as compliant and the Worklet exits 0 during evaluation without re-running msiexec, because the DisplayName is already present. Subsequent runs are no-ops until an administrator removes the Streamer, at which point the next evaluation flags the endpoint and remediation reinstalls the client.