Grr I'm trying to roll new UAGs for the above and my uag deploy is hanging right after it prints the username. IIRC in the past this was due to a bad resource path, which makes sense since I'm on new vcenters now after the umpteeth VCF redeploy at our org. The thing is, I verified the vi:\\ resource path with OVFTool....and even removed the trailing / just in case that's still a thing with OVFTool.

We're seeing issues with the April patches and VMware Tools 12.5.1. We're currently running 12.5.1 in production with the February patches without issue. When logging into a VM with the April patches applied, the session locks. Configuring the pool to use the Horizon IDD for display driver resolves the issue. Repairing and removing/reinstalling has no effect. Horizon 2312.1 with Windows 10 22H2 as the guest OS. We have a case open with Broadcom who hasn't provided detail yet but indicated this may be an issue on the Windows side.

Hello, we have the following situation. Horizon Client logs in from remote with RSA. User starts desktop. Everything works fine as it should. Then user logs off the VDI, but leaves the Horizon Client open. After some time users starts again the desktop, desktop loads, but now it goes to the Windows Logon Screen. So no SSO anymore. Entering username and PW and the user can log in. Is there a way, to force the Horizon Client to reauthenticate after a time, to avoid this issue? Or some another way to have SSO to Windows working? Thanks.

Another question, in Horizon what Tools can you recommend to troubleshoot slow Windows Logins? If I compare with Citrix Director the Helpdesk Tool doesn't supply so much detailed information. I can see lets say that its GPO, but thats it. Is there something else you can recommend?

Has anyone experienced any issues with the Horizon client on Windows 11, where intermittently lag/jitter will be experienced with the mouse, where the session doesn't respond at all (active, but not responding), and a CTRL+ALT+DEL is required on the client side to re-capture and click back (also resulting in CTRL sticky keys on the session). Usually these periods of time occur around this Windows Event Log: Event Source: IsolatedUserMode Event Description Secure Trustlet \??\C:\WINDOWS\System32\NgcIso.exe Id 6 and Pid 5564 started with status STATUS_SUCCESS. First, this occurred only on Windows on ARM, however I'm experiencing it on x86 clients as well now. Google'ing the event log, I see similar reports where this happens with other applications and is related to "Core Isolation" which is part of Windows 11 security. I tried to disable the memory protection, however it's still occurring. Anyone seen this or have any workarounds? It's getting really annoying, especially when on Zoom/Teams, as I completely lose all audio/video.

Good day, does anyone have experience with Horizon 8 on AWS (EC2) - 2-way trust between AWS Managed AD (simple) and on-prem self-managed AD (s2s vpn)? What concerns me is "[ws_winauth] LogonUser FAILED, error=1326 (The user name or password is incorrect.)". Is this because of not having Domain or Enterprise Admin on the AWS side?

i know a bunch of you are probably at nutanix.next, but for the rest of us stuck at home that might have missed the big news: https://www.omnissa.com/insights/Omnissa-Nutanix-AHV-hypervisor/

Question: From what I remember, Horizon (8 or any other version) could not natively provision resources on Azure. For that you needed to use the Edge Gateway appliance to connect to the Horizon Cloud service and the Horizon Cloud entitlement to display the combined resources (on prem + cloud). So at that stage is really two solutions combined, the on-premises one plus the cloud one, versus a single on-premises one that could provision cloud resources directly (like Parallels RAS or Citrix CVAD can do). Am I missing something?

I know I can simply load the horizon agent on Azure VMs but that simply means they may show up as resources available (i.e., a desktop) but there will be no way to treat this as a pool that will scale up and down, create new VMs, etc. It is just a pool of VMs, completely unmanaged.

Is somebody running a Horizon 8 and up-to-date Teams (VDI optimized) client? If yes I would love to get some outputs for my script. Just run the following in a Horizon VDI session with started and optimized Teams. Output should be something like 32xx or 31xx...

# Path to JSON file
$tfwPath = "$env:LOCALAPPDATA\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\tfw\vdi_connection_info.json"
 
# Check if the file exists
if (-Not (Test-Path -Path $tfwPath)) {
    Write-Error "The file vdi_connection_info.json cannot be found: $tfwPath"
    exit 1
}
 
# Get and convert JSON
$jsonContent = Get-Content -Path $tfwPath -Raw | ConvertFrom-Json
 
# Get the last entry for the session (new session)
$session = $jsonContent.VdiConnectionInfo | Select-Object -Last 1
 
# Extract data from JSON
$vdiState = $session.vdiConnectedState
$vdiVersion = $session.vdiVersionInfo
$devices = $session.devices

$vdiState.vdiMode

We need to renew our Horizon licenses in the coming months. In the past, we used Horizon for Desktop licenses. We understand that the new licenses are now called VVF for VDI. The challenge is that we are also using vSAN, and the 100 GB per core included in the VVF license is not sufficient to cover our cluster. Unfortunately, adding additional vSAN capacity through TB-based licenses is not permitted. Switching to a standard VVF/VCF license combined with Omnissa is also very expensive. Do you know of any trick or workaround to increase our licensed vSAN capacity by increasing the number of cores in a cost-effective and simple way? For example, what if we add some nested ESXi hosts to the cluster and keep them powered off—would that be a legal solution?

does someone using Windows Defender with instant clone?

before i put a ticket in, the 2503 Omnissa client isnt' installing as part of an SCCM task sequence anymore, and its causing other apps to fail - Asking if theres a suggested way to install it? Errors saying Windows Firewall needs to be running now... What is the proper way to install this now in a task sequence?

