![]() There are no concurrent session limits for RDS CALs in anything that I've read. Same deal, CALs can't change hands more often that once every 90 days, and like most MS licensing tracking is based on the honor system.ĮDIT: Read the link below for a good explanation of how each of the two licensing models works. * If your CALs are per-device the license server doesn't track usage of them, you have no reporting and all tracking needs to be manual. Those CALs work the same as any other MS license, they can't change hands more often than once every 90 days. Configuring Windows Server 2012 Remote Desktop Services Licensing involves 2 step process. The Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server. * If your CALs are per-user the license server will issue a CAL to the AD account the 2nd time it connect to the server, this can all be tracked through license usage reports in the licensing server, that user can connect to any RDS host servers that uses that license server without being issued a second CAL. The licensing mode for the Remote Desktop Session Host server is not configured. I'll look for the docs, but as I recall the process: I'm 99% sure that's incorrect, there aren't any concurrency limits that I'm aware of in RDS, very few (if any) MS products have any type of concurrent session licensing, I can't even think of an example. If you say have 5 servers and 15 licenses, no more than 15 RDP sessions can be established across all the server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |