Windows Server 2003 is a server operating system produced by Microsoft. Introduced on March 28th, 2003 as the successor to Windows 2000 Server, it is considered by Microsoft to be the cornerstone of their Windows Server System line of business server
products.
Windows Server 2003 is well-known for its good stability, security and user friendliness compared to other server operating systems or even its precedessor Windows 2000. According to Microsoft, Windows Server 2003 takes less time to set up and is much easier to configure than Windows 2000.
Here is how to set up Windows Server 2003:
Before you install Windows Server 2003 on a computer, particularly in cases when you are creating a new network infrastructure, you should create a map of what your network will look like. The server's role, such as acting as a domain controller or a multihomed router (a Windows Server 2003 configured with more than one network interface card) or a NAT server, dictates not only the server's hardware configuration, but also the configuration of that server (and the services that it provides).
Server Hardware Requirements
Windows Server 2003 requires a minimum hardware configuration to run. Microsoft's suggested minimum hardware requirements (and some Microsoft recommendations) for Windows Server 2003 (Standard) are listed here:
* CPU speed: 133MHz (550MHz recommended)
* RAM: 128MB (256MB recommended; 4GB maximum on Standard Server)
* Disk space for setup: 1.5GB
* CD-ROM drive: 12X
* Monitor: Super VGA capable of providing 800 x 600 resolution
Using Supported File Systems
Windows Server 2003 supports the entire range of file systems supported by Microsoft operating systems. This ability was first introduced with Windows 2000 Server. You can have FAT, FAT32, and NTFS partitions or volumes on your server's hard drives. A description of each file system follows:
* FAT-FAT volumes use a file allocation table that provides the name of the file and the location of the actual clusters that make up the file on the hard drive. FAT is a holdover from the days of DOS. I see no compelling reason to use FAT volumes on your
servers.
* FAT32-FAT32 is an extension of the FAT file system. It uses disk space on a drive more efficiently than FAT and was designed for Windows 95/98.
* NTFS-NTFS 5 is the newest version of the NT file system (NTFS 5 was first introduced with Windows 2000 Server). It provides increased security for files on NTFS volumes and supports more robust file system recovery. Microsoft recommends that you use NTFS as your file system on your Windows servers. It is also required if you want to install Active Directory on a server to make it a domain controller. It really makes sense to use NTFS volumes on your servers unless you need to create a dual-boot server on which a legacy operating system requires a FAT or FAT32 partition to run on the server. Actually, in most cases, it doesn't make sense to deploy a server on a network that was configured for dual-boot. NTFS provides the stability, the security, and other bells and whistles that makes it the appropriate choice for your server drive implementations.
Performing a Clean Installation
Windows Server 2003 R2 contains two product discs. Disc 1 contains Windows Server 2003 with Service Pack 1 (SP1). Disc 2 contains the installation files for the Windows Server 2003 R2 optional components. Both discs use the same Product Key.
To install Windows Server 2003 on a server that is not configured with a previous operating system, set up the system so that it boots to the CD-ROM drive (using the computer's BIOS settings utility). The clean installation consists of two different phases: a text phase and then a Windows phase. During the text phase, you specify (and create, if necessary) the
partition that will be used as the target for the Windows Server 2003 installation.
Text Mode Installation Phase
1. Insert the Windows 2003 installation CD1 into your CD-ROM drive, then restart the machine.
2. The server boots to the CD. Windows Setup will check the computer's configuration, prompt you to press the F2 key to start system recovery (don't press this key), and load core files into memory. When Windows Setup prompts you to Setup Windows, use the Recovery Console, or Exit, press Enter to continue the installation process.
3. The Windows Licensing Agreement appears. After reading the licensing information, press F8 to continue.
4. Windows Setup will display the disk partition screen.
* If the hard disk is unpartitioned, you can create and size the partition on which you will install Windows Server 2003.
* If the hard disk is already partitioned, but has enough unpartitioned disk space, you can create an additional partition in the unpartitioned space.
* If the hard disk already has a partition that is large enough, you can install Windows Server 2003 on that partition. If the partition has an existing operating system, you will overwrite that operating system if you accept the default installation path. However, files
other than the operating system files, such as program files and data files, will not be overwritten.
* If the hard disk has an existing partition, you can delete it to create more unpartitioned space for the new partition. Deleting an existing partition erases all data on that partition.
After selection press Enter to continue installation.
5. You are asked to format the new partition. You are provided with a choice of NTFS or
FAT. Because domain controllers require an NTFS partition to run the Active Directory, you typically want to select NTFS. Select the file format (using the error keys) and then press Enter.
6. The setup program formats the partition and then copies installation files to the server. After the appropriate files are copied, the server reboots. This ends the command-line portion of the Windows Server 2003 setup. The graphical phase of the installation will begin.
Windows Installation/Configuration Phase
7. It will then begin to load device drivers based upon what it finds on your computer. You don't need to do anything at this stage.
8. Windows Setup will prompt you to set regional and language options. Click the Customize
and Details buttons, select the appropriate check boxes for the correct regional options, then click Next.
9. On the next screen, provide your name and organization. Then click Next to continue.
10. Enter the product key, then click Next.
11. The next screen asks you to select your licensing method. You can license your network either per server or per seat. If you select Per Server (the default), specify the number of concurrent connections using the spin box. After you select the licensing mode, click Next.
12. Enter a computer name for the server and an Administrator password. If you attempt to use a password that doesn't meet Windows 2003's definition for a strong password (e.g., at least six characters; doesn't contain "Administrator" or "Admin"; contains uppercase and lowercase letters, numbers, and non-alphanumeric characters), Windows Setup will warn you and you'll have to click Yes to continue with your chosen password. Click Next.
13. The next screen enables you to set the time zone for your computer and the current date and time (if necessary). After you set these parameters, click Next to begin the network installation phase.
14. After the network installation phase performs several checks and detects your network settings, confirm your TCP/IP settings when prompted.
The installation defaults to using DHCP (to automatically assign an IP address), but you can configure a static IP address or specify a different configuration if the DHCP server isn't available. To modify the TCP/IP settings, select Custom settings, click Next.
Select Internet Protocol (TCP/IP), then click Properties.
After you finish modifying the TCP/IP settings, click OK, then click Next.
15. You can choose whether this server belongs to a workgroup or a domain. The default setting is that the computer is not on a network or is on a network with a workgroup instead of a domain. The default workgroup name is WORKGROUP. Whether you will use the server in a workgroup or a domain, at this point it is best to go with the default and complete the Windows Server 2003 installation and configuration. Press Next to continue.
16. The installation will continue without further user input. This final phase of the installation includes further configuration, including copying of files, creating the Start menu, registering components, and finalizing the settings.
17. After the installation is complete, the server reboots.
After the server restarts, press Ctrl+Alt+Del.
At the password prompt, supply the password you set for the Administrator account during the installation process. You will be logged on to the server.
Tuesday, May 12, 2009
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment