Windows Server 2003 R2 Editions and Features
|
Features
|
Standard Edition
|
Enterprise Edition
|
Datacenter Edition
|
File Server Resource Manager
|
√
|
√
|
√
|
Storage Manager for SANs
|
√
|
√
|
√
|
Active Directory Federation Services (ADFS)
|
|
√
|
√
|
ADFS Proxy
|
|
√
|
√
|
ADFS Web Agents
|
√
|
√
|
√
|
Active Directory Application Mode
|
√
|
√
|
√
|
Distributed File System – Replication with Remote Differential Compression
|
√
|
√
|
√
|
Distributed File System – Cross-File Remote Differential Compression*
|
|
√*
|
√*
|
Print Management Console
|
√
|
√
|
√
|
Microsoft Management Console 3.0
|
√
|
√
|
√
|
Windows SharePoint Services V2 SP2
|
√
|
√
|
√
|
.NET Framework 2.0
|
√
|
√
|
√
|
Subsystem for UNIX Applications
|
√
|
√
|
√
|
UNIX Interop (NIS Server, Password Sync, NFS Admin, etc)
|
√
|
√
|
√
|
x64 Availability
|
√
|
√
|
√
|
WS-Management
|
√
|
√
|
√
|
* Only one of the replication partners is required to be an Enterprise Edition or Datacenter Edition.
System Requirements
In general, system requirement for Windows Server 2003 R2 are the same as the following general Windows Server 2003 system requirements:
Windows Server 2003 R2 System Requirements
|
Requirement
|
Standard Edition
|
Enterprise Edition
|
Datacenter Edition
|
Minimum CPU Speed
|
133 MHz
|
• 133 MHz for x86-based computers
• 733 MHz for x64-based computers
|
• 400 MHz for x86-based computers
• 733 MHz for x64-based computers
|
Recommended Minimum CPU Speed
|
550 MHz
|
733 MHz
|
733 MHz
|
Minimum RAM
|
128 MB
|
128 MB
|
512 MB
|
Recommended Minimum RAM
|
256 MB
|
256 MB
|
1 GB
|
Maximum RAM
|
• 4 GB for x86-based computers
• 32 GB for x64-based computers
|
• 64 GB for x86-based computers
• 1 TB for x64-based computers
|
• 128 GB for x86-based computers
• 1 TB for x64-based computers
|
Multiprocessor Support
|
Up to 4
|
Up to 8
|
• Minimum 8-way capable machine required
• Maximum 64
|
Disk Space for Setup
|
1.5 GB
|
• 1.5 GB for x86-based computers
• 2.0 GB for x64-based computers
|
• 1.5 GB for x86-based computers
• 2.0 GB for x64-based computers
| Getting Started with Windows Server 2003 R2
As described earlier, the Windows Server 2003 R2 operating system is comprised of two product installation CDs. The first installation CD contains Windows Server 2003 with SP1. The second installation CD contains the components specific to Windows Server 2003 R2. Both CDs use the same product key. You can install Windows Server 2003 R2 either locally from the product CDs, or from your network.
To start Setup for a new installation from the product CDs
Determine whether the computer on which you want to start Setup can be started from the CD-ROM drive and whether you want to perform a new installation (not an upgrade). Continue only if both are true.
Insert the first CD in the drive, and then restart the computer.
Follow the instructions in your computer's startup routine to start the computer from the CD.
Wait for Setup to display a dialog box, and then follow the Setup instructions.
Important
When you are prompted to enter the product key, enter the product key that comes with the Windows Server 2003 R2 installation CDs. Entering this product key now ensures that you will not be prompted to enter a product key again later, during installation of the second CD.
After you set up Windows Server 2003 with SP1, log on to the computer with your administrator password. You are then prompted to insert the second CD.
Follow the Setup instructions.
To start Setup for a new installation from the network
On a network server, create a shared resource called \\servername\share, where servername is the name of your server, and share is the name of the shared resource that you are creating.
Copy the i386 folder from the first CD to the shared resource.
Copy the folder named “Cmpnents” from the second CD to the shared resource.
Note
The shared resource now contains two folders: \\servername\share\i386 and \\servername\share\cmpnents.
On the computer on which you want to install Windows Server 2003 R2, connect to the shared folder that contains the Setup files. Navigate to the i386 folder and click winnt32.exe.
Wait for Setup to display a dialog box, and then follow the Setup instructions.
Important
When you are prompted to enter the product key, be sure to enter the product key that has been provided to you for Windows Server 2003 R2. By entering this product key, you will not be prompted to enter a product key again later, during the second half of the installation.
After Setup for Windows Server 2003 with SP1 is complete, log on to the computer with your administrator password. The second half of the installation for components specific to Windows Server 2003 R2 starts automatically.
Follow the Setup instructions.
Notes
When installing the operating system, if for some reason a product key that belongs to a different copy of Windows Server 2003 is entered, the operating system installation will complete successfully. However, when you log on to the computer for the first time after you install the operating system itself, installation of the components contained on the second CD, on which the components specific to Windows Server 2003 R2 are located, will not start automatically. You will need to insert the second CD or reconnect to the shared network resource that contains the Setup files, navigate to the \cmpnents\R2\ folder, and click setup2.exe in order to finish installation of Windows Server 2003 R2. Setup will prompt again for the End User License Agreement (EULA), and a product key. When this occurs, the product key provided for Windows Server 2003 R2 must be entered.
When the second CD is installed, Windows Server 2003 R2 resource files are simply loaded on the server in a location that will enable you to install them later, but the components themselves are not installed. After Windows Server 2003 R2 is set up, individual Windows Server 2003 R2 components can be installed using Add or Remove Programs, and selecting Manage Your Server (MYS)/Configure Your Server (CYS).
If the computer on which Windows Server 2003 R2 is installed is a domain controller but the Active Directory schema version is earlier than the Windows Server 2003 R2 schema version, the following error message will be displayed:
Setup cannot continue because the schema version of this domain controller is not compatible with Windows Server 2003 R2. Before you can install Windows Server 2003 R2, you must upgrade the schema version to Windows Server 2003 R2. Before you can successfully install Windows Server 2003 R2 on any of the Windows Server 2003 domain controllers in this forest, you must first upgrade the Active Directory schema. To upgrade the schema, on the schema operations master, run Adprep.exe /forestprep. The Adprep.exe command-line tool is available in the Cmpnents\r2\adprep directory on the Windows Server 2003 R2 installation CD. For a list of criteria for upgrading or for more information about extending the schema, see Help and Support.
If you receive this error message, you must upgrade the Active Directory schema before you can proceed.
|
