Do you want this server to be a Terminal Server, for multi-user
access, or do you just want to connect to it for remote
administration?
If you want a TS, yes, you will need to install and activate a 2003
TS Licensing Server and install TS CALs on it for every device or
user which connects.
If you only need remote administration: no, you do not need any TS
CALs. AND: do *not* install Terminal Services at all, since TS on
2003 implies "Application Server mode". Just enable Remote Desktop
for Administration in Control Panel - System - Remote.
And there is no reason why you should not be able to use your W2K
client to connect to the 2003 server. Just download and install the
latest rdp client:
http://www.microsoft.com/downloads/details.aspx?familyid=80111f21-
d48d-426e-96c2-08aa2bd23a49&displaylang=en
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Don Miller" wrote on 06 sep 2006 in
microsoft.public.windowsnt.terminalserver.misc:
> I'm putting my first server on my network to act as a test
> machine. It will have Win2003 standard. I want to access the new
> server using my dev machine (Win2K Pro) using TS like I now
> access a remote dedicated server (at a datacenter using TS)
> since it doesn't have a keyboard or monitor.
>
> Do I need a separate license for TS along with Win2003? Does
> Win2003 support TS along with Remote Desktop (that I apparently
> cannot use with my Win2K Pro machine)?
>
> Since I have neither the server or Win2003 yet, I want to make
> sure I can access the new machine on day one.
>
> Thanks for any tips or directions to articles on this subject.