The remote session could not be established from remote desktop ____ because its temporary license has expired

We have a Windows Server 2008 Enterprise installed and performing Remote Desktop Services.  We had installed a 90 day temporary license.  It ran out of time this week.

We bought 2 x 5 CAL user licenses and installed and activated them on the same licensing server. We are still getting the error message:

The remote session could not be established from remote desktop ____ because its temporary license has expired

Now I have gone into the license server and I see my 10 user licenses, but my expired temp license is still in there with the usernames.  

Not sure how to get my RDP to respond now?

Thanks ahead of time for your reply.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Radhakrishnan RSenior Technical LeadCommented:

Terminal Services server issues temporary licenses to all the client machines connecting to terminal services. It is required for the terminal services to process the request in timely fashion and will generate the hardware ID to keep the licensing information for client machine. This hardware ID is stored on client machine. This hardware ID is used to check the expiry of license. If license is expired terminal services server can not re-issue license to same computer account. Generally all the temporary license are valid till 90 days.

There are two ways to get rid of this when a client machine needs to have access to Terminal Services session but its license has expired:

Change the computer name.
Remove the License key from client computer.
The second method is very useful. It just requires a registry setting to be removed from client computer. The following registry settings must be removed from client computer:
After deleting above sub-keys try connecting to your Terminal Services server you should be able to get in.

If the above method didn't help then have a look at this MS article

Hope this helps you to resolve the issue.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.