davidjuste
asked on
Terminal Server Service does not start after domain controller demoted to member server
Hi
We have an old Terminal Server which use to be a domain controller (windows 2000) which was setup by an engineer who's left. Since the demotion to domain member server. The Terminal Server Service does not start. And if Clients try to logging to TS they receive: The terminal service client 'PCNAME' has provided an invalid license.
How can we get the TS Services to start assigning license to client, since Terminal Services Licensing can only be run on Domain Controllers. Is it possible. We currently have 3 domain controller.
We have an old Terminal Server which use to be a domain controller (windows 2000) which was setup by an engineer who's left. Since the demotion to domain member server. The Terminal Server Service does not start. And if Clients try to logging to TS they receive: The terminal service client 'PCNAME' has provided an invalid license.
How can we get the TS Services to start assigning license to client, since Terminal Services Licensing can only be run on Domain Controllers. Is it possible. We currently have 3 domain controller.
tonyperth
Install terminal services licencing on one of your DC's then go in to the terminal server's configuration and point it at the new licencing server. If you still have licencing installed on the terminal server, uninstall it.
ASKER
thanks will try this
Try opening the services snaping and check the account that the Terminal Services service is running under. Usually it runs under the local system account.
ASKER
I followed an article that recommeded some steps as below. I then converted the server to virtual server in a lab and did the following.
1.) Demoted Server win2000.
2.) Upgrade Server to Windows 2003
3.) Under : [HKEY_LOCAL_MACHINE\SYSTEM
delete the following keys (X509 Certificate, X509 Certificate ID & Certificate) reboot the server.
5.) when server is online : Open Terminal Server Licensing and the server is in license activated mode :) and able to assign client license that logs onto it. But the license will be (2000) only Terminal Server license.
This works for us as this is our only Terminal Server.
1.) Demoted Server win2000.
2.) Upgrade Server to Windows 2003
3.) Under : [HKEY_LOCAL_MACHINE\SYSTEM
delete the following keys (X509 Certificate, X509 Certificate ID & Certificate) reboot the server.
5.) when server is online : Open Terminal Server Licensing and the server is in license activated mode :) and able to assign client license that logs onto it. But the license will be (2000) only Terminal Server license.
This works for us as this is our only Terminal Server.
ASKER
so we will use this method in the live enviroment. Thanks for your help Acstechee.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.