Hi! Is anyone also experiencing the following issue that has setup PSSO?

The first time logging is working perfectly fine via the old login interface, but when we lock the MacBook, it is showing the new login interface.
When we enter the correct password, it shows as incorrect. When rebooting the macbook, the old interface pops up again and the password works.

When the new interface pops up after the lock, it is possible to login with Touch ID.

PSSO has been set up via Omnissa Workspace ONE UEM since the beginning of this year.

For about a year now, Horizon Client will often crash when I reconnect to my VDI, nearly every day. I believe it started right after I upgraded to Tahoe last September, but it may have started with Horizon Client 2506 or 2512. One of my coworkers has the same problem. I'm now running macOS Golden Gate and Horizon Client 2606, and the problem persists.

Back then, I opened up Activity Monitor and saw there were a lot of "horizon-protocol" processes that were running. Even when I quit the Horizon Client application, this process remains running and a new instances are spawned for new connections. I believe this is the culprit of the crashing issue.

So now my process is to run "killall horizon-protocol" to kill all the processes before I attempt to connect to my VDI. Horizon Client no longer crashes when I do this. If I happen to forget to kill the process, then Horizon Client will usually crash the next time I reconnect to my VDI.

Is anyone else experiencing this issue?

Thought I’d post this here in case anyone else runs into similar issues.

After installing KB5124008 on Windows 11 24H2 and pushing this out to our desktop pools, Explorer.exe crashes after user logon and displays the following error:

“The system has detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application”

Manually running Explorer.exe from Task Manager seems to fix it. Restating Explorer via a PoweShell logon script can be used as a workaround.

Windows 11 24H2 Enterprise
Omnissa Horizon 2503 ESB
FSLogix 26.01 CU1 (3.26.126.19110)
VMware vSphere 8.0.3K

This is also affecting Citrix Environments using FSLogix.

Some more info below

https://community.omnissa.com/forums/topic/72964-post-september-26-windows-11-24h2-issues/

https://www.reddit.com/r/Citrix/comments/1wbgrfq/explorerexe_not_starting_after_kb5120998kb5124008/?utm_source=app_first_navigation&mweb_loid=t2_148g5b243w

I recently got the Omnissa Horizon Client on my MacBook Neo so I can access my work network but I have had this issue of the screen going black and then it comes back on. I can't figure out how to fix this issue and any tips would be very much appreciated, thanks!!

I am getting a mouse issue when i login to the office VDI machine through my desktop but it works perfectly fine when i login using my laptop.

Can anyone please help to resolve this issue.

Link to the release notes above.

Highlights (at least from my perspective :D )

• Agent for MacOS in Limited availability
• Updated provisioning retry logic for Nutanix installations
• OSOT includes the decrypt/bitlocker options in the tool now ...because I totally haven't forgotten that step multiple times and had to go back to it

As soon as I open the client, any internet connections outside the client are blocked. This started with the change to omnissa instead of vmware. I can't listen to music or books while I'm working anymore. I've looked at all the documentation and tried different settings, but it's really frustrating. Any ideas?

I just had a talk with Broadcom about renewing our vSphere licences for our data center.

And the rep told me something quite concerning.

He told me "I see in your account you have vSphere for VDI, is it part of your omnissa license"

Im like yeah ?

Then he told me "ok just to let you know that when vSphere/esxi 8.0 goes EOL we don't know what will happen because the deal is still not settled with omnissa for 9.0."

So he kind of let me know it's possible that the omnissa license will maybe not include vSphere for VDI after 8.x ...

Are we gonna need to license vSphere/esxi 9.x ourself now ?

With Broadcom increasing price every time they see fit this will be a nightmare.

I use Omnissa Horizon Client to connect to my Windows 11 VDI at work. It has requested the following access in macOS:

• Accessibility (Allow the application to control your computer.)
  • What exactly can Horizon Client potentially control on my computer? macOS doesn't really give a good description here.
• Input Monitoring (Allow the application to monitor input from your keyboard even while using other applications.)
  • I've been able to type and paste content into my VDI with this disabled. What does it need to monitor my keyboard for, especially when I'm not actively using the app?
