- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Horizon 8 2111 upgrade after Administrator Page Blank Screen
Hi,
I upgraded from Horizon 8 2012 to Horizon 8 2111. When I click on the application, Horizon Administrator Page opens as Blank Screen.
Address bar " https://127.0.0.1/admin/#/login " When I changed it to , the page opened.
I found a resource that didn't work.
I cleaned the browser cache and the problem was not solved.
Any suggestions? Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same issue, luckily I took a snapshot ahead of time. I can logon with the loopback address too but can't connect to any desktops. I had to revert it back to 2106.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wow! I thought it was just me. Same problem here. Except, I did a CLEAN install on Windows Server 2022. I just don' t get the login Screen. I tried Google Chrome and Firefox but getting the login to appear is pretty much hit or miss.
I thought it was ADLDS so I uninstalled that also, but got the same result.
Just tried to externally login (different network machine and this time I got the login screen. I don't know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The locked.properties file is the most common issue, its what is described in the initial link, how are you connecting to the connection server? Directly or through a loadbalancer? If its through a loadbalanced adress makes sure balancedHost is configured in locked.properties
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a simple setup with only VMware Horizon Connection Servers to upgrade, so I don’t have multiple products and solutions to worry about as far as interoperability and order of operations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For me this first happened during the first attempt to connect to the CS using the localhost link on the Desktop. I also have a UAG 2111 installed but again, this was a fresh install, that would have needed to to be configured for the UAG.
/
I guess the question is what is responsible for presenting/calling that login box, on top of the Background.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same issue on 2111. Were you able to figure it out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry. No.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.