We are running Wyse P20's with VMware view connecting to Windows 7 virtual desktops via PCoIP only. All desktops are assigned and have a permanent 😧 drive to keep user settings. All firmware, software, patches and drivers are the latest. We have deployed the Wyse P20's to several employees very successfully. Up till now the monitors have been dual Dell 1950 FP 19" monitors.
We originally had extensive issues with setting the resolution on the clients once they connected to the VM, but resolved it by just choosing the resolution we wanted on the P20 device before we connected to a view client. Not sure now if this is how everyone is really solving this problem or not. Once connected you can see all the resolution options on the VMview/Windows 7 client and you can select them, they just do not take or keep the changed setting past the users logoff. But, since setting the resolution on the P20 clients worked we just moved on.
We are now to the point where we would like to deploy the P20's to users with 30" HP LP3065 displays, but we are having a problem with the resolution. These displays are native 2560 x 1600 and 1200 x 800, there are no other native resolution options. Obviously our desktop graphic cards up till this point have been scaling the resolution to what the user wants. When the P20 is left with the resolution option in the "native" setting (via access it through the options settings menu) it will try to connect to the desktop at 2560 x 1600 and the screen goes black and stays black. If you set the resolution to 1200 x 800 (again via the options menu) it will connect to the virtual view machine, but it will not keep any other choices for screen resolution.
I can't imagine this is right and how it is suppose to be working. Should we be able to select 1920 x 1200 on the windows client and have it keep that for use when they are connecting via the P20 or are we bound to the native resolution of the monitor the P20 is hooked to?
Any help woudl be greatly appreciated.
If your monitor is connected using the DVI-D port then you are locked into using native resolutions. If you connect using the D-sub port, VGA port, or however you prefer to call the thing, you can change your resolution to a lot of different settings. I'm not totally familiar with your setup, but if you connect using analogue then you have more options for resolution. This is what I expirenced using XPe on HP thinclients and regular old RDP.
We are using the DVI port's for the 30" monitors and it does not have analog ports on this device. I know the P20 use VESA monitor support with Display Data Control DDC, but did not think that was limiting the resolution choices.
If anyone else is using P20's what monitors are you using and are you limited to the native resolution also?
I thought I would share what I have discovered about the resolution issue. I do find this implementation to be slightly strange and I am not sure I understand why it is being implemented this way. Let me lay out a few things that are a given here in hopes anyone else having this problem can understand what they are seeing. I believe this to be a Teradici and Vmware issue not a Wyse issue.
The Wyse P20 client is using Teradici PCoIP with Display Data Control DDC. The PCoIP software is detecting from the monitor firmware the highest native resolution that is supported, along with the other supported resolution settings. In this case it was detecting 2560 x 1600 and 1200 x 800 for the HP LP3065 30” monitor. Currently the screen resolution limitation on the hardware/PCoIP is 1920 x 1200 for the Wyse P20. In VMware view when creating the linked clone pool the monitor resolution is set to 1920 x1200, but the PCoIP selects the HIGHEST resolution possible by default, even if this resolution exceeds all specs and VMware option settings.
Each time the P20 is booted when connected to the HP LP3065 it selects the 2560 x 1600 “native” resolution. To get it to change you need to select a different setting in the device option settings. YES, the device. Selecting the resolution on the VM works IF you select one of the detected resolutions on the monitor, but the device and the view client do not talk to each other about this and the view client presents the end user with every resolution possible. How many end users will ever know what the monitor is capable of? The PCoIP device try’s to be clever and prevent you from selecting the incorrect resolution, but does not present the user with any information why it did not change or why the screen is blank. Not sure why a message could not be embedded into the firmware here for this.
So, I have to wonder why, since PCoIP is just sending compressed screen data down the wire it cares about anything more than the max resolution supported on the attached monitor and why it cannot work with VMware view to present acceptable options to the user. I can connect to a VMware view linked clone with GoToMyPC, VMware view client and dameware and they will let you select ANY scaled resolution.
What am I missing here, because I have a feeling this is just a design not totally thought out. If the idea is wanting more companies to adopt VMware view technology it should not be a step back for things like this.
We are running WYSE P20's and have many users that think the native resolution leaves the text on the screen too small, and want it changed. Most of our monitors with the thin clients are 19" standard, though we have some 17" standard and some 19" and 24" wide. We wrote out a script that runs at startup and changes the resolution for them. Not an elegant or graceful solution, but that's our current workaround.