VMware Horizon Community
nejko
Contributor
Contributor
Jump to solution

Multiple desktops per user

Hello,

I have successfuly set up an VMware View environment with View Composer and Wyse V10L thin clients. Currently every domain user always gets logged in into the same desktop (currently automatically provisioned). Is it possible for a user to be assigned two or more desktops and then choose one to log in to? If yes, how? I couldn't find this in the documentation.

Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
Rodos
Expert
Expert
Jump to solution

It will have to be two pools. You may have to setup two that are the same config, not great.

To test it use the view client, once you have it working on the view client you can try it on the wise. Sorry I don't have any version numbers as it worked out of the box on the latest terminals I had, but not on the earlier ones. If you are on the latest it should be sweet. If I had access to them I could check but unfortunately I don't.

Let us know how you get on.

Rodos

Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/

Rodos {size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/{color}{size}

View solution in original post

Reply
0 Kudos
12 Replies
randyf25
Enthusiast
Enthusiast
Jump to solution

All you need to do is entitle the same user to multiple groups. The problem that you will have with the Wyse V10L is that it doesn't support multiple assigned workstations. Well, I'm running the latest firmware from Wyse on our V10Ls and it's not working. I am dealing with Wyse

on this issue as they had mentioned it should work.

To confirm simply access the web interface or load the View Client on a Windows PC and you'll see all machines the user is entitled to use.

Troy_Clavell
Immortal
Immortal
Jump to solution

have you considered using non-persistent pools? As the other poster has suggested using WYSE Terminals with the Thin OS will present problems if a user or group is entitled to multpile pools.

Reply
0 Kudos
Rodos
Expert
Expert
Jump to solution

As has been mentioned as soon as an account has multiple entitlements they can choose, but you can also default one.

the first versions of the Wyse integration would only give you the default not a choice, but as others have mentioned with the latest software it will give you a choice.

The thing that I can add is, its does work. If its not working for you then start debugging and call support.

Rodos

Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/

Rodos {size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/{color}{size}
nejko
Contributor
Contributor
Jump to solution

Entitle a user to multiple groups? Or pools? So I cannot assign two virtual machines from the same (automatic) pool to a user? Which "the latest" do you have in mind? Today I installed WNOS 6.3 ... is there any special configuration option I should use to make it offer all the assigned virtual machines?

Thanks.

Reply
0 Kudos
Rodos
Expert
Expert
Jump to solution

It will have to be two pools. You may have to setup two that are the same config, not great.

To test it use the view client, once you have it working on the view client you can try it on the wise. Sorry I don't have any version numbers as it worked out of the box on the latest terminals I had, but not on the earlier ones. If you are on the latest it should be sweet. If I had access to them I could check but unfortunately I don't.

Let us know how you get on.

Rodos

Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/

Rodos {size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/{color}{size}
Reply
0 Kudos
nejko
Contributor
Contributor
Jump to solution

Okay, it works with View Client now, however I can't make it work with Wyse. As I said, I am using WNOS 6.3.0_12 (28 December 2008) and this is my wnos.ini:

autoload=1

AdminMode=yes Username=admin Password=pass

Privilege=High

DESKTOP=bg.jpg

SignOn=yes

SessionConfig=ALL

DomainList=TESTDOMAIN

VDIBroker=https://10.10.11.11/

Timeserver=10.10.11.3

TimeZone='GMT + 01:00' ManualOverride=yes Daylight=yes

Language=Sloven

TCXLicense=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

TCXLicense=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

DesktopColorDepth=32

ConnectionBroker=default

If the user has only one entitlement, the login works great and I just fall in my virtual machine. If the user has two entitlements, after logging in on wyse, I get two small RDP icons on the Wyse desktop, which have no hostname set, therefore I cannot connect to either of the VMs. If I set the ConnectionBroker to "VDM", then the login window on Wyse V10L is different (it shows the VDM logo), but when I try to log in, I get the error "not support tunnel".

So any additional hints are welcome.

Thanks.

Reply
0 Kudos
Rodos
Expert
Expert
Jump to solution

Um, the two icons is the right behavior however not sure why they don't work. If you had the wrong version you would not get the two icons. You say they don't have a host name, weird.

Afraid I don't have access to some to do some trouble shoot. Do you have any support you can call in from Wyse? Log files? Each pool works when their is only one entitlement?

Rodos

Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/

Rodos {size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/{color}{size}
Reply
0 Kudos
nejko
Contributor
Contributor
Jump to solution

Yes, I have the icons. And yes, the pools work when there is only one entitlement (one or another). Actually, there was only one time when the hostnames were empty, currently (I am testing this again now), the hostnames of both RDP connections are set to some ID (one of them is 49d32592-887a-49c9-ac57-6635391f8192). When I double click the icon, I get the errors:

VDI: cannot connect

and then (after a few seconds) this error disappears and another one pops up:

49d32592-887a-49c9-ac57-6635391f8192: Connection failed

After that I can only click OK and that's it. In View Administrator -> Events, I can see this warning:

(SESSION:A28897A06AA610D3C089470FAB889A0A) Wyse device has not specified a Device GUID in the request headers. Falling back to using MAC.

But I am not sure that these are related. Are there any other logs I could take a look at? I have contacted WYSE support, but didn't get an answer yet.

Thanks.

Reply
0 Kudos
TomHowarth
Leadership
Leadership
Jump to solution

moved to the View Manager Forum

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
Reply
0 Kudos
Dave_O
Contributor
Contributor
Jump to solution

If you go to the broker, configuration, view servers, select the view server, click edit, check the "Direct connection to desktop" and OK it will correct this error

By default the connection manager in the Wyse client does not do full screen and allows you to connect multiple sessions, by reselecting the Wyse Connection Manager and connecting to another session.

This is just the behaviour I don't want!

If anyone knows how to use the VDM (XML) settings and get full screen I would be very interested.

It would actually be nice if the location and syntax of the wnos.ini and user.ini file on the broker (if the XML format uses these ) or the files that control the default RDP session settings from the broker could be made available (in this case for the Wyse clients)

Dave O

Reply
0 Kudos
ussi
Contributor
Contributor
Jump to solution

Hi, we have the same problems like u. We wrote the german support of wyse an e-mail and they told us that the vmware api overwrites some parameters.

We now try to configure wit GPO (http://www.vmware.com/pdf/viewmanager3_admin_guide.pdf) page 146/150.

But we are also interested in this xml file/configuration that is mentioned in the changelog of thin os 6.3. (VDM: if support VDM XML API in build as 6.3, it uses XML API,

else it uses INI API.)

(sry for my bad english)

Reply
0 Kudos
Dave_O
Contributor
Contributor
Jump to solution

Ussi

Dude I lived in Munster for 2 years and your written English is better than my written German ever was. In the absence of any documentation I have set the connection broker type back to "default" rather than "VDM" as single session access is essential and await any information on the Wyse settings. I would, however, rather use the XML configuration for client management.

Reply
0 Kudos