Horizon 2603 has gone GA today - https://docs.omnissa.com/bundle/horizon8-rnV2603/page/Horizon8-ReleaseNotes.html

Looks like it breaks New Teams Slimcore

has anybody managed to get post-sync scripts working on nutanix yet? i can't even see where it's exposed in the interface, and if it's strictly reliant on a single specific script name baked into the gold image, that kind of defeats the utility across multiple datacenters

uh let me rephrase that, has anyone managed to get them working when for whatever reason they dont show up in an environment? i see the expected screen in my lab, but at my customer's site there's still nothing useful on the guest customization screen

.. and only on one connection server, oh good, apparently it's an Edge problem and not wanting to update that one part of the wizard vs. pulling from cache

Anyone looking at going to 2603 yet? Planning our next upgrade cycle from 2503.1 and considering between 2512.1 and 2603.

2512.1 is solid and have it deployed at multiple customers. I deployed 2603 on GA, but I'm having a ton of issues with it and persistent VMs. Bunch of issues with Client Folder Redirection, agent availability, Teams slimcore optimization causing Teams to crash, etc. Working on Instant Clones in my lab, but having issues with all my persistent VMs (even when deploying brand new VMs, fresh install for everything).

I'm hoping someone else can report back if they are having the same issues or not with 2603. No one else has posted anything online, and I can re-produce this 100% of the time on persistent VMs, and I don't have anything weird/odd deployed in my lab environment.

We put 2603 up in our lab but we don't make much use of persistent VMs. If there's a quick test we can put together, we could give it a try.

Essentially on persistent VMs, upgrade the agent, and then the issues occur. Teams crashes on slimcore optimization, Client Folder Redirection doesn't work, and some other anomalies where the new BLAST system tray icon disappears shortly after load because it crashes, and some clipboard stuff.

Also happens on new VMs with fresh installs as well. Happens 100% of the time on any persistent VMs I update, but the issues don't occur on my non-persistent VMs for whatever reason.

I pinged PMs... they are on it, it is "known" 😞

Submitted some logs/dumps yesterday and we identified it was because my CPU doesn't have the BMI2 instruction set (old proc).

Unlikely that most customers will come across this, but there are some remote scenarios where some would, so it's good to find this quick 🙂

Threads please lads

has anybody had any luck getting DEM Computer Policies to work on AHV "instant" clones? I keep seeing event log messages indicating that it checks to see if it's on an IC, decides it's not so skips processing

has anybody had any success (or tried) to install the latest horizon agents from the command line (scripted or not) when you have to deal with the pairing mechanism (vdm_pairing mechanism/vdm_server_name/vdm_admin_username/vdm_admin_password) ? no matter what it seems to fail trying to bind to the connection server ldap to do that necessary (At least for nutanix and i imagine other capacity providers) part .. thought maybe it was a password thing but that doesnt even seem to matter if there's special characters or not in play

Does anyone know if there are any flags for Cloneprep Debug mode for AHV like there is for vSphere? Like: Troubleshooting Instant Clones in the Internal VM Debug Mode

This message was deleted.

Hi everyone, Has anyone seen issues with Teams Optimization on Horizon integrated physical clients after upgrading to the latest Horizon Agent? One of my customers is using physical clients as Remote PCs together with Microsoft Teams Optimization. According to the customer, this setup had been working well until recently. However, after installing the latest Horizon Agent, we're now seeing the following issues: • Teams Optimization no longer works (neither WebRTC nor SlimCore). • Only the audio output device from a locally connected USB headset is available in the Remote-PC, the microphone is not. What's interesting is that if the same user connects to an Instant Clone VDI, everything works as expected, including Teams Optimization and the headset microphone. I also came across this community thread, which seems to describe a related issue: community.omnissa.com/forums/…/3 However, in that case the problem is the speaker/audio output, while the microphone continues to work. In our case, it's the opposite: the speaker is redirected correctly, but the microphone is missing on the Remote PC. Has anyone experienced something similar with the new Horizon Agent Versions? Horizon Client Version is also 2603

I've encountered an issue where audio artifacts like crackling/popping noises can be heard sporadically when using multiple speakers in a Horizon session. How to reproduce: • Multiple audio output devices (speakers) are connected to the client endpoint • Horizon Client is configured to redirect all speakers to the remote desktop (i. e. Horizon Client Settings → Real-Time Audio-Video → Preferred speaker: All) • An audio device other than the one that has been connected to the client first is selected as the default device within the remote session (in other words, the device that was connected to the client first is not affected by this problem) • Play pink/brown noise or a low frequency sine wave test tone to make the audio artifacts more apparent I've tried multiple versions of the Agent, Client (Windows and Linux) and OS (Windows 10 and 11), no change in behaviour whatsoever though. Has anybody else run into this?

I know this channel is a bit less active than the citrix ones - have there been any former citrix shops that have switched to Omnissa with feedback, good or bad?

In case anyone is having Omnissa issues today, my company just found there's an Omnissa outage for the North American region. Omnissa Workspace ONE Status - Horizon Cloud Service next-gen: Increased Request Error Rate - All Region

Looks like there's a ton of issues with Azure hosted services, and M365 as well.

makes sense since all the omnissa cloud stuff is on azure

Has anybody switched an on-prem Horizon environment from Subscription/SaaS to Term licenses before? I'm getting a Messaging Clients alert in the Horizon Console (Disconnected, last seen at ...) after changing the license mode. I've already tried deleting the Horizon Edge in the Horizon Cloud portal (Capacity → Horizon Edges) and restarting and/or shutting down the Horizon Edge Gateway appliance. I have also rebooted the connection servers. Is there anything else I have to decommission?

Horizon 2606 is looking pretty good 🙂

Released earlier this week in case anyone missed it.

Is anyone else fighting the Microsoft September Windows Updates? ref: Black Screen After User Login Due to Explorer.exe Failing to Launch Post-September 2026 Windows Updates (KB5124008 / KB5129195) in Omnissa Horizon Environments (6001783)

Ran into a weird issue with Horizon 2603 where published apps fail to launch when deployed using App Volumes. According to support, this affects 2603 and 2606. We were given a hot patch Horizon connection server build that resolved the error for us. Published Applications Fail to Launch When Using App Volumes on Horizon 2603 and 2606 :: lettucebuns.io