I think I may have made a mistake. I wanted 15 CALs to be displayed on my RDS server, but the license manager only displays 10. I don`t know if I should install these new CALs or if I should place them under the same agreement, so that they are automatically reinstalled in the license manager. Valid for: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016 With the next CMdlet, you can list all the RDS CAL packages installed on the server: I received an internal request, although I am not convinced of why you want to know the details (which servers). We have a cluster of two servers (active/backup) on which the authentication license is configured on the main servers and backup (WS2016). A group of users (z.B. 10) initiated sessions via remote locations for the cluster, but none of the servers displays license authentication (no license is displayed as 0 in the dashboard). But meetings/connections are above. The question is how to determine which server provides which authentication license number to which user, and how to view it (not sure that the authentication license manager can do so)? Initially, 50 licenses x 4 groups (a total of 200 licenses) were configured on main servers and backup servers.
It could be confusing and difficult to understand the situation. I hope that a professional administrator can advise me and appreciate your early feedback. Thank you. When we implement “THE RDS CAL User” in a Windows Server 2019 server, you can set up one of the next steps before installing the remote shutdown service. We cannot use a CAL RDS from a Windows 2012 server to access future versions of Windows Server 2016 or 2019, but we can use later versions of RDS-CALs to access previous versions of Windows Server editions. Click the right button on our server name, then click Activate the server now, and the message will appear because you need to restart the remote deactivation license service. Until the service is restarted, this license server cannot issue RDS user CALs per user in the domain and you cannot track or report the use of RDS Pro user CAL on that license server. Note that you need an Internet connection on the computer on which the remote deactivation license manager is running, but not on the computer on which the license server is running.
To license RDP customers, your RDS license server must be activated. To do this, open the remote casually deactivating license manager, click the right button on your server`s name and select Activate the server. Normally, this error is displayed on the RD license server if we haven`t set up the right group policy for the license servers. So let`s see how we do it. Name file C:-Windows System32-Lserver-TLSLic.edb in C:-Windows32-TLSLic.edb_bak System, then restart the “Remote Dehred Service.” This removes all CAL RDS licenses from the server, and we need to reactivate them for later use. Click Next and select the “Destination Server Reboot Automatically” if necessary, then click Install The server automatically restarts during the installation process, and finally we`ll show up under the screen if the installation has been successful.