- Planning the Server Installation
- Server Hardware Requirements
- Checking Hardware and Software Compatibility
- Understanding Server Licensing Issues
- Choosing to Upgrade or Make a Clean Installation
- Using Supported File Systems
- Performing a Clean Installation
- Performing an Upgrade
- Understanding Windows Product Activation
- Choosing Between a Workgroup and a Domain
- Summary
- Q&A
Q&A
What two hardware considerations should be an important part of the planning process for a Windows Server 2003 deployment?
Any server on which you will install Windows Server 2003 should have at least the minimum hardware requirement for running the network operating system. Server hardware should also be on the Windows Server 2003 Hardware Compatibility List to avoid the possibility of hardware and network operating system incompatibility.
What are the possibilities for licensing clients in relations to your servers running Windows Server 2003?
Client licenses can be handled in two different modes. The per-server mode provides a license for a definite number of concurrent connections to the server. The per-seat mode requires a license for each network user on the network. Recording and managing licensing is handled by the Licensing snap-in.
What are the options for installing Windows Server 2003?
You can install Windows Server 2003 on a server not currently configured with a NOS, or you can upgrade existing servers running Windows 2000 Server and Windows NT 4.
What are the options for file systems on a new Windows Server 2003?
Windows Server 2003 supports NTFS, FAT, and FAT32 partitions. It is a best practice to use NTFS on system volumes and any other volumes on which you want to have the added security provided by NTFS permissions. NTFS is required if you want to install the Active Directory to make the server a domain controller.