In a non-persistent Citrix Virtual Desktop environment running Windows 11 VDAs, users connecting via Dell Wyse 5070 and 3000 series thin clients experience issues when moving between physical terminals:

• The desktop session roams successfully to the new thin client endpoint.

• The local USB scanner attached to the new terminal is not recognized or available inside the active VDI session.

• Users are forced to manually disconnect and reconnect the Citrix session or restart the physical scanner to restore functionality.

While the ICA session transfers smoothly during session roaming, the local USB stack on the target thin client fails to automatically re-bind the scanner device handle to the existing VDA session context without a refreshed handshake or device re-enumeration.

To resolve USB scanner redirection issues during session roaming, apply the following policy and client-side configuration changes:

1. Enable Server-Side Citrix USB Redirection Policies

In Citrix Web Studio, ensure the following policies are configured and applied to your target VDI Delivery Group:

• Client USB Device Redirection: Set to Allowed.

• Client Plug and Play Device Redirection: Set to Allowed.

2. Configure USB Auto-Connect Rules (VID/PID Filtering)

Implement explicit auto-connect rules via Citrix Workspace App Group Policy (GPO) using the specific Vendor ID (VID) and Product ID (PID) of the scanner model:

• Add a rule directing Citrix Workspace App to automatically connect the scanner device whenever a hotplug or session transfer event occurs.

3. Adjust Local Dell Wyse Thin Client USB Settings

On your Dell Wyse 5070 and 3000 series thin clients (Wyse ThinOS, ThinLinux, or Windows IoT):

• Configure the local terminal policy so that attached USB imaging/scanner devices automatically connect and redirect to active sessions upon startup and reconnect events.

When users roam an active non-persistent Windows 11 VDI session between Dell Wyse thin clients, attached USB scanners fail to re-initialize automatically.
This occurs because the session moves without re-binding the scanner's local USB stack, requiring a manual disconnect/reconnect or hardware restart to function.