Can you share what your architecture looks like? Typically that message is seen when TCP 32111 is blocked between the Horizon Client and the Horizon Agent (or UAG/Security Server if tunneling is enabled) which is required for USB redirection.
UAG? Security Servers? Connection Servers? Is tunneling enabled/disabled on the connection servers? Load balancer?
Hi there. Thanks for your response.
There is no firewall between Client and Agent, so nothing stopping TCP32111 that I'm aware of. Other than the agent change, there is no architectural difference between our VDI Pool running on the older 6.x client and the VDI pool running on 7.4. It's also the same golden image, other than running on a different snapshot to install the newer agent.
Error occurs when on the LAN, which isn't using UAG.
3x Connection Servers (7.4.0-74004), all have tunnelling, load balanced via JetNexus. Load balancer seems to be only doing port 443 though it is the same rule for the old pools too.
Do you have VMware User Environment Manager deployed by any chance? There's an issue in Horizon agent 7.4 and 7.5 that might break USB redirection if UEM is installed.
If so, could you try again after creating a REG_DWORD registry value UemFlags in key HKLM\Software\VMware, Inc.\VMware VDM\Agent\USB, and setting it to 1?
What happens if you do telnet "ip of your connection server" 32111 from your VDI?
Since you have tunneling enabled the requirement is a little different (Make sure HTTPS Secure Tunnel is enabled on the connection server).
In addition to allowing TCP 443 from the Horizon Client to the connection server which you are already doing you need to allow TCP 32111 from the connection servers to the Horizon Agent.
Almost certain it isn't a firewall issue as we are getting this behaviour:
- USB Redirection not available on desktop
- If user disconnects session and reconnects on same physical machine, USB redirection then works
If we telnet to tcp32111 from a vdi desktop we just get Connection Refused. But we get this from both a working and failing machine.
It's also only failing 50% of the time from the same subnets to the same connections servers.
With regards to the UEM reg change - really weird behaviour we haven't seen before:
- Change made on golden image with new key added
- New snapshot taken
- Desktops recomposed
- login to recomposed desktop
- New reg key isn't there!
1 person found this helpful
If user disconnects session and reconnects on same physical machine, USB redirection then works
That pretty much points to the Horizon agent issue.
New reg key isn't there!
Sorry, can't help you there – I know just enough about Horizon to build the UEM integration, but I have no clue about Horizon infrastructure topics.
Maybe a bit premature, as we don't know for certain yet whether the USB redirection is blocked because of that Horizon agent issue, but that particular issue has been fixed in Horizon 7.6 (and you'll need the corresponding UEM 9.5 release to enable that fix.)
Is it possible to get this registry setting into the configuration without having to modify the golden image? I'd like to test it before committing to a recompose of the pool. Thanks.
janasrs If you are using a test VDI pool you could set the pool to "Never" for the "Delete or Refresh Machine on Logoff" pool setting. That will allow you to make a change to a VM in that pool and reboot it without it refreshing. Alternatively you can try putting the VM in Maintenance Mode prior to logging into the console and then rebooting after your change, then take the VM out of MM so you can test the connection. The first option is best, in my opinion.
hi did you check it ?
its working with you or now
Had the same issues. Disable the Agent Client Drive Redirection. You may also have to disable App Volumes as well.
Our Symantec Antivirus was causing the issue. This is what we had to do to resolve it.
Disable the Agent Client Drive Redirection. You may also have to disable App Volumes as well.
we disable it an we faced the same issue ,