We had the same exact issue after upgrading our connection servers to 2111. With the help of VMWare technical support we were able to get things working by doing the following 2 things. Add these ...
See more...
We had the same exact issue after upgrading our connection servers to 2111. With the help of VMWare technical support we were able to get things working by doing the following 2 things. Add these two lines to the file c:\Program Files\VMWare\VMWare View\Server\sslgateway\conf\locked.properties checkOrigin=false enableCORS=false Use 127.0.0.1 instead of localhost in the URL. The updates that patch the Apache Log4j vulnerability apparently prevents the use of localhost Example: https://127.0.0.1/admin The FQDN should work as well (https://myConnectionServer.domain.com/admin) Hope this helps.
Has anyone had any luck correcting this issue? We're experiencing the same thing on 5.1. It does seem apparent that it's detecting different monitor configs in different states.