Quantcast
Channel: ฟอรัม Remote Desktop Services (Terminal Services)
Viewing all articles
Browse latest Browse all 25135

RDS 2012 License Problem

$
0
0

Guys,

I have a Physical Server 2012 installation running with a Core 2012 virtual machine as a DC;  Both are domain joined as part of a SBS2008 network.

Remote desktop services has been configured on the Physical 2012 installation and has been running fine till today when no user can connect any more.  It looks like the the 120day grace period has expired though as far as I'm aware all of the licensing has been installed configured and there have been  no alerts to indicate otherwise;

RDS License diagnostics is reporting:

The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server server2012 does not have any installed licenses with the following attributes:
Product version: Windows Server 2008 or Windows Server 2008 R2
Licensing mode: Per User
License type: RDS CALs

Which doesnt make sense as the RDS Cals installed are 2012 and the RDS server is Server 2012.

- All of the RDS roles are installed on the physical 2012 server (along with RD Licensing);

- It has been activated as a RD Licensing server and 5 2012 RDS User cals have been installed;

- RDS - Overview - Deployment properties - RDS Licensing - has been set to per user and Server2012 specified as the licensing server;

- I have adjusted group policy to set the following items

computer config / administrative / windows components / remote desktop services / remote desktop session host / licensing / use the specified remote desktop license server

computer config / administrative / windows components / remote desktop services / remote desktop session host / licensing / set the remote desktop licensing mode

I have deleted the REG_BINARY key from

HKLM\system\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

After a server restart people are now able to access the server again remotely.  However license diagnostic is still showing the same error.  I'm concerned that the issue may occurs again - any thoughts on how to resolve?

Thanks

Asim


Viewing all articles
Browse latest Browse all 25135

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>