I performed an in place upgrade of Horizon View 6.2 over the weekend and have been very happy with the performance and features. However, I am having a bit of an issue with Windows 10 Enterprise. The VDI desktop does not resize/scale as expected. It seems that whatever the Windows 10 desktop setting is set in vSphere, seems to remain when connecting with the View Client.
I had this issue in Horizon View 6.1.1 with the 3.4 client, but didn't sweat it until this recent release.
I wanted to eliminate my Windows 10 Enterprise image as being the culprit, so I installed a fresh version of Windows 10 Enterprise 64-bit with the latest VMware Tools and View Agent and the issue persists.
I am running vCenter 6.0.0.b and ESXi 6 with the latest patches. I can validate the screen resize/scale issue occurs on multiple endpoints, so I do not believe the issue is with the endpoint device and the client.
I had this issue in my staging pool, but with Windows 7. Solution was to completely uninstall the View Agent from the parent image, reboot, reinstall. I've had similar issues in the past and even though VMware swears you should just be able to update the View Agent in-place, it's more trouble than not when it doesn't work. Stick to uninstalling, rebooting, installing.
Not at all. I find the Horizon View is one of the easiest and most reilable to update. In fact, I have upgraded from 6.0 to present within the first few days of its release with no issues to production. Cant say the same for my luck with vCenter and vSphere
Exactly, after upgrade to 6.2....I upgraded the agents but people's VM's weren't scaling correctly. I had to uninstall agent, reboot, install agent, reboot again and all was good. It was a big pain in the butt.
Sorry to bring back an old post, but I am seeing something similar following upgrade to View 6.2 with Windows 10 clients.
If I enable 3D Rendering on my Windows 10 pool of VDIs the desktop does not render correctly when logging in, the start menu appears "ghosted" and apps don't draw correctly on the screen.
I have to disable 3D Rendering on the pool, but this is not ideal.
I have pools of Windows 7 and Windows 8.1 VDI that work fine with 3D Rendering enabled, I am only seeing this issue on Windows 10 VDI.
Has anyone else seen similar behaviour?