La distribución de los hombres en función misma de las condiciones de la

You install Windows Server 2003 from a set of files on your installation CD, the files in the I386

directory. As with all installations, though, there’s the very important question, “How do I make my computer able to see, copy, and execute these files?” The size of I386 _{means that you can’t put the}

whole operating system on a floppy. (Those days are waaaay gone forever.) Instead, you’ll have to deliver the files to your computer in one of several ways:

◆ Put I386 _{on a bootable CD-ROM disc. This is how it ships from Microsoft. It’s easy to just}

boot the CD and follow the prompts, but this method won’t work for every system because some systems lack CDs, and some older systems have CD drives but cannot boot from them. Thankfully, this is not a very common problem, but it does pop up now and then.

◆ Put I386 _{on a shared volume on the network. This works, but you then have to somehow get}

the computer booted up enough to access network shares. We’ll talk more about this later. ◆ Set up a Remote Installation Services (RIS) server and set up your computer to boot to the RIS

server with a Preboot eXEcution (PXE) client. I’ll cover that in the later section on RIS. ◆ Set up a simpler operating system (DOS or Windows 98 without the GUI, for example)

on the computer, copy I386 _{to the computer’s local hard disk, and start Setup from inside}

the simpler operating system. You’ll see how to do this when we discuss the winnt.exe _and winnt32.exe _commands.

NT and 2000 veterans may be waiting for me to list the last option: start from boot floppies. For systems that had CD-ROM drives but could not boot from them, NT and 2000 could generate four floppies that could “wake the computer up” enough to read the CD-ROM drive and commence Setup. That’s no longer available under Server 2003.

From MS-DOS, Windows 3.1, or Windows for Workgroups 3.11, you will need to start your setup in the DOS-based mode found with winnt.exe_{. Or, from Windows 9x, you can start in Safe}

Mode Command Prompt and run winnt.exe _{after issuing the LOCK command.}

From a Windows 9x system, or earlier versions of NT, you’ll launch the installation from the

winnt32.exe_{. This GUI version of the setup executable gives you that user-friendly, yes-or-no click}

method of initiating the install. For this example, I’m using the drive letter F: as the CD source on an Intel-based system. To follow along, select Start/Run and enter the following:

F:\I386\winnt32.exe

When Upgrading

If you have a system that can be upgraded to Server 2003, you will immediately reach the prompt to decide whether to run a clean install or an upgrade. If you do not have an upgrade-capable machine, you will be informed that an upgrade is not available, and the upgrade option will be grayed out.

106 CHAPTER 5 SETTING UP AND ROLLING OUT WINDOWS SERVER 2003

If running an upgrade, you’ll see an overall list of things that Setup will do, as well as a Welcome to Windows Setup opening wizard screen where you first choose whether to do an upgrade or not. You’ll then see the License Agreement screen, where you click I Accept This Agreement. But do take a minute to read it—most people don’t realize that in agreeing you assent to becoming an organ donor if Bill Gates needs a transplant. Okay, I’m kidding, but seriously you really should read this End User License Agreement or EULA (pronounced “yoola”) and every other one that you agree to…some of them are pretty scary!

Following the license agreement, Setup will ask for the 25-character product key, presuming that you have a version of Server 2003 that requires that. Larger organizations will have CD-ROMS with the niftier corporate version of Setup, which does not require a product key.

Next you’ll see something new to Server’s Setup program: Get Updated Setup Files. (New to Server, but XP’s done it since 2001.) The idea here—which is an great one, in my opinion—is that Microsoft realizes that over time bugs and security holes appear; in fact, it’s downright scary to install Windows 2000 on a system that’s attached to the Internet, as some IIS worms will actually find it and infect it before you’re even finished installing the silly thing! The updated Setup files (or Dynamic Update, as it’s called) let you pull down installation files that are newer than the ones on your CD, files that would be prepatched against the worm du jour. Now, of course, those files can be pretty large; as I write this there aren’t really any downloadable Setup files to speak of, but I’m sure in time you’ll need to download a few hundred megabytes of updated files. That’s why you’ll like that you can collect the dynamic update files to a share on your network and then tell Setup to use those files from a local share, rather than making you do a day-long download every time you install Server 2003. I’ll cover more on dynamic updates later in this chapter.

Once you’ve told Setup whether or not to use dynamic updates, it goes out and checks for any par- ticular items that might cause trouble with the installation. That’ll look something like Figure 5.1.

FIGURE 5.1

SETTING UP AND INSTALLING 107

You’ll likely get at least a few warnings; read them, and if they’re no problem just click past them to continue Setup. If you have a real showstopper, as in my figure, then Setup will just stop.

Let me say again: read those warnings and errors! Microsoft does a pretty good job of explaining what they mean and how to address them. For example, note the IIS one—believe it or not, Setup disables IIS unless you’ve run their IIS Lockdown Tool, something that I personally don’t care for, or unless you make a Registry change. While an automatic Next is often the answer for wizards, it’s not in this case. Imagine running what seems to be a simple upgrade on your Web server, only to find that the Web server doesn’t work anymore!

Once you’ve gotten past the warnings, assuming that you have any, then the system doesn’t ask you much else—upgrades don’t require a lot of interaction.

When Installing Fresh

If, on the other hand, you started Setup from inside NT 4 or Win2K Server, then you will initially see the same things just described in “When Upgrading.” But in a fresh install, unlike an upgrade, Setup will then need a bunch of answers from you.

Following the Product Key page, you get the Windows Setup page. This lets you set the desired language and accessibility settings.

Copy Installation Files from This Folder Refers to the place from which you will be

installing Windows Server 2003. This is useful if you’re installing from a folder where you’ve precopied all of the I386 _{files. If you’re installing from the CD, then you typically needn’t}

worry about this.

Copy to This Folder on My Hard Drive Tells Setup what directory to install Server 2003

to. This defaults to \Windows _{(note the new directory—no more} winnt_{!) but it can be changed to}

another directory if you want. If you intend to install multiple copies of Server on a system, then use a different directory name. This field won’t take the drive letter. Note that if you’re upgrading from 2000 or NT, you’ll end up with two OSes—one in \winnt _{and one in} \windows_{. That can}

pose some problems, so either tell it to put the OS in \winnt _{so it’ll overwrite the old one, or skip}

starting Setup from inside the old OS and just boot from the CD and wipe the hard disk clean before installing Windows Server 2003.

Copy All Installation Files from the Setup CD Creates a complete setup source on one of your local hard drives under the directory \$win_nt$.~ls. Under this directory, you will find the

I386 _{source you are so familiar with.}

Note Most systems won’t need the Copy All Installation Files option selected. Server 2003 will do a pretty good job

of loading the right drivers to reconnect you to your source after the reboot. However, if you fail to find your source for the text-based setup, this option will get you back on track.

I Want to Choose the Install Drive Letter and Partition During Setup Allows you to

define which partition you will be installing Server 2003 in. Select it and you will get a prompt following the reboot to choose your partition.

Accessibility Options Those available for Setup include the Narrator and Magnifier. By select- ing these options now, the tools will be available during the next installation phase.

108 CHAPTER 5 SETTING UP AND ROLLING OUT WINDOWS SERVER 2003

After this page in the wizard, Setup asks about dynamic updates, and then copies the installation files to your hard disk. Setup’s now ready for the text-based portion of Setup, and it’ll prompt you for a reboot.