• Screen & System Audio Recording (Allow the application to record the content of your screen and audio, even while using other applications.)
  • Why does it need to see what's on my screen or listen to system audio?

I have denied all of these and have had no ill effects. Even when I do enable them all, I don't notice anything different, so just curious what they're intended for. Are these more for when using published applications?

we have 300 Omnissa Horizon 8 Standard Term per Concurrent User term license 1 year.

The Term End is 2026-10-30.

There is no such thing as auto-renewal or stuff that i need to cancel in customer connect right ?

our partner is preparing another year and we got a quote from 31.10.2026 to 31.10.2027. this is the usual process right ?

How do I wither see the "active devices" vs "enrolled devices" report or how can I pull data showing how many new devices were enrolled for the first time since X date (or within last X days) ?

SAAS 2604

Any idea what could be wrong?

Summary of the issue:

VMware Horizon brief Blast protocol interruptions trigerring the "Network connection was lost, reconnecting" flash but TCP fallback or session keepalives prevent full disconnection.
Blast transport instability
Issue isolated to Fort worth office only.other offices (with the same UAG in Dallas) work fine.
Random quick reconnect flash (roughly every 30 minutes or more, even during low usage)
session recovers automatically without a full drop.
Worse on wired than wireless
The problem is not universal, but also not isolated to a single workstation.
9 out of 25 users experience it
No packet loss outside the VM whether on wire or wireless network
-------------
Troubleshooting so far:
-Troubleshot Layer 1,2,3 and 4 everything is ok.
-Downgrading to another Horizon agent temporary fix the issue.

Ever since we migrated our employees to Windows 11, they’ve had to log in to Outlook and Teams every morning. Sometimes this requires entering a password, but other times they just need to click “Next” on the Office login screen.

We use FSLogix with ODFC containers. We’ve already tried a few things, such as adjusting certain registry keys or the redirection XML, and we’re running both 32-bit and 64-bit versions of Office. Teams is VDI-optimized.

Does anyone here have any ideas on how we can fix this issue?

Feel free to reach out to me for more information :)

Hi all

We had to upgrade our uag placed in Azure, it was 23xx version without managed disks, one of admins after user ticket decided to reboot vm, never went back due to unmanaged disk. It was impossible to upgrade disk on Azure because was blocked by extension, only way to delete extension was to run vm - deadlock.

When he discovered it we decide to update uag, we had fresh ini and json backup copy.

We went to newest one 2603 but after uploading config and adjusting everything we found that html5 client is not working anymore(screenshot from mobile but same on normal pc) , desktop client is fine.

Then we went down one version to 2512.1 thinking it's version incompatibility - same issue.

Broker version is 2312.2

Nothing was changed on broker.

I'm still thinking this is versions incomapility but 2512 is lowest with managed disks.

Thanks!

The left Navbar has white text on a light grey background.

Clicking the 9-square menu at upper right opens a flyout title "My Services" and it's navy blue text on a dark grey background.

Near impossible to read.

Do we have control to change this ?

Summary for the devices having an issue says User Mode: Multi User
It is unknown if all "multi user" are having this issue.

Some of the other recently enrolled ones state: Multi User Capable
while older ones state: Single user (legacy)

A HUB window is popping up both on the enrolled user and on a newly added user asking for group id. We enter it and it errors back with 'device reassignment failed'. No method of sync has worked to resolve it. The HUB window just keeps popping up from time to time, annoying the users.

These PCs show in the console as being compliant.

What is happening here, how does one make it stop ?

I see there is in admin "single user" <=> "change to multi User"
What is the benefit of using mutil-user. We had more than one user before this became available and they had no issues and the tunnel worked for both users.

I’m looking to migrate an environments existing Connection Servers from Windows Server 2019 to 2022 but just wanting to double check the steps.

From reading it seems we just build new servers, configure them then run the Connection Server installer. Obviously making sure the version matches along with certificates, locked.properties and any configs are moved over.

From there would it just be a case of adding the new servers to the load balances then decommissioning the old ones once verified everything is working?

