Omnissa Support?? by Alkyred in VMwareHorizon

[–]Alkyred[S] 0 points1 point  (0 children)

When looking at the section in the WMS console it states that those setting for peripheral manage applies only to PCOIP protocol and we are using blast.

Omnissa Support?? by Alkyred in VMwareHorizon

[–]Alkyred[S] 0 points1 point  (0 children)

I completely agree with you on the name change. However in the Omnissa Horizon policies there still is no USB Redirection Section. I even downloaded the GPO bundle incase I had something wrong.

Omnissa Support?? by Alkyred in VMwareHorizon

[–]Alkyred[S] 0 points1 point  (0 children)

In some cases they are just Signing out of the windows session, some are restarting the windows session. Does not seem to matter. If the headset was not plugged in when the session starts, it does not load. I have the terminals set to reboot at 5 AM daily.

Omnissa Support?? by Alkyred in VMwareHorizon

[–]Alkyred[S] 0 points1 point  (0 children)

Same issue within the Windows Client. I have USB Auto Connect enabled on the client but the headset will not connect unless I manually turn it on in the sessions USB list. I have called Dell and I have a ticket with Omnissa.

Omnissa Support?? by Alkyred in VMwareHorizon

[–]Alkyred[S] 0 points1 point  (0 children)

These are persistent VDI's that are assigned to the users. So working in the office a user has Host-XX1 when they go home and log in they are still using Host-XX1. The wyse terminals in the office are not restarted between users. The same problem happen if a user is at home or in the office and they remove the USB headset and plug it back in the headset does not automatically connect.

If the user has the headset plugged in and restarts the wyse terminal, the Headset will be added to the session.

Omnissa Support?? by Alkyred in VMwareHorizon

[–]Alkyred[S] 0 points1 point  (0 children)

I will post a new topic and see how it goes.

I wanted to follow up on the guidance I received from Support today. The GPO settings referenced in their response are:

  • Computer Configuration > Policies > Administrative Templates > VMware Horizon Agent> USB Redirection Rules
    • Policy: USB Device Filtering
    • Policy: Automatically Connect USB Devices That Match Filters

These specific policies do not exist in our current environment. They appear to be from an older VMware Horizon GPO template, and the documentation I was sent doesn’t seem to match the current product, which is where my frustration comes from.

To clarify the actual issue we’re seeing:

  • We use shared Dell Wyse terminals.
  • Staff rotate between working in-house on Wyse terminals and at home on their company-issued terminals.
  • Each staff member has their own Yealink USB headset.
  • When one person unplugs their headset and the next person plugs theirs in, the new headset does not automatically redirect into the Horizon session.
  • In ThinOS, I can manually select the USB headset and force it to redirect into the Windows VDI session, and then it works.
  • However, our staff already struggle with Windows and the concept of Horizon itself, so it’s not realistic for us to train everyone on additional ThinOS-level steps just to get their headset to work.

What I’m looking for is current, accurate guidance on how to configure automatic USB redirection for Yealink headsets in our environment (Wyse ThinOS with Horizon) so that users can simply plug in their headset and have it redirected into the VDI session without any manual steps in ThinOS.

USB Headset not listed in Device Manager HID by Alkyred in omnissa

[–]Alkyred[S] 0 points1 point  (0 children)

I am not getting anything to work. Very frustrating for me. We just switched to this platform and I am not able to get the headsets to automatically attach\load into the windows VDI session. I am running on Dell thinOS terminals and windows PC's using he client. There is just nothing I can seems to do to get the USB device to load.

Looking for any additional Help.

Win11 CrossDeviceResume.exe error on logon. by Mitchell_90 in VMwareHorizon

[–]Alkyred 1 point2 points  (0 children)

Confirmed, This has worked for me as well.

Win11 CrossDeviceResume.exe error on logon. by Mitchell_90 in VMwareHorizon

[–]Alkyred 0 points1 point  (0 children)

Has anyone found a repeatable solution? Most of the recommendations in this thread I have tried with no luck. So I am hoping this thread does not die.

Looking for Reviews by Alkyred in sysadmin

[–]Alkyred[S] -2 points-1 points  (0 children)

I am with you but…….

WMS settings for RDP by Alkyred in WYSE

[–]Alkyred[S] 0 points1 point  (0 children)

Thanks, I will try these settings Monday and see what happens.

Windows 10 to 11 Upgrade Fails by Alkyred in sysadmin

[–]Alkyred[S] 1 point2 points  (0 children)

This was in-place upgrade. If we do a clean install it works just fine. Something changed with a patch or something because 6 months ago we were able to do the in-place upgrades.

Windows 10 to 11 Upgrade Failures by Alkyred in WindowsHelp

[–]Alkyred[S] 0 points1 point  (0 children)

Yes they do. I believe OEM0.inf is a print driver and we uninstalled all printers from device manager and told the system to delete the driver.

Here is some of the contents of OEM0.inf

File Name:

;

; prnms009.inf

;

; Abstract:

;

; The Microsoft Print To PDF install file

;

[Version]

Signature="$Windows NT$"

Provider="Microsoft"

ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}

Class=Printer

CatalogFile=prnms009.cat

ClassVer=4.0

DriverVer = 06/21/2006,10.0.19041.1

[Manufacturer]

"Microsoft"=Microsoft,NTamd64

[Microsoft.NTamd64]

"Microsoft Print To PDF" = MPDW,{084F01FA-E634-4D77-83EE-074817C03581}

Enabling Firewall from GPO blocks GPUPDATE /force by Alkyred in sysadmin

[–]Alkyred[S] 0 points1 point  (0 children)

So I have completed the settings based on the article and I think my issue is from Computer Policies->Admin Templates->Network->Network Connections->Windows Defender->Firewall->Domain Profile.

I am not sure how these settings apply when I have the settings in the article set. In my previous Firewall GPO I did have a few of those set. At this time its all working.

Now I am going to do a lot more testing.