![]() I've removed the agent and tools and installed them in the correct order. Thankfully, we are in pilot at the moment but this issue is starting to annoy me.ĭoes it matter too much if I run 7.6 agent on the workstation and 7.4 on the Horizon server components? I've raised a case with VMware who stated that we should put in a task to logout the workstation completely at the end of the day which is not really an acceptable answer. Session is completed unusable and unable to logout.Ĭhecking vCenter, the CPU and the VM looks to be pinned however after logging on to the VM using the local admin account (took 90 mins to login, the CPU is not pinned. A stated goal in the VMware Horizon documentation is 'to provide an excellent out-of-the-box configuration for most local area network (LAN) use cases, negating the need to perform complex tuning or learn hundreds of policy settings. Point your mouse at the top of the remote desktop window until the menu bar appears and then click the Disconnect button. User disconnects and reconnects at another time and they are faced with a black screen (intermittent)ģ. User logs on via PCOIP and connects to workstation fine.Ģ. Horizon Client for Windows is supported with the latest maintenance release of the following deployment types: VMware Horizon 8 version 2006 and later. Our Horizon infrastructure is on VMware Horizon 7.4Ĭlient agents are on 7.6 (due to issues with Persona not working correctly with 7.4)ġ. Resolution This issue is resolved in VMTools 11.3.0 version. ![]() We are experiencing a really odd issue in VMware Horizon 7.4 and Windows 10. Black screen occurs due to an issue in the WDDM SVGA driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |