![]() Use the following procedure to change the discovery scope of a license server by using Remote Desktop Licensing Manager. If the license server is a member of a workgroup, and then you join the license server to an Active Directory domain, the discovery scope for the license server is automatically changed from Workgroup to Domain. When I installed the 2019 licenses should I of specified that only X amount were for 2019 & Y amount for 2012? If so how do I go about removing the licencees and re-adding them? OR is there somehting I have done incorrectly.You can use Review Configuration in the Remote Desktop Licensing Manager tool to change the discovery scope of the license server after the RD Licensing role service has been installed on the computer. The 145 I have just purchasedĪs you can see from the below if I look at the License manager on the central server it does not appear to allot the 2012 RDS licenses from the 2019 ones, but has created a new License type and is saying it is overused. Which Seems to work and if i log onto one of the 2012 servers and run the RD License Diagnoser it tells me I have 152 licenses spare. I have a GPO in place to point the 2019 / 2012 RDS server back to the central licensing server. ![]() So if a user connected to a Windows 2012 RDS server then it would allot them one of the 2019 user licenses. Thinking that they would be backwardly compatible with Windows 2012. When I install the licenses I selected open license ![]() I have just bought 145 Windows 2019 RDS user licenses to cover both 2019 & 2012 RDS servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |