A fully functional and activated 2012 Remote Desktop Session Host server displayed the following message:
This was a simple setup on one server with the: connection broker, Session Host and Licensing server with 2012 CAL’s installed.
Even though the licensing seems to be configured correctly, in server manager:
and powershell:
Licensing diagnostics:
everywhere you look, everything seems to be OK. But the license manager shows something odd:
No licenses are being used? This server was used since late 2012. Some interesting things could also be found in the event logs, the following events appear:
EventID: 1130
Source: TerminalServices-RemoteConnectionManager
The Remote Desktop Session Host server does not have a Remote Desktop license server specified. To specify a license server for the Remote Desktop Session Host server, use the Remote Desktop Session Host Configuration tool.
and:
EventID: 1128
Source: TerminalServices-RemoteConnectionManager
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up.
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.
Note: you must take ownership and give admin users full control to be able to delete this key.
After a reboot the server should be working again, licenses are now being used:
Although everything seemed to be ok and configured correctly with valid licenses, it seems that the setup was still in a 180 day grace period, even though it was correctly configured.
A possible bug in RDS 2012?
Works thanks for the write up!
if i do so is there any discrepancy happening,pls suggest
if i delete this key is there any negative impact on my netywork or do i need to take a backup ofr the same.
I haven’t encountered a single issue, but is it’s always wise take a snapshot or make a backup before making this change.
It works!!! client is able to resume using TS. But strange that in my case the license server still reported no TS licesnse being issued out. Wondering if there is a permanent fix for it. Otherwise I would have to delete this registry key once again after every 120 days.
Great! If there are still no licenses being used on the licence server, then it isn’t really fixed. It will return in 120 days, try checking all licence options just like I did in the article. And perhaps you also need the steps pointed out by Dave:
http://www.blackforce.co.uk/2014/02/17/2012-rds-server-the-remote-desktop-session-host-server-does-not-have-a-remote-desktop-license-server-specified
Wow.. I have looked all over for this fix and I found a few locations that had a brief mention of it but not in this detail. Had two servers I was battling with this problem and both are up now. Thank you!
Thank you for taking the time to write this issue up and find the solution. The issue just hit use today and the suggested fix worked!
Nice catch
Thx alot – works like a charm…
Seems to be a MS Bug 🙂
works for 2008r2 too
Thank you
It says:
Unable to delete all specified values
@Abe
Note the note:
Note: you must take ownership and give admin users full control to be able to delete this key.
Click the key you want to take ownership of.
On the Edit menu, click Permissions.
Click Advanced, and then click the Owner tab.
Under Change owner to, click the new owner, and then click OK.
Thanks so much for this hint of “taking ownership” I was wondering how to make the permission.
This was a huge help. Fixed the issue with RDS 2012 not recognizing license server even though it was installed on the same box!
BIG BEER – where to send it?
Beer is always welcome! 🙂
You are lucky boy. You saved my ass right now and I am from Czech republic. So seriously: where can I send a pack of Pilsen/Bud (your choice)?
Nice catch – thank you for the article!
Hi,
Just wondering if you tried this first to point to the Licensing server?
Although I can understand why you may not have done this.
1.Open an elevated Windows PowerShell prompt
2.Type the following command on the PS prompt and press Enter:
$obj = gwmi -namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting
3.Run the following command to set the licensing mode:
Note: Value = 2 for Per device, Value = 4 for Per User
$obj.ChangeMode(value)
4.Run the following command to replace the machine name with License Server:
$obj.SetSpecifiedLicenseServerList(“LicServer”)
5.Run the following command to verify the settings that are configured using above mentioned steps:
$obj.GetSpecifiedLicenseServerList()
@Graham
Hi, I tried a lot of things, not everything I tried was in the blog item. But i tried this as well, didn’t work though.
Eric
After hours of troubleshooting and looking for a solution. Your Resolution worked for me. Thanks a lot for this.
Thanks a lot!! This solution also worked for me! Now i am not in grace period anymore.
Thanks @Graham!!!
Hours searching at microsoft technical forums and with everything well configured and the licences activated the server failed to issue licenses.
Because I couldn’t set the license server with the microsft wizard, with your suggestion everything was solved 🙂
You saved my day!!!
Thanks! This actually fix my issue!
$obj.GetSpecifiedLicenseServerList() is not working
Did you supply the correct license server name in the command between () ?
You are a god. Almost 4 hours of crushing my face against the desk, and then I found this. Fixed it instantly. WTF, Microsoft????
[…] fonte: http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
Trying this on server 2012, the Reg_Binary re-appears after a reboot.
That’s correct, but the licensing should be working after the reboot. You can check this in the license manager. You should be able to see licenses in use.
http://www.360ict.nl/blog/wp-content/uploads/2013/04/Licencemanager.png
I have done this for a few 2012 boxes, but the key ALWAYS comes back, and I have to repeat after 180 days. It always shows 0 licenses issued…..
Gracias Excelente me salvaste
It works for me. Thanks. You are BIG !
[…] Taken from http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
Excellent, after 1 day fight with W2012 RDS I found this website and now I am winner. Thx a lot.
I also encountered this same error in Server 2008 R2 RDS… The same fix worked like a charm.
Thank you!
Nice job on finding this out and posting the fix. Had the same exact issue and your solution saved me a boat load of time – thanks! Eric Verdurmen for Microsoft CEO!
Well, they are looking for a new guy! But I don’t think I would be the right person for the job 😉
I’m glad it worked for you!
Thank you, that was the trick !
Problem solved by above mentioned solution…. Great!!! Thanks
[…] Zdroj: http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
Name what you want and I shall grant it boy.
You’re a star. Thanks very much.
Thanks a lot! You are a star.
If you didn’t know, I’ll tell you now.
YOU ARE ‘DA MAN!!
Worked for me on 2012.
[…] poměrně dost lidí, nakonec jsem našel jednoduchou radu jak to vše zprovoznit. Podle článku http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ stačí pouze upravit hodnotu v registru. Nevím, zda je to legální ,ale jede […]
Thank you very much! This worked great for Server 2008 R2 as well.
Ran into the same problem today even though it seemed a bit different :
The License manager showed that licences were issued but the ID1030 event was still shown in the Event Viewer.
And instead of ID 1028 it show ID1029 but with the same text (in german though on this machine 😉 )
I deleted the key but havnt started the server yet – as most users are still conncted at the moment – new users still get the above shown error.
Will restart later and report 😉
Many, many thanks…
Right On -worked and saved the day!
[…] Source : 360ict.nl […]
I had this issue. However following this didn’t resolve the issue. I had to carry out a few extra steps in WMI to fix it.
http://www.blackforce.co.uk/2014/02/17/2012-rds-server-the-remote-desktop-session-host-server-does-not-have-a-remote-desktop-license-server-specified
Hi !
This was super 🙂
It worked for my RDS solution on Azure Cloud (Azure Virtual Machines – MS Windows Server 2012). Thank you, Thank you !!!!
Best regards
Ole Henrik Oftedal
System Engineer
Timeflex Systemer AS
http://www.timeflex.com
http://www.timeflex.no
[…] This was posted by Eric Verdurmen at this site: http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
http://support.microsoft.com/kb/2916846 should resolve the issue.
Nice, can somebody verify if this really fixes this?
Thank you so much.
[…] http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
Hi Eric
Did you have success with the hotfix? If yes , can you please mention hotfix as a solution in the article instead of deleting the Grace period key.
Thanks
Roop
I usually just fix it using the described workaround, haven’t tried the hotfix yet. It could be worth a shot though, but as far as I can see the hotfix fixes certificate issues.
If you try it and it works, please tell us.
Yes. It does work for us. Thanks.
Thank you so much man!
I wonder if this issue will really come back after 180 or 120 days?
Hi,
It didn’t came back after that period.
Installing http://support.microsoft.com/kb/2916846 should fix the issue permanently
The solution is quite elegant and helps, but the problem reoccures after 3 month. Will try hotfix mentioned below or just create a task schedule what will clean registry key like once a month (when installing Windows updates)
Some are indeed reporting this, strange. On all the machines I had to do this, I only had to do in once.
Please report back if the hotfix fixes it permanently.
Thank you Dale for the link. This link fixed my issues.
http://www.blackforce.co.uk/2014/02/17/2012-rds-server-the-remote-desktop-session-host-server-does-not-have-a-remote-desktop-license-server-specified
[…] http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
Thanks for the solution to this problem, it worked.
Hi,
This seems to have fixed my issue however the licenses are still not being issued properly. All that has done has reset the grace period again. Has anybody else had this?
I think the final steps in the link that Vivek provided has fixed my issue so thanks to you both for your help. Much appreciated.
GREAT!
Work fine!!!
Fantastic tip. It was working at once, and it has saved “my life”. Thanks a lot.
[…] http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
You save our life thanks a lot perfect superb hasta la vista
Newsflash
Microsoft, we need to RDP to servers to manage them so you can make money. Free RDP licenses!!!!
Would like to confirm this works with server 2008R2.
Heyie
Thanks a ton for the tip.
But my major issue is that I am totally locked out of the server and cannot access it at all as whenever I try to connect it gives me the same error on RDP and I cannot physically sit on the server as it is an offshore server set up remotely.
Can you help me with this?
Hi,
That can be troublesome indeed, but I beleave an admin session is still possible, try using /admin in mstsc to connect to the server. Assuming you cannot connect to the Console using tools like Dell RAC, HP ILO or any other way to connect to the console.
good luck!
Thanks so much…this really saved me valuable time hunting down why the licensing server didn’t recognize itself.
[…] fonte: http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
We had the same issue at a customer site running Citrix XenDesktop 7.1 were W2K8 R2 server desktops are published. After modyfing the vdsik image för W2K8 (using Citrix Provisioning Server) with the registry fix the issue was resolved. Many thanks for sharing this information. Great stuff!
This solved my problem – thanks!!!
Hi,
I have a problem with installing W12 RDS as it always says:”Your version of microsoft windows does not support following data formats:..” and then comes list with about 150 items I don’t understand at all. I have W7 with all the latest uptades.
Try this if the reg key comes back automatically, this so work for me.
https://www.blogger.com/comment.g?blogID=2228947945609574437&postID=7270917380434225993&page=1&token=1417054276314
Excellent! It helped me also! Life saver!
Just wasn’t sure, at first, how to take ownership on Security of the key but your answer here helped me again! I guess whenever that is done, it works!!
[…] http://www.360ict.nl/blog/no-remote-desktop-licence-server-availible-on-rd-session-host-server-2012/ […]
thanks guys..it helped!
Nailed it! Was having a HELLUVA time with an offsite server that was reprovisioned. it kept looking back at an expired timebomb entry and would not let me finish configuration remotely. saved my a$$
This works for Windows Server 2012 and Windows Server 2012 R2.
Available hotfix is only for 2012, not R2.
Somebody knows if there is a hotfix for 2012 R2?
Bonjour
Merci, merci…
You’ve just save me from the big BUG, happy new year.
Thanks for the help. Luckily for me this was the first link I tried. Worked like a charm!!!
Add me to the list of people who this resolved my issue on Windows Server 2012 R2. Now if only the hotfix applied to R2 as well…
I think I love you, this has been an issue for me for weeks, LIFESAVER!!!!
Amazing !It’s working after follow your steps .Many thx.
My server is NOT running on original windows server 2008r2, will it still work for extending RDP 120 days grace period.?
I am getting following message : No remote desktop license server is specified, remote desktop services will stop working in 10 days if a license server is not specified. Click this message to launch the RD session host server configuration tool to specify a license server for the RD session host server to use.
I only use the mentioned fix to fix 2012(R2) RDSH servers to fix it not seeing valid licenses. I never tried it on a 2008R2, I also never encountered the issue on a 2008R2 server.
What happens if we don’t do this and 180 day period expires? Does it by default activate the CALs or it just stops working?
It stops working, working and activated CALs should work immediately.
Still getting this on nearly every RDS I deploy 2012 or 2012R2 and the strange thing is, that some of these servers were already in use for about a year or a half – so more than 180days …. I dont get it. I didnt even use the grace period on these servers but installed the licenses the day i’ve setup the machine.
The deletion of the registry value always seems to help though
I’m having this problem ON my Remote Desktop License Server itself. My Session Host is a different server. Effectively, My Remote Desktop License Server cannot find itself to issue itself Remote Desktop Licenses. The only way I can access it after the “Grace period” is by way of the “console” on my vSphere.
This solution fixed it, for a couple more months, but it still insists it is unconfigured.
Have you checked the configuration using the methods I used in the article?
Deleting the grace period key is policy violation. Installing the hotfix http://support.microsoft.com/kb/2916846 is the correct resolution.
Using the hotfix should be the first thing to try, but if it doesn’t work and you have a valid license installed which isn’t working. This fix does come in handy.
The fix isn’t available for 2012R2, and some are reporting that they also experience it on those servers.
In this case you’re doing it to fix a bug, not being able to use the licenses which you bought. It’s a bit of a grey area really.
We have Terminal license expired on windows server 2008 R2. We access the server by remote desktop only and have no access to physical server. As terminal license was expired I could not log into server but from other server in domain using Administrativ Tools->Remote Desktop Services -> Remote Desktop I was able to log into server from other server and delete the file from GRACE PERIOD as expalined above. We were going to put permanent fix later but after 1-2 days its locked the license again and I am not able to log into server again.
If I try to log from other server like I did before using Administrativ Tools->Remote Desktop Services -> Remote Desktop I can not log in. It just says disconnected from server.
Can anyone help with this to suggest what can I do to log into server.
Haven’t you got a DRAC or ILO in that server? And I believe a console session still works, look at: http://www.360ict.nl/blog/mstsc-command-line-switches-a-bit-more-explained/
RDP will still work but you will need to RDP with the /admin option: mstsc /v:servername /admin
Hi Guys,
I also share a tweak if you want to make the the grace period forever or for 600+ days.
If you extent and change the server date to another year, lets say 1st March 2017 or 1st march 2016 and log off and re login the server. Once you do that then login to server and delete the registry key mentioned above.
After this log off from server and re login to the server and bring back the original date of the server (for e.g. 1st March 2015) to correct date time and year.
You will see that now the grace period have been extent for 600+ days.
Caveat – Do not try this in case you’ve license antivirus or IIS server running. It would be prudent to disable/uninstall them prior doing date change else this will causes unnecessary issues. or make server out of network before you do this and STOP all critical services prior doing this.
Enjoy the unlimited days guys!!
Works for server 2008R2 as well. Thanks!! Saved me.
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Hi, we buy 40 RD License and 5 servers and all server in domain.
i want to configure per user mode.
how to give 8 RD license each server.
kindly provide me step by step\
thanks
Hi, I don’t think it’s possible to assign per user licenses to servers. You could just limit the number of users per server to 8.
http://social.technet.microsoft.com/wiki/contents/articles/21180.rd-licensing-demystified-how-it-works.aspx
Thanks a lot, it saved me my job! Thanks again, facing this issue for four days and got the solution in 4 minits, a big hug and many many thanks!
Tried this on Server 2008, after removing the reg key and rebooting the key was added back by the system. The license server error was still present.
Found that if I deleted the key and then went back into RD License Manager –> My Server –> Right Mouse click and choose Advanced: Reactivate Server. The server was working and licenses are being used.
Have not had a chance to try this on another server (maybe you can and post back), thinking that after installing the RD Role and before performing the configuration for the license server, delete the reg key above. Have the system in a state where there is no Grace Period key in place, before adding the license server.
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY […]
Just a quick followup as I do my second PC and find a little more information.
In addition to the issue with the registry key present for the grace period I found that I also needed to set the license server using the power shell. “Eric Verdurmen” linked above (blackforce.co.uk) that shows how to do this. My setup is a little different in that I don’t have a domain license server, rather we have CALs from the Open License program – activated by connecting to Microsoft and then the license is installed locally.
From the link to the blackforce.co.uk site we have:
$obj.SetSpecifiedLicenseServerList(“Licenseserver.yourdomain.com”)
I changed this to:
$obj.SetSpecifiedLicenseServerList(“localhost”)
Following this I went back into the RD License Manager –> Advanced –> Reactivate server. License is activated, issues resolved.
I too don’t have a domain, single RDS, licensing on the same server. Deleting the key works but I still don’t have any licensed beeing “Issued”. The count is always at 0.
I’ve applied the hotfix but same result. I fear that the issue will come back in 120 days.
After the fix, there should be issued licenses, if there aren’t. The fix didn’t work
This fails with a ‘you cannot call a method with a null expression’
This sometimes happens when you copy the code, and paste it in a powershell window, paste the code in notepad first, replace all the spaces an quotation marks. This should fix it.
Thank you so much for posting the solution. I spent an entire day removing no RDP licence error when connecting to the RDS server. After following your instructions, I was able to fix the issue in matter of minutes. Thank you once again!
Hello,
I’ve seen this issue on Windows 2012 R2 and really could use the hotfix on this platform. Any one know if this is coming out or what to do other than the registry edits?
Larry
Hello,
Great blog entry. We’re having this issue with some Windows 2012 R2 RDS servers and want to apply some sort of Microsoft Hotfix for this newer operating system like the one that exists for Windows 2012. Does anyone know if there’s something out there to compliment http://support.microsoft.com/kb/2916846?
thanks in advance,
Larry
Not as far as I know. It would be great if they did though. Perhaps you could report it to Microsoft? Just to put it on their radar.
Hello,
It has been half a year since I reported the same issue on Windows 2012 r2 and I didn’t get anywhere with Microsoft on my call BUT I have seen another customer with this issue and also see on people starting to see this issue more often with Windows 2012 R2.
Has anyone else with Windows 2012 R2 found a permanent fix for this problem as deleting the registry key is a temporary fix.
thanks all,
Larry
Lord Eric, thanks a lot, you are welcome to Cancún México whenever u want
Great !, in support Microsoft (forums, e-mail, phone) does not provide solutions to this
Thank you!
wow, thank you so much for this solution!
Group Policy setting takes precedence over the license servers configured in Remote Desktop Session Host Configuration.
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY […]
Awesome, thank you
Spot on! This sorted it for me!
Still working for me with Windows 2008 R2 with all updates to date. Thanks mate!
Note: I compared registry values with another server and GracePeriod and all its subkeys were not present.
great!! Thanx
“Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server”
To activate the licenses or better to hook the RDS service to the already inserted licenses you must launch GPEDIT.MSC and go to:
Computer Configuration > Administrative Template > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing
Removing the Hex Key from the registry solved the issue here as well.
It boggles the mind that as of April 2016 Microsoft still has not resolved this issue from their server software. A licence update was done as per Microsoft documentation, the server was showing rds licensing to be valid and all systems were “green”; yet when the grace period ended, nothing worked anymore.
Jean,
You said it very well – this should be included in a hotfix for Windows 2012 R2 yesterday.
Please Microsoft do this!
thanks,
Larry
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY […]
Thanks for the write up, it has been a life saver!
I have licenses installed, but every few months I have to delete the GracePeriod registry. Any idea why?
Did you check the configuration of the licensing server?
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Legend!
Thank You Very much!!!
Thank you so much
Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much Thank you so much
I beleive this is fix you’re looking for https://support.microsoft.com/en-us/kb/2916846
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Thanks, you saved me from a lot of headaches. Great solution!
To this day . This solution still works!!
Where do we send the beer?
Thank you Sir !
Like the Note said. Make sure you take ownership of the permissions for that particular Key. Otherwise this fix will not work !
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
I have purchased xenapp eseentials with remote access licneses, xenapp doCumentaion says if I am paying extra cost for remote access licenses I dont need RDS CAL’s how come when I RDP into my VDA I see there that Remote desktop services will expire in 120days? I dont need to install the CAL licenses A/Q to the xenapp essentials documentation then How will I get rid of this warning? Can anyone help me with this.
according to:
https://www.citrix.com/global-partners/microsoft/resources/xenapp-essentials-faq.html
you still need RDS licenses
But I have purchased the CAL Licenses from azure marketplace along with xenapp, and in there documentaiton they have written that I dont required to install those licenses If I have purchased from Citrix? So I dont need the RDS CAL’s, then how come I am facing this warning on one of my VDA.
From what I know, you still need the CAL’s, and they’re located in the customer Azure subscription service.
I haven’t tested Xen App essentials myself, so I can’t help you here.
Is it possible to check via script/reg entry if RDS licensing is activated?
I have couple of systems where users did not bother to uncheck not-required roles before installation so filtering those machines serving as actual RDS Licesing machines via SCCM (SMS_G_System_SERVER_FEATURE.Name = “Remote Desktop Licensing” or SMS_G_System_SERVER_FEATURE.ID = 131) is difficult.
Thanks.
You could run a powershell query on all servers:
Get-WindowsFeature -computer {computername} -name “RDS-Licensing” | ? {$_.installed -eq $true}
And if it’s installed, check wether or not it’s activated. I don’t know how the latter part can be done though.
Thanks for the post – was wracking my brain on this one for a while on a server that appeared to be correctly licensed but still wouldn’t let people connect. Deleting the registry key sorted the problem out.
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Thank you, life saver !
The solution fixed a problem I was experiencing for months in my Citrix XenApp + Pvs environment. My golden image / vDisk had the non-default value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod and it only impacted the FIRST LOGON on each of my XenApp servers. I can’t thank you enough!
Perfect – deleting the GracePeriod Binary entry solved also my problem:
5 years after you published it – it still works!
You rocks!!!
/JN
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Excellent, the only one that got this right. Thank You
i had a same issue
my enviromant have 24 RDS session host servers and 1 rds licensing server. all RDSH servers point to licensing server so there are no any issue from that side.
i delete registry binary and problem sorted so far ..
i just want to know what happend after 120 days ? i mean shall i delete same key again after 120 days?
In most cases, 1 time deletion is enough.
If it’s working correctly, you should be able to see licenses being used on the licensing server.
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Cheers Microsoft. Now means my lab can have RDP access past the grace period. 🙂
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
It has been more than 6 years since you post it. But it worked ‘today’
I’m glad it worked for you
Many Thanks for this post!
Like the writer before me, this post helps me also in 2019.
Thanks, oud-collega! 🙂
Fijn dat je er nog iets aan hebt 🙂
thanks! been looking for this fix!
Thanks a lot ! Solved my problem on Server 2019 RDP with SBS 2011 DC after hours of trial and error.
[…] Grace Period has expired even though RD Licensing is properly configured, see Eric Verdumen No remote Desktop Licence Server availible on RD Session Host server 2012. The solution was to delete the REG_BINARY in […]
Thanks, bug still happens in 2019, just fixed it for me 7 years later
This also works for Server 2016!