I am a fan of TS in Win2K. I think it was a very good decision to put it in there. I do a majority of my admin tasks on Win2K Servers using TS sessions.
Now, here are some things to think about.
1) It does not replace actually getting up and standing in front of the server. If there are applications that launch when the server boots up and is first logged into (like Lotus Domino, the mail server my company uses) then TS is no help. In those cases, when I need to see what is happening on the console screen, I go to the server. But unless that is the case, TS works. I have installed applications in TS sessions (installed Crystal Reports 8 once on a server, and that is a major install!).
2) TCP port 3389 will be open on your server, as this is the listening port for TS. If you have servers that are unscreened on the Internet (without firewall protection for some INSANE reason!) then DON'T PUT TS ON!!! There are tools out there that can crack a Windows password using TS, doing a dictionary attack. I haven't read about many attacks on port 3389, but everyone knows what that port is for when the see it open on the Internet. Just think of it this way: with TS running, you have an open Console-like connection available, as if your server room door was wide open and available to anyone walking by on the street. Make sure your security settings (firewall, router access lists, etc.) are set.
3) Performance is light, in my observations. Maybe 5 MB RAM used just to have TS installed and running without connections. If there are connections on it, then you need to factor that in with your servers hardware capabilities.
