Posts

The UAG That Wouldn't Stay Diagnosed | When Vendors Don't Have the Answer

The UAG That Wouldn't Stay Diagnosed | When Vendors Don't Have the Answer Field Notes — VDI Access Infrastructure The UAG That Wouldn't Stay Diagnosed A power cycle fixed it. That's not the same thing as knowing why it broke — and the gap between those two facts is the actual lesson. Environment: VMware Horizon, dual UAG / dual RADIUS / dual Connection Server Trigger: post-maintenance full reboot Vendor documentation is good at describing the happy path. It's much thinner on what happens when every component in a Horizon access chain gets rebooted in the same maintenance window and one of them comes back slightly wrong — wrong enough to fail intermittently, not wrong enough to fail obviously. This is one of those cases. The environment Topology External Horizon Client traffic terminates at a load balancer VIP, which distributes across two Unified Access Gateway (UAG) nodes. Two RADIUS servers handle OTP, and t...
Post a Comment
Read more

How to Fix VMware Horizon "VDP Connect Failure" on Low-Spec PCs

How to Fix VMware Horizon "VDP Connect Failure" on Low-Spec PCs The Mind-Boggling VDI Fix: Resolving Horizon View "VDP Connect Failure" via Client Downgrade Published: June 2026 | Category: IT Infrastructure & VDI Troubleshooting 1. The Incident: A Sudden "VDP Connect Failure" and Immediate Disconnection In the world of VDI administration, some errors defy standard troubleshooting logic and leave you feeling completely dumbfounded. Recently, a specific user reported that they could no longer connect to their virtual desktop. Upon trying to establish a session using the VMware Horizon Client , a generic "VDP Connect Failure" pop-up would trigger, and the client would immediately drop the connection and close. "We changed the entire network routing, tested different internet service pro...
Post a Comment
Read more

How to Fix Microsoft Teams "Not Optimized" Error in VMware Horizon VDI (Teradici Tera2 Zero Clients)

How to Fix Microsoft Teams "Not Optimized" Error in VMware Horizon VDI (Teradici Tera2 Zero Clients) Fixing Microsoft Teams "Not Optimized" Error in VMware Horizon VDI with Teradici Tera2 Zero Clients Published: June 2026 | Category: VDI & Cloud Workspace Troubleshooting 1. The Issue: Microsoft Teams "Not Optimized" Warning When running Microsoft Teams within a VMware Horizon View Virtual Desktop Infrastructure (VDI), users frequently encounter a prominent warning banner stating: "Teams is not optimized for VDI" or "Not Optimized." This status indicates that the Horizon media optimization engine has failed to load. As a result, all audio and video processing is forced to run on the VDI host server rather than being offloaded to the endpoint device. This leads to: Severe audio/vi...
Post a Comment
Read more

PCoIP VDI Connects on Any Wi-Fi — Except Home: Root Cause and Why the Real Fix Isn't What You Expect

  PCoIP VDI Connects on Any Wi-Fi — Except Home: Root Cause and Why the Real Fix Isn't What You Expect Published: 2026 | Category: VDI Infrastructure / PCoIP / Remote Access The Short Version A user connects to VMware Horizon VDI without issues from office networks, coffee shops, and external Wi-Fi. The moment they try from home, the session authenticates successfully, then hits a black screen and disconnects. Mobile hotspot works fine. The problem is not the VDI infrastructure, not the client, and not the user. It is the home ISP router's NAT behavior — and it is outside the IT administrator's control. 1. The Symptom Pattern This issue follows a consistent pattern that makes it recognizable once you have seen it: VDI connection works on office network VDI connection works on external Wi-Fi (coffee shops, client sites, co-working spaces) VDI connection works on mobile hotspot (LTE/5G tethering) VDI connection fails at home — login screen appears, authenticati...
Post a Comment
Read more

Windows 11 24H2 Breaks VDI Authentication: How Cross-Domain Apps Lock Your Horizon Account (Event ID 4648)

  Windows 11 24H2 Breaks VDI Authentication: How Cross-Domain Apps Lock Your Horizon Account (Event ID 4648) Published: 2026 | Category: VDI Infrastructure / Windows Authentication The Short Version After upgrading to Windows 11 24H2, users in environments where a VDI domain and a separate application domain share the same account username begin experiencing unexpected VDI account lockouts. The trigger is any application — Outlook, internal messengers, network-mapped drives, SSO-integrated systems — that attempts to authenticate against its own domain at runtime. Windows 11 24H2 changed how it handles explicit credential logon internally, causing the application's authentication request to bleed into the VDI domain. The result: Event ID 4648, failed logon attempts against the VDI domain, and account lockout. Microsoft has not released a fix as of 25H2. 1. The Environment Where This Breaks This issue surfaces specifically in environments with the following conditions: VM...
