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. Additionally, the issued RDS CAL amount is not deducted from the total Windows Server 2019 RDS CALs. The 'Total' and 'Available' values remain 0. 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. When a user connects to a 2012 RDS Server, a Windows Server 2012 'Built-in OverUsed' RDS CAL category appears and shows the value only for the issued RDS CAL. 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. Let’s first start this roundup by covering an excellent remote desktop connection manager called Remote Desktop Manager (RDM) from Devolutions. 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 English to German translation results for Remote Desktop Licensing Manager designed for tablets and mobile devices. I have just bought 145 Windows 2019 RDS user licenses to cover both 2019 & 2012 RDS servers.
0 Comments
Leave a Reply. |