The above screenshot shows that there are 4 users who are connecting to 2008 R2 Session Host Server and 1 user who connects to 2012 R2. For more detailed info, you may check below article:
#Windows terminal server 2008 cal windows
Windows Server 2012 RDS CALs can be issued to 2003, 2008/R2 terminal server. Meaning that Windows Server 2012 CALs will work with Server 2008 R2 RDS CALs are not forward compatible, only backward compatible. A 2012 RD Licensing server will serve 2012/2008 R2/2008/2003 servers, so you may consolidate your RDS CALs onto a Server 2012 RD Licensing server if you would like to. Server 2012 RDS requires a Server 2012 RD Licensing server.
#Windows terminal server 2008 cal install
The column “Built-in Overused” represents the number of user connections to Windows Server 2008 R2 servers where a Per User license was issued.ĭo you need to install additional Windows Server 2008 R2 RDS CALs too, or is this a compatibility behavior?
The "Built-In Overused" group will display only the number of licenses issued and no " Remaining" or "total", because in the background the 2008 RDS CALs are not actually installed. Since, this group is displayed separately, the number of licenses will not be deducted directly from the 2012 RDS CAL group. This is to make admins visible that 2012 licenses were issued for older terminal servers for which no dedicated (in this case the 2008 R2) RDS CALs are installed. Here, in this case it is just a reporting mechanism to tell that these number of users have logged in without an appropriate CAL. Starting with Windows Server 2012 R2 license server, when only Windows Server 2012 RDS CALs are installed and a user logs on to a Windows Server 2008 R2 RDS Server, the "Built-in OverUsed" group is displayed and the user gets a 2008 R2 "Built-In Overused" RDS CAL. Why are the "Built-In Overused" RDS CALs “issued” counted but not the “total” and “remaining” too? If the most appropriate RDS CAL is not available, a license server running Windows Server 2008 R2 issues a Windows Server 2008 R2 RDS CAL, if available, to a client connecting to a terminal server running Windows Server 2003 or Windows Server 2000. For example, a license server running Windows Server 2008 R2 tries to issue a Windows Server 2008 R2 RDS CAL for clients connecting to an RD Session Host server running Windows Server 2008 R2, and a Windows Server 2003 TS CAL for clients connecting to a terminal server running Windows Server 2003. Why are Windows Server 2008 R2 RDS CALs not deducted from the installed Windows Server 2012 RDS CALs?īy default, a license server attempts to provide the most appropriate RDS CAL for a connection. After the applicable licenses get installed, this group goes away and the number of licenses issued gets synchronized with the installed license group. This was an indication for admins that they must install licenses. The "Built-In Overused" group was also used in earlier operating systems if the licensing mode was being set to Per User but no "per user" CALs were installed on the license server and the users will still connect to the terminal servers. What is the "Built-in OverUsed" group and is it ok to have it? Additionally, the issued RDS CAL amount is not deducted from the total Windows Server 2012 RDS CALs. The "Total" and "Available" values remain 0. However, when a user connects to a Windows Server 2008 R2 RDS Server, a Windows Server 2008 R2 "Built-in OverUsed" RDS CAL category appears and shows the value only for the issued RDS CAL.
When a user connects to a Windows Server 2012 R2 Session Host, a Windows Server 2012 "per User" RDS CAL is issued. In the case above, the license server is used to issue RDS CALs to users when they connect to both Windows Server 2008 R2 and Windows Server 2012 R2 Session Host Servers. Under “License Program” you then see “Built-in Overused”. Under these circumstances, you may see a line item in your 2012 R2 license manager that says “Windows Server 2008 or Windows Server 2008 R2 -Installed TS or RDS Per User CAL”. Hello AskPerf! My name is Prachi Singh and today I will be talking about a behavior that can occur when users attempt to pull licenses from a 2012 R2 License server via a 2008 R2 Session Host. First published on TECHNET on May 07, 2015
0 kommentar(er)
