Dual monitors with zero client PCoIP not working

[gwebb6]

I am attempting to get dual monitors working with a VM via a zero client with View on it, over PCoIP. It is not working and I thought I would come to the experts. Any help would be appreciated. Here is the technical run down:

Windows XP Pro (32-bit) VM built on vSphere Client 4.0.0.

VM Tools installed, VM added to domain, VM Agent 4.0.1 installed, Windows updated, all in this order (through client mode).

Dell FX100 zero thin client with firmware 3.2.0 (v287) with two (2) Dell U2410 (24 inch monitors) designed for 1920x1200 @ 60Hz.

Configured with VMware View Manager 4.0 as part of an Individual Desktop that is Non-persistent. View Manager has the default display protocol as PCoIP, Max number of monitors set to 2 (I also tried setting it to 4 earlier, just for the heck of it), and the resolution of each monitor set to 1900x1200 (I also tried setting it to 2560x1600 earlier, just for the heck of it).

The VM was configured for 128 MB of ram (I shouldn’t need this much), and I set the “Maximum number of displays” to 2 (again, I also tried setting it to 4, just for the heck of it). It always reverts back to 1 monitor, even though the “Recent Tasks” show it was reconfigured.

Checking the VMname.vmx these are the key lines you may be interested in:

svga.vramSize = “134217728”

svga.numDisplays = “4”

svga.maxWidth = “10240”

svga.maxHeight = “6400”

Finally, I cannot go into the display settings in PCoIP mode. The single monitor works great, but I can’t go right-click, properties, Settings tab. The Settings tab is not there. It is there in client mode and it ‘sees’ two monitors, but when I enable the second monitor it reverts back to one.

Any ideas here? I need dual monitors on PCoIP.

[morrisosu]

I would you imagine you have already read this:

http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/

What settings do you see on the display tab when you go into the console of the VM in vCenter?

[Linjo]

I played around with this today and it worked fine, I did however use View 4.5 so I would recommend to update to that.

On the zero-client you should enable both monitors and set the correct orientation.

Does it work if you connect from a Windows PC with 2 monitors?

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[gunnarb]

You can't run dual 24 inch monitors on a Dell FX100. That zero client only has 64MB of memory, 128MB is required for dual 24 inch. THe Wyse P20 would support it, also I think my Samsun NC240 supports it.

It's not your VM, its your client. Check out this blog post (look in my comments where I talk about the memory difference, and I specifically talk about the dual 24 inch issue)

http://communities.vmware.com/blogs/gunnarb/2010/02/15/pcoip-review

-Gunnar

[gwebb6]

Going in reverse order here...

Gunnarb,

Not to burst your bubble, but 24's do work with the FX100. I've gotten it to work 1-to-1 (with the host card in the Dell R5400, PCoIP) and now with the VM PCoIP. It was a nice write up, though :). The latest patch/firmware (3.2.0) may fix your problem.

Linjo,

Thanks for the response. As much as I want 4.5 I can't have it yet. The idea to try View Client on a desktop was a great idea though, but I already solved the problem.

Morrisosu,

I've seen a nearly identical article to the one you posted, but the one I read did not mention installing .NET framework. I tired that, and boom! It now works! Thank you for your help.

[Linjo]

Great that you got it working!

I actually wrote the article...

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[gunnarb]

My bubble is offically bursted. I blogged on that freakin issue! Maybe you're right it might be a firmware 3.2 thing. Of course it could be just a lie that I believed, I thought I learned that from Wyse, but it may have been from wponder (VMWare forum guy). I never did test it for myself, I run Samsung's and opted not to buy the FX100 due to the uniqueness of the Samsung solution. Sorry I gave incorrect information.

Gunnar

[gwebb6]

Ha, no worries. You were going off of what you were given. I do appreciate the help however. Thanks again!

[LabsIT]

I am working on the same thing right now, but using a Wyse P20.

I found this page to be helpful, http://communities.vmware.com/blogs/virtualdesktop/2009/12/05/vmware-view-4-with-pcoip-multimonitor

At the bottom of the page it talks about how to get the Settings tab back for Display Properties.

The dual monitors started randomly working for me. I think what did it was to have all the settings you want put in to the View pool, then shut down the VM. Log in to the Zero Client and have it log in to the VM. For me, what it did was power on the VM and changed all the display settings to the correct resolution and turned on the second monitor.

The odd thing about it is, that when you look at the Video card settings of the VM it still says it is maxed at 1 display, but it has 2 on it.

[gunnarb]

VM settings are overrided by pool settings, so this makes perfect sense.

