OPERATIONAL DEFECT DATABASE
...
...
Horizon Clients earlier than version 5.0 do not connect as expected with Connection Server version 7.8.
To fix this issue, you must train your users to use domain\username or UPN to authenticate. Alternately, you can configure certain global settings for Connection Server version 7.8 to determine how users with Horizon Clients earlier than version 5.0 can log in to the server:The following table describes logon scenarios and related global settings you need to configure in the Connection Server's global client settings. One domain, optimized for user experience with improved security Hide domain list in client user interface = falseSend domain list = false Username worksDomain\username failsUPN worksCommand line with domain fails Multiple domains, optimized for user experience with improved security Hide domain list in client user interface = trueSend domain list = false Username failsDomain\username worksUPN worksCommand line with domain works Horizon 7 version 7.7 user experience Hide domain list in client user interface = falseSend domain list = true User selects domain from a drop down menuUsername worksDomain\username worksUPN worksCommand line with domain works Optimized for security Hide domain list in client user interface = trueSend domain list = false Username failsDomain\username worksUPN worksCommand line with domain works
Documentation : https://docs.vmware.com/en/VMware-Horizon-7/7.8/horizon-security/GUID-FB9FE1B3-677D-4363-A7B0-66E939A56469.htmlAnnouncement Details : https://blogs.vmware.com/euc/2019/03/logon-vmware-horizon.html
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