💻 EUC Blog - Deploying Horizon Cloud Next-gen Edge on Amazon WorkSpaces Core 💻 Every now and then we see a great blog that breaks down AWS-specific domain knowledge for configuring EUC by an independent site that I just have to share with the community. This Sharing for Better blog leaves nothing to the imagination and makes it easy to follow if you're setting up Omnissa Horizon on WorkSpaces Core. Thread in Slack Conversation

With the Windows OS Optimisation tool 2503 for Windows Store should Notepad and Snipping tool be added for Windows 11?

https://us.omnissa.one/event/a54b2cb4-aa9b-4825-9739-a156b0a2078b/omnissa-one?utm_ca[…]-global%E2%80%8B&utm_medium=organicsocial&utm_source=linkedin Omnissa ONE 2025 Registration opened!

Did anyone else just get a blank contract update from "prod@omnissa.com" show up in their boxes?

Anyone hitting "Failed to connect to Connection Server" after upgrading to Horizon 2503? Issue described here - https://kb.omnissa.com/s/article/6000956. The KB specifically calls out WorkSpace One being involved, but we are not using WS1 and have the same issue with the same log file entries. Omnissa says that we need a hot patch which will take 1-2 weeks to get to us. In the meantime, the only fix is for users to delete the Horizon cookies from their browser or use an incognito tab.

Horizon 2506 dropped overnight! Got it loaded up in my lab this morning (upgraded from 2503) with no issues. If anyone is considering it, make sure you've reviewed the relevant KBs for the branding change, and LDAP namespace change. Reading the release notes yesterday, I'm pretty sure you NEED to complete the name change prior to upgrading to 2506 (using the powershell script, or having a fresh install of 2503).

Did the release notes for the new Windows client version not get added? The link to it fails but other client versions have working links to theirs https://docs.omnissa.com/bundle/horizon-client-windows-RNV2506/page/HorizonClientWindows-ReleaseNotes.html

Has anyone leveraged Horizon DaaS? If so, what has been the experience so far?

Does anyone have a good document I could reference for deploying Horizon on Azure?

Hi all, what is the best practice for instant clone Win11 VDI-s? I configured Hybrid Join, and wait for Hybrid Join. So after VDI creation it can take quite long until the new VDI is Joined and sign-in enabled. I can imagine a scenario, when users log in then log on, and then log in. and then there is no free VDI which is already joined. So no login possible. 1. I can think, to have always enough VDI-s spare. But how to understand the user behavior, to size this correctly. 2. To enable seamless SSO, then no hybrid Join is needed to SSO, and problem not existing. But there is security concerns as I understand. 3. In Conditional Access to make some rules that VDI-s must not be hybrid joined. maybe something else? Thanks.

Hi all, recently Omnissa made available provisioning in Nutanix. I'd like to know if any of you already tested this new feature and your thoughts please. I have a Customer going to Acropolis and is afraid if this is working or not. Thanks. https://www.omnissa.com/insights/blog/omnissa-horizon-8-support-for-nutanix-ahv/

Virtualization Based Security, is it recommended to turn it on on Windows 11 VDI? If yes, can you recommend some guides? Thanks.

Curious, I know Omnissa Horizon only supports activation via KMS (or MAK, but we aren't going to talk about that). While I generally recommend this, I see more and more customers going against this recommendation, and utilizing the M365 Virtualization benefits, where it provide virtualization benefits via Pro to Enterprise Uplift during Azure Hybrid join, thus performing Windows 10 Enterprise activation. What's interesting is that while "slmgr /dlv" and Windows itself, both show that it succesfully activated Windows 11 Enterprise via Subscription, the background of the desktop still shows "Activate Windows". Anyone know how to get rid of that, or if something is missing?

Different topic.... I know Windows 11 25H2 isn't officially supported, but decided to give it a whirl since it's so close to the 24H2 code base..... And, it's working pretty good with Horizon 2506 and App Volumes 2506 🙂

Teams 2.0 (Slimcore) Beta testing is underway! I'm a member of the Tap Program, and wanted to let you guys know that Horizon will FINALLY be getting the slimcore version. We get the beta software next week for testing, and the project runs for a couple months. It will move quickly, as Slimcore was already available for Citrix, and they learned alot during that rollout. Due to NDA, I cannot provide many details, but the timeline is OK to discuss. Just know that it is finally coming in Q1 2026!

Is it possible to integrate multiple Entra ID tenants for access to horizon?

This advisory is to formally inform you of a recently identified issue affecting Virtual Desktop launches and connections when using the Omnissa Horizon Windows Client. The issue arises after the installation of the Microsoft Windows Patch update KB5066835 on end-user devices. Recommended Mitigation Strategy To ensure service continuity while a permanent resolution is being developed, please take the following actions based on your current environment: 1. If KB5066835 has not yet been installed: 2. Action: We strongly recommend deferring the installation of the Recent Windows update (KB5066835) until an official corrective patch from Omnissa or Microsoft is released and validated. 3. If KB5066835 has already been installed and desktop connection issues are observed: a. Option A (Client-Based Mitigation): Temporarily uninstall updates KB5066835 and its prerequisite KB5065789 from affected devices. b. Option B (Interim Access): Use the Horizon HTML Client (browser-based access) as a fully functional workaround to maintain connectivity to your virtual desktop. Status and Resolution The Horizon Engineering Team has assigned the highest priority to this issue. We are actively investigating the root cause and collaborating closely with relevant partners to identify, test, and release a validated fix at the earliest possible time. We will issue a follow-up communication as soon as a corrective update becomes available or if there are any significant developments in the resolution process. We sincerely appreciate your patience, cooperation, and understanding as we work diligently to restore full functionality and stability. If you have any questions regarding the prerequisites or this update, please contact Omnissa Support. Sincerely, The Horizon Cloud Service Team