Remote desktop services, rdp connection broker, windows server 2008 r2, windows server 2012 r2
EVENT LOG System
EVENT TYPE Error
OPCODE Info
SOURCE Microsoft-Windows-Terminal
EVENT ID 1069
DATE / TIME xxxxx
COMPUTERNAME xxxx
MESSAGE The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Session Host server has not been configured. Licensing mode must be configured for continuous operation
We are getting above error from our windows server 2012 servers. this comes back every 120 days.
in order to troubleshoot, i found my domain controller which is windows server 2008 r2 server as RDS server
where under RDS license manager i see following on my windows server 2008 DC server
Rd license manager
Windows server 2008 or windows server 2012 - installed tls or rds per user CALS
license program volume license - total it is showing 180
i took help from other experts and they mentioned following :
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
"Use the specified RD license servers" = myservername
"Set the Remote Desktop licensing mode" = Per User
some experts are mentioning Problem is, DC is the RD License server which CANNOT HOLD THE 2012R2 RDP licenses.
Transfer RD License Server to the 2012 R2 server, which can hold both the older 2008 AND 2012 R2 RDS licenses.
some are mentioning : Volume Licensing has nothing to do to choose the 2012 or 2016 for RD Licensing. It's the highest version and thus can hold 2008, 2012 and 2016 licenses.
other experts are mentioning : that i have not purchased and installed RDS Client Access Licenses , how can this be
possible as i see my windows server 2008 r2 server which is also our DC is also RDS server
so i am confused whether to implement above registry change on windows server 2008 r2 server (which is our DC) and that should fix the problem , is there any group policy i can do that as license program is volume license and it can hold all 2008, 2012, 2016 licenses?
or do i need to to have another windows s server 2012 Remote desktop licensing server , for that do i need to migrate anything from present domain controller which is 2008
i just wanted a permanent fix.
EVENT TYPE Error
OPCODE Info
SOURCE Microsoft-Windows-Terminal
EVENT ID 1069
DATE / TIME xxxxx
COMPUTERNAME xxxx
MESSAGE The RD Licensing grace period has expired and Licensing mode for the Remote Desktop Session Host server has not been configured. Licensing mode must be configured for continuous operation
We are getting above error from our windows server 2012 servers. this comes back every 120 days.
in order to troubleshoot, i found my domain controller which is windows server 2008 r2 server as RDS server
where under RDS license manager i see following on my windows server 2008 DC server
Rd license manager
Windows server 2008 or windows server 2012 - installed tls or rds per user CALS
license program volume license - total it is showing 180
i took help from other experts and they mentioned following :
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
"Use the specified RD license servers" = myservername
"Set the Remote Desktop licensing mode" = Per User
some experts are mentioning Problem is, DC is the RD License server which CANNOT HOLD THE 2012R2 RDP licenses.
Transfer RD License Server to the 2012 R2 server, which can hold both the older 2008 AND 2012 R2 RDS licenses.
some are mentioning : Volume Licensing has nothing to do to choose the 2012 or 2016 for RD Licensing. It's the highest version and thus can hold 2008, 2012 and 2016 licenses.
other experts are mentioning : that i have not purchased and installed RDS Client Access Licenses , how can this be
possible as i see my windows server 2008 r2 server which is also our DC is also RDS server
so i am confused whether to implement above registry change on windows server 2008 r2 server (which is our DC) and that should fix the problem , is there any group policy i can do that as license program is volume license and it can hold all 2008, 2012, 2016 licenses?
or do i need to to have another windows s server 2012 Remote desktop licensing server , for that do i need to migrate anything from present domain controller which is 2008
i just wanted a permanent fix.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'd also suggest you remove the RDS license server after you create the new one. It's against best practice..
Coralon
Coralon
ASKER
thanks for all reply
so is there any article which i can refer for following:
Create a 2012R2 (or higher) RDS License server. (You can try upgrading your existing license server, but you will very likely have potential problems while the server is being updated).
2. Activate the RDS License server (in the MMC, right click on the server and select Activate)
3. Install your RDS licenses - there is a built in wizard when you right click the server that will let you request/install & activate RDS licenses in the system. However, you will require the correct agreement numbers - your EA, open licenses, etc. whatever you have purchased. (This is usually the hardest part).
also once i have installed rds on new server for ex. contoso-2016 , do i need to install Desktop Session Host role service on the same contoso-2016 with the Remote Desktop Connection Broker role service also installed or Remote desktop connection broker role service has to be installed separate. can you tell me difference between remote desktop session host and remote desktop conenction broker. do i need to point other member servers to remote desktop session hist server so that they can get the license and dont come back with expired license pop up?
so is there any article which i can refer for following:
Create a 2012R2 (or higher) RDS License server. (You can try upgrading your existing license server, but you will very likely have potential problems while the server is being updated).
2. Activate the RDS License server (in the MMC, right click on the server and select Activate)
3. Install your RDS licenses - there is a built in wizard when you right click the server that will let you request/install & activate RDS licenses in the system. However, you will require the correct agreement numbers - your EA, open licenses, etc. whatever you have purchased. (This is usually the hardest part).
also once i have installed rds on new server for ex. contoso-2016 , do i need to install Desktop Session Host role service on the same contoso-2016 with the Remote Desktop Connection Broker role service also installed or Remote desktop connection broker role service has to be installed separate. can you tell me difference between remote desktop session host and remote desktop conenction broker. do i need to point other member servers to remote desktop session hist server so that they can get the license and dont come back with expired license pop up?
To serve out licenses you do not need the Remote Desktop Session Host role, you need the Remote Desktop License Server role.
This is a good article on it with screenshots: http://woshub.com/install-
The Session Host is where the user sessions run. It is the multi-user core of Windows.
The Session Broker is the machine that manages the connections to the Session Hosts. I am fairly sure that the Broker does not need to talk to the License Server, I believe it is only the Session Hosts that need to communicate with the License Server. (I am a Citrix guy, I haven't done a straight RDS configuration).
The essentials of RDS licensing have not changed. When a user connects to an RDS Session Host, the system checks for a license in the user's registry (Citrix actually manages the license codes for the users, and it is different than generic RDS). If there is not a license present, the server contacts the license server on behalf of the user again and checks out a license to the user and stores it in their registry. The licenses are checked out. Once the license hits 60 days then at a random interval (between the 60 - 89 days) the Session Host will contact the license server to renew the user's license for another 90 day period. It will continue to retry at each logon until it renews, or expires. Once the license expires, it reclaims the license to the pool. This is what keeps users from accidentally exhausting the license pool. The per-device licenses work exactly the same way, except the license key is stored in the connecting machine's registry. (Again, Citrix manages this differently).
Once you run the licensing server console, you literally right click on the server to do the Activate and to get the licenses. It is that simple..
You *can* run multiple roles on a single server, but it's not best practice. Normally, you'd have separate servers for your gateway, your license server, your broker, and your session host(s). Depending on the size of the you could have the various roles pooled (except the license server).
Coralon
This is a good article on it with screenshots: http://woshub.com/install-
The Session Host is where the user sessions run. It is the multi-user core of Windows.
The Session Broker is the machine that manages the connections to the Session Hosts. I am fairly sure that the Broker does not need to talk to the License Server, I believe it is only the Session Hosts that need to communicate with the License Server. (I am a Citrix guy, I haven't done a straight RDS configuration).
The essentials of RDS licensing have not changed. When a user connects to an RDS Session Host, the system checks for a license in the user's registry (Citrix actually manages the license codes for the users, and it is different than generic RDS). If there is not a license present, the server contacts the license server on behalf of the user again and checks out a license to the user and stores it in their registry. The licenses are checked out. Once the license hits 60 days then at a random interval (between the 60 - 89 days) the Session Host will contact the license server to renew the user's license for another 90 day period. It will continue to retry at each logon until it renews, or expires. Once the license expires, it reclaims the license to the pool. This is what keeps users from accidentally exhausting the license pool. The per-device licenses work exactly the same way, except the license key is stored in the connecting machine's registry. (Again, Citrix manages this differently).
Once you run the licensing server console, you literally right click on the server to do the Activate and to get the licenses. It is that simple..
You *can* run multiple roles on a single server, but it's not best practice. Normally, you'd have separate servers for your gateway, your license server, your broker, and your session host(s). Depending on the size of the you could have the various roles pooled (except the license server).
Coralon
Point your Broker/Session Hosts to that license server.
Keep them the same version.
Done.