Terminal Server license server(s)? RDP client for Windows2K?

[humbletech99]

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?

[snowmonkey]

You need a BDC for sure in order to have the Licenses for terminal server available all the time in case !!!

For Windows 2000 user....I would suggest to use the MS package for RDP, it work just as well as it does for Windows XP:

http://www.microsoft.com/windowsxp/d...dclientdl.mspx

What I'm not clear about is that, Why do your users need VNC or even terminal services access to the servers.....you as admin should be the only one with those kind of access.


Cheers

[humbletech99]

We want to run processes on the servers as the users. This is for large processing tasks that are bigger than workstations should do.

BDC? AD doesn't strictly have BDCs. Do you mean BDC TSLSs?

[snowmonkey]

Originally Posted by humbletech99

We want to run processes on the servers as the users. This is for large processing tasks that are bigger than workstations should do.

BDC? AD doesn't strictly have BDCs. Do you mean BDC TSLSs?

You don't need to have AD on a server to make is BDC.......BDC could handle you TS licensing if you PDC goes down.



Cheers