Skip to main content

Windows Remote Desktop (Splashtop) Policy

Updated today

The Windows Remote Desktop Windows Policy allows administrators to manage whether Splashtop remote access is allowed or restricted on Windows devices.
This policy is useful for organizations that want to control remote support or remote access tools across BYOD and corporate-owned Windows endpoints.

Use this policy to enforce company rules on remote access, compliance requirements, and endpoint security controls.


Requirements

  • Windows 10 or later


Overview

Splashtop is a popular remote access tool used for IT support, remote work, and secure endpoint access.
This policy enables IT administrators to centrally manage whether Splashtop functionality is permitted on the device.

Blocking or restricting remote access tools can help organizations:

  • Maintain compliance with security frameworks

  • Reduce the attack surface

  • Prevent unauthorized remote access

  • Enforce approved remote support workflows


Configurable Settings

Enable Splashtop

This setting determines whether Splashtop functionality is allowed on the device.

Options include:

  • True – Splashtop is allowed

  • False – Splashtop is blocked or disabled

  • Null – Use Windows’ system default

When set to False, Splashtop functionality is prevented from running on the device.
This ensures no remote control sessions can be initiated through Splashtop.

Minimum Requirements: Windows 10+


Best Practices

  • Set Enable Splashtop = False on high-security or compliance-restricted endpoints.

  • Permit Splashtop only on devices that require remote support access.

  • Combine this policy with Windows Application Blacklist/Whitelist Policies for stricter enforcement.

  • Use Device Groups (e.g., Support Team, Field Technicians) to allow Splashtop only where needed.


How to Configure

  1. Open the Swif Admin Console

  2. Navigate to Policies → Create New Policy

  3. Select Windows Remote Desktop Windows Policy

  4. Choose whether to allow or block Splashtop

  5. Click Continue

  6. Assign the policy to device groups

  7. Save and apply

Devices will enforce the policy after their next MDM sync.


Troubleshooting

Splashtop is still accessible after blocking the policy

  • Ensure the device has been checked in recently

  • Confirm no local admin has manually reinstalled or re-enabled Splashtop

  • Pair this policy with Windows Application Control for stricter enforcement

Splashtop sessions fail to connect when enabled

  • Ensure network firewall rules allow Splashtop traffic

  • Verify Splashtop Streamer is installed and configured correctly

  • Check antivirus or endpoint protection logs for blocked activity

Did this answer your question?