View 4.6 - Windows 7 VM will not detect second display

[NetCE]

I've been trying to resolve this issue for the last few days, any help would be appreciated.  We are currently running View 4.6 with composer and Windows 7.  We have a WIndows 7 parent image that a VAR set us up one; I am currently trying to create a new parent image to be used with the production floating pool we will eventually deploy.

On a vanilla install of WIndows 7 Pro, after installing VM Ware Tools and the View 4.6 Agent, I am unable to get the VM to actually display on dual monitors.  This is with both the fat windows client on a XP machine connected to dual monitors, and a WYSE thin client connected to dual monitors.

The test pool with the original Win 7 parent works with dual monitors fine.

The new parent does not.

I am using PCOIP, I have tried with the WDDM and the SVGA II driver, both to no avail.  In the new pool, I have the "max monitor" setting set to "2".

In both instances, when going to the "screen resolution" setting in Win 7, I see the single monitor with its settings blacked out, and the second monitor is not detected.

When logging in to the pool with the old parent image, I see both monitors with their settings blacked out, and it works fine.

What am I missing with my new parent image?

ps.  I tried creating the new parent image directly on ESXi, and also on Workstation and then converted to ESXi ...

[Raresh]

Some issues that may cause this:

1. Make sure you are not using RDP as the default protocol by mistake. Dual monitors is not supported with RDP only with PCoIP.

2. Open device manager and check the driver for your video adapter. It must be provided by VMware with the version 7.14.1.49. If it is not ending in .49, click to upgrade and select it from the list of available drivers.

3. Try removing and reinstalling VMware Tools. There are issues when the View Agent was installed prior to VMware Tools.

Hope this helps - Richie.

[Linjo]

Dual monitors ARE fully supported with View (up to 10 if I remember correctly)

I agree with the driver stuff, also make sure that you are choosing multimonitor when you are connected.

Another thing is to verify that "Base Video" is checked in sysconfig boot options.

// Linjo

[Raresh]

According to VMware's documentation, dual monitors are not supported when using RDP (mostly if you are using a zero client such as Wyse P20). It is fully supported over PCoIP.

I checked the option to check the base video in msconfig and dual monitors over PCoIP stopped working when the option is enabled.

[tacticsbaby]

Try setting your video memory to auto-detect. Set your monitors at 2 displays (although neither of these should be needed). You may even want to power cycle your Wyse terminal (I had to do this a few times). But most importantly after making your configuration changes on your VM make sure to RESET your VM, NOT RESTART, but RESET your VM from within the View manager. RESET will allow the VM to reload the settings from the .vmx file. This has helped me many times through this problem and may help you. Let me know.

[tacticsbaby]

I almost forgot to say that after you do these things you should then go to the display settings on your VM, if it works then you will see a management interface for the second monitor. If you see the management interface then check the box that says extend my desktop...

[Stu_McHugh]

During the login process there should be a box called 'Display' in the bottom right hand side as shown in the screen shot I've attached.  Click on the drop down the select 'Multi-monitor'

[tacticsbaby]

I don't think this will be available on a Wyse.

[S_D]

Check whether there are any GPOs being applied which limit the number of screens the desktop will utilize.  I've seen the selection windows greyed out and locked to "display on a single monitor" or some such - on zero clients.  There may be something else going on too, but VMs in another pool will have that same setting set to "stretch across multiple monitors" and two monitors will be used by View.  This was with View 4.6 and vSphere 4.1, using the xx.49 SVGA driver from the most recent View Agent.

[NetCE]

Thanks for the replies.

Just to clarify a few things:

I have ensured that PCIOP is being used, on both the WYSE client and the Windows Client.

I have tried with auto-detect for memory settings, and have set memory to max of 128MB, both to no avail.

On the parent image where dual monitors is working, as  well as the new image, all of the management options in "Screen  Resolution" are blacked out - I can't modify them. (no GPO restrictions  are applied)

When connecting to the pool on the Windows Client, I make sure to select "multi-monitor" as the option.  This will put a single window in-between my 2 monitors.

[tacticsbaby]

Sorry to hammer this one, but did you RESET the VM(s) in question? This is sometimes needed to activate settings in the .vmx file. Please note that a simple reboot or shutdown of the VM is not the same as a RESET.

[NetCE]

Hello Tacticsbaby;

Sorry for not answering your post in my reply.

Yes, I have reset the VM(s).

[S_D]

Hi NetCE.  Have you tried disconnecting and reconnecting the second-monitor DVI cable from the back of the zero client after it boots?  We did that after the VM booted (across one display) and the second monitor was then detected.  It takes a disconnect & reconnect from the View session in order for the zero client to pass – to View – that it now has an additional monitor present.  After the zero client becomes "aware" of the second monitor, the Win7 VM doesn't exhibit the same behavior, even if you log out and re-login or connect to a different VM altogether.

We're filing a bug with the firmware company since the same thing happened with (3) different zero clients from different manufacturers.

[tacticsbaby]

I think this may be a winner. Disconnecting and reconnecting the second monitor has helped me fix this issue as well. We use Wyse P20 clients and Windows XP for the VMs.

[S_D]

I'm glad that worked for you!  Another possible solution - which is actually a series of steps - is outlined here:

http://kb.vmware.com/kb/1027899

Try that if the cable disconnect-reconnect step doesn't work.

[tacticsbaby]

Thanks S_D!

[mburgard]

I have tried multiple vmware KB's including those previously listed on these forums.  I have found that the SVGA 2 video driver on the VM is stable with Windows 7, but the mouse performs like the VM tools are not installed so it does not meet end user acceptance.  I have also found that on a Wyse R50L and P20, you do not actually have to disconnect...you can lock the desktop.  When you log back in, it will reinitialize the video display drivers and it corrects the issue.

When our users first login (users are on the R50L, P20 is for testing only) the mouse alignment is also off on the horizontal axis.  The further right you move the mouse, the further off the alignment is off.  It gets annoying very quickly trying to guess where you will actually click from the position of the cursor.  I have an open case with GSS but do not yet have a resolution.

I have also experienced the issue from a HP t5545 client which seems to rule out Wyse.  The Linux client is ruled out with the P20 (Teradici client)...so it seems the issue is with either the Windows 7 video driver, the View Agent, or the implementation of PCOIP on all clients.  I would appreciate any assistance if any one else has any further info.  Locking/unlocking or disconnecting/reconnecting is a workaround...not a fix...

[greenroom]

We have had a similar issue New windows seven desktop on Wyse V10LE, RDP view connections.

The issue was we have several firmware versions on the wyse clients.

The testing was on an old firmware version, once we upgraded the firmware we were fine.

hope that helps

[kermada]

I have video driver version 7.14.1.1134.  How do I get the latest version, 7.14.1.49, for Fusion?

I have installed vmtools twice to no avail.