Maudelin,
"Building" a server takes in a lot of territory. Are you talking about physically building a server (i.e. you need hardware recommendations)? Or are you merely talking about loading the OS on a server?
We could also use a little moreinformation about your goal.
Will this be an additional Domain controller in an existing Active Directory domain? Or will you be creating a new domain? Or will this simply be a member server fulfilling a specific function (file server, databaseserver, Terminal server, email, etc.) in an existing domain.
In general, you need to determine the function of the server. This will drive hardware requirements and software configuration. Next, it's time to do your homework to determine all the steps you need to take based on your desired goal.
As a best practice (if you have the leeway to do so), you should conduct the installation/configuration in a test environment (one not connected to the production network).
If the test installation works successfully, you can conduct installation/configuration on the production server. Depending on the role and configuration needed, you may be able to simply join the test server to the domain.
I'm sorry I can't be more specifichere, but there are too many variables without knowing your specific environment and requirements.
There are literally dozens of books (by publishers such as Sybex, New Riders, IDG, Que, etc.) dedicated to installing and configuring a Win2K server. Almost all of them will include step-by-step procedures for installing and configuring a generic server. I'm hesitant about recommending a specific book because what works for me (or contains the info I need) probably won't work for
(continued)
