Once assigned, a device CAL is assigned to a device, whether connected
of disconnected.
The real con would be that it would be up to *you* to ensure that all
your devices were assigned a CAL so *you* weren't breaking MS licensing.
Ex. uttsc session with no disconnect, and you hotdesk to five Sun Rays.
If those devices never previously were assigned a TS CAL, and you
didn't have any device CALs left, you'd be in vioation.
The other downside is windows has no idea that you changed clients for
any location-based awareness software running on the windows side.
Check out the the autoreconnect option, but you'll need to supply your
credentials (like using Oracle VDI for the front end to Terminal server)
to make that work.
On 1/6/12 2:00 PM, Art Peck wrote:
Let's start a discussion of the pros and cons of using the "-H
nodisconnect" option on the uttsc invocation.
Would one "con" be that it consumes a Device CAL until the users logs
out of Windows??
Art
_______________________________________________
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
