Tech Support Guy banner
  • Please post in our Community Feedback thread for help with the new forum software! If you are having trouble logging in, please Contact Us for assistance.
Status
Not open for further replies.
1 - 2 of 2 Posts

·
Registered
Joined
·
69 Posts
Discussion Starter · #1 ·
I'm looking at setting up windows 2003 terminal servers all over the place to replace the awful thing people are currently doing here - vncing servers with one small shared password among everyone <holding my hands over my ears for the backlash>. Don't blame me, it's another awful legacy I have to get rid of...

1. I've got to set up a Terminal Server Licensing server and was thinking about putting this on my second domain controller. I was wondering what would happen in this server dies, though. Is there some way of having resilience in this scenario? Perhaps a second Licensing server or something, the way you have 2 or more Domain Controllers?

2. Also, I know that Windows XP has an RDP client, I've used before on many occasions, but what about all the Windows 2000 clients that I still have out there. What should I do for them to access the new Terminal Servers?
 

·
Registered
Joined
·
2,960 Posts
I'm not 100% sure on #1, but I believe that the TS licensing becomes integrated into the AD, so if one DC goes down, the other one will be able to check licensing. On another note, if you are using the TS for administration only, I don't believe you needs the TS Licensing to be installed.

For #2, you can download the latest version of the RDP client from MS's website. It should also be available through Windows Updates, although I think Win2K isn't supported any longer, other than Critical Updates.
 
1 - 2 of 2 Posts
Status
Not open for further replies.
Top