Is it necessary to install ADDS to enable cal in Windows Server 2016 Standard? We can now see the message that you need to restart the Remote Desktop Licensing service. Until the service restarts, this license server cannot issue RDS Pro USER CALs to domain users, and you cannot track or report the use of RDS Pro CALs on this license server. After that, the server can issue licenses (RDS CAL) to clients. Reason 1. You entered the RDS license information incorrectly. Reason 2. You do not have an Internet connection. Reason 3. TCP port 443 (outbound) is blocked on the firewall (port 443 is required to communicate with Microsoft servers to activate RDS licenses). Reason 4. You try to install an incorrect version of RD CLs on the server. (For example, you try to install RDS Cals for Server 2019 on a Windows Server 2016.) To see the compatibility of the RDS CAL version, click here.

You must install your RDS CAL on a compatible RD license server. Each RDS license server can host licenses of 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 earlier versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2. In this tutorial, you will find detailed instructions on how to correct the “License Installation Wizard” error: “The license agreement data provided to Microsoft is not valid. Review any information you provide, make any necessary corrections, and then resubmit your application. If the problem persists, try a different connection method. Use the following information to install remote desktop services client access licenses (CALs) on the license server. After THE CALs are installed, the license server issues them to users accordingly. My RDS user scales are for Server 2016 and were purchased via an MPSA agreement. Rds license servers will be installed on my 2016 domain controller server. Due to application compatibility, my RDS session hosts are Server 2012 R2. .

Now restart the Remote Desktop Licensing service in the Windows Services section and click the Refresh button available on the right side of the Remote Desktop Licensing Diagnostic. We can see that the diagnostician has the message “The Remote Desktop Services License Diagnostician has not identified any licensing issues for the RD Session Host server. Additional information such as license mode and number of licenses is also displayed in the same window. Select the “Select server from server pool” option. Select Our Server in the server pool and click Next. If you use the per-user model, the license is not enforced and each user is granted a license to connect to a RD Session Host from any number of devices. The license server issues licenses from the available RDS CAL pool or the overused RDS CAL pool. It is your responsibility to ensure that all your users have a valid license and do not have overused CALLs, otherwise you are violating the terms of the Remote Desktop Services License Agreement. On the Completed screen of the License Installation Wizard with the error “The license agreement data provided to Microsoft is not valid..”: The VERSION OF THE CAL must match the version of the server software it is accessing. Older versions of CALs cannot be used with the latest version of the server software, but RDS CALs from the latest version can be used with an older version of the server software. More information about this letter VL: www.microsoft.com/en-us/Licensing/learn-more/brief-windows-server-2012-rds.aspx.

(same info for 2016) If we are implementing “RDS user CAL” in a Windows Server 2019 server, configure one of the following before proceeding with the Remote Desktop Service installation. This removes the license currently installed on the server and prompts the license installation step again. Finish it and complete the conversion. This completes the rebuild and installation of the new RDS CAL on the server. To install RDS licenses on the Remote Desktop license server, you must know the authorization number and license key. You can find this information (rds authorization number and license key) in the confirmation email you received when you purchased RDS licenses or in the Microsoft Volume Licensing Service Center (after you signed in to your account). After the RDS license server is activated and running, you can reconfigure RD Session Host to obtain CALs from that server. You can specify the license type and license server name by using the Server Manager GUI by using PowerShell or the GPO. The RDS License Server Activation Wizard starts. Here you need to choose your preferred activation method.

If your server is connected to the Internet, it can automatically connect to Microsoft servers and activate the RDS license server. If there is no direct access to the Internet from the server, you can activate the server through a web browser or by telephone. Rename the file C:WindowsSystem32lserverTLSLic.edb to C:WindowsSystem32lserverTLSLic.edb_bak and start the service: Specify the product version (Windows Server 2019/2016), the license type (RDS Pro User CalP), and the number of licenses to install on the server. The server will restart automatically during the installation process and finally we will be displayed under the screen if the installation was successful. When you`re done, click Close. If no warning is displayed and the message “The RD License Diagnosticer has not identified any licensing issues for the RD Session Host server” is displayed, the RDSH server may successfully receive RDS CALs for remote users/devices. Any idea how to install them? When I enter all my information into activate.microsoft.com, it says, “The license agreement data provided to Microsoft is not valid. Review any information you provide, make any necessary corrections, and then resubmit your application. If the problem persists, contact Microsoft Product Support by replacing your connection method with Phone. The fact is that I get my MPSA agreement number from the signed Microsoft documents and people on the phone get it wrong when they try to do it too, and then they want to open a file and have a technician call me, etc.

.