Setting up a Windows domain network

[wherzwaldo]

I need to set up a Windows domain network, probably using Windows 2000 Server (2003 is still pretty expensive). However, I am a little confused with the terminology.

If I buy a X-client license, does that include the Win2K Server OS itself, or does that include just the ability for the OS to allow X number of clients to connect to the network? Will I have to buy the server OS separately? Likewise, if I buy the server OS, will I have to buy an X-client license?

Also, I consider myself an advanced/expert user of most Windows operating systems, but I am a total newb when it comes to servers. Would the setup of a domain be pretty intuitive, or should I find a Win2K Server for Dummies equivalent? The server's primary use would be as a network's file/Exchange server; it won't be running a web/FTP/SQL/etc server on the Internet.

And just so you know, yes, it HAS to be a domain (not just a workgroup), and yes, it HAS to be Windows (not [insert Linux flavor of the month]).

 

[schnarkle]

Usually the server license will include 5 CALs. (Client Access Licenses).

Also 2003 is a big improvement over 2000 IMO. If you can swing it that is. You should definitely read up on installing and creating new domains before sticking in the cd and clicking away though.

This is a great book easy to read and you'll learn a lot. Any Mark Minasi book on the subject is great.

 

[wherzwaldo]

Cool.

Now, the client access things wouldn't replace the client OSs, correct? Most computers are running XP Professional.

 

[schnarkle]

No, the CAL's are only licenses for your pc's to connect.
Be aware though that the PC's MUST have XP PRO if you are running xp clients. XP HOME CANNOT connect to a real domain... workgroups only for that.