Sam,
I'm assuming you're referring to the terminal services
client, which allows someone to remotely log on and
establish a session no your Win2K server.
All you need to do in order to accomplish this is to use
the Win2K server's terminal services client administrator
to make the insatllation disks (takes two floppies). Run
that on the remotes to install the Terminal Services
client software on the remote. Back on the server, you'll
need to set up the terminal service, and specify which
domain accounts have what privileges, etc.
When users log on froma client, the client specifies to
the host what account they sign on with. If I am
(e-mail address removed) domain, that has nothing to do with the
security credentials I have when I log on remotely to the
server, as I get whatever security credentials the accoutn
has on the server that I log on with, as if though I were
actually sitting at the server's keyboard. So, if I log
on to yourdomain.local as "Administator" using the
terminal services client, I have administrative rights on
your server, irrespective of what rights I have (or don't
have) on my own local machine.
You'll prob. want to creaet AD accounts on your server to
manage yoru terminal services users. Just remember that
those AD accoutns have nothing to do with the domains
where the users are remotely connected.
Oh... and one more thing... If you're firewalled, you're
goign to need to open up a port in your firewall, or
Terminal Services clients won't be able to hit yuor
server. Offhand, I forget the port number, but if you
need to know it, reply and I'll check it for you.
I hope that answers your questions!
JIM
