uemFlags USB reg entry Fix :

[Douglas42Adams]

Sorry - i couldn't find a ton of info on the below Fix.

Anyone know if this only applies to Horizon agent 7.4 / 7.5 ?.. we are on 7.6 atm.

also- if we were being affected by it any idea if just USB Redirection plain doesnt work ?

HKLM\Software\VMware, Inc.\VMware VDM\Agent\USB (if the key is not present, create it)

uemFlags (DWORD) to 1

thanks .

[DEMdev]

Hi dimich34,

Do you see anything in the Horizon agent logs that references UEM? I'm not that familiar with Horizon, so I can't be more precise, unfortunately...

[Alfordlab]

I have the same issue.

I Have to disconect a reconnect the USB in order to be able to see it on the windows.  Did you find a solution for this issue?

2020-03-26T14:26:37.717-06:00 INFO  (048C-187C) <MessageFrameWorkDispatch> [wsnm_desktop] Agent configuration for Usb over virtual channel: disabled, Usb Collaboration: enabled, Usb Collaboration VC for primary session: enabled

2020-03-26T14:26:37.717-06:00 INFO  (048C-187C) <MessageFrameWorkDispatch> [wsnm_desktop] Send the USB virtual channel flag 0 to broker.

2020-03-26T14:27:06.130-06:00 INFO  (0720-0870) <2160> [vmware-vvc] VVC: Proxy fwd filter send msgCloseListener, name=RDP__CARANOC, hub: 0x000001A28BA8B830, PlatformId: 1, VvcSid: 1

2020-03-26T14:27:06.130-06:00 WARN  (0720-18DC) <MessageFrameWorkShare> [vmware-vvc] VVC: Received VVC_CTRL_OP_CLOSE_CHAN_ACK for channel not in the closing state, instance: prxy-fwd-1-1824, channelId: 48, state: closed

2020-03-26T14:27:37.826-06:00 INFO  (0720-0870) <2160> [vmware-vvc] VVC: Proxy fwd filter send msgCloseListener, name=RDP__CARANOC, hub: 0x000001A28BA8B830, PlatformId: 1, VvcSid: 1

2020-03-26T14:27:37.826-06:00 WARN  (0720-1904) <MessageFrameWorkShare> [vmware-vvc] VVC: Received VVC_CTRL_OP_CLOSE_CHAN_ACK for channel not in the closing state, instance: prxy-fwd-1-1824, channelId: 50, state: closed

2020-03-26T14:28:09.323-06:00 INFO  (0720-0870) <2160> [vmware-vvc] VVC: Proxy fwd filter send msgCloseListener, name=RDP__CARANOC, hub: 0x000001A28BA8B830, PlatformId: 1, VvcSid: 1

2020-03-26T14:28:09.323-06:00 WARN  (0720-18DC) <MessageFrameWorkShare> [vmware-vvc] VVC: Received VVC_CTRL_OP_CLOSE_CHAN_ACK for channel not in the closing state, instance: prxy-fwd-1-1824, channelId: 52, state: closed

2020-03-26T14:28:40.819-06:00 WARN  (0720-1904) <MessageFrameWorkShare> [vmware-vvc] VVC: Received VVC_CTRL_OP_CLOSE_CHAN_ACK for channel not in the closing state, instance: prxy-fwd-1-1824, channelId: 54, state: closed

2020-03-26T14:28:40.819-06:00 INFO  (0720-0870) <2160> [vmware-vvc] VVC: Proxy fwd filter send msgCloseListener, name=RDP__CARANOC, hub: 0x000001A28BA8B830, PlatformId: 1, VvcSid: 1

2020-03-26T14:28:58.290-06:00 INFO  (048C-052C) <MessageFrameWorkDispatch> [wsnm_desktop] USB over Virtual Channel is installed.

any idea of what to do ?

[DEMdev]

Hi Alfordlab,

Which versions of Horizon and DEM/UEM are you using? Does your Horizon agent log contain "Can't get a valid sessionId within 60 seconds for channel" messages?

[Alfordlab]

I'm using the horizon 7.11

Does your Horizon agent log contain "Can't get a valid sessionId within 60 seconds for channel" messages?

No it does not.  but in order to have the usb working I need to disconect and reconect the usb from my thin client.

[DEMdev]

Hi Alfordlab,

in order to have the usb working I need to disconect and reconect the usb from my thin client.

I don't know much about USB redirection, but that sounds like another issue.

If you disable DEM for a test user (as described in KB 2138928), does the problem still occur?

[Shreyskar]

Hi Alfordlab

Is this issue reproducible on all type of clients Or is it happening only for thin clients?

Also it is possible that USB initialization might be timing out hence we have to increase the timeout, but are you able to reproduce the issue without UEM agent?

[Alfordlab]

It is happening only on the thinclient. any IDEA? How can i increase the time out?

[RachelW]

Hi dimich34​,

Yes, I did resolve the issue USB redirection.  I made to registry entries on the image and that seemed to help.

1) HKLM\Software\VMware, Inc.\VMware VDM\Agent\USB\UemFlags DWORD = 1

2) HKLM\Software\VMware, Inc.\VMware VDM\USB\WaitForSessionIdTimeout Value = 360. 

We have a disclaimer that the user must click ok on to continue logging into the desktop.  Prior to adding #2 above, if the user did not click Ok quick enough ( like within 30 seconds) it would timeout and prevent the USB devices from being redirected.  When I added the WaitForSessionIdTimeout key and set the value to 360, that gave the user 5 minutes to click OK on the disclaimer without disabling USB redirection on the desktop.

Hope that helps and is not too late.

Apologize on the late response.

[Shreyskar]

Hi Alfordlab,

A combination of UEMflag set to 1 and adding a delay for USB timeout, will fix this problem.

Setting UEMFlags to 1 is applicable ONLY for thinclients as it just bypasses any USB horizon smart policy configured thorough UEM manager.