We have Windows 10 and Windows 7 Desktops all running Horizon View Agent 7.4.0. These are all instant clone desktops. On first login the Windows 10 desktops usb redirection fails with the error USB redirection is not available for this desktop
If you then disconnect and reconnect after like 30 seconds of USB initializing (which is a long time compared to Windows 7) the USB devices will show up properly.
On our Windows 7 desktops the USB redirection works properly every time and is much faster to initialize.
We have the same issue with the Agent 7.4 in Windows 7 and Windows 10 Pools.
With the Agent 7.3.2 we don´t have problems.
Great, so they reverted the change that was made in 7.3.1 in 7.4.0. This is like the 3rd time VMware has done this with one of their products.
even on windows 8.1 we faced the same issue and its randomly
Having same issue. Tried 4.3.1 and no joy. Starting to make me crazy. Even the VMware engineers are having trouble.
what do you mean by 4.3.1 ? Horizon version ?
Sorry. That was a typo. I meant 7.3.1
For clarity of the issue are you explaining, is this issue with the PCoIP protocol or the BLAST protocol, or both?
Same results using both BLAST or PCoIP
On my initial connection using BLAST or PCoIP it shows USB Unavailable. If I disconnect from the desktop (not log off) and reconnect using BLAST or PCoIP again, the USB becomes available.
If I log off from the desktop and reconnect using BLAST or PCoIP it again is USB unavailable until I disconnect and reconnect
I found this regedit helped with the issue in 7.3:
reg.exe add "HKLM\Software\VMware, Inc.\VMware VDM\Agent\USB" /t REG_DWORD /v UemTimeouts /d 120 /f
jmatz135
I am assuming you are adding this to the master golden image and recomposing or are you using a script to add it to the desktops themselves?
I put this in the master golden image.
Going to try now without UEM and see if that is the issue first. then I will try the Regedit. Will update shortly. Takes me 20 minutes to fully recompose each time. Thanks for the advice.
Alternatively, set the pool to neither refresh nor delete on logoff. Then you can modify the existing test VM and reboot it without losing your changes. This would save you the potential time "waste" of recomposing from a snapshotted template. 🙂
But I would not get the same machine each time, correct?
Correct. That would only work if you modified every VM in the pool. Typically for testing like this I create 1-3 VMs in a "test" pool.
First test with removing UEM gave the same results so I can now exclude UEM as the culprit. I will now be trying using the registry edit.
OK, well it looked promising, but it now just waits for 2 minutes for the USB to become unavailable with the registry key added.
Do you actually have the policy for the pool set to allow USB? I only ever had the problem when trying to use USB and UEM smart policies to control USB. Do you have any firewalls in place between your physical desktop and the VDI desktop? USB traffic is on a different port 32111 than normal PCOIP or BLAST traffic.
Edit: Also, are you connecting directly to connection servers or is there a device that you use like an F5 appliance in between?
I was thinking firewall, but that went out the window when I noticed it worked on reconnect.
No smart policy has been applied via UEM. I have tried it though,