15 Replies
· · ·
Datil
OP
Jul 3, 2020 at 13:37 UTC
Err, nothing below. Did you check the Event Log for the message?
0
· · ·
Mace
OP
Best Answer
Jul 3, 2020 at 13:45 UTC
open Gpedit.msc Computer Configuration->Administrative Templates-> Windows Components-> Remote Desktop Services-> Remote Desktop Session Host-> Licensing. Use the specified Remote Desktop license servers set the server that has RDP cals or running in trial
Buy Cals or
To renew RDS grace period, you need to find the following registry key and delete the GUID
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Terminal Server\RCM\GracePeriod”
Before you can delete the registry key, you need to change ownership. You can do that by following these steps:
Right-Click on the key.Click on “Permissions”.Click on “Advanced”.Click on “Owner”.Select “Administrators”.Click on “Apply”You can now delete the key. Reboot the server and you now have a new grace period.
1
· · ·
Thai Pepper
OP
Jul 3, 2020 at 13:55 UTC
Jim Peters wrote:
Err, nothing below. Did you check the Event Log for the message?
LOL yea the image may help.
0
· · ·
Thai Pepper
OP
Jul 3, 2020 at 13:58 UTC
JitenSh wrote:
open Gpedit.msc Computer Configuration->Administrative Templates-> Windows Components-> Remote Desktop Services-> Remote Desktop Session Host-> Licensing. Use the specified Remote Desktop license servers set the server that has RDP cals or running in trial
Buy Cals or
To renew RDS grace period, you need to find the following registry key and delete the GUID
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Terminal Server\RCM\GracePeriod”Before you can delete the registry key, you need to change ownership. You can do that by following these steps:
Right-Click on the key.Click on “Permissions”.Click on “Advanced”.Click on “Owner”.Select “Administrators”.Click on “Apply”You can now delete the key. Reboot the server and you now have a new grace period.
I do have the cals - I'll make the changes and report back shortly. Will I need to reboot the server once the changes are made or will a gpupdate work ok?
JitenSh
Mace
0
· · ·
Mace
OP
Jul 3, 2020 at 14:02 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
There is no need to reset the grace period if you do in fact have CALs. Install them in License Manager on your licensing server, activate them and then edit the RDS deployment properties to point to the licensing server. You need to do this even if your licensing service is on the same server.
2
· · ·
Thai Pepper
OP
Jul 3, 2020 at 14:12 UTC
Da_Schmoo wrote:
There is no need to reset the grace period if you do in fact have CALs. Install them in License Manager on your licensing server, activate them and then edit the RDS deployment properties to point to the licensing server. You need to do this even if your licensing service is on the same server.
OK changes have been made. How will I know of the changes are working or not besides logging in and out?
0
· · ·
Mace
OP
Jul 3, 2020 at 14:24 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
Garnock12 wrote:
Da_Schmoo wrote:
There is no need to reset the grace period if you do in fact have CALs. Install them in License Manager on your licensing server, activate them and then edit the RDS deployment properties to point to the licensing server. You need to do this even if your licensing service is on the same server.
OK changes have been made. How will I know of the changes are working or not besides logging in and out?
The licensing diagnoser tool will tell you if you have a configuration problem. You should check Licensing Manager and see if licenses are being issued. I believe a license is only issued after the 2nd time a device or user connects.
0
· · ·
Thai Pepper
OP
Jul 3, 2020 at 14:26 UTC
Da_Schmoo wrote:
Garnock12 wrote:
Da_Schmoo wrote:
There is no need to reset the grace period if you do in fact have CALs. Install them in License Manager on your licensing server, activate them and then edit the RDS deployment properties to point to the licensing server. You need to do this even if your licensing service is on the same server.
OK changes have been made. How will I know of the changes are working or not besides logging in and out?
The licensing diagnoser tool will tell you if you have a configuration problem. You should check Licensing Manager and see if licenses are being issued. I believe a license is only issued after the 2nd time a device or user connects.
OK I'll give it a few hours and see how things go. If I don't get back today I hope everyone has a great weekend
0
· · ·
Mace
OP
Jul 3, 2020 at 14:44 UTC
If you have CALS
open Gpedit.msc Computer Configuration->Administrative Templates-> Windows Components-> Remote Desktop Services-> Remote Desktop Session Host-> Licensing. Use the specified Remote Desktop license servers set the server that has RDP cals
Set the Remote Desktop licensing mode user or device
0
· · ·
Thai Pepper
OP
Jul 6, 2020 at 18:25 UTC
JitenSh wrote:
If you have CALS
open Gpedit.msc Computer Configuration->Administrative Templates-> Windows Components-> Remote Desktop Services-> Remote Desktop Session Host-> Licensing. Use the specified Remote Desktop license servers set the server that has RDP cals
Set the Remote Desktop licensing mode user or device
It's still popping up but I think I forgot to set the type of CAL. Is one better than the other?
JitenSh
Mace
0
· · ·
Mace
OP
Jul 6, 2020 at 18:32 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
Garnock12 wrote:
JitenSh wrote:
If you have CALS
open Gpedit.msc Computer Configuration->Administrative Templates-> Windows Components-> Remote Desktop Services-> Remote Desktop Session Host-> Licensing. Use the specified Remote Desktop license servers set the server that has RDP cals
Set the Remote Desktop licensing mode user or device
It's still popping up but I think I forgot to set the type of CAL. Is one better than the other?
Just like Server CALs, you purchase what is appropriate for your environment. User CAL licenses a user to use the service from any device. Device CAL licenses that device to access the service regardless of who the user is. That said, if you are in a Workgroup environment, you have to use Device CALs.
The nice thing with 2019 is you can convert User to Device and vice versa. You could not do that before. However, you need to choose what matches the CALs you purchased in order to install and activate them. Afterwards you can convert them.
0
· · ·
Thai Pepper
OP
Jul 6, 2020 at 18:39 UTC
In RD licensing manager I have 8 Per user cals. I'll update the policy to set that. I assume I'll need to reboot a time or two?
0
· · ·
Mace
OP
Jul 6, 2020 at 18:41 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
Shouldn't need to reboot.
0
· · ·
Thai Pepper
OP
Jul 6, 2020 at 18:45 UTC
oh ok that is cool. I thought policy changes weren't immediate>????
0
· · ·
Mace
OP
Jul 6, 2020 at 18:47 UTC
Microsoft Remote Desktop Services expert
50 Best Answers
207 Helpful Votes
If you're using Group Policy to apply the licensing server info you'd have to force an update from a command prompt or reboot if you don't want to wait for the refresh.
1
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Archived Forums
>Remote Desktop Services [Terminal Services]
Question
-
0
Sign in to vote
Hi folks-
I have an old windows server 2008terminal services farm of 2 serverswhich is having this issue. I have a new farm of 2008 r2 std which is not having the same issue. I inherited the old farm. This started yesterdaywhen one of the old servers started to get this message when logging in as an administrator:
'Cannot find a valid terminal services license server. Terminal services will stop working because this computer is past it's Grace period and has not connected to a valid terminal services license server. Click this message to launch the terminal services configuration tool to specify a valid license server.'
So I trace this back to the RDP license server which turns out to be a domain controller. It seems that a supporting role service for RDP licensing role was removed or missing somehow. So I removed it from the domain controller and moved it to another new memberserver. It transferred successfully and the licensing diagnosis on the new RDP license server 'did not identify any licensing problems for the remote desktop session host server' which is great. I pointed both servers in my new farm and both servers in my old farm to the new RDP licensing server and the new farm seems just fine, but the old farm still gets this message.
I'm still migrating users over from old farm to new and don't want anyone to suffer login problems on either farm as we complete the transition. The problem definately seems to be with the old farm, but it says we are past our grace period. Any suggestions to avoid problems in the old farm while migrating? I'm not seeing any event log errors regarding the RDP licensing on either server in the old farm. Thanks.
- Edited by capitan12 Thursday, September 26, 2013 7:20 PM
Thursday, September 26, 2013 7:19 PM
All replies
-
0
Sign in to vote
Hi,
Thanks for your Post in Windows Server Forum.
The error which you faced can be take occur due to different reason.
- If temporary License Expired.
- It can also occurs due to incorrectly perform security check.
- If RDSH Server cannot communicate with RD License Server.
- If there is any problem with RD licensing mode.
In reference to your issue, there is Microsoft Hotfix [KB 2028637] available, kindly download and install.
Review Topic “Events: Remote Desktop Services Client Access License Availability” in below link, for more information on the issue.
//thwack.solarwinds.com/docs/DOC-158046
Hope This Helps!
Thanks.- Marked as answer by Dharmesh SMicrosoft employee Monday, October 7, 2013 1:07 AM
Saturday, September 28, 2013 4:16 AM
Reset 120 day RDS Grace period on 2016 and 2019
brandon.lee
4 minutes read
If you have a home lab environment or other lab that you continually test various solutions, licensing and trial expiration is a challenge that you constantly tend to run into. It is just part of the fun of lab environments. While most trials are fairly “hard and fast” and don’t allow you to reset the trial expiration, if you work with Microsoft Windows Server and Remote Desktop Services [RDS], there is a “hack” that allows you to effectively reset the expiration of Remote Desktop Services grace period where you can essentially rewind the clock on your RDS licensing if you are making use of this role inside your lab environment. In my lab environment, I am making use of Windows Server 2019 for my Windows workloads. In this post, I will show how to reset 120 day RDS Grace period on 2016 and 2019 Windows Server. Let’s see.
Remote Desktop Services will stop working in 0 days
1 tháng trướcThe error Licensing Mode for Remote Desktop Session Host is not Configured often triggers triggers when the RDS host is running in grace period.
As a part of our Server Management Services, we help our Customers to fix Windows related errors regularly.
Let us today discuss the possible causes and fixes for this error.
403
Ваш сайт заблокирован панелью управления хостингом
Обычно это происходит если хостинг не продлен или закончился баланс. Пожалуйста, войдите в личный кабинет, чтобы продлить ваш аккаунт.
Активация услуги после продления происходит моментально.