This seems a bit counterintuitive. I just want to make sure Client Assignment works as intended in this case:
I Use a generic local Windows User to Connect to vWorkspace via Web Access ('connectionbroker\Novell Tools')
The connection to the client is made with RDP security layer (not network) to allow Novell logon an creation of a local user. (actually it is pGina - LDAP with local gateway user).
The Computer Group is set to reprovision after logout.
Now when setting 'Client Assignment' to either organizational unit or Group i can connect from 2 different clients an will get the the same desktop which may lead to "concurrent logins" - eg the first user seeing the message that userB tries to login..
I found that if i set Client Assignment to 'Device Address' every time the user connects it will be directed to a new Desktop wich is desired. Even when connecting via Java Connector (127.0.0.1)
DELL-Andrew W1
378 Posts
1230
1
Posted March 4th, 2013 14:00
Hello,
Yes, this is normal.
We do the same for schools where everyone in a class logs in with a generic account but need a different desktop.
We normally recommend Device name but Device address is fine.
Obviously User, Group and OU cannot be used because it is not unique.
Thanks, Andrew.