View Client-Win 7 screen resolution

[cshells]

So I have a deployment of Windows 7 desktops. When the user logs onto their View desktop the options to change screen resolution is greyed out. We currently don't have any of the View GPOs templates in place and none of the domain GPOs deny privilege to changes these settings. The user can change these options on their local computer but not on their View VM. I am kind of lost where these setting are being blocked.

Also, on the same deployement, the icons in Windows 7 are too big. The option to change text and icons is already set to small. Is there another option in View itself to change this?

[gunnarb]

View itself is greying out the options.  How you change resolution depends on the client you are using.  What client are you using?

Gunnar

[cshells]

Ya it is greying them out. The Vmware View version?

We are running view 4.6. Some of our users are on wyse thin clients and the others are view client installed on windows xp. We are using PCoIP for all of them.

[gunnarb]

No I meant that is the answer to your question: View itself greys them out.  Its not GPO, its how View works.

Can you clarify what Wyse clients are they using, "Thin Clients" or "Zero Clients" (IE the Wyse P20).

As far as your XP folks go, View resolution will change on the fly.  If you do full screen it'll match the resolution.  If you want a resoltuion change outside of that you'll have to change the resolution on the terminal (XP) first.

For a Zero Client, you just have to set the resolution in the client itself, reboot and it'll go to that native resolution.

Gunnar

[cshells]

Oh ok I got ya.

We are using Wyse R90LE7s and the Wyse P20s.

So whatever the resolution on the client will be the resolution on the view client? So when users want to change resolution on the view client they can just change the resolution on the local/client machine?

[gunnarb · Accepted solution]

That's pretty much it.

[cshells]

Thanks! That answers those problems.

So another quick question for you. I have a windows 7 client who has a multi-monitor setup (2 screens) when they logon to their view desktop the desktop shows up as a single desktop in the middle of both screens. I know on some of the XP clients we have, the version of the RDP client can affect the multi-monitor setup. (IE. Spanning is showing up instead of mulit-monitor. Which I read you can update the RDP client to 7.0 and it should fix that). What would affect the windows 7 clients?

[gunnarb]

vRAM

http://myvirtualcloud.net/?p=2253

Strange though I thought you were doing PCoIP.  Are you doing RDP?  If so then some of the stuff I said above is wrong.  RDP cannot change resolution on the fly, it is set during connect and that's it.

Gunnar

[cshells]

We are using PCoIP, and actually I may have read wrong. Which would makes sense as to why I was confused about the RDP Client.

So we have XP clients that only have the option to use spanning mode instead of multi-monitor on their view client. I was googling around to figure out why certain XP clients only had the option of using spanning and I ran across something about the version of RDP client that was installed. II was going to research this more, but I figure while I have someone with your knowledge already here I might as well ask.

[gunnarb]

Okay, ya you shouldnt' have to worry about spanning, PCoIP is too smart for that crap.

It is most likely either a vRAM issue or if you are using a Zero Client it could be firmware, svga driver devtap reset (this is a fun one!), or you're using a DVI to VGA converter and that throws your Zero Clients off so they can't sync to the second screen.

Since moving to 5.0 I rarely have my Zero Clients only go to one screen, but it still happens on occasion, so I too run across this issue on occasion but most of the time i jsut log off and back on to resolve it.

Gunnar

[cshells]

The smarter it is, the less problems I have to deal with. Works for me.

Ok so why would the vRam affecting some of the computers and not others? All of the users who get the spanning option instead of multi-monitor are using XP, but I have other XP users who have multi-monitor as an option. Same with windows 7, just different issue. I have two win7 users that have multi-monitor but the desktop shows up in the middle of both monitors. Then my other win7 user uses multi-monitor just fine. Does the DVI to VGA affect XP/7 clients also?

[gunnarb]

I don't that the DVI/VGA would make a difference for none Zero Clients because the View Client relies on the OS in that case.

Are all of your users using one pool? If so then this will become more difficult to troubleshoot.  If not, then vRAM settings change per pool (and per VM if you fool with them).  So one VM might work and the other not.  I would try testing with a known bad user and have that same user connect to the same pool/vm on a known good client.  This way you could determine if it is the VM or the client that is the issue.

Gunnar

[cshells]

They are all in one pool. Ok so I just went and checked the bad user. If I log into someones elses VM it works correctly. When I logon to the bad users VM, I select multi-monitor and the desktop ends up in span mode. So if they are all in the same pool what how would some of the users end up getting span mode while others getting true multi-monitor. They should all have the same configurations.

[gunnarb]

That just tells me it has nothing to do with View, its the client itself.  Not sure what to tell you about that, I don't do a lot of work with the Windows based end clients.  I'd just just reimaging it.

[cshells]

Oops sorry...I didn't explain that very well at all.

So I went to the bad users computer, logged onto her VM (multi-monitor), and the monitor ended up in span mode.

On the same bad users computer, I logged onto a different VM (mulit-monitor), and it was true mult-monitor like it should be.

So it is the VM and not the client computer. So this would have to do with vRam? Which is weird because they are all in the same pool.

[gunnarb]

THat is weird. The VM itself may be jacked a bit. Have you tried refreshing hte VM that that user connects to?