Linux - Software Lifecycle - Uninstall Splashtop Streamer

What the Splashtop Streamer Uninstaller does

This Automox Worklet™ removes Splashtop Streamer remote access software from Linux endpoints. The Worklet takes a comprehensive approach to removal, checking multiple installation methods and cleaning up thoroughly.

The Worklet first stops the Splashtop Streamer service using both systemctl and the traditional service command. If an official uninstaller exists at /opt/splashtop-streamer/uninstall.sh, the Worklet runs it in silent mode. The Worklet then removes any packages through the system's package manager.

Finally, the Worklet deletes residual files and directories including /opt/splashtop-streamer, /etc/init.d/splashtop-streamer, /var/log/splashtop*, /var/lib/splashtop*, and /etc/splashtop*. This thorough cleanup removes configuration files and logs that would otherwise remain after standard package removal.

Why remove Splashtop Streamer from your endpoints

Remote access software provides convenient support capabilities but creates security risks when not centrally managed. Unauthorized Splashtop installations may allow remote connections that bypass your organization's security controls and audit logging.

Organizations often standardize on a single remote support tool for compliance, licensing, and management purposes. This Worklet helps you remove Splashtop installations as part of a migration or to enforce policies restricting remote access software.

The thorough cleanup approach prevents remnants from causing confusion or conflicts with other software. Removing log files also eliminates any sensitive data that may have been captured during remote sessions.

How Splashtop Streamer removal works

1. Evaluation phase: The Worklet checks for Splashtop Streamer using multiple detection methods: the splashtop-streamer command, the /opt/splashtop-streamer directory, the /etc/init.d/splashtop-streamer service file, dpkg package listings, and rpm package queries. If any of these indicators are present, the endpoint is flagged for remediation.

2. Remediation phase: The Worklet stops the Splashtop service, runs the official uninstaller if available, removes packages using apt-get, dpkg, dnf, yum, zypper, or rpm as appropriate, and deletes all residual directories and files. A final verification confirms complete removal.

Splashtop Streamer removal requirements

• Linux endpoint with dpkg (Debian/Ubuntu) or rpm (RHEL/CentOS/Fedora/SUSE) package manager

• Root or sudo privileges for service management, package removal, and file deletion

• No active remote sessions through Splashtop (connections will be terminated)

Expected state after Splashtop Streamer removal

After successful remediation, Splashtop Streamer is completely removed from the endpoint. The splashtop-streamer command is no longer available, the /opt/splashtop-streamer directory is deleted, and no Splashtop packages appear in the system's package database.

The Splashtop service no longer runs, and the endpoint does not accept incoming Splashtop connections. All configuration files, logs, and cached data are removed. Users cannot reconnect through Splashtop until the software is manually reinstalled.

How to validate uninstall splashtop streamer e changes

1. Run this Worklet on a pilot Linux endpoint and review evaluation output for uninstall splashtop streamer e.

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 set, exit, else.

4. Validate remediation effects from script operations such as set, log, exit, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for uninstall splashtop streamer e. 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 set, exit, else and remediation operations such as set, log, exit. Use these indicators to verify that endpoint changes match intended policy outcomes.