Post a Comment
Read more

How to Fix Zscaler and VMware Horizon VDI Disconnection Loops

How to Fix Zscaler and VMware Horizon VDI Disconnection Loops How to Fix Zscaler and VMware Horizon View Client Crashes & Disconnections In modern enterprise environments, pairing Zscaler Client Connector with VMware Horizon View Client is a standard practice for secure remote work. However, many IT administrators and end-users frequently encounter frustrating issues, ranging from sudden application crashes to constant VDI disconnections. Because both applications operate at a deep network driver level to intercept traffic and manage encrypted tunnels, they often cross paths and interfere with one another. In this article, we will break down the most common crash case studies, their root causes, and how to configure them to work together seamlessly. 1. Common Crash and Issue Symptoms A. Sudden Horizon Client Crashes (Hang / Force Close) Symptom:...
Post a Comment
Read more

Fixed: VMware Horizon UAG "Unrecognized Request Detected" Warning

Fixed: VMware Horizon UAG "Unrecognized Request Detected" Warning Horizon UAG: Solving the 'Unrecognized Request Detected' Mystery Published: May 5, 2026 | Category: VDI Infrastructure & Security Overview of the Symptom In a VMware Horizon environment, administrators often encounter a yellow warning on the Unified Access Gateway (UAG) stating: "Unrecognized request detected." Curiously, the Connection Server remains healthy (Green), and the event often vanishes from the Horizon Console after a few minutes. 1. Root Cause Analysis This alert is a result of the UAG’s built-in security filtering. It triggers when the UAG receives traffic that does not conform to the expected Horizon protocol or HTTP standards. External Bot Scanning: As an edge device, the UAG is frequently hit by automated scanners (e....
Post a Comment
Read more

Popular posts from this blog

Troubleshooting VMware Horizon Client vdpConnect_Failure Issue

  Introduction VMware Horizon Client is a widely used solution for virtual desktop infrastructure (VDI). However, users may encounter various connection issues, one of which is the vdpConnect_Failure error. This error often results in a black screen followed by a disconnection, preventing users from accessing their virtual desktop. In this article, we will explore the possible causes of this issue and provide step-by-step solutions to resolve it. Common Causes of vdpConnect_Failure 1. RPC Server Unavailable One of the most common reasons for vdpConnect_Failure is the unavailability of the Remote Procedure Call (RPC) server . This can occur due to: The RPC service being stopped or disabled Network issues preventing communication with the server Firewall blocking required ports 2. Display Protocol Issues (Blast/PCoIP/RDP) Horizon Client uses different display protocols such as Blast, PCoIP, or RDP . If there are misconfigurations or compatibility issues with the selected protocol, ...
Read more

VMware Horizon Agent “Protocol Error” — Fixed by Windows Firewall Configuration

  🖥️ VMware Horizon Agent “Protocol Error” — Fixed by Windows Firewall Configuration Overview Recently, I encountered an issue where several Horizon Agent–based virtual desktops in our environment showed the status “Starting other services” or “Protocol Error” in the Horizon Administrator console. Even after reinstalling the Agent (version 2206 ), the problem persisted. Symptoms Horizon Agent status: “Starting other services” → “Protocol error” Horizon main services appeared to be running normally Event Viewer showed Event ID 7000 for services such as: PASVC – failed to start LUFAV – not installed Reinstalling the Agent (even using Repair mode ) did not solve the issue Root Cause After deeper inspection, we discovered that on the affected VMs: Windows Defender Firewall (Domain Profile) → “Block all incoming connections, including those in the list of allowed apps” was checked (enabled). This setting silently blocks all inbound traffic , ev...
Read more

VMware / Omnissa Horizon Agent Unreachable – Causes and Fixes (Complete Troubleshooting Guide)

  Keywords: VMware Horizon Agent Unreachable, Omnissa Horizon Agent unreachable, Horizon View troubleshooting, Blast service issue, Horizon Agent not responding, VDI connectivity problem In VMware Horizon (now branded as Omnissa Horizon ), administrators frequently encounter the “Agent Unreachable” state in the Horizon Console. While a simple reboot often resolves the issue, persistent cases indicate deeper infrastructure, service, or network-layer problems. This guide provides a structured root-cause analysis and remediation checklist suitable for production VDI environments. What Does “Agent Unreachable” Mean? When a desktop shows Agent Unreachable , the Horizon Agent inside the VM cannot communicate with the Connection Server . The failure typically occurs in one of these control paths: Horizon Agent → Horizon Connection Server Blast Secure Gateway (BSG) → Agent Windows OS services → Horizon Agent service Firewall or network layer blocking agent heartbeat ...
Read more