FatPog

No enable host redirection option in 2111 it seems Have attached screenshot of the connection settings. In this environment there is one for internal, and another for external (behind UAG) No settings in locked.properties other than default.

Have attached Cheers

Hi team I am trying to upgrade from 2111 to 2312.1. Upgrading the connection server from 2111 to 2312.1 works initially. I can log in, see that it is version 231.2 and launch a desktop session. However, when I reboot the connection server it stops working. I cannot get to console. The services are all still running. The issue appears to be similar to this article, but solution does not seem to be applicable to me JAVA_TOOL_OPTIONS on a VMware Horizon Connection Server = Not Good (stevenbright.com) Any ideas what could be causing this?

Hi team I have to upgrade this environment which does not conform to best practices and it has been a bit of a headache. I am seeing some behavior that I do not understand. There are two connection servers. The primary server, con1 resolves to connect.mydomain.com. I access the admin console via connect.mydomain.com/admin Now there is supposedly no load-balancer. But when con1 is down/disabled and I go to con2.mydomain.com/admin it redirects to connect.mydomain.com/admin. What drives this behavior? I noticed that the config.properties file has a clientHost=connect.mydomain.com. Is that it or is there something else that drives it? Cheers

So I have not touched Horizon in nearly 3 years and have been tasked with upgrading an environment that I have no prior knowledge of. I am running into issues. It is a very messy setup. There are no load balancers or setup documentation. The idea is to go from 2111 to 2406.Currently this environment has one UAG and two CS. One CS is for internal purposes (Con1) and the other for external connections (Con2). The UAG has its connection URL pointed to con2.domain.local and its thumbprint points to the SHA1 of a wildcart cert *.company.com The CS both have the wildcard certificate loaded (vdm). Now somehow connecting is working fine under 2111. Not that I understand it because the wildcard cert has no knowledge of con2.domain.local. Is there some hidden setting somewhere that could translate anything? I follow the upgrade process. I can upgrade the CS to 2406. Once upgraded I can still connect to the desktops internally via CS (I did notice that it overwritten the branding back to default. Any tips on how to save the custom branding appreciated). Next I do the UAG. Deploy new one and import settings. Now this did not work and I believe that this is because of SHA1 setting not being supported. I configured it manually with same settings but changed it to SHA256. The certificate was already SHA256.And things don't work via UAG anymore. I believe it should not work because the connection url domain name does not match the wildcard. But I am stumped over how it works with 2111. What am I overlooking? I have not verified yet but could it be a setting in one of the properties files that got overwritten with the CS upgrade?From memory, I saw an error along the lines of "vmware horizon rejecting request unexpected host header". The Horizon settings in UAG are green but in CS admin portal it says unreachable.I hope this makes sense.