archives technorata gallery music

Installing Windows Server 2003 Standard Edition

November 19th, 2007
winserv2003web1.png

Possibly I’m bored or I am actually being responsible and documenting a successful Server 2k3 install. I attempted something similar last year using a wiki when I was studying for an MSCE exam (I passed thanks much). Since then I’ve been busy with web development projects and haven’t had much reason to mess with Windows server’s aside from basic administration tasks. However, I’m getting the itch to get back on track and finish my MSCE and where better to start than by documenting a Windows Server 2003 installation.

Note: This is all being done in VMWare Server on a Linux host OS - Ubuntu Gutsy to be specific.

Windows Server 2003 Requirements

Let’s do away with all the obvious stuff.

  1. Computer and processor: 133-MHz processor required; 550-MHz or faster processor recommended; support for up to four processors on one server.
  2. Memory: 128 MB of RAM required; 256 MB or more recommended; 4 GB maximum.
  3. Hard disk: 1.2 GB for network install; 2.9 GB for CD install.
  4. Drive: CD-ROM or DVD-ROM drive.
  5. Display: VGA or hardware that supports console redirection required; Super VGA supporting 800 x 600 or higher-resolution monitor recommended.

On with the installation…

So before I continue, I’ll just add the obvious fact that we’ll need the space formatted for NTFS. So next…

  1. Insert the CD, boot up the system, install in the desired partition using NTFS (NTFS Quick is fine too) and let the setup finish.
  2. When prompted for licensing scheme, I selected the option that clients would have licenses. It’s a guess and what made me decide to do this write up in the first place.
  3. After setup is complete, login. There is no domain to log into yet, we’ll create the domain shortly.
  4. After logging in, a large window will appear labeled ManageYour Server. Locate and click the add or remove a role link. This is where we’ll begin to create our domain controller.
  5. On the Configuration Options page, since this is our first server in the domain, we will select Typical configuration for a first server.
  6. In the Active Directory Domain Name page we will give our domain a name. Mine is TestNet.local. I used the default .local extension but Microsoft allows others as well.
  7. On the NetBIOS Name page I used the default provided given my AD Domain name; TESTNET.
  8. You should be presented with a summary of configuration options at this point. Mine was:
    Install DHCP server (if required)
    Install Active Directory and DNS server (sets up this server as a domain controller)
    Create the following full domain name: TestNet.local
  9. Click Next and the configuration will be applied and the system will restart.
  10. Log back in (you’ll see the domain name listed now) and a page presents you with all the configuration changes.
  11. Okay, now let’s do all our Windows updates. This will take some time. So fire up IE, start the updates and go grab some coffee or stimulant of choice.

That’s enough for now…I’ll cover finishing the install in Part 2

DNS Configuration

So now we’ll configure our DNS, specifically I want to check that reverse lookups are have been installed.

  1. Open DNS Management, then expand your server node
  2. Locate and right click the folder Reverse Lookup Zones selecting New Zone
  3. Click Next and in the next window select Primary Zone
  4. Click Next and select To all DNS servers in the Active Directory forest…
  5. Click Next and input your network number in the area labeled Network ID. So for a refresher, if your network range was 192.168.1.1 - 254 your Network ID would be 192.168.1. Click Next
  6. If prompted to configure Dynamic Updates, select Allow only secure… just to be safe. This will only allow AD clients to alter DNS records so remember if you’ll need to manually update entries for non-AD members.
  7. Click Finish

So that’s it, pretty easy. Something to note, you won’t see your DNS clients immediately creating their PTR or reverse lookup records, it can take some time. As long as you followed the instructions in Step 6 above, your AD clients will update dynamically. However, if you can’t wait, you can create the resource record by right clicking in the Reverse Zone node and selecting New Pointer (PTR).

Comments are closed.

-->