NickTT's Posts

I will have to turn on debugging and do some more testing to get the actual logs from the client but while looking through my Enterprise Log aggregation tool, I spotted this message from someone else that has the 8.6 Client. HORIZON_SESSION:TERMINATED:Horizon Session terminated due to inactive I see that same message for everyone that drops. So it seams the 8.6 client isn't reporting back that the session is still active.   This was my session at the exact time I dropped, I was chatting in Teams. uag-esmanager: [pool-7-thread-1]INFO utils.SyslogManager[terminateSession: 497][108.51.115.200][nthoman][Horizon][5c24-***-d1bc-***-16f1-***-6d0b] - HORIZON_SESSION:TERMINATED:Horizon Session terminated due to inactive - Session count:615, Authenticated sessions: 18   This in the release notes for 8.6 has me wondering.... https://docs.vmware.com/en/VMware-Horizon-Client-for-Windows/2206/rn/vmware-horizon-client-for-windows-2206-release-notes/index.html Support for timeout warning and timer You can configure the warning to be displayed and set the timer at which the warning is displayed before a user is forcibly disconnected from a remote desktop or published application. You can also configure the message that is displayed when the user is forcibly disconnected. Display timeout message before forced disconnect You can configure a message and timeout warning to be displayed before a user is forcibly disconnected from a remote desktop or published application.  

We have 3 UAG all same versions. <Published Horizon URL for Clients> 2 in Production These operate with DNS Round Robin and a basic availability check to make sure the host is up. I use the same icon file check in the Horizon LB setup guide to check for system availability so I can take a unit offline for maintenance if needed. Only one record is ever returned in the DNS response. 1 in DR Will only get traffic if both production units are down. Oracle calls this Traffic Management Steering Policies and is a DNS feature. Think of it like load balancing light.   "Traffic Management Steering Policies enable you to configure policies to serve intelligent responses to DNS queries, meaning different answers (endpoints) may be served for the query depending on the policy logic."   Network traffic is 100% healthy. Oracle tool checks availability every 30 seconds and has great reporting to show any possible traffic issues. We also monitor with ThousandEyes eternally for redundancy monitoring and traffic is clean. Finally, I can confirm traffic flow through gateway monitoring and see no sessions are going through DR site. Something is different with the 8.6 client and how it is handling the network sessions. I was reading the release notes for it and see they introduced custom timeout warning messages. I am wondering if that is hardcoded or not tracking correctly and forcing the connection closed after 3 hours. The drop is EXACTLY 3 hours though. I can set a stopwatch to it.   

I still find issues with audio in 8. The volume and mute keys not doing anything even though windows is shows the volume going up and down. This seems to be tied to the HTLM5 redirected stuff though. Work around is just use the volume controls in sites like YouTube instead. The bigger issue we are running into is if you use Laptops as your terminal. We have discovered that if you undock a laptop while on Horizon and then dock back up, Teams will no longer work with your audio devices. It will refuse to pickup or connect to meetings till you completely close the Horizon Client and then relaunch it on the laptop. You don't have to restart your VDI machine. This seems to "unstuck" the audio hooks built into the Horizon Client for Teams and lets Teams behave as expected. I REALY miss S4B.... it worked SOOO much better in VDI.

We have strange behavior too... We have NVIDIA P6 cards that we are testing on Synergy 480 GEN 10 blades. Besides an ESX 7.0.2 bug that causes the host to Panic and Crash... , we also see issues with Teams. For us the big issue is when you share your desktop and minimize Teams so you get that little Toast window in the bottom right with call controls. The Toast will vanish but if yo hover over the location, the buttons are still there and active. It causes one to accentually hang up when trying to click on something that is behind the "Invisible Toast". (Insert Genesis joke)   Known Panic and Crash https://kb.vmware.com/s/article/85775

I have 9427 open from my Universal Access Gateway to my Internal Network. I don't have it open from external as it's not listed as the needed ports. Port Protocol Source Target Description 443 TCP Internet Unified Access Gateway For web traffic, Horizon Client XML - API, Horizon Tunnel, and Blast Extreme 443 UDP Internet Unified Access Gateway UDP 443 is internally forwarded to UDP 9443 on UDP Tunnel Server service on Unified Access Gateway. 8443 UDP Internet Unified Access Gateway Blast Extreme (optional) 8443 TCP Internet Unified Access Gateway Blast Extreme (optional) 4172 TCP and UDP Internet Unified Access Gateway PCoIP (optional) 443 TCP Unified Access Gateway Horizon Broker Horizon Client XML-API, Blast extreme HTML access, Horizon Air Console Access (HACA) 22443 TCP and UDP Unified Access Gateway Desktops and RDS Hosts Blast Extreme 4172 TCP and UDP Unified Access Gateway Desktops and RDS Hosts PCoIP (optional) 32111 TCP Unified Access Gateway Desktops and RDS Hosts Framework channel for USB Redirection 9427 TCP Unified Access Gateway Desktops and RDS Hosts MMR and CDR

Lack of control of updates is also silly with Teams. It's like MS tossed out their Enterprise playbook completely.  We are running in Optimized mode. However getting there was a problem because people started installing Teams in their user profile. Had to build a script to delete it and install it the "VDI" way to get that Optimized mode to switch on. I bumped up the memory reservations on the two Horizon connection servers to 8GB with a max of 16GB available to the OS. I read here that people saw better performance with Teams once they made that change. I'll have to wait and see. I also put in rules to keep the Horizon Servers on separate hosts. Confirmed DRS isn't bouncing the servers and VMs around, especially around times users report issues. Anything else to look at would be helpful.

Ours has been crap. Constant audio, video and sharing issues when in VDI. No issue when the machine is physical. I have gone as far as even setting DSCP priorities for Horizon to see if it helps with no luck. I am ready to toss Horizon out. Not sure how this is really saving me any time or money when I can get micro desktops for under $500 with dedicated CPU, Graphics and HD per person. I already have to get them anyway as a "Terminal" machine. Any tips? We are running in optimized mode with Blast. Only around 200 users with 2 connector servers.