[riki78]

Hello

we have also problems with connection 2 Monitors.

But in our case sometimes the second monitors connects and at other times not...

i have found this in the pcoip_server log followings:

10/05/2010, 15:28:36.970> LVL:2 RC: 0 MGMT_SYS :SESSION ACTIVE

10/05/2010, 15:28:36.970> LVL:2 RC: 0 MGMT_IMG :CODEC: Processing MGMT_IMG_APDU_TYPE_CFG_ACK.

10/05/2010, 15:28:36.970> LVL:2 RC: 0 MGMT_IMG :Client has no preferred display topology. Using default values

10/05/2010, 15:28:36.986> LVL:2 RC: 0 MGMT_IMG :Native resolution of the client display 0 is 1280x1024

10/05/2010, 15:28:36.986> LVL:2 RC: 0 MGMT_IMG :Native resolution of the client display 1 is 1280x1024

10/05/2010, 15:28:36.986> LVL:2 RC: 0 MGMT_IMG :Client display 2 is not connected

10/05/2010, 15:28:36.986> LVL:2 RC: 0 MGMT_IMG :Client display 3 is not connected

10/05/2010, 15:28:36.986> LVL:2 RC: 0 MGMT_IMG :Topology processing result: 1(111)

10/05/2010, 15:28:36.986> LVL:2 RC: 0 MGMT_IMG :Native resolution of the client display 0 is 1280x1024

10/05/2010, 15:28:36.986> LVL:0 RC: 0 MGMT_IMG :set_display_topology: display[0]: (0, 0) 1280 x 1024

10/05/2010, 15:28:36.986> LVL:0 RC: 0 MGMT_IMG :set_display_topology: display[1]: (1280, 0) 1280 x 1024

10/05/2010, 15:28:37.002> LVL:2 RC: 0 MGMT_KMP :>>> Rxed SET_KBD_LOCALE: language=0x0807 layout=0x0000

10/05/2010, 15:28:37.127> LVL:2 RC:-500 MGMT_IMG :Error in VMwareResolutionSet_SetDisplayTopology: 2 displays requested, 5 tries remaining .

10/05/2010, 15:28:37.127> LVL:2 RC: 0 MGMT_IMG :cfg_process: minimum quality is set to 40

10/05/2010, 15:28:37.127> LVL:2 RC: 0 MGMT_IMG :cfg_process: maximum initial quality is set to 90

10/05/2010, 15:28:37.142> LVL:0 RC: 0 IMG_FRONTEND :Calling open display for Tera1 PCoIP peer

10/05/2010, 15:28:37.158> LVL:0 RC: 0 IMG_FRONTEND :configure_displays: 1 display(s) initially reported!

10/05/2010, 15:28:37.189> LVL:0 RC: 0 IMG_FRONTEND :configure_display[0]--* id: 1 mon_id: -1 pos: (0,0) w: 1024 h: 768

10/05/2010, 15:28:37.189> LVL:0 RC: 0 IMG_FRONTEND :configure_display[0]--bpp: 32 --pitch: 4096 --map size: 1552 --fb size: 3145728

10/05/2010, 15:28:37.189> LVL:0 RC: 0 IMG_FRONTEND :configure_displays[0]--rot: 0 --pre-rot pitch: 4096 --frontend motion is enabled

10/05/2010, 15:28:37.189> LVL:0 RC: 0 MGMT_IMG :Image Engine detected display #0 (1024x768) with offset (0x0)

10/05/2010, 15:28:37.189> LVL:2 RC: 0 MGMT_IMG :CODEC: State change from CODEC_CFG_EXCHANGE to CODEC_DMT_EXCHANGE

Have someone an idea what could be the problem?

We have set 2 Monitors in the View Manager, the vmx file shows correctly.

Is it possible that the vm has not enough Memory to conncet 2 Monitors? We have vms with windows xp and 512MB RAM.

Best Regeards

Simon

[Zirkle]

I don't have any log file like that, but I'm having the same problem where my wyse p20 sometimes connects both screens, sometimes it doesn't.  I can hit crtl+alt+del and then hit esc after it shows the lock/task manager list and the second monitor starts working fine.  This is win 7, view 4.5 or what ever the newest version is that released about 5 months ago.  It seems like it happesn on our wide screen monitors more than our standard monitors.

Any suggestions, did you find a fix?

Thanks

[Linjo]

This thread is a bit old, I suggest you start a new one with your specific problem since the original creators problem was solved.

Please also post the firmware on the P20 in the new thread.

// Linjo