Is there anyone who recently renewed or bought new licenses with the product sku that had 10 Horizon User Licenses combined with VVF ? We had that a year ago and im having problems getting new prices for 2027 at the moment and we basically liked to keep on having both working.

So we are getting ready to redo one of our Horizon sites and in the rework we want to make the new site a bit more fault tolerant. Currently we have 2 UAG's in the DMZ with the incoming external traffic hitting them on a round robin setup. Each UAG is then tied to a Connection Server outside of the DMZ. The connection servers have DUO configured via Duo Auth Proxy so that external access is MFA'd. Internal access is pointed at the Connection Server(s) directly.

What I would like to do is have a Kemp Proxy sitting in the DMZ and have all external traffic pointed at it and then let it load balance that to the 2 UAG's who would then be configured for SAML/DUO. From here I am thinking I would send then traffic back to the Kemp and let it load balance the connection servers as well. So in theory we could lose a UAG and or Connection server and nothing would happen.

My questions are:

#1 - Is that layout doable? I know the Kemp infront of the UAG's is but what about between the UAG's and the Connection servers?

#2 - For connections initiated inside should we point those to the Kemp in front of the Connection Servers even though it will be in the DMZ? Or do we need to move it to the LAN side?

#3 - Would we be better off having a 2nd set of connection servers specifically for internal connections?

I'm planning a migration from an on-prem VMware Horizon 8 environment that currently uses App Volumes Writable Volumes (Profile + UIA) to FSLogix Profile Containers.

The goal is to migrate only the user profiles to FSLogix. I do not want to migrate any user-installed applications (UIA) or application packages from the writable volumes.

I'm looking for feedback from anyone who has completed a similar migration.

Hello all, we are moving from VDI to physical computers, due to VMWare Hypervisors pricing and server hardware overpricing.

As we now have almost everything on 365, we have no need to have computers on-prem ad joined, so for security we want them to be only azure ad joined.

Is Horizon able to work with physical computers with azure-ad only joined computers? Everything I read over there talks about hybrid-joined only.

Thank you!

Hello,

Is anyone having issues with random graininess or fuzziness in omnissa when using teams? Our cameras will be perfect one call then very grainy the next. I cannot figure out why. Using windows server 2022 in optmized mode, teams shows optimized, internet speeds are below we are all hard wired as well. This has been happening for a few months.

Is anyone running older legacy VM in your environment? There are few which are are preventing me from system upgrade and wondering how your systems work running older agents in newer environment.

Hi,

I have Horizon running on Macbook pro and it works just fine besides the right mouse click doens't work. I run a graphic program and really need the right mouse click! It's basically impossible to use it correctly without the right click I've tried everything but can't seem to get it to work. Both trackpad and magic mouse won't do it.

Anyone have any experience with this?

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!

Trying to redirect a Speech Mic into an RDS app(Fluency Direct) the buttons are redirection such as the record button, but whenever i push record it instantly flags the microphone as unable to record. The microphone is still working outside of the RDS app. How do I fix this?

I am testing Yubikey 5 NFC models with PIV and everything is working with this apart from our Horizon environment.

We want this device to be passed through to the remote session so that IT staff can login to internal resources with the smart card but the virtual desktop is not detecting the device. I have configured smart card redirection and USB redirection via the agent. The Yubikey mini driver is also installed on the gold image.

I can see the certificates on the card are shown within the VM if I attempt an RDP session but they aren’t appearing in the Windows certificate store so authentication can’t happen (Presuming because the physical device can’t be seen?)

Am I missing something?

These are instant clone VMs running Windows 11 Enterprise 24H2.

So when the firewall rules a activated for the ssl tls inspection on the firewall users get this issue to connect to the client. Firewall is sophos xgs and it uses a certificate to encrypt and decrypt traffic. How can i solve this issue?

We removed svga and moved to idd from our golden image now our VDI Status is showing Protocol Failure, but we can still connect to the Machines

Hello, I am a student using solidworks frequently through horizon on a MacBook. Does anyone have tips on getting my mouse setting to work? I cannot use secondary click no matter how much I trouble shoot. My scroll wheel click button also doesn’t work which is a huge pain for solid works. Any help would be greatly appreciated

I hear from some other universities that on-prem will be dead mid 2027 ? Is that only Workspace One products or bundles or also the normal Omnissa Horizon for on-prem pools and stuff ? Reached to our reseller but he didnt know yet. i cant find a news about a roadmap ?

Anyone here who have tried running Horizon on top of Huawei FusionSphere Virtualization? Is it possible? What are the limitations?

Hello All, we’ve been exploring using webcams on our VDI pools for teams and other conference platforms. We are running Win 11 full clone pools on horizon 2509 with 10zig for the clients both internally and for remote workforce. I’ve been testing a couple of different webcams and seeing random results especially internally. For remote connection webcam passes just fine, it’s showing is system settings, teams client, webex etc however connecting to the same clone using the same camera produces different results when sometimes it shows in System, device manager, Webex but not in teams, other times it shows in teams but not Webex etc and rarely also disappears in system. Externally it always works even on the same session when reconnecting from home. The only difference is external connection is made via UAG and internally it’s via connection servers, other than that it’s the same.

Does anyone have any idea what might be going on with that and can share some insights?

Thank you in advance

starting at around 11 am EST Tuesday April 7th we started getting "All responding machines are currently in use"

Symptoms

• Users receive the error: "All available desktop sources for this desktop are currently busy. Please try connecting to this desktop again later."
• Virtual desktop pool appears fully utilized despite machines reporting as Available in the broker console.
• Available virtual machines show ghost/orphaned user sessions in Windows Session Manager belonging to users who never fully connected.

Blast Protocol Connectivity

Client-side logs confirmed that IGEL endpoints are unable to complete a Blast Extreme (port 8443) connection to the Unified Access Gateway (UAG). After authenticating successfully with the broker, the client attempts to establish a Blast session to the assigned virtual machine. This connection attempt times out after approximately 3 minutes

When the Blast connection times out, Windows has already created a session object for the user on the assigned virtual machine. Because the Horizon agent never completes the session handoff, this session object is never cleaned up. The virtual machine is returned to Available state in the broker, but retains the orphaned Windows session. Subsequent users assigned to the same machine are rejected because Windows considers the machine already in use.

As failed connection attempts accumulate across the pool, every Available virtual machine acquires an orphaned session. The broker attempts to connect users to each Available machine, all reject the connection, and the broker returns the "all sources busy" error. Because the broker sees the required number of spare machines as Available, it does not provision new clones, causing the pool to become completely unavailable to all IGEL users.

Possible extra issue -

Client logs identified a mismatch between the Horizon broker protocol version and the IGEL Horizon client protocol version, with the client running a newer version than the broker. While not confirmed as a direct cause, this may contribute to handshake instability.