Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices
Microsoft Terminal Services licensing information is stored in the Sun Ray data store automatically upon Windows session startup, using the existing LDAP schema. No administrator setup or intervention is required.
Licenses can be administered, such as listing and deleting
licenses, with the utlicenseadm command. See
the utlicenseadm man page for details.
The Windows connector supports both per-user and per-device Terminal Server Client Access Licenses (TS-CAL):
Per-user mode - The user's hotdesking experience is virtually seamless.
Per-device mode - The user must reauthenticate every time they hotdesk to a different client to ensure correct TS-CAL license handling.
If you access terminal server functionality provided by Microsoft operating system products, you need to purchase additional licenses to use such products. Consult the license agreements for the Microsoft operating system products that you are using to determine which licenses you must acquire. Currently, information regarding Terminal Services can be found at: http://www.microsoft.com/windowsserver2008/en/us/how-to-buy.aspx
To show the different behavior between the per-user and per-device modes, let's start with the user logging into a Sun Ray session with a smart card and opening a connection to a Windows session. Table 17.10, “Windows Licensing Modes” shows what happens next when the user removes the smart card and inserts it again.
Table 17.10 Windows Licensing Modes
The User Removes the Smart Card and... | Per-user Mode | Per-device Mode |
|---|---|---|
Reinserts the Smart Card in the same client. | The user is instantly reconnected to the existing Windows session. | The user is instantly reconnected to the existing Windows session. |
Inserts the Smart Card in a different client. | The user is instantly reconnected to the existing Windows session. | 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:
|
You can use the -H nodisconnect option of the
uttsc command to prevent the Windows
connector from disconnecting upon detection of hotdesking
events.
With the -H nodisconnect option, the Windows
connector does not disconnect and reconnect when a hotdesk
event occurs, nor does it refresh licenses on different
clients. Instead, it uses the original license granted upon
connection to the first client. This behavior might cause you
to inadvertently violate your Microsoft Terminal Server
license agreement. Because you have full responsibility for
license compliance, be aware of the danger and use the
-H nodisconnect option only with caution.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices