License your RDS deployment with client access licenses (CALs). 3 minutes to read.
![]()
The Sentinel RMS License Manager may be installed on one or more computers to. And runs a shared software, it obtains a license from the license server, which then. Clustered virtual environments are not supported for web-activated licensing. Compatibility matrix between client version and license manager version.
Contributors. In this article Applies to: Windows Server (Semi-Annual Channel), Windows Server 2016 Each user and device that connects to a Remote Desktop Session host needs a client access licenses (CAL). You use RD Licensing to install, issue, and track RDS CALs. When a user or a device connects to an RD Session Host server, the RD Session Host server determines if an RDS CAL is needed. The RD Session Host server then requests an RDS CAL from the Remote Desktop license server. If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client is able to connect to the RD Session Host server and from there to the desktop or apps they're trying to use. Although there is a licensing grace period during which no license server is required, after the grace period ends, clients must have a valid RDS CAL issued by a license server before they can log on to an RD Session Host server.
Use the following information to learn about how client access licensing works in Remote Desktop Services and to deploy and manage your licenses:. Understanding the CALs model There are two types of CALs:. RDS Per Device CALs. RDS Per User CALs The following table outlines the differences between the two types of CALs: Per Device Per User CALs are physically assigned to each device.
CALs are assigned to a user in Active Directory. CALs are tracked by the license server. CALs are tracked by the license server. CALs can be tracked regardless of Active Directory membership. CALs cannot be tracked within a workgroup. You can revoke up to 20% of CALs.
You cannot revoke any CALs. Temporary CALs are valid for 52–89 days.
Temporary CALs are not available. CALs cannot be overallocated. CALs can be overallocated (in breach of the Remote Desktop licensing agreement). When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host. The second time that device connects, as long as the license server is activated and there are available CALs, the license server issues a permanent RDS Per Device CAL.
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. The license server issues licenses from the available CAL pool or the Over-Used CAL pool. 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. To ensure you are in compliance with the Remote Destkop Services license terms, track the number of RDS Per User CALs used in your organization and be sure to have a enough Per User CALs installed on the license server for all of your users. You can use the Remote Desktop Licensing Manager to track and generate reports on RDS Per User CALs. Note about CAL versions The CAL used by users or devices must correspond to the version of Windows Server that the user or device is connecting to. You can't use older CALs to access newer Windows Server versions, but you can use newer CALs to access earlier versions of Windows Server.
The following table shows the CALs that are compatible on RD Session Hosts and RD Virtualization Hosts. 2008 R2 and earlier CAL 2012 CAL 2016 CAL 2008, 2008 R2 license server Yes No No 2012 license server Yes Yes No 2012 R2 license server Yes Yes No 2016 license server Yes Yes Yes Any RDS license server can host licenses from all previous versions of Remote Desktop Services and the current version of Remote Desktop Services.
For example, a Windows Server 2016 RDS license server can host licenses from all previous versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2.
Error: FLEXlm Error: -15 Cannot connect to license server Error Message The following error message displays when starting an ArcGIS Desktop application: 'FLEXlm Error: Cannot connect to license server. The server (lmgrd) has not been started yet, or the wrong port@host or license file is being used, or the port or hostname in the license file has been changed.
Feature: ARC/INFO Server name: server1 License path:Below are examples only @server1;c: arcgis arcexe82 sysgen license.dat @server1;c: Prog1 ESRI License arcgis9x @server1;c: Prog(x86) ESRI License arcgis9x FLEXlm error: -15,10. System Error: 10061 'WinSock: Connection refused' For further information, refer to the FLEXlm End User Manual, available at 'www.globetrotter.com'.
Program not run.' Cause ArcGIS cannot connect to and check out a license from a license server.
Solution or Workaround. First, verify that the License Path indicated in the error message is the correct host name or IP address of the license manager system. If the License Path is 'NotSet', then Desktop Administrator has not been configured with the location of the License Manager. FAQ: Why is 'NotSet' listed in the Desktop Administrator License Manager folder?. If the 'License Path' is correct, then the license manager may not be running. If the license manager system cannot be accessed, contact a license administrator for assistance. Otherwise, perform the following troubleshooting steps on the license manager system.
Restart the License Manager: Click Start Programs ArcInfo License Manager License Manager Tools. Check the Configuration using Services radio button. Select the Start/Stop/Reread tab. Click Stop Server. Click Start Server. Perform a Status Enquiry to confirm that the licenses are available: Click the Server Status tab and click the 'Perform status enquiry' button.
'Display Everything' should be selected. Verify that there are no errors in the status enquiry. O LMStatus. Check the license manager log file for any errors. On the Config Services tab, click View Log. Problem: Messages in the license manager log file. If the status enquiry and log files do not indicate any errors, there may be a firewall running on the license manager system.
How To: Configure Windows XP's Internet Connection Firewall to work with the License Manager. If issues persist, contact ESRI Support for further assistance. Related Information.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |