Re: View client for Windows - display resolution

fafa24 · ‎08-31-2015

Dear All,

We have an issue with a brand new Dell XPS 13 laptop. This laptop has a native resolution of 3200 dpi. When this laptop connects to a View desktop the icons and text are very small. It is not possible to work with a view desktop.

The latest View Horizon for View client is installed on the Dell XPS 13. Is there a way to adjust display resolution using RDP? The view client connects to a physical desktop using RDP, but even connecting with PCoIP or RDP to virtual view pool the resolution is the same. I do not understand since for the pool the resolution is restricted to 2560 dpi.

I hope there is a way to resolve it that one can work with View desktops with a Dell XPS laptops.

Thanks,

Edy

TonyHuynh201110 · ‎08-31-2015

Hi,

What you are asking for is High DPI scaling. We have support for it with Macbooks (due to retina display), but this isn't supported yet with Windows clients.

grossag · ‎09-01-2015

There is an experimental value you can use to enable scaling for high DPI screens, but it doesn't apply to RDP sessions. RDP does natively support syncing DPI to Server 2012 R2 and Windows 8.1 remote desktops though. For the non-RDP case refer to VMware Horizon View client and high DPI screens for more information.

fafa24 · ‎09-07-2015

I applied this experimental setting as per the blog

KEY: HKCU\software\vmware, inc.\vmware vdm\client

Value: DWORD: EnableSessionDPIScaling 1

1 = on

0 = off

The "VMware, inc" key didn't exist in the current user hive, so I created everything. Since I have found it a bit strange that the key didn't exist, I also created the reg key in the local machine hive.

But we both keys in the current user and local machine I didn't see a difference connecting to the VDI desktop.

The computer is a Dell XPS 13 with Windows 10 installed. The View client 3.4 is installed.

I guess that I need to wait until VMware release a new client.

Thanks,

Edy

grossag · ‎09-09-2015

That registry key should be there. Make sure that you are looking in "VMware, Inc." Also you don't need to go under Wow6432Node under HKCU (but you would under HKLM).