Server 2012 RDP Licensing

Hi Guys

I have a "Windows Server 2012 Standard" which has been running for about 2 years with RDP.

yesterday I started getting the following message:
"Remote Desktop Services will stop working because this computer is past its grace period and has not contacted at least a valid Windows Server 2008 license server. On the RD Connection Broker server, use Server Manager to specify licensing settings"

I did some googling and found a registry entry to delete, which I deleted.
HKLM\System\CurrentControlSet\Control\Terminal Server\RCM\Grace Period

Now I get the following message:
"Remote Desktop Services will stop working in 120 days if this computer does not contact at least a valid Windows Server 2008 license server. On the RD connection Broker server, use Server Manager to verify or configure licensing settings"

Like I said it has been OK till now, we have no other server on the network.
Any ideas?
ErgsAsked:
Who is Participating?
 
Cliff GaliherConnect With a Mentor Commented:
You'll probably want to remove and re-add the licensing sever in server manager then. Unless you decided to skip server manager and manually force settings via group policy (even worse.) in which case, you'll need to edit (or preferably remove) the group policy.
0
 
Cliff GaliherCommented:
You need to set up an RDS licensing server, buy RDS CALs, and install them on the licensing server. RDS has never been free.
0
 
ErgsAuthor Commented:
I just noticed something interesting. I went to "RD Licensing Diagnoser" and it is looking for this server but with the old IP address.

IMPORTANT NOTE: We changed IP addresses for this server a few days ago, hope this helps
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
ErgsAuthor Commented:
As I mentioned it has been running for 2 years and I do have valid licenses installed
0
 
Cliff GaliherCommented:
I've seen people misuse the two admin sessions, and your question didn't specify that you've actually configured any RDS roles. Working for two years isn't any guarantee that the system was set up properly.

If you are are certain that you have a licensing server and CALs, based on your followup, make sure all DNS entries are up to date. Delete old A records, flush DNS, and retest. In 2012, the RDCB is the arbiter of all and the entire infrastructure must be healthy.
0
 
ErgsAuthor Commented:
Would it be a matter of reconfiguring RDP Services?

as you can see from the attached image it is looking for a server with an IP address of 10.10.10.2
We changes our IP range a few days ago to 10.131.32.x
Capture.JPG
0
 
Cliff GaliherCommented:
IF the name didn't change then you shouldn't need to reconfigure. When setting up RDS, server FQDNs are the default, not direct IP addresses. So that is why making sure no old DNS records to the server name exist and why flushing DNS cache is important. Restarting the server wouldn't hurt either.
0
 
ErgsAuthor Commented:
OK so I checked DNS and made sure there are no entries to old IP address. I did a reboot. When I run RD Licensing Diagnoser it is still looking for a server with the old IP address.

Can't remember but I may have used IP address instead of FQDN when I first set it up.
0
 
ErgsAuthor Commented:
OK all working now.... I cheated, I added the old IP as a secondary IP and RDP services seem to be happy.
0
 
ErgsAuthor Commented:
didn't try it, it would have been my next attempt. Fixed the problem by adding the old IP as a secondary IP address
0
All Courses

From novice to tech pro — start learning today.