Hello,
I am having trouble getting VirtualHere to isolate USB devices to individual RDP sessions on a Windows Remote Desktop Session Host. I need devices authenticated and bound to the current RDP session, but the behavior differs depending on how the client is launched and I cannot find a reliable way to achieve per‑session isolation.
Environment
Windows Server running Remote Desktop Session Host (tested on windows server 2022 and windows server 2025). Multiple concurrent RDP user sessions. VirtualHere Server and Client are on the same network. Please advise if you need exact OS build numbers and I will provide them. My virtualhere version on the terminal server (virtual here clients) system is 6.0.1
Problem summary
When I install and run the VirtualHere client as a Windows service the client process is available in each user session and I can open the VirtualHere UI inside sessions, but any devices exposed by the service appear to be shared across all sessions and are not isolated to a single RDP session. Isolation Mode does not appear to be available.
When I run the VirtualHere client as a normal per‑user process (not a service) and (with or without) Session Isolation in the client UI the client will not start in more than one user session concurrently. In this case I cannot run a separate client instance for each user session, so I cannot attach devices independently per session.
When I run the virtualhere client software as an admin and try to manage the devices for the rdp sessions, I cannot see any running rdp sessions on the server, there by I cannot send a device to a rdp session.
What I have already checked
I verified the Session Isolation option in the client UI under Advanced Settings. I confirmed RemoteFX is turned off per the documentation, after this did not work I tried allowing remote FX on the Windows server 2022, and this did not change anything after a reboot. I can provide client and server logs and the service vhui.ini or config.ini on request.
Basically I thin I have tried every configuration, but I seem to fail every time.
Before you ask I purchased two different licenses for two different virtual here servers, and I have tried licensing them and not licensing them, both does not work.
.
You do not run the virtualhere client in the rdp session, nothing runs inside the session.
You run the client on the machine that runs the remote desktop terminal. I.e the machine that runs mstsc.exe (Microsoft Terminal Services Client). When you do that the virtualhere client (when running in RDP mode) will look for active client sessions on the machine and list them so that when you right click on the device it will show "Send To" and the sessions will be listed there. When you send to the session the device is passed across RDP to appear as a USB device attached just for that session to the Remote Desktop USB Hub in device manager.
The virtualhere server can run wherever you want on the network (or even on the same machine as the client)
The virtual here server runs…
The virtual here server runs on a Linux Debian 13 with KDE; the Linux machine is acting as an RDP client. If I'm understanding you right, I should use a VirtualHere client to connect the client on my Linux machine to the server on the Windows machine, am I right?
.
OK, thats not a supported scenario by virtualhere for rdp isolation.