USB Redirector TS Edition: Remote USB Access for Terminal Servers

How to Set Up USB Redirector TS Edition on Windows Server

Overview

This guide shows step-by-step how to install and configure USB Redirector TS Edition on a Windows Server to enable remote USB device access for Terminal Services / Remote Desktop Services sessions.

Prerequisites

  • A Windows Server (2012 R2, 2016, 2019, 2022 — assume latest supported OS).
  • Administrative rights on the server.
  • USB Redirector TS Edition installer (downloaded from vendor).
  • Remote Desktop Services (RDS) or Terminal Services role installed if you plan to use RDS sessions.
  • Client machines with USB Redirector client (if connecting from remote endpoints).
  • Network connectivity between server and clients.
  • Ensure any required ports are allowed in the server firewall (default TCP port 3200; confirm in product docs).

Step 1 — Prepare the server

  1. Log in to the server with an administrative account.
  2. Install RDS/Terminal Services role if you intend to use multi-user remote sessions:
    • Open Server Manager → Add Roles and Features → Remote Desktop Services → follow prompts to install required services.
  3. Disable conflicting USB drivers/tools that may block exclusive access to USB devices.

Step 2 — Install USB Redirector TS Edition

  1. Run the USB Redirector TS Edition installer as Administrator.
  2. Accept the license and follow installer prompts.
  3. When asked, choose the “TS Edition” integration option.
  4. Allow the installer to add the kernel-mode driver if prompted (required to redirect many device types).
  5. Reboot the server if the installer requests it.

Step 3 — Configure server-side service

  1. After reboot, open the USB Redirector management console (or Services snap-in if provided).
  2. Ensure the USB Redirector server/service is set to start automatically.
  3. In the management console, configure connection settings:
    • Listen port (default 3200) — change only if it conflicts with other services.
    • Authentication method — enable password or Windows authentication per your security policy.
    • Encryption — enable TLS if available for secure transport.
  4. If the server is behind a firewall or NAT, configure port forwarding for the chosen port.

Step 4 — Configure Remote Desktop Services integration

  1. In RDS deployment settings, ensure device redirection policies do not conflict:
    • Open Group Policy Editor (gpedit.msc) or Domain GPO for RDS hosts.
    • Navigate to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection.
    • Make sure policies like “Do not allow supported Plug and Play device redirection” are set to Disabled or Not Configured.
  2. If using session collection settings, confirm the USB Redirector TS plugin/driver is available to session hosts.

Step 5 — Install and configure client components

  1. On the client workstation (the machine that has the physical USB device), install the USB Redirector client or Local Agent.
  2. Run the client application and add the USB device you want to share. Typically this involves:
    • Selecting the physical USB device from a list.
    • Marking it as “Share” or “Publish to server.”
  3. Configure the client to connect to the server’s IP/hostname and port. Provide authentication credentials as required.
  4. Test the share: confirm device status shows as “Shared” on the client.

Step 6 — Connect and use the redirected USB device in an RDS session

  1. From an RDS session on the server or from a remote user session, open the USB Redirector management console or client plugin within the session.
  2. Locate the published/shared device (should appear in the device list).
  3. Connect to the device — the device will be attached to the user’s session and behave like a locally connected USB device.
  4. Verify device functionality in the session (e.g., open scanner software, access mass storage, test dongle-licensed apps).

Troubleshooting

  • Device not visible: confirm client shows device as shared and server shows incoming connection; check

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *