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?

 

[supportahm1980]

you win 2k machine or even xp machine can download the newest rdp software version 6

http://support.microsoft.com/kb/925876

As far as your senario are you asking for remote access to the server rather then VNC? Or do you want terminal services for you employees....like citrix?

 

[humbletech99]

yes I do want users to be able to get a remote session but I think that citrix is only for thin client boxes, right?

My users all have PCs and just want to run some processes on a central server rather than local desktops because the server can do it faster.

So we will use rdp client that you proposed and terminal server on these processing servers

unless anyone has a better idea.

 

[dberg35]

I use Terminal Services and the 2003 Server you have to purchase licenes and can get costly. 2000 Server licensing is free and unlimited for XP and W2K clients. Citrix would work but and costs more than Terminal Services.

 

[58sniper]

Citrix and TS both work on thin clients. Thin clients are great when it's time to replace those PCs.

Put your licensing on your DC as requested. If you follow best practices, your DC shouldn't be down for unplanned maintenance very often.

Install the tsweb component on the TS box so people can use IE as the RDP client.

Search here for info on GPOs for TS boxes to keep things stable and secure.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[Stevehewitt]

If your using VNC then I guess your using it for admin? In that case you have 2 free TS concurrent connections anyway - WinXP has version 5 of the RDP client, and version 6 is on the Windows Update / MS site free now too. You could deploy it using SUS/WSUS, Windows Updates or as mentioned above use the IE RDP ActiveX Client.




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[humbletech99]

no it's not only for admin, users need to run large processing tasks on servers which is why I am exploring Terminal Services.