Windows - Software Lifecycle - Restart Splashtop Streamer Service

What the Splashtop Streamer restart Worklet does

This Automox Worklet™ monitors the SRServer process, which is the core component required for Splashtop remote connectivity on Windows endpoints. If the process is not detected, the Worklet automatically restarts the Splashtop Streamer service to restore functionality.

The Worklet performs three key actions: checking whether the SRServer process is currently running, restarting the Splashtop Streamer service using Windows service management, and verifying that the process successfully starts. A 10-second wait allows time for the service to fully initialize before the verification check.

This approach verifies that remote connectivity is restored without requiring manual intervention or endpoint restarts, minimizing disruption to IT operations teams relying on Splashtop for remote support.

Why restart the Splashtop Streamer service

Splashtop is a critical remote access platform used by IT operations teams to manage Windows endpoints across distributed environments. When the Splashtop Streamer service stops running, remote sessions become unavailable, preventing support teams from accessing endpoints remotely.

Service failures can occur due to application crashes, Windows updates, or resource constraints. This Worklet detects these failures automatically and restores connectivity by restarting the service, eliminating the need for manual intervention or waiting for the endpoint owner to restart their machine.

By maintaining continuous Splashtop connectivity, you reduce mean time to resolution (MTTR) for endpoint issues, improve operational efficiency, and keep your support team can access endpoints whenever needed.

How Splashtop Streamer service restart works

1. Evaluation phase: The Worklet checks for the presence of the SRServer process on the endpoint. If the process is running, the endpoint is compliant and no action is needed. If the process is not detected, the endpoint is flagged for remediation.

2. Remediation phase: The Worklet restarts the Splashtop Streamer Service using PowerShell's Restart-Service command with the Force flag. After restarting, the Worklet waits 10 seconds for the service to initialize, then verifies that the SRServer process is running. If the process starts successfully, remediation succeeds; if the process fails to start, the Worklet reports the failure.

Splashtop Streamer restart requirements

• Splashtop Streamer application must be installed on the Windows endpoint

• Windows 7 or later (Server or Workstation editions)

• PowerShell 2.0 or later available on the endpoint

• Administrative privileges required to restart Windows services

Expected Splashtop connectivity after remediation

After the Worklet completes remediation, the SRServer process should be running and the Splashtop Streamer service should be in the running state. You can verify this by attempting to establish a remote session to the endpoint through the Splashtop console or by checking the Services application on the endpoint (services.msc) and confirming that the Splashtop Streamer Service is listed with a status of Running.

Remote access should be fully restored, allowing IT operations teams to connect to the endpoint for support, troubleshooting, or remote administration without additional user intervention.

How to validate restart splashtop streamer service changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for restart splashtop streamer service.

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 Get-Process, Write-Output.

4. Validate remediation effects from script operations such as Write-Output, Get-Service, Restart-Service, then rerun evaluation for compliance.