Microsoft terminal services client access licenses

When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host. When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices. It's your responsibility to ensure that all of your users have a valid license and zero Over-Used CALs—otherwise, you're in violation of the Remote Desktop Services license terms.

An example of where one would use the Per Device model would be in an environment where there are two or more shifts using the same computers to access the RD Session Host s. If you want external users—such as business partners, external contractors, or customers—to be able to access your network, you have two licensing options:.

External Connector licensing. An EC license assigned to a server permits access by any number of external users, as long as that access is for the benefit of the licensee and not the external user. Each physical server that external users access requires only one EC license regardless of the number of software instances running. An "instance" is an installed copy of software. The right to run instances of the server software is licensed separately; the EC, like the CAL, simply permits access.

Under the Per Core model, when the server software is running in the physical OSE, you must license all physical cores on the server. To determine the number of core licenses you need, count the total number of physical cores for each processor on the server, and then multiply that number by the appropriate core factor. You do not need to purchase additional CALs. Software licensed by core. Specialty Server licensing. Specialty Servers are server-only licenses that generally do not require CALs.

Specialty Servers require a server license for each instance of the server software running on a server. You can run the instance in a physical or virtual operating system environment. By exception, some products provide more specific use rights.

Included with the ML are the rights to run the corresponding management server software, so you do not need to acquire separate licenses for the management server software. Software licensed by ML. Cal and MLs. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Please rate your experience Yes No. Any additional feedback? Important This section, method, or task contains steps that tell you how to modify the registry. After you verify that the new license server is functioning correctly, deactivate the old license server. To do this, uninstall the Terminal Services Licensing component on the old server. You should regularly back up the Terminal Services license server by using Windows Backup or a similar tool.

Regular backups help protect your licensing data from accidental loss if the system experiences hardware or storage failure. When you back up a Terminal Services license server, back up both the system state data and the folder in which the Terminal Services license server is installed.

By doing this, you make sure that data in both the registry and the Terminal Services license server database is backed up. If you restore the system state data and the database to the original Terminal Services license server, any unissued licenses are restored correctly, assuming you haven't replaced the operating system on the computer.