ishki

I've observed higher CPU usage in case of a CS that's running on a Windows Server 2022, compared to ones running on Server 2019. However, as we only upgraded one Win server to that newer version, I don't have much statistical evidence of that correlation. You may want to test toggling off settings "Cloud delivered protection" and "Automatic Sample Submission" from Windows Security/Virus and Threat protection/Manage Settings on the windows server your CS is running on. Also, you can define under "Exclusions" that Defender should not scan your Connection Server folders.

Hello, Are there any plans to offer NSX (with full firewalling features) as an optional OEM component to Horizon license bundle? It's not too clear now what and from which counter we should purchase if we intend to upgrade Horizon licenses and keep using and updating NSX in a Horizon-only environment as before. It would be way less messy and frustrating if we could avoid making separate deals with Broadcom for that purpose.

Right now I can see and use all necessary licenses but I'm quite worried what awaits by the end of the year, when we must renew those. We use both VSAN and NSX in our Horizon setup and if I'm not mistaken, it's just very restricted "sample" VSAN capacity that comes bundled with Horizon offering by default, as it's apparently basically fixed to Horizon & VVF. A huge concern is whether if that's an dead end wrt. said extras and we practically would have to throw away the bundled VVF licenses and purchase new VCF ones at full price in order to be able to open path for decent capacity VSAN and NSX (+get additional licenses for NSX firewalling, as the VCF-bundled version of course now lacks by default that key part of NSX functionality). All in all in that case the price tag may get so high we have no other choice than to start looking for alternatives.

For me Desktop Pool view is probably the most actively used, due to frequent need to monitor pool usage and push image updates, etc. It would be great if the pool error status indicator which is now a tiny red dot could be changed to more visually noticeable alert (perhaps highlighting the whole row, for example). If I may suggest another thing for consideration; in each Pool the Stop Provisioning on Error option is now strictly an on/off choice. I'd guess sometimes an error might be caused by just a momentary glitch, so if there would be an option to define number of errors (for instance, 5 tries ) to be tolerated before stopping, that might save users from basically unnecessary VM outage esp. considering out-of-working hours situation when manual admin intervention takes time.

Has anyone else noticed increased Conncetion Server CPU load once upgrading to 2406? In our test environment, CS1 and CS2 still show load at 0,5GHz or less but CS3 and CS4 have constantly jumped to around 3GHz even though the test environment has hardly any users connected. Looking at the process list on affected CS reveals that TomcatService.exe is the main consumer of CPU resources. Rebooting the servers drops it down for some time but does not have a lasting effect.