Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

Servers — Thu, 26 Aug 2010 08:53:00 GMT

interesting and informative article. thanks for posting.

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

Diego — Tue, 24 Aug 2010 17:19:01 GMT

If I'm using a MS Certification Authority, the TS Licensing use this certificate to encrypt the database?

If yes, assuming that the certificate is automatically renewed by the CA - the "corruption" can be avoided?

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

chandramma — Wed, 04 Aug 2010 06:54:23 GMT

what you’ve put here. there is a really great chart that breaks down all of the different types of remote desktop software

it’s very useful for readers

thank you very much,

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

luismendeze — Fri, 28 May 2010 14:55:09 GMT

Yes this procedure works very fine

I entered to the regedit and erased the next keys

HKLM\Software\Microsoft\TermServLicensing\Certificates.

HKLM\System\CurrentControlSet\services\TermservLicensing\Parameters\Certificates.000

HKLM\System\CurrentControlSet\services\TermservLicensing\Parameters\Certificates.001

I restarted the server and there it was, The terminal server licensing was actived again and is issuing temporary licenses again...

I had no to uninstall the terminal server licensing. This procedure is valid. Very Good. Thanks to all you.

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

Gerry — Thu, 27 May 2010 07:54:14 GMT

Thanks for posting this. It worked like a charm. Saves me days for finding the licenses.

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

Mahomed — Mon, 19 Apr 2010 07:31:26 GMT

Thanks for this. I was getting the same error as in the screenshot when trying to re-activate. After deleting the certificates I was able to re-activate wihtout any problems. I am glad I didn't have to go digging for the licenses.

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

Subhash Tiwari — Thu, 08 Apr 2010 15:08:31 GMT

You can also try to reactivate the Terminal Server certificate from https://activate.microsoft.com

using this site you can enter you license server id and product id and then it will gives you confirmation id using that you can reactivate the server.

Cheers,

Subhash Tiwari Orient Technologies Mumbai India

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

termserv — Mon, 05 Apr 2010 15:59:03 GMT

@phiggins:

This link is supposed to point back to the "To delete the license server certificate" section above.

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

phiggins — Mon, 05 Apr 2010 15:41:28 GMT

When I click on the "Delete the license server certificate" link in the last paragraph, I get an error message from the MSDN Blogs site telling me "Access Denied: Post Permission Denied Either this forum does not exist or you are not allowed to post." (And I had to register there first.)

Could you fix that link, please? I could really use those instructions.

re: Event 17 – Certificate Corruption on Terminal Services/Remote Desktop License Servers

Jason Carter — Fri, 02 Apr 2010 12:25:32 GMT

My RDS Server is internet connected, however, when I attempt to re-active my server I get the following message: The RD LIcensing Manager received and unrecognized response from the Microsoft Clearinghouse. The Site may be experiencing problems or your internet connection may not be functioning properly. Check your internet connection and retry the operation. If the problem persists, trying using a differnt connection method.

I know my connection is working correctly, is the clearing house site having issues today?