ofox's Posts

Hi @sfe45 , I would like to check with you a few things in order to understand your issue better. Thin-Client -> Horizon-Server -> Horizon-Client-> Linux WST It looks like a nested topology, could you clarify that Is Horizon-Server a Horizon Connection Server or a Horizon Agent? Is "Horizon-Client" a Windows VM that runs a Horizon Agent as well as a Horizon Windows client? Is "Linux WST" a virtual Linux VM or a physical Linux machine that runs Horizon Linux Agent?

michelkeus_stwg had a good point ‎.   In addition to USB redirection feature that you guys seem to be using, the latest release 2306/8.10 adds FIDO2 support the first time and Yubikey is the device that we have verified for FIDO2. The release has gone alive last week and you could try the new feature out to see if it meets your need better.

"until she prints the receipt for the transaction and the desktop hangs for 60-90 seconds" How does the user print? Does she start printing in the remote session or from her local end point? If the former what printer does she use? Does she try a different printer? When the hang is over does the printing go through eventually?

Are you using a VDI desktop session? In 7.13.x the GPO is named as "Printer Name for RDSH Agents" and it applies for RDSH session only as its name calls out. In 8.1+ it's called "Printer Name Schema" and we extended to VDI. I guess that's the reason.

It's recommended to use the matching version of Horizon Agent and its GPO. So if you are using 7.13 Agent please use the same version of GPO. Any new feature in a newer version of GPO would only work on the same version(and beyond, but not older) of Agent.

@Jackson_Goverme  kindly check this out. https://support.microsoft.com/en-us/topic/march-28-2023-kb5023778-os-build-22621-1485-preview-d490bb51-492e-410c-871f-50ad01b0f765 This update addresses an issue that affects USB printers. The system classifies them as multimedia devices even though they are not.

Microsoft has just released the fix https://learn.microsoft.com/en-us/windows/release-health/windows-message-center Highlights for the Windows 10, version 22H2 update: ·         This update addresses an issue that affects USB printers. The system classifies them as multimedia devices even though they are not.   Please try the new OS out and let us know if it works for you.

I would like to provide an update. We've escalated the support ticket that we filed to MSFT since last week. According to the latest update from MSFT support it's related to a known issue in one of their drivers. A next update is supposed to be soon.

Hi Jackson_Goverme, sad to see many customers have been impacted by this. We've been actively chasing MSFT on the issue. In the meanwhile, if you're not using Zero client, please try to use VIP(for Horizon8) or Virtual Printing(for Horizon 7) accordingly. 

VMware has provided all necessary info/data to MSFT per request and highlighted that multiple Horizon customers are experiencing this issue. We're waiting for a progress update from MSFT. Will keep the Communities posted.

To scottjones74, if you're using Thin Client that runs Horizon client software inside, then you could use VIP feature for all printers and it should not have the issue discussed here. If you're using Zero client(no Horizon software in there) then you have to leverage USB redirection feature for USB printers, which would hit the issue. This is what I meant. If you are having a printing issue with Thin Client + VIP combination then it is very likely a different issue. You could engage your VMware contact.  

The issue here is pertaining to certain Win10 OS versions on VMs, while the issue mentioned in KB  https://kb.vmware.com/s/article/89812 was about some driver in VMs - no matter what Windows OS version is. If you are using a thin client as opposed to a zero client please try to use printer redirection feature rather than USB redirection feature for those USB printers. In Horizon 8 the only printer redirection feature is VMware Integrated Printing(VIP), while in Horizon 7 the default is Virtual Printing(i.e. ThinPrint). Using printer redirection feature would not hit this the issue discussed here. Note that, the difference between a thin client and a zero client from Horizon perspective, the former runs Horizon Linux client or a customized version of that inside so it supports almost full of Horizon features. While zero client does NOT have Horizon client software inside thus only supports very limited Horizon features(Yes USB-R, no VIP etc.)

Not sure. Horizon 8 has a great performance improvement in RTAV(i.e., Microphone and Webcam). But your problem might not be related. What's your Horizon Agent version when you are using 8.x client? Did you try another app like Teams or Webex? And did you try only single-monitor setup? Also did your Zoom peer see and hear you okay on their computer?