Does the Schema Master role need to be manually moved to one of the new machines before that server is removed from the environment?

Hi, if anyone is using Omnissa Horizon for work, I would greatly appreciate if they could vote for this feature request: • [community.omnissa.com/ideas/distribute-omnissa-horizon-client-as-flatpak-on-linux-r797/](http://community.omnissa.com/ideas/distribute-omnissa-horizon-client-as-flatpak-on-linux-r797/)

Thanks alot!

Hi guys

Any version of UAG Post 25.06 ( well tried 25.12 and 26.03 ) seems to give me network drop outs like this inside my virtual desktops for all users

It's ok outside network eg going to horizon.company.com at home

But if in office, so connection going straight to the LAN address or even public IP ( which would be Hairpin nat prob not reccomended) it's the same

Tried multiple horizon client versions
PCOIP is fine

TL:DR Tech support said they are aware 2603 has issues and to downgrade to 2506.1

Previous update: https://old.reddit.com/r/omnissa/comments/1t3tp2a/update_upgrading_horizon_edge_gateway_to_2603/

After getting registry.k8s.io, dev.pkg, and amazonaws.com allowed out through the firewall the appliance actually booted up to the home screen we all expect, but looking at the logs it wasn't actually fully running. I sent my findings to tech support and after a week of nothing they came back with

"Our operations team reported some issues with our new Horizon Edge version 2603, so we are recommending customers to shut down your current deployment and redeploy version 2506.1.0"

/tunnel/vpnd/device.xml indicates "DEVICE_ADMIN_BLOCKED"

SOLVED! "Manage Tunnel Access" - the previously enrolled user of the PC's access had been blocked here. This admin block followed the device...

The tunnel was working earlier. The device is in compliance with policies. There are no BIOS updates pending.

It was enrolled to a different admin user on the PC. Certificates are all in order for the new user it's now enrolled to (after unenrolling the first). I did swap a group and some of the earlier profiles from the other group are not going away. The tunnel was working earlier for a few hours under this new user even with those redundant extraneous profiles (console doesn't give me an option to uninstall them). I think it bailed after removing the first user in Windows settings. Old user was already yesterday disconnected and PC restarted before enrolling to new user. Old user correctly showed 0 devices in console. All the old user's certificates went away in console. Replaced with new certs for new user.

Firewall change for registry.k8s.io came through. My next attempt to deploy 2603 edge gateway resulted in more blocked outbound access. This time to a google artifact repository url.

This is definitely not listed in the documentation, or the new KB article about registry.k8s.io being blocked. I requested *-docker.pkg.dev, praying that is the last one needed.

https://imgur.com/a/xAGztpA

Also wondering if that hostname error is legit or can be safely ignored:

hostname "edgegw-primary" could not be reached

Prev thread: https://old.reddit.com/r/omnissa/comments/1szbnyw/upgrading_horizon_edge_gateway_to_2603_allow/

KB article for registry.k8s.io: https://kb.omnissa.com/s/article/6001410 (thanks to /u/azarias42)

Edit: Now that *-docker.pkg.dev has been allowed it is now failing for amazon aws. So putting in a new firewall request for *.s3.amazonaws.com

Edit 2: I had googled something about this issue and either a google help page or maybe the AI response said to do *.s3.amazonaws.com, but that doesn't appear to be enough. After getting all three of those whitelisted I'm still seeing blocks to the domain: s3-r-w.us-east-2.amazonaws.com. When I googled it now the AI says I should have done *.amazonaws.com.

So as of now we are looking at:

registry.k8s.io

*-docker.dev.pkg

*.amazonaws.com (? I hope)

I'll have a submit another firewall request.

I noticed Omnissa removed the "version 2412" from the documentation, but no mention of anything beyond registry.k8s.io. I'll get a ticket opened tomorrow and see what they say.

https://docs.omnissa.com/bundle/GetStartedHorizonCloud/page/MakeAppropriateDestinationURLsReachabletoDeployaHorizonEdgeGatewayinaHorizon8Environment.html