Ivar Janmaat wrote:
Ok, I think we are configured in a per device-mode.
If I read it correctly I think a per user-mode would be the preferred
mode for Sunrays don't you agree?
Still I find it strange that the "disconnect" action in per device
mode takes place when inserting the smartcard in the new DTU.
I conclude this is the case because the old sessions appears for a
fraction of a second before the reauthentication takes place.
I would expect the disconnect to take place when I remove the
smartcard form de first DTU.
The reconnect can than start directly when I insert the card in the
new DTU.
This would save time and looks better.
Or do other problems appear when it would be solved this way?
It won't disconnect if we insert to the same DTU and that feature will
be lost if we do
disconnect just on smartcard removal.
Thanks
P.S.M.Swamiji
Ivar
Brad Lackey wrote:
This behavior is a by-product of using per-device licensing for the
WTS...
From the uttsc Admin guide...
Hotdesking and Licensing Modes:
Terminal Server Client Access Licenses can be configured in two modes
on the
Windows Terminal Server: per-user and per-device. In per-user mode,
the user’s
hotdesking experience isvirtually seamless. In per-device mode, the
requirement
that each DTU use the appropriate license requires an extra login
when a user
hot desks to a different DTU.
The differences in the user’s hot desking experience are summarized
below.
Note – The Sun Ray administrator may choose to set a policy that
requires the user
login with username and password to access the Sun Ray session.
Per-userMode:
The user logs into a Sun Ray session with a smart card and opens a
connection to a
Windows session.
1. The user removes the smart card and reinserts it in the same DTU.
2. The user removes the smart card and inserts it in a different DTU.
In both cases, the user isinstantly reconnected to the existing
Windows session, and
other features and services are unaffected.
Per-deviceMode:
The user logs in to a Sun Ray session with a smart card and opens a
connection to a
Windows session.
1. The user removes the smart card and reinserts it in the same DTU.
The user isinstantly reconnected to the existing Windows session.
2. The user removes the smart card and inserts it in a different DTU.
The Windows login screen prompts the user for username and password,
after
which the user is reconnected to the existing Windows session. Other
features and
services are similarly affected. For example:
Windows Media Player stops playing audio, although the application is
still
active on the Windows session. The user needs to replay the audio.
Any serial port transfer is stopped.
All the command line options specified remain valid.
Note – The uttsc command providesa CLI option(-O) that can be used to
prevent
the Sun Ray Connector from disconnecting upon detection of hotdesking
events.
Please see the uttsc man page for details.
Ivar Janmaat wrote:
Hello,
I was wondering if someone else has noticed the way Windows
connector behaves when you move from one Sunray to another with a
smartcard.
My setup is:
A demo Windows 2003 server, setup in a way that all rdp users get
logged in with username xxxx aan password yyyy without asking for
athentication.
Sunray 3.1, solaris sparc server with Sunray connector running in
CAM mode.
1. I put my smartcard in a Sunray
2. I get a CAM session where I can start the Sunray connector to
Windows.
3. I get logged in to windows without typing anything
4. I pull out my card and the session disappears
So far it's what I would expect.
Now the strange thing is going to happen.
5. I put the smartcard in another Sunray and I see the Windows
session assosiated with this smartcard directly on my screen. But
this is only a fraction of a second. Then it looks like the session
is logged out and logged in again. Since this is all automatic it's
not a real problem but it makes me wonder...what is happening?
I read somewhere, but don't know where anymore, that the Sunray
connector disconnects and connects again if you move from one client
to another since this is "standard" rdp client behavior. But why
degrade the Sunray to a standard rdp client? Why reconnect and delay
hotdesking if you don't have to?
Or am I missing something here?
Kind regards,
Ivar Janmaat
raywyse
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
