You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1141 lines
50 KiB
1141 lines
50 KiB
**********************************************************************
|
|
Windows Server 2003, Datacenter Edition
|
|
Setup Text Files, Part 2 of 4:
|
|
Running Setup and
|
|
Upgrading on Cluster Nodes
|
|
|
|
**********************************************************************
|
|
|
|
|
|
This part of the text file series provides recommendations for
|
|
preparing your system for a new installation or an upgrade, and it
|
|
explains how to run Setup for Microsoft Windows
|
|
Server 2003, Datacenter Edition.
|
|
|
|
Later sections in this text file provide information about upgrading
|
|
a server cluster to Windows Server 2003, Datacenter Edition. With
|
|
Windows Server 2003, Datacenter Edition, you can use clustering
|
|
to ensure that users have constant access to important server-based
|
|
resources. With clustering, you create several cluster nodes that
|
|
appear to users as one server. If one of the nodes in the cluster
|
|
fails, another node begins to provide service (a process known as
|
|
failover). Mission-critical applications and resources remain
|
|
continuously available.
|
|
|
|
For more information about the deployment of servers, see the
|
|
Microsoft Windows Server 2003 Deployment Kit. You can view the
|
|
Windows Deployment and Resource Kits on the Web at:
|
|
|
|
http://www.microsoft.com/reskit/
|
|
|
|
The following list of headings can help you find the information that
|
|
applies to you. For information about planning an upgrade or a new
|
|
installation, see Datactr1.TXT. For information about performing a new
|
|
installation on server cluster nodes, see Datactr4.TXT.
|
|
|
|
Sections in this text file about running Setup:
|
|
-----------------------------------------------
|
|
1.0 Preparing Your System Before Running Setup
|
|
2.0 Starting Setup on an x86-based Computer
|
|
3.0 Starting Setup on an Itanium Architecture-based Computer
|
|
4.0 Planning for Unattended Setup
|
|
5.0 Entering Server Settings for a New Installation
|
|
6.0 Product Activation for Products in the
|
|
Windows Server 2003 Family
|
|
|
|
Sections in this text file about upgrading on cluster nodes:
|
|
------------------------------------------------------------
|
|
7.0 Preparing for Upgrading Clustering
|
|
8.0 Upgrading a Cluster from Windows 2000 to
|
|
Windows Server 2003, Datacenter Edition
|
|
8.1 How Rolling Upgrades Work
|
|
|
|
Sections in Datactr3.TXT about upgrading on cluster nodes:
|
|
----------------------------------------------------------
|
|
Section 8 cont'd.
|
|
8.2 Restrictions on Rolling Upgrades
|
|
8.3 Resource Behavior During Rolling Upgrades
|
|
8.4 Alternatives to Rolling Upgrades from Windows 2000
|
|
|
|
|
|
======================================================================
|
|
1.0 PREPARING YOUR SYSTEM BEFORE RUNNING SETUP
|
|
======================================================================
|
|
|
|
|
|
This section describes the basic steps to take in preparing your
|
|
server before running Setup.
|
|
|
|
If you are installing Windows Server 2003, Datacenter Edition,
|
|
on server cluster nodes, be sure to read Datactr4.TXT.
|
|
|
|
----------------------------------------
|
|
1.1 Checking the System Log for Errors
|
|
----------------------------------------
|
|
If the computer already has a working operating system, review the
|
|
system log for recent or recurring errors (especially hardware errors)
|
|
that could cause problems during the installation. For information
|
|
about viewing event logs, see Help for the operating system on
|
|
your computer.
|
|
|
|
----------------------
|
|
1.2 Backing Up Files
|
|
----------------------
|
|
Before you run Setup, it is recommended that you back up your current
|
|
files, unless the computer has no files or the current operating
|
|
system files have been damaged. You can back up files to a variety of
|
|
different media, such as a tape drive or the hard disk of another
|
|
computer on the network.
|
|
|
|
-------------------------------
|
|
1.3 Disconnecting UPS Devices
|
|
-------------------------------
|
|
If you have an uninterruptible power supply (UPS) connected to your
|
|
target computer, disconnect the connecting serial cable before running
|
|
Setup. Setup automatically attempts to detect devices connected to
|
|
serial ports, and UPS equipment can cause problems with the detection
|
|
process.
|
|
|
|
|
|
======================================================================
|
|
2.0 STARTING SETUP ON AN X86-BASED COMPUTER
|
|
======================================================================
|
|
|
|
|
|
This section explains how to start Setup for a new installation on an
|
|
x86-based computer. For an explanation of how to start Setup on an
|
|
Itanium architecture-based computer, see "Starting Setup on an Itanium
|
|
Architecture-based Computer" later in this text file.
|
|
|
|
Setup works in several stages, prompting you for information, copying
|
|
files, and restarting.
|
|
|
|
For important information to help you make the initial choices
|
|
offered by Setup, see Datactr1.TXT. For information about unattended
|
|
Setup and other options available when you start Setup, see "Planning
|
|
for Unattended Setup" later in this text file.
|
|
|
|
---------------------------------------------------
|
|
2.1 Providing a Mass Storage Driver or a HAL File
|
|
---------------------------------------------------
|
|
If you have a mass storage controller that requires a driver supplied
|
|
by the manufacturer, or if you have a custom Hardware Abstraction
|
|
Layer (HAL) file supplied by the manufacturer, provide the appropriate
|
|
driver file or HAL file during Setup.
|
|
|
|
2.1.1 Mass Storage Drivers and the Setup Process
|
|
-------------------------------------------------
|
|
If you have a mass storage controller (such as a SCSI, RAID, or Fibre
|
|
Channel adapter) for your hard disk, confirm that the controller is
|
|
designed for products in the Windows Server 2003 family by
|
|
checking the hardware and software compatibility information in the
|
|
Windows Catalog at:
|
|
|
|
http://www.microsoft.com/windows/catalog/
|
|
|
|
If your controller is compatible, but you are aware that the
|
|
manufacturer has supplied a separate driver file for use with products
|
|
in the Windows Server 2003 family, obtain the file (on a floppy
|
|
disk) before you begin Setup. During the early part of Setup, a line
|
|
at the bottom of the screen prompts you to press F6. Further prompts
|
|
will guide you in supplying the driver file to Setup so that it can
|
|
gain access to the mass storage controller.
|
|
|
|
If you are not sure whether you must obtain a separate driver file
|
|
from the manufacturer of your mass storage controller, you can try
|
|
running Setup. If the controller is not supported by the driver files
|
|
on the Setup CD and therefore requires a driver file that is supplied
|
|
by the hardware manufacturer, Setup stops and displays a message
|
|
saying that no disk devices can be found, or it displays an incomplete
|
|
list of controllers. After you obtain the necessary driver file,
|
|
restart Setup, and press F6 when you are prompted.
|
|
|
|
2.1.2 Using a Custom HAL File
|
|
------------------------------
|
|
If you have a custom Hardware Abstraction Layer (HAL) file supplied
|
|
by your computer manufacturer, before you begin Setup, locate the
|
|
floppy disk or other medium containing the file. During the early part
|
|
of Setup, a line at the bottom of the screen prompts you to press F6:
|
|
at this time press F5 (not F6). After you press F5, follow the prompts
|
|
to include your HAL file in the Setup process.
|
|
|
|
---------------------------------------------------------------------
|
|
2.2 Starting Setup for a New Installation on an x86-based Computer
|
|
---------------------------------------------------------------------
|
|
This section explains how to start Setup for a new installation on an
|
|
x86-based computer. For an explanation of how to start Setup for an
|
|
upgrade, see "Starting Setup for an Upgrade" later in this text file.
|
|
For an explanation of how to start Setup on an Itanium
|
|
architecture-based computer, see "Starting Setup on an Itanium
|
|
Architecture-based Computer" later in this text file.
|
|
|
|
For information about unattended Setup and other options available
|
|
when you start Setup, see "Planning for Unattended Setup" later in
|
|
this text file.
|
|
|
|
2.2.1 Starting a New Installation from a CD
|
|
--------------------------------------------
|
|
If you use the Setup CD, you have several options for starting Setup,
|
|
as explained in the following procedures.
|
|
|
|
Note: If you are running Setup on a computer running
|
|
Microsoft Windows 3.x or MS-DOS, for best efficiency, use disk
|
|
caching. Otherwise, the Setup process (started from Winnt.exe)
|
|
could take a long time. To enable disk caching on a computer
|
|
running Windows 3.x or MS-DOS, you can use SMARTDrive. For
|
|
information about SMARTDrive, see the documentation for
|
|
Windows 3.x or MS-DOS.
|
|
|
|
>>>TO START SETUP FROM THE CD ON A COMPUTER RUNNING MS-DOS
|
|
|
|
1. Insert the CD in the drive.
|
|
|
|
2. At the command prompt, type:
|
|
|
|
d:
|
|
|
|
where d is the drive letter of the CD-ROM drive.
|
|
|
|
3. Type:
|
|
|
|
cd i386
|
|
|
|
4. Type:
|
|
|
|
winnt
|
|
|
|
5. Follow the Setup instructions.
|
|
|
|
>>>TO START SETUP FROM THE CD ON A COMPUTER RUNNING WINDOWS
|
|
|
|
Before starting this procedure on a computer running
|
|
Microsoft Windows NT 4.0, apply Service Pack 5 or later.
|
|
|
|
1. Insert the CD in the drive.
|
|
|
|
2. To begin Setup, do one of the following:
|
|
|
|
* For a computer running any version of Windows other than
|
|
Windows 3.x, wait for Setup to display a dialog box.
|
|
|
|
* For a computer running Windows 3.x, use File Manager to change
|
|
to the CD-ROM drive and to change to the I386 directory, and
|
|
then double-click Winnt.exe.
|
|
|
|
3. Follow the Setup instructions.
|
|
|
|
>>>TO START SETUP FOR A NEW INSTALLATION FROM THE CD ON AN X86-BASED
|
|
COMPUTER
|
|
|
|
Another way of using the Setup CD is to start the computer from
|
|
the CD-ROM drive. This method applies only if you want to perform a
|
|
new installation, not an upgrade. Using this method, you can perform
|
|
an installation on a computer that does not have an operating system,
|
|
although you can also use this method on computers that have operating
|
|
systems.
|
|
|
|
1. 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.
|
|
|
|
2. Insert the CD in the drive, and then restart the computer.
|
|
|
|
3. Follow the instructions for your operating system to boot the
|
|
computer from the CD.
|
|
|
|
4. Wait for Setup to display a dialog box, and then follow the
|
|
Setup instructions.
|
|
|
|
2.2.2 Starting a New Installation from a Network
|
|
-------------------------------------------------
|
|
To install Windows Server 2003, Datacenter Edition, from a
|
|
network, you either share the files directly from the CD or copy them
|
|
to a shared folder. Then, you start the appropriate program to
|
|
run Setup.
|
|
|
|
>>>TO INSTALL WINDOWS SERVER 2003, DATACENTER EDITION, FROM A
|
|
NETWORK (X86-BASED COMPUTERS ONLY)
|
|
|
|
1. On a network server, share the installation files, either by
|
|
inserting the CD and sharing the CD-ROM drive or by copying the
|
|
files from the I386 folder on the CD to a shared folder.
|
|
|
|
2. On the computer on which you want to install Windows Server
|
|
2003, Datacenter Edition, connect to the shared Setup files:
|
|
|
|
* If you are sharing the CD-ROM drive, connect to the shared
|
|
drive and change to the I386 folder.
|
|
|
|
* If you are sharing a folder, connect to that folder.
|
|
|
|
3. Find and run the appropriate file in the I386 directory of the
|
|
CD or in the shared folder:
|
|
|
|
* From a computer running MS-DOS or Windows 3.x, run Winnt.exe.
|
|
|
|
* From a computer running Microsoft Windows 95, Windows 98,
|
|
Windows Millennium Edition, Windows NT with Service Pack 5 or
|
|
later, Windows 2000, or Windows XP, run Winnt32.exe.
|
|
|
|
4. Follow the Setup instructions.
|
|
|
|
======================================================================
|
|
3.0 STARTING SETUP FOR AN UPGRADE
|
|
======================================================================
|
|
|
|
|
|
If you are upgrading to Windows Server 2003, Datacenter Edition,
|
|
you can start Setup from the CD or from a network.
|
|
|
|
For information about providing a mass storage driver or a Hardware
|
|
Abstraction Layer (HAL) file during Setup, see "Providing a Mass
|
|
Storage Driver or a HAL File" earlier in this text file.
|
|
|
|
IMPORTANT: To run Setup for an upgrade, you must be a member of the
|
|
Administrators group on the local computer. If the computer is joined
|
|
to a domain, members of the Domain Admins group might be able to
|
|
perform this procedure. As a security best practice, if you start
|
|
Setup from a computer running Windows 2000, consider using Run as.
|
|
|
|
Run as is a secondary logon method that you can use to start commands
|
|
or programs using a different security context. For example, you can
|
|
log on as a member of the Users group and, without logging off, run a
|
|
command as a member of the Administrators group. To find more
|
|
information in Windows 2000 about Run as, on a server running
|
|
Windows 2000, click Start, click Help, click the Search tab, and then
|
|
search for "runas."
|
|
|
|
>>>TO START AN UPGRADE FROM THE CD ON A COMPUTER RUNNING WINDOWS
|
|
|
|
1. Insert the CD in the drive, and wait for Setup to display a
|
|
dialog box.
|
|
|
|
2. Follow the Setup instructions.
|
|
|
|
>>> TO START AN UPGRADE FROM A NETWORK
|
|
|
|
1. On a network server, share the installation files by either
|
|
inserting the CD and sharing the CD-ROM drive or by copying
|
|
the files from the I386 folder on the CD to a shared folder.
|
|
|
|
2. On the computer on which you want to install Windows
|
|
Server 2003, Datacenter Edition, connect to the shared
|
|
folder or drive that contains the Setup files.
|
|
|
|
3. Run Setup.exe.
|
|
|
|
4. Follow the Setup instructions.
|
|
|
|
|
|
======================================================================
|
|
4.0 STARTING SETUP ON AN ITANIUM ARCHITECTURE-BASED COMPUTER
|
|
======================================================================
|
|
|
|
|
|
This section explains how to start Setup for a new installation on an
|
|
Itanium architecture-based computer. For an explanation of how
|
|
to start Setup on an x86-based computer, see "Starting Setup on
|
|
an x86-based Computer" earlier in this text file.
|
|
|
|
In computers with the Itanium processor or the Itanium 2 processor,
|
|
the Extensible Firmware Interface (EFI) is the interface between a
|
|
computer's firmware, hardware, and operating system. The EFI defines a
|
|
new disk partition style called a GUID partition table (GPT), which is
|
|
available only for Itanium architecture-based computers. The
|
|
installation partition on an Itanium architecture-based computer must
|
|
be on a GPT disk. Setup automatically specifies GPT for the disk used
|
|
for installation. You can still read and write to master boot record
|
|
(MBR) volumes, which are common to most PCs, but you cannot install
|
|
on one.
|
|
|
|
You cannot access GPT disks locally from an x86-based computer. If
|
|
you want to move a disk from an Itanium architecture-based computer to
|
|
an x86-based computer, use an MBR disk. This is true regardless of
|
|
whether the disk is basic or dynamic.
|
|
|
|
Before installing, verify that you are using the correct version of
|
|
the firmware. For more information, refer to the hardware
|
|
manufacturer's documentation.
|
|
|
|
IMPORTANT: Itanium architecture-based computers require a
|
|
minimum 100-MB FAT partition for the operation of the EFI. This
|
|
EFI system partition is created automatically during Setup, and it
|
|
stores programs and information files that the EFI uses to start
|
|
the operating system. Do not delete or reformat this partition.
|
|
|
|
Setup also creates a Microsoft Reserved Partition (MSR), which is
|
|
required by the operating system. The size of this partition depends
|
|
on the size of the hard disk. On drives less than 16 GB in size, the
|
|
MSR is 32 MB. On drives greater than or equal to 16 GB, the MSR is
|
|
128 MB. Do not delete or reformat this partition.
|
|
|
|
>>>TO START SETUP ON AN ITANIUM ARCHITECTURE-BASED COMPUTER
|
|
|
|
1. Immediately after turning on the computer, insert the Setup CD
|
|
in the CD-ROM drive.
|
|
|
|
2. When the EFI Boot Manager menu appears, select the CD-ROM
|
|
option.
|
|
|
|
3. When prompted, press any key to start from the CD-ROM.
|
|
|
|
4. Follow the on-screen Setup instructions.
|
|
|
|
|
|
======================================================================
|
|
5.0 PLANNING FOR UNATTENDED SETUP
|
|
======================================================================
|
|
|
|
|
|
This section provides general information about unattended Setup. For
|
|
detailed instructions on running unattended Setup (also called
|
|
automated installation), see "Automating and Customizing
|
|
Installations" in the Windows Server 2003 Deployment Kit. You can
|
|
view the Windows Deployment and Resource Kits on the Web at:
|
|
|
|
http://www.microsoft.com/reskit/
|
|
|
|
To simplify the process of setting up a product in the Windows
|
|
Server 2003 family on multiple computers, you can run Setup
|
|
unattended. To do this, you create and use an answer file, a
|
|
customized script that answers the Setup questions automatically.
|
|
Then, you run Winnt32.exe or Winnt.exe with the appropriate options
|
|
for unattended Setup. Choose the command according to the operating
|
|
system that is running when you start unattended Setup:
|
|
|
|
* To start unattended Setup on a computer running MS-DOS or
|
|
Windows 3.x, use Winnt.exe (with the appropriate options).
|
|
|
|
* To start unattended Setup on a computer running Windows 95,
|
|
Windows 98, Windows Millennium Edition, Windows NT, Windows
|
|
2000, Windows XP, or a product in the Windows Server 2003
|
|
family, use Winnt32.exe (with the appropriate options). With
|
|
Windows NT 4.0, before starting unattended Setup, apply Service
|
|
Pack 5 or later.
|
|
|
|
To learn about unattended Setup, see the following sources:
|
|
|
|
* For detailed instructions on running unattended Setup (also
|
|
called automated installation), see "Automating and Customizing
|
|
Installations" in the Windows Server 2003 Deployment Kit
|
|
(described in the first paragraph of this section).
|
|
|
|
* To view the command options available for Winnt.exe: On a
|
|
computer running Windows 3.x or MS-DOS, insert the Setup CD
|
|
for Windows Server 2003, Datacenter Edition, in the CD-ROM
|
|
drive and open the command prompt. Then, change to the CD-ROM
|
|
drive, change to the I386 directory, and type:
|
|
|
|
winnt /?
|
|
|
|
* To use an x86-based computer to view the command options
|
|
available for Winnt32.exe: On a computer running Windows 95,
|
|
Windows 98, Windows Millennium Edition, Windows NT,
|
|
Windows 2000, Windows XP, or a product in the Windows
|
|
Server 2003 family, insert the Setup CD for Windows
|
|
Server 2003, Datacenter Edition, in the CD-ROM drive, and open
|
|
the command prompt. Then, change to the CD-ROM drive, change to
|
|
the I386 directory, and type:
|
|
|
|
winnt32 /?
|
|
|
|
* To use an Itanium architecture-based computer to view the command
|
|
options available for Winnt32.exe: On an Itanium
|
|
architecture-based computer running Windows XP 64-Bit Edition;
|
|
the 64-bit version of Windows Server 2003,
|
|
Enterprise Edition; or the 64-bit version of
|
|
Windows Server 2003, Datacenter Edition, insert the Setup CD
|
|
for the 64-bit version of the product in the CD-ROM drive and
|
|
open the command prompt (click Start, click Run, and then type
|
|
cmd). Then, change to the CD-ROM drive, change to the IA64
|
|
directory, and type:
|
|
|
|
winnt32 /?
|
|
|
|
|
|
======================================================================
|
|
6.0 ENTERING SERVER SETTINGS FOR A NEW INSTALLATION
|
|
======================================================================
|
|
|
|
|
|
If you are upgrading, you can skip this section because Setup will
|
|
use your previous settings.
|
|
|
|
After you start Setup, a process begins in which necessary Setup
|
|
files are copied to the hard disk. During this process, Setup displays
|
|
dialog boxes that you can use to select various options.
|
|
|
|
The following sections outline the items that you specify as you run
|
|
Setup. Before working with these sections, see Datactr1.TXT for
|
|
important background information about issues such as partitions, file
|
|
system choices, and the handling of TCP/IP name resolution.
|
|
|
|
Note: If you have a mass storage controller (such as a SCSI, RAID,
|
|
or Fibre Channel adapter) for your hard disk, see "Providing a Mass
|
|
Storage Driver or a HAL File" earlier in this text file.
|
|
|
|
If you have specialized hardware that requires a custom Hardware
|
|
Abstraction Layer (HAL) file supplied by your computer manufacturer,
|
|
see "Using a Custom HAL File" earlier in this text file.
|
|
|
|
|
|
Choosing or Creating a Partition for Windows Server 2003,
|
|
Datacenter Edition
|
|
--------------------------------------------------------------
|
|
During a new installation of Windows Server 2003, Datacenter
|
|
Edition, a dialog box gives you the opportunity to create or specify a
|
|
partition on which you want to install. You can create a partition
|
|
from the available unpartitioned space, specify an existing partition,
|
|
or delete an existing partition to create more unpartitioned disk
|
|
space for the new installation. If you specify any action that will
|
|
cause information to be erased, you will be prompted to confirm
|
|
your choice.
|
|
|
|
For more information, see "Planning Disk Partitions or Volumes for
|
|
New Installations" in Datactr1.TXT.
|
|
|
|
IMPORTANT: If you delete an existing partition, all data on that
|
|
partition is erased.
|
|
|
|
Performing a new installation of Windows Server 2003,
|
|
Datacenter Edition, on a partition that contains another operating
|
|
system overwrites the existing operating system.
|
|
|
|
|
|
Selecting Regional and Language Options
|
|
---------------------------------------
|
|
You can set up Windows Server 2003, Datacenter Edition, to use
|
|
multiple languages and regional options.
|
|
|
|
If you select a European country or region in the list of
|
|
countries/regions, or if you live in a country or region where the
|
|
euro has been introduced, it is a good idea to verify that the default
|
|
currency settings in Regional and Language Options meet your needs.
|
|
After you run Setup, you can modify these options by clicking
|
|
Regional and Language Options in Control Panel.
|
|
|
|
|
|
Personalizing Windows
|
|
---------------------
|
|
Enter your name and, as an option, your organization.
|
|
|
|
If you select a European country or region in the list of
|
|
countries/regions, or if you live in a country or region where the
|
|
euro has been introduced, it is a good idea to verify that the default
|
|
currency settings in Regional and Language Options meet your needs.
|
|
After you run Setup, you can modify regional and language options by
|
|
clicking Regional and Language Options in Control Panel.
|
|
|
|
|
|
Choosing a Licensing Mode
|
|
-------------------------
|
|
Select your client licensing mode. For information about licensing
|
|
modes, see Datactr1.TXT. If you are unsure which mode to use,
|
|
select "Per Server," because you can change once from "Per Server"
|
|
mode to "Per Device or Per User" mode at no cost.
|
|
|
|
|
|
Entering Your Computer Name
|
|
---------------------------
|
|
During Setup, in the Computer Name and Administrator Password dialog
|
|
box, follow the instructions for entering your computer name. The
|
|
recommended length for most languages is 15 characters or less. For
|
|
languages that require more storage space per character, such as
|
|
Chinese, Japanese, and Korean, the recommended length is 7 characters
|
|
or less.
|
|
|
|
It is recommended that you use only Internet-standard characters in
|
|
the computer name. The standard characters are the numbers from 0
|
|
through 9, uppercase and lowercase letters from A through Z, and the
|
|
hyphen (-) character. Computer names cannot consist entirely
|
|
of numbers.
|
|
|
|
If you are using DNS on your network, you can use a wider variety of
|
|
characters, including Unicode characters and other nonstandard
|
|
characters, such as the ampersand (&). Using nonstandard characters
|
|
might affect the ability of non-Microsoft software to operate on your
|
|
network. For more information about DNS, see "Name
|
|
Resolution for TCP/IP" in Datactr1.TXT.
|
|
|
|
The maximum length for a computer name is 63 bytes. If the name is
|
|
longer than 15 bytes (15 characters in most languages, 7 characters in
|
|
some), computers running Windows NT Server 4.0 and earlier will
|
|
recognize this computer by the first 15 bytes of the name only. In
|
|
addition, there are additional configuration steps for a name that is
|
|
longer than 15 bytes. For more information, in Help and Support
|
|
Center, see "Namespace planning for DNS." To view Help and Support
|
|
Center, after running Setup, click Start, and then click Help
|
|
and Support.
|
|
|
|
If a computer is part of a domain, you must choose a computer name
|
|
that is different from any other computer in the domain. To avoid name
|
|
conflicts, the computer should be unique on the domain, workgroup, or
|
|
network. If this computer is part of a domain, and it contains more
|
|
than one operating system, you must use a unique computer name for
|
|
each operating system that is installed. For example, if the computer
|
|
name is FileServerNT when the computer is started with Windows NT
|
|
Server 4.0, the computer must have a different name, perhaps
|
|
FileServerNew, when it is started with a product in the Windows
|
|
Server 2003 family. This requirement also applies to a computer that
|
|
contains multiple installations of the same operating system. For more
|
|
information, in Help and Support Center, see "Planning your domain
|
|
structure."
|
|
|
|
|
|
Setting the Administrator Account Password
|
|
-------------------------------------------
|
|
During Setup, in the Computer Name and Administrator Password dialog
|
|
box, type a password of up to 127 characters in the Administrator
|
|
Password box. For the strongest system security, use a password of at
|
|
least 7 characters, and use a mixture of uppercase and lowercase
|
|
letters, numbers, and other characters, such as *, ?, or $.
|
|
|
|
IMPORTANT: After Setup is completed, for best security, change the
|
|
name of the Administrator account (it cannot be deleted) and keep
|
|
a strong password on the account at all times. For more information
|
|
about security and the administrative rights and permissions held
|
|
by the Administrator account and the Administrators group, see Help
|
|
and Support Center. You can view Help and Support Center after
|
|
Setup is complete by clicking Start, and then clicking Help
|
|
and Support.
|
|
|
|
|
|
Setting the Date and Time
|
|
-------------------------
|
|
During Setup, in the Date and Time Settings dialog box, set the date,
|
|
time, and time zone. If you want the system to automatically adjust
|
|
for daylight saving time, select the "Automatically adjust clock for
|
|
daylight saving changes" check box.
|
|
|
|
You can change your computer's date and time after Setup is complete.
|
|
If your computer is a member of a domain, your computer clock is
|
|
probably synchronized automatically by a network time server. If your
|
|
computer is not a member of a domain, you can synchronize your
|
|
computer clock with an Internet time server.
|
|
|
|
|
|
Specifying Networking Settings
|
|
------------------------------
|
|
You can specify networking information for TCP/IP or other protocols
|
|
during Setup, or you can use typical settings and then make any
|
|
necessary changes to your networking configuration after installation.
|
|
|
|
For basic background information about TCP/IP configuration and
|
|
Setup, see "Networks: TCP/IP, IP Addresses, and Name Resolution" in
|
|
Datactr1.TXT. For additional information about TCP/IP configuration,
|
|
see Help and Support Center as well as the Windows Deployment and
|
|
Resource Kits for the Windows Server 2003 family. To open Help
|
|
and Support Center, after completing Setup, click Start, and then
|
|
click Help and Support.
|
|
|
|
>>>TO ALLOW SETUP TO ASSIGN OR OBTAIN AN IP ADDRESS
|
|
|
|
* When you click "Typical settings" in the Networking Settings
|
|
dialog box, Setup checks to see if there is a DHCP server on
|
|
your network. If there is a DHCP server on your network, DHCP
|
|
provides an IP address. If there is no DHCP server on your
|
|
network, Setup will use a limited IP addressing option called
|
|
Automatic Private IP Addressing (APIPA). On a server using
|
|
APIPA, complete the network configuration after Setup, because
|
|
a server using APIPA can communicate only with other computers
|
|
using APIPA on the same network segment.
|
|
|
|
For basic background information about IP address configuration,
|
|
including additional information about the limitations of
|
|
APIPA, see "IP Addresses" in Datactr1.TXT.
|
|
|
|
>>>TO SPECIFY A STATIC IP ADDRESS AND SETTINGS NEEDED FOR DNS AND WINS
|
|
|
|
1. During Setup, in the Networking Settings dialog box, click
|
|
"Custom settings," and then click Next.
|
|
|
|
2. In the Networking Components dialog box, click Internet
|
|
Protocol (TCP/IP).
|
|
|
|
3. Click Properties.
|
|
|
|
4. In the Internet Protocol (TCP/IP) Properties dialog box, click
|
|
"Use the following IP address."
|
|
|
|
5. In IP address, Subnet mask, and Default gateway, type the
|
|
appropriate addresses.
|
|
|
|
6. Under "Use the following DNS server addresses," type the
|
|
address of a preferred DNS server and, optionally, an alternate
|
|
DNS server.
|
|
|
|
If the local server is the preferred or alternate DNS server,
|
|
type the same IP address as assigned in the previous step.
|
|
|
|
7. If you will use a WINS server, click Advanced, and then click
|
|
the WINS tab in the Advanced TCP/IP Settings dialog box to add
|
|
the IP address of one or more WINS servers.
|
|
|
|
8. Click OK in each dialog box, and continue with Setup.
|
|
|
|
|
|
Specifying the Workgroup or Domain Name
|
|
---------------------------------------
|
|
A domain is a group of accounts and network resources that share a
|
|
common directory database and set of security policies and might have
|
|
security relationships with other domains. A workgroup is a more basic
|
|
grouping, intended only to help users find objects such as printers
|
|
and shared folders within that group. Domains make it easier for an
|
|
administrator to control access to resources and keep track of users.
|
|
For more information, see "Deciding Between Workgroups and Domains"
|
|
in Datactr1.TXT.
|
|
|
|
For more information about name conflicts, see "Entering Your
|
|
Computer Name" earlier in this text file.
|
|
|
|
|
|
Choosing Server Components
|
|
--------------------------
|
|
You can use the Windows Components Wizard to select the appropriate
|
|
components for your server. To use this wizard, after running Setup,
|
|
click Start, and then click Control Panel. In Control Panel,
|
|
double-click Add or Remove Programs, and then, on the left side of the
|
|
dialog box, click Add/Remove Windows Components. With this wizard you
|
|
can choose and install individual components.
|
|
|
|
|
|
======================================================================
|
|
6.0 PRODUCT ACTIVATION FOR PRODUCTS IN THE WINDOWS
|
|
SERVER 2003 FAMILY
|
|
======================================================================
|
|
|
|
|
|
After you install a product in the Windows Server 2003 family,
|
|
if the product was purchased individually rather than through a volume
|
|
licensing arrangement, you will have to activate the product unless
|
|
your hardware manufacturer has preactivated it for you. Product
|
|
activation is quick, simple, and unobtrusive, and it protects your
|
|
privacy. It is designed to reduce software piracy (illegal copies of a
|
|
product). Over time, reduced piracy means that the software industry
|
|
can invest more in product development, quality, and support. This
|
|
results in better products and more innovation for customers.
|
|
|
|
The following details help explain product activation:
|
|
|
|
|
|
Software reminders
|
|
------------------
|
|
Until you activate your product, it provides a reminder each time you
|
|
log on and at common intervals until the end of the activation grace
|
|
period stated in your End-User License Agreement (30 days is the
|
|
typical grace period). If your activation grace period passes and you
|
|
do not activate the product, your computer will continue to function,
|
|
except that when you log on locally or log on through Remote Desktop
|
|
for Administration (the new name for the Windows 2000 functionality
|
|
known as Terminal Services in Remote Administration Mode), you will
|
|
only be able to use the Activate Windows Wizard.
|
|
|
|
|
|
How the software handles activation
|
|
-----------------------------------
|
|
Activation is simple and anonymous. When you activate your product,
|
|
it means that your product key is now associated with the computer
|
|
(the hardware) it is installed on. After that happens, your product
|
|
key cannot be used for activation on other computers (unless you are
|
|
enrolled in a special program that permits additional activations, for
|
|
example, a program through the Microsoft Developer Network (MSDN)).
|
|
|
|
Your local operating system does some of the work of creating the
|
|
association between your product key and the computer it is installed
|
|
on. It uses your Product ID, which is derived from your product key,
|
|
and puts it together with a coded number (called a hardware hash) that
|
|
uniquely represents the hardware components that make up your computer
|
|
(without representing any personal information or anything about the
|
|
software). When you activate, you provide this number, through the
|
|
Internet or by phone, so that it can be confirmed as representing a
|
|
legal installation. After you activate, if another person has an
|
|
illegal copy of your software, and that person tries to use your
|
|
product key to activate the software on another computer, the coded
|
|
numbers will show that your product key is already associated with a
|
|
particular set of hardware (your computer). The other person's
|
|
activation will not work.
|
|
|
|
The Installation ID that the local operating system generates,
|
|
representing the association between your product key and the computer
|
|
it is installed on, is used only for the purpose of activation.
|
|
|
|
|
|
Methods for activation
|
|
----------------------
|
|
After your operating system is installed, begin activation by
|
|
clicking Start, and then clicking Activate Windows. (You can also
|
|
click the key icon that appears in the lower right corner of the
|
|
screen.) By following the instructions on the screen, you can activate
|
|
through the Internet or by phone:
|
|
|
|
* Internet: When you activate through the Internet, your computer
|
|
transmits coded information that shows that your product key
|
|
is associated with your computer hardware. Activation is
|
|
carried out through a secure server. A confirmation ID is
|
|
passed back to your computer, automatically activating your
|
|
product. This process normally takes just a few seconds to
|
|
complete. No personally identifiable information is required
|
|
to activate your product.
|
|
|
|
* Phone: When you activate by phone, information on the screen
|
|
guides you through a few simple steps. When you choose the
|
|
country or region where you are located, a phone number
|
|
(toll-free, wherever possible) is displayed on your screen. When
|
|
you call the number, a customer service representative asks for
|
|
the Installation ID that is displayed on your screen. The
|
|
customer service representative enters that number into a secure
|
|
database, confirms that the number represents a legally
|
|
installed product, and provides a confirmation ID to you. Then,
|
|
you type the confirmation ID into the spaces provided on the
|
|
screen, and activation is complete.
|
|
|
|
|
|
Reactivation (rarely needed)
|
|
----------------------------
|
|
If you overhaul your computer by replacing a substantial number of
|
|
hardware components (not just a few), the operating system might view
|
|
your hardware as a completely different computer, not the one on which
|
|
you activated. In this situation, you can call the telephone number
|
|
displayed on the telephone activation screen, and, through a quick,
|
|
simple process, you can reactivate your product.
|
|
|
|
|
|
---------------------------------------------------------
|
|
6.1 Product Activation Compared to Product Registration
|
|
---------------------------------------------------------
|
|
Product activation is not the same as product registration. As
|
|
discussed above, product activation is required, and it is completely
|
|
anonymous. Product registration, in contrast, is completely optional,
|
|
and it allows you to provide personal information, such as your e-mail
|
|
address, if you choose. Registration entitles you to receive
|
|
information about product updates and special offers directly from
|
|
Microsoft. All registration information provided is stored securely,
|
|
and no information is ever loaned or sold to other parties.
|
|
|
|
|
|
======================================================================
|
|
7.0 PREPARING FOR UPGRADING CLUSTERING
|
|
======================================================================
|
|
|
|
|
|
The following sections provide information on the initial steps
|
|
needed for upgrading clustering:
|
|
|
|
* Understanding the basic preparations needed.
|
|
|
|
* Confirming your hardware compatibility with Windows
|
|
Server 2003, Datacenter Edition.
|
|
|
|
* Choosing from the available options for upgrading.
|
|
|
|
|
|
----------------------------------
|
|
7.1 Other Sources of Information
|
|
----------------------------------
|
|
Following are sources of additional information on server clusters
|
|
and other topics related to high availability:
|
|
|
|
* For more information on server clusters, you can view Help and
|
|
Support Center topics for Windows Server 2003, Datacenter
|
|
Edition, on the Web. One way to view this information is to
|
|
work from any computer that has Internet access (regardless
|
|
of the operating system running on that computer). You can view
|
|
Help and Support Center topics at:
|
|
|
|
http://www.microsoft.com/windowsserver2003/proddoc/
|
|
|
|
Another way to view this information is to open Help and Support
|
|
Center. To do this, go to a computer running Windows
|
|
Server 2003, Enterprise Edition, or Windows Server 2003,
|
|
Datacenter Edition, click Start, and then click Help
|
|
and Support.
|
|
|
|
* For more information about deployment and management of servers
|
|
and server clusters, see the Windows Deployment and Resource Kits
|
|
on the Web at:
|
|
|
|
http://www.microsoft.com/reskit/
|
|
|
|
* For information about backup and recovery planning, change
|
|
management, configuration management, and other concepts
|
|
related to operational best practices, see resources in the
|
|
Information Technology Infrastructure Library (ITIL). To see
|
|
a description of ITIL, go to:
|
|
|
|
http://www.itil.co.uk/
|
|
|
|
Note: Web addresses can change, so you might be unable to
|
|
connect to the Web site mentioned here.
|
|
|
|
|
|
----------------------------
|
|
7.2 Hardware Compatibility
|
|
----------------------------
|
|
Ensure that your entire cluster solution (including your drivers as
|
|
well as your hardware) is compatible with products in the
|
|
Windows Server 2003 family by checking the hardware compatibility
|
|
information in the Windows Catalog at:
|
|
|
|
http://www.microsoft.com/windows/catalog/
|
|
|
|
|
|
--------------------------------------
|
|
7.3 Options for Upgrading Clustering
|
|
--------------------------------------
|
|
You have several options when upgrading clustering. You can:
|
|
|
|
* Upgrade a cluster that is running Windows 2000,
|
|
possibly through a rolling upgrade. For more information, see
|
|
"Upgrading a Cluster from Windows 2000 to
|
|
Windows Server 2003, Datacenter Edition," later in this
|
|
text file.
|
|
|
|
* Perform a new installation of Windows Server 2003,
|
|
Datacenter Edition, and install the Cluster service at the same
|
|
time. For more information about this option, see "Installing
|
|
on Cluster Nodes" in Datactr4.TXT.
|
|
|
|
|
|
--------------------------------------------
|
|
7.4 Quorum Resource Options for an Upgrade
|
|
--------------------------------------------
|
|
With clusters running Windows Server 2003, Datacenter Edition,
|
|
you can choose between three ways to set up the quorum resource (the
|
|
resource that maintains the definitive copy of the cluster
|
|
configuration data and that must always be available for the cluster
|
|
to run). These options are:
|
|
|
|
* Single node server cluster
|
|
|
|
* Single quorum device server cluster
|
|
|
|
* Majority node set
|
|
|
|
Before upgrading, refer to "Quorum Resource Options" in Datactr4.TXT
|
|
to learn more about these options.
|
|
|
|
|
|
======================================================================
|
|
8.0 UPGRADING A CLUSTER FROM WINDOWS 2000 TO
|
|
WINDOWS SERVER 2003, DATACENTER EDITION
|
|
======================================================================
|
|
|
|
|
|
If you are upgrading from Windows 2000 to Windows Server 2003,
|
|
Datacenter Edition, on cluster nodes, you might be able to perform a
|
|
rolling upgrade of the operating system. In a rolling upgrade, you
|
|
sequentially upgrade the operating system on each node, making sure
|
|
that one node is always available to handle client requests. When you
|
|
upgrade the operating system, the Cluster service is automatically
|
|
upgraded also. A rolling upgrade maximizes availability of clustered
|
|
services and minimizes administrative complexity. For more
|
|
information, see the next section, "How Rolling Upgrades Work."
|
|
|
|
To determine whether you can perform a rolling upgrade, and
|
|
understand the effect that a rolling upgrade might have on your
|
|
clustered resources, see "Restrictions on Rolling Upgrades"
|
|
in Datactr3.TXT. For information about ways to upgrade your cluster
|
|
nodes if you cannot perform a rolling upgrade, see "Alternatives to
|
|
Rolling Upgrades from Windows 2000" in Datactr3.TXT.
|
|
|
|
|
|
-------------------------------
|
|
8.1 How Rolling Upgrades Work
|
|
-------------------------------
|
|
This section describes rolling upgrades on server clusters. For
|
|
information about methods, restrictions, and alternatives to rolling
|
|
upgrades, see the sections that follow this section.
|
|
|
|
There are two major advantages to a rolling upgrade. First, there is
|
|
a minimal interruption of service to clients. (However, server
|
|
response time might decrease during the phases in which a fewer number
|
|
of nodes handle the work of the entire cluster.) Second, you do not
|
|
have to recreate your cluster configuration. The configuration remains
|
|
intact during the upgrade process.
|
|
|
|
The four phases of a rolling upgrade are described in the
|
|
following section.
|
|
|
|
|
|
8.1.1 Phases of a Rolling Upgrade
|
|
----------------------------------
|
|
A rolling upgrade starts with two cluster nodes that are running
|
|
Windows 2000. In this example, they are named Node 1 and Node 2:
|
|
|
|
Phase 1: Preliminary
|
|
--------------------
|
|
Each node runs Windows 2000 Datacenter Server with the following
|
|
hardware and software:
|
|
|
|
* A cluster storage unit using Fibre Channel, not SCSI. Fibre
|
|
Channel is the only type of cluster storage on the list of
|
|
compatible hardware for Windows Server 2003, Datacenter
|
|
Edition. (Note that SCSI can be used for a two node cluster
|
|
with Windows Server 2003, Enterprise Edition, not
|
|
Windows Server 2003, Datacenter Edition.)
|
|
|
|
* The Cluster service component (one of the optional components of
|
|
Windows 2000 Datacenter Server).
|
|
|
|
* Applications that support a rolling upgrade. For more
|
|
information, see the application documentation, and "Resource
|
|
Behavior During Rolling Upgrades" in Datactr3.TXT.
|
|
|
|
At this point, your cluster is configured so that each node handles
|
|
client requests (an active/active configuration).
|
|
|
|
Phase 2: Upgrade Node 1
|
|
-----------------------
|
|
Node 1 is paused, and Node 2 handles all cluster resource groups
|
|
while you upgrade the operating system of Node 1 to Windows
|
|
Server 2003, Datacenter Edition.
|
|
|
|
You are now running a mixed-version cluster. A mixed-version cluster
|
|
is a cluster in which the nodes are running different versions of the
|
|
operating system. Although mixed-version clusters are supported by
|
|
Windows Server 2003, Datacenter Edition, they are not the optimal
|
|
configuration. It is recommended that you upgrade all nodes to the
|
|
same operating system by completing the final two phases of the
|
|
rolling upgrade.
|
|
|
|
When your cluster is in a mixed version state, it is recommended that
|
|
you do not make any changes to the cluster configuration, such as
|
|
adding or removing nodes. It is also recommended that you do not make
|
|
changes to any of the cluster resources while your cluster is in a
|
|
mixed version state.
|
|
|
|
Phase 3: Upgrade Node 2
|
|
-----------------------
|
|
Node 1 rejoins the cluster. Node 2 is paused and Node 1 handles all
|
|
cluster resource groups while you upgrade the operating system on
|
|
Node 2.
|
|
|
|
Phase 4: Final
|
|
--------------
|
|
Node 2 rejoins the cluster, and you redistribute the resource groups
|
|
back to the active/active cluster configuration.
|
|
|
|
IMPORTANT: If you plan to add nodes to the cluster, add them after
|
|
completing the rolling upgrade. Before adding additional nodes,
|
|
ensure that your entire cluster solution is compatible with
|
|
products in the Windows Server 2003 family.
|
|
|
|
For cluster disks, you must use the NTFS file system and configure
|
|
the disks as basic disks. You cannot configure cluster disks as
|
|
dynamic disks, and you cannot use features of dynamic disks such as
|
|
spanned volumes (volume sets).
|
|
|
|
|
|
8.1.2 Performing a Rolling Upgrade
|
|
-----------------------------------
|
|
For an outline of the rolling upgrade process, see the preceding
|
|
section "How Rolling Upgrades Work." To perform the following
|
|
procedure, you must be a member of the Administrators group on the
|
|
local computer, or you must have been delegated the appropriate
|
|
authority. If the computer is joined to a domain, members of the
|
|
Domain Admins group might be able to perform this procedure. As a
|
|
security best practice, consider using Run as to perform this
|
|
procedure. Run as is a secondary logon method that you can use to
|
|
start commands or programs using a different security context. For
|
|
example, you can log on as a member of the Users group and, without
|
|
logging off, run a command as a member of the Administrators group. To
|
|
find more information in Windows 2000 about Run as, on a server
|
|
running Windows 2000, click Start, click Help, click the Search tab
|
|
and then search for "runas."
|
|
|
|
IMPORTANT: For information about what resources are supported
|
|
during rolling upgrades, see "Restrictions on Rolling Upgrades"
|
|
and "Resource Behavior During Rolling Upgrades" in Datactr3.TXT.
|
|
|
|
>>>TO PERFORM A ROLLING UPGRADE FROM WINDOWS 2000
|
|
|
|
1. Confirm that your systems are running Windows 2000 and use
|
|
resources that are supported during a rolling upgrade, as
|
|
described in "Restrictions on Rolling Upgrades" and "Resource
|
|
Behavior During Rolling Upgrades" in Datactr3.TXT.
|
|
|
|
2. Confirm that your hardware is designed for or is compatible
|
|
with Windows Server 2003, Datacenter Edition.
|
|
|
|
3. In Cluster Administrator, click the node that you want to
|
|
upgrade first.
|
|
|
|
4. On the File menu, click Pause Node.
|
|
|
|
5. In the right pane, click Active Groups.
|
|
|
|
6. In the right pane, click a group, and then on the File menu,
|
|
click Move Group. Repeat this step for each group listed.
|
|
|
|
The services will be interrupted during the time they are being
|
|
moved and restarted on another node. After the groups are moved,
|
|
one node is idle, and the other nodes handle all
|
|
client requests.
|
|
|
|
7. Use Setup for Windows Server 2003, Datacenter Edition, to
|
|
upgrade the paused node from Windows 2000. (For information
|
|
about running Setup, see the sections on starting Setup, earlier
|
|
in this text file.)
|
|
|
|
Setup detects the earlier version of clustering on the paused
|
|
node and automatically installs clustering for
|
|
Windows Server 2003, Datacenter Edition. The node
|
|
automatically rejoins the cluster at the end of the upgrade
|
|
process, but is still paused and does not handle any
|
|
cluster-related work.
|
|
|
|
Note: As you begin the setup process, you will receive a
|
|
warning message about using the tempdrive option for Setup.
|
|
Provided you have followed the preceding steps, you can click
|
|
OK and proceed with Setup without using this option.
|
|
|
|
8. To verify that the node that was upgraded is fully functional,
|
|
perform validation tests such as confirming that the operating
|
|
system recognizes your network connections and, using Device
|
|
Manager, ensuring that the operating system recognizes all of
|
|
your storage devices.
|
|
|
|
9. In Cluster Administrator, click the node that was paused, and
|
|
then on the File menu click Resume Node.
|
|
|
|
Note: When you use Cluster Administrator for the first time
|
|
on the upgraded node, Cluster Administrator will prompt you
|
|
to "Open connection to cluster." In the "Cluster or server
|
|
name" field, type a period (.). This will connect you to the
|
|
cluster on the local upgraded node. Although you can connect
|
|
to the cluster by typing the cluster name, if you do so you
|
|
will be connected to the cluster on the Windows 2000 node and
|
|
then will be required to respond to several warning messages.
|
|
|
|
10. Repeat the preceding steps for the remaining nodes.
|
|
|
|
(additional Setup information in Datactr3.TXT)
|
|
|
|
|
|
Information in this document, including URL and other Internet
|
|
Web site references, is subject to change without notice.
|
|
Unless otherwise noted, the example companies, organizations,
|
|
products, domain names, e-mail addresses, logos, people, places
|
|
and events depicted herein are fictitious, and no association
|
|
with any real company, organization, product, domain name,
|
|
e-mail address, logo, person, place or event is intended or
|
|
should be inferred. Complying with all applicable copyright laws
|
|
is the responsibility of the user. Without limiting the rights
|
|
under copyright, no part of this document may be reproduced,
|
|
stored in or introduced into a retrieval system, or transmitted
|
|
in any form or by any means (electronic, mechanical, photocopying,
|
|
recording, or otherwise), or for any purpose, without the express
|
|
written permission of Microsoft Corporation.
|
|
|
|
Microsoft may have patents, patent applications, trademarks,
|
|
copyrights, or other intellectual property rights covering subject
|
|
matter in this document. Except as expressly provided in any
|
|
written license agreement from Microsoft, the furnishing of this
|
|
document does not give you any license to these patents, trademarks,
|
|
copyrights, or other intellectual property.
|
|
|
|
(c) 2002-2003 Microsoft Corporation. All rights reserved.
|
|
|
|
The names of actual companies and products mentioned herein may
|
|
be the trademarks of their respective owners.
|