We're seeing a random new issue (couple weeks new), where the Horizon client hangs sometimes up to a minute on the loading desktop screen when connecting to a desktop pool. It happens on instant clone pools as well as full clone desktops. We've eliminated going through load balancers, we've gone directly to brokers, we have tried internally, externally, different client types, etc. We can't identify a consistent way at all to reproduce it, it just happens or it does not.
We plan on opening a ticket, but was trying to seeif anyone has come upon this before. To our knowledge there has been no network/firewall change to lay the blame at, and our Horizon infrastructure/Windows desktop has remained unchanged: 7.13, Windows 10 20H2 (some 22H2).
Thanks in advance.
1. Try to login VDI from Browse (HTTP)
Check there also same issue persist, try step 2 and 3.
2. Verify horizon client recent version on your laptop or desktop.
3. Try to reinstall horizon agent in master image and recompose pool once.
This issue will happen Horizon client try to communicate Horizon agent. If it is take time to communicate both..we will face loading page on Horizon client.
Major possible case :
Horizon client and agent are need to be reinstall.
(Mostly we changed some settings on master image. Then we directly composed to pools.
Best practices is if we do any changes on master , try to reinstall agent as well.
For me it is work. Try it.
The first attempt to connect to a VM that is turned off will maintain a long loading state (it will connect in about 5 minutes). If I end the session during loading and try to reconnect, then, connected immediately.
Our issue is still ongoing. It's a random issue and all of the listed troubleshooting steps in this thread were eliminated early on as causes/fixes. We are currently engaged with VMware professional services on a Horizon 8 upgrade, and when finished we plan to take a fresh look at it. I'll update the thread as we go along.
The slowness in loading a desktop can happen randomly on both persistent as well as non-persistent desktops. So the profile creation in this scenario is moot.