CHAPTER 3

                            UNATTENDED INSTALLATIONS OF

                         MICROSOFT WINDOWS 2000 SERVER

 

 

Lesson 1:  Preparing for an Unattended Installation of

Windows 2000 Server

 

 

You create an answer file when you run an unattended installation of Windows 2000 Server. 

Also, you are going to install Windows 2000 Server on several computers over the network. 

Therefore, you must create at least one set of distribution folders.

 

 

Creating the Answer File

 

The answer file is a customized script (usually saved as a .txt file) that allows you to run an

unattended installation of Windows 2000 Server.  The I386 directory of the Windows 2000

Server installation CD-ROM contains a sample answer file, Unattend.txt that you can edit and

us in your unattended installation.  You can give the unattended file another name, if you have

different types of unattended installations.

 

 

Note that other programs such as the Sysprep tool, which is used to facilitate the creation of a

disk image of your Windows 2000 Server installation, also use answer files. 

 

======================================================================

Filename                     When the file is used                  ***IMPORTANT ***

======================================================================

 

<filename>.txt            When performing an unattended installation.  You can use any

                                    name for the .txt file.  Unattend.txt is the name of the sample

                                    answer file included with Windows 2000 Server.

 

Winnt.sif                     When installing Windows 2000 Server from a bootable

                                    CD-ROM drive.

 

Sysprep.inf                 When using the Sysprep tool to create a disk image of your

                                    Windows 2000 server installation.

 

======================================================================

 

winser3.html                                                   PAGE 2                                                       2001/01/12

 

 

 

Answer File Format

 

An answer file consists of section headers, keys, and values for each key.  Most of the section

headers are predefined, but some can be user defined.  You can copy this file from the CD-ROM

to writeable media, like a fixed disk, and then edit the file as necessary to meet the needs of your

unattended installation.  You can also rename the file.

 

 

 *** See sample of the Unattend.txt file ***     ** Could be on MCSE, know the

                                                                                    sections on the Unattend.txt file

 

You do not need to specify all the possible keys in an answer file if the installation does not require them. 

Invalid key values generate errors or can cause incorrect behavior after setup.

 

The answer file is broken into sections.  A section name is enclosed in brackets, as in the following

example:

 

[UserData]

 

Sections contain keys and the corresponding values for those keys.  Each key and value are separated

by a space, an equal sign and a space:

 

BitsPerPel = 8

 

Values that have spaces in them require double quotes around them:

 

OrgName = “Microsoft Corporation”

 

 

Some sections have no keys and merely contain a list of values:

 

 

Comment lines start with a semicolon:

 

;Setup program runs without requiring user input.

 

 

 

Answer File Keys and Values

 

Every key in an answer file must have a value assigned to it; however, some keys are

optional, and some keys have default values that are used if the key is omitted.  Key values

are strings of text, unless numeric is specified.  If numeric is specified, the value is decimal

unless otherwise noted.

 

 

======================================================================

 

winser3.html                                                   PAGE 3                                                      2001/01/12

 

 

 

 

NOTE:  Keys are not case sensitive; they can be uppercase or lowercase.

 

The Unattend.doc file has detailed information about the answer file keys and values.  You

can find Unattend.doc in the Deploy.cab file on the Windows 2000 Server installation CD-ROM,

under the \Support\Tools folders.  To extract or view the contents of the Deploy.cab file, use

Windows Explorer.

 

 

IMPORTANT  Running Setup.exe or 2000rkst.msi from the \Support\Tools folder installs the

Windows 2000 Support Tools in Support.cab, but it does not extract the Unattend.doc file

or any of the other compressed files in Deploy.cab.

 

***** See the charts on page 103 and 104 *****

 

 

Creating the Answer File Manually

 

To create the answer file manually, you can use a text editor such as Notepad. 

 

 

Creating the Distribution Folders

 

To install Windows 2000 Server on multiple computers over a network, you must create at least one

set of distribution folders.  The distribution folders typically reside on a server to which the destination

computers can connect.  This allows users to install Windows 2000 Server by running Winnt.exe or

Winnt32.exe on those computers.

 

In addition, distribution folders allow you to update future images by editing the files in the distribution

folders to generate updated images without having to start from the beginning.

 

To help load balance the servers and to make the file-copy phase of Windows 2000 Setup faster, you

can create distribution folders on multiple servers to support the installation process on computers that

are running Windows 95, Windows 95, Windows NT, or Windows 2000.

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 4                                                       2001/01/12

 

 

 

 

To create a distribution folder manually, connect to the network server on which you want to create the

distribution folder, and create a \\W2kdist folder on the network share.  You can choose different names

to distinguish the different folders.

 

For each edition of Windows 2000, copy the contents of the \I386 folder to the distribution share

created for it.  For instance, if you are preparing a distribution for Windows 2000 Server, create

and share a folder named \W2kdists and copy the \I386 directory on the Windows 2000 Server

installation CD-ROM to it.

 

NOTE:  The distribution share to support a default installation of Windows 2000 Server requires

approximately 313 megabytes (MB) of disk space.

 

 

Structuring the Distribution Folder

 

*** See page 106 ***

 

 

I386 (on Windows 2000 installation CD-ROM Copied to Distribution Share)

 

This is the primary Distribution folder. It contains all the files required to install Windows 2000

Server.  You copy the contents of this folder from the Windows 2000 Server installation CD-ROM

to the root of the distribution share.

 

 

\$OEM$ (On Distribution Share and Copied to $WIN_NT$.~LS)

 

This subfolder is located directly beneath the primary distribution folder.  During Setup you can

automatically copy directories, standard Microsoft format 8.3 files, and any tool needed to your

automated installation process to \$OEM$.

 

\$OEM$ provides the necessary folder structure for supplemental files to be copied to the target

computer during Setup.

 

\$OEM$ can contain the optional file Cmdlines.txt, which contains a list of commands to be run

during the GUI mode phase of Setup.

 

As long as Setup finds \$OEM$ in the root of the distribution point, it will copy all the files found

in this directory to the $WIN_NT$.~LS temporary directory created during the Text mode phase

of the Setup.  During Setup, subfolders of \$OEM$ are copied to the corresponding location on

the target computer.

 

 

======================================================================

 

winser3.html                                                   PAGE 5                                                       2001/01/12

 

 

 

 

NOTE:  All folders described next are located on the distribution share below \$OEM$ and are

copied to various locations on the computer running Setup.

 

 

\$OEM$\textmode (Copied to $WIN_NT$.~BT)

 

The \$OEM$\textmode subfolder contains new or updated files for installing mass storage

device drivers and HALs.

 

All files placed in the \$OEM$\textmode subfolder (HALs and drivers) must be listed in the

[OEMBootFiles]  sections of the answer file.

 

 

\$OEM\$$ (Copied to %windir% and Subfolders of %windir%)

 

The structure of the subfolder must match the structure of a standard Windows 2000 installation,

where \$OEM$\$$ matches %windir%, \$OEM$\$$\System32 matches %windiw%\System32,

and so on.

 

NOTE:  In Windows 2000, %systemroot% is equivalent to %windir%

 

 

\$OEM$\$1\Drivers (Copied to $systemdrive$\Drivers and Subfolders of

$systemdirve$\Drivers)

 

The \$OEM$\$1\Drivers subfolder, which is new for Windows 2000, allows you to place new

or updated Plug a Play device drivers and their supporting files (catalog files and .INF installation

files) in and below the Drivers subfolder.

 

 

\$OEM$\$1\Sysprep (Copies to %systemdrive%\sysprep)

 

The \$OEM$\$1\Sysprep subfolder contains the files needed to run the Sysprep utility.

 

 

\$OEM$\drive_letter

 

During Text mode, the structure of each \$OEM$\drive_letter subfolder is copied to the root of the

corresponding drive in the target computer.  You can create subfolders within these subfolders.  For

example, \$OEM$\E\Misc causes Setup to create a \Misc subfolder on the E:drive.

 

Files that have to be renamed must be listed in the $$Rename.txt file.  Note that the files in the

distribution folders must have short names (format 8.3).

 

 

 

======================================================================

 

winser3.html                                                   PAGE 6                                                       2001/01/12

 

 

 

 

In Class Notes:

 

Unattend Install command udf n:[unattend.txt]

 

At the Command Prompt type:

 

N:>winnt32^/u:unnattend.txt^/s:n:  (s is the source)

 

At the Run command:

 

N:\winn32^/u:unattend.txt^/s:n:

 

 

Lesson Summary:

 

answer file, which is a customized script file that contains multiple optional sections that you modify

to supply information about your installation requirements.

have created.  You must create at least one set of distribution folders to install Windows 2000 Server

over the network.

 

 

Lesson 2:  Automating the Installation of Windows 2000 Server

 

Automated installations of Windows 2000 Server involve running Setup with an answer file.  You can

perform automated installations on multiple computers so that Setup can take place in an unattended

fashion.  The following installations can be automated:

 

·        The core Windows 2000 Server operating system

·        Any application that does not run as a service.

·        Additional language support for Windows 2000 Server through the installation of various

language packs

·        Service packs for Windows 2000 Server

 

 

Performing an Unattended Installation

 

To perform an unattended installation of Windows 2000 Server, you must specify the answer file

when you run Setup.  There are three basic types of unattended installations that you can use to

set up Windows 2000 Server:  The bootable CD-ROM,  the Winnt.exe method, and the

Winnt32.exe method.

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 7                                                       2001/01/12

 

 

 

 

Bootable CD-ROM

 

To start Windows 2000 Setup in unattended mode from the Windows 2000 Server installation

CD-ROM, the following conditions must be met:

 

The computer must support the El Torito Bootable CD-ROM (no emulation mode) format to boot

from the CD-ROM drive.

The answer file must be named Winnt.sif and be placed on a floppy disk to be inserted into the

floppy drive as soon as the computer boots from the CD-ROM.

The answer file must contain a [Data] section with the required keys specified.

Wait 10 seconds till reboot machine.  The caching is written to the Hard Drive then it reboots.

 

 

Winnt.exe or Winnt32.exe

 

 

The following Winnt.exe command provides an example for implementing an unattended installations:

 

            Winnt^/s:Z:\I386^/u:Z:\unattend.txt^/t:c

 

Note the use of the /u: command line switch, which indicates an unattended installation.  The /t: switch

indicates which drive Setup will copy the source files to continue the installation.  Z:\I386 is the network

location containing the Windows 2000 installation source files.  The local computer must map the Z:

drive to the network share containing the I386 subfolder before the example command line will work.

 

 

Automating the Installation of Windows 2000 Server

 

Several methods are available for creating an automated installation of Windows 2000 Server. 

The method you choose depends on the desired outcome.

 

For example, Syspart and Sysprep can be used together in certain setup installation scenarios.

 

 

======================================================================

 

winser3.html                                                   PAGE 8                                                       2001/01/12

 

 

 

In addition to the basic installation there are several more methods:

 

·        The Winnt32.exe Setup program along with the /syspart parameter

·        The System Preparation Tool (Sysprep)

·        System Management Server (SMS)

·        Bootable CD-ROM

 

These methods either build on or replace the over-the-network unattended installations method

described above.  The following table provides detains about when to use each installation method:

 

 

 

======================================================================

Installation                                                                                                            Clean

Method               Use                                                            Upgrade                Installation

======================================================================

 

Syspart                Used for Clean installation to                          No                         Yes

                            Computers that has dissimilar

                            Hardware.

 

Sysprep               Use Sysprep when the master computer         No                          Yes

                           and the target computers have identical

                           or nearly identical hardware.

 

SMS                  Use SMS to perform managed upgrades           Yes                        No          

                          Of Windows 2000 Server to multiple

                          Systems, if they are spread out geographically.

 

Bootable         Use the bootable CD-ROM method with a          No                      Yes

CD-ROM       computer whose BIOS allows it to boot from

                         the CD-ROM.

 

RIS (Remote   Use RIS with a computer that supports PXE or    Yes                     Yes

Installation     a bootable RIS diskette.  Either method allows

Service)           the computer to connect to a networked RIS

                        Server during the initial boot process and receive an

                        Installation of Windows 2000 Professional.

 

=======================================================================

 

NOTE:  As of the writing of this kit, RIS can roll out automated installations of Windows 2000

Professional only.  It does not support automated installations of Windows 2000 Server.  Future

enhancement to RIS might allow roll-outs of Windows 2000 Server and other operating systems.

 

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 9                                                       2001/01/12

 

 

 

 

Before you do an installation you must determine if it is an upgrade or a clean installation.  If you do

not perform a clean installation, note that because an automated installation is unattended, a clean

installation can replace existing partitions or files on existing partitions.  Application files and data

files can still remain on partitions, although applications should be reinstalled to reregister them with

the new operating system installation.

 

 

Using Syspart

 

Syspart is executed by including it as a parameter of the Winnt32.exe setup program.  Winnt32

with the Syspart switch is run on a reference computer to complete the first phase of installation. 

If the reference computer and the computers on which you will complete the installation of Windows

2000 Server do not have similar hardware, you can use the Syspart method.  It is quicker to install.

 

Syspart requires that you use two physical disks, with the primary partition on the target hard disk. 

However, the target hard disk does not need to be located in the master computer.  It can be in

another computer on a network, as long as it is a clean disk with no

operating systems installed.

 

If you require a similar installation and operating system configuration on hardware types in which the

HALs or mass storage controllers differ, you can use Syspart to create a master set of files with the

necessary configuration information and driver support.  The file set can then be used on dissimilar

systems to properly detect the hardware and consistently configure the base operating system.

 

 

The following information provides more details about the parameters and values used when

running the Winnt32.exe Setup program:

 

some or all of the prompts the end user normally responds to during Setup.  Using an

answer file is optional when creating the master file set.

/s commandline switches if you want to install from multiple sources simultaneously.  The

first source is a network drive, the second source is a local CD-ROM drive.

hard disk. 

secondary hard disk. 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 10                                                    2001/01/12

 

 

 

 

use the /tempdrive command line switch, make sure you have sufficient free disk space on your

second partition to install both

Server.  See Page 124 for the list of drives.

 

NOTE:  Syspart will automatically mark the drive as active in preparation for moving it to the target computer.

 

 

Using Sysprep

 

Sysprep is a tool that facilitates creating a disk image of your Windows 2000 Server installation.  Disk

duplication is a good choice if you need to install an identical configuration on multiple computers.  To

use the Sysprep tool, you should install Windows 2000 Server on a reference computer.

 

Using Sysprep you boot to the floppy and it creates an image of C drive.  You must have the identical

SAM and HAL.

 

TIP  Create a CD-ROM containing the disk image or move the image to a network location so that the

mage can be used to rapidly set up many identical or nearly identical computers.

 

 

To use Sysprep, the master computer and target computes must have identical HALs, Advanced

Configuration and Power Interface (ACPI) support, and mass storage devices.  Windows 2000

automatically detects plug and play devices, and Sysprep redetects and re-enumerates the devices

on the system when the computer is turned on after Sysprep has run.

 

NOTE:  Because the master and target computers must have identical HALs, ACPI support, and mass

storage devices, you might need to maintain multiple images for your environment.

 

If your environment includes multiple types of hardware-dependent systems, you can user Syspart in

conjunction with Sysprep to create a master of each type.

 

Before you begin, choose a computer to us as a reference computer.  The reference computer must

have Windows NT Server or Windows 2000 Server installed.

 

NOTE:  Sysprep can also be used to create installation of Windows 2000 Professional.

 

 

======================================================================

 

winser3.html                                                   PAGE 11                                                     2001/01/12

 

 

 

 

The Sysprep Process

 

Installing Windows 2000.  You should have the same hardware on the server computer as the target

computer.  The computer should not be joined to a domain while it is being built.  In addition, the

local administrator password should be kept blank.

 

Configuring the Computer.  You should be logged on as the administrator when you install and

customize Windows 2000 Server and the associated applications.

 

Validating the image.  You should run a client audit, based on your criteria, to verify that the image

configuration is correct. 

 

Preparing the image for duplication.  Once you are confident the computer is configured exactly the

way you want, the system can be prepared for duplication.  You run Sysprep with the optional

Sysprep.inf file.

 

Duplicating the Installation.  The hard disk is used to run plug and play detection, create a unique

SID and run the Mini-Setup wizard the next time the system is started.

 

 

WARNING  Components that depend on the Active Directory services cannot be duplicated. 

Local users and groups should not be created on the member server because new SIDs will not

be assigned to these user and group accounts.

 

 

Sysprep Files

 

To use Sysprep, run Sysprep.exe manually or configure Setup to run Sysprep.exe automatically by

using the [GuiRunOnce} section of the answer file.  To run Sysprep, the files Sysprep.exe and

Setupcl.exe must be located in a Sysprep folder at the root of the system drive

(%systemdrive%\Sysprep\)

 

The Sysprep files prepare the operating system for cloning and start the Mini-Setup wizard.  An

optional answer file, Sysprep.inf, can be included in the Systprep folder.  Sysprep.inf contains

default parameters that can be used to provide consistent responses where appropriate.

 

When the Mini-Setup wizard has successfully completed its tasks, the system will reboot one last

time, the Sysprep folder and all its contents will be deleted, and the system will be ready for the

user to log on.

 

 

 

======================================================================

 

winser3.html                                                   PAGE 12                                                     2001/01/12

 

 

 

 

The sysprep files are defined in the following sections:

 

========================================================================

Parameter                   Description

========================================================================

 

-quiet                           Runs Sysprep without displaying onscreen messages.

 

-nosidgen                    Runs sysprep without regenerating SIDs that are already

                                    on the system.

 

-reboot                        Automatically reboots the computer after Setup shuts it

                                    down, eliminating the need for you to manually turn the

                                    computer back on.  The only time you will want to use

                                    this switch is if you are auditing the Sysprep process and

                                    want to make sure the Mini-Setup wizard is working

                                    properly.

 

==========================================================================

 

 

Sysprep.inf

 

The Sysprep.inf file is an answer file used during the cloning process to provide unique configuration

information for each of the target computers.    Sysprep.ink needs to be placed in the

%systemdrive%\Sysprep\folder or on a floppy drive.

 

If you use Sysprep.inf when creating the master computer and when running Sysprep, use the

floppy disk method to provide an alternate Sysprep.inf.

 

** See the sample of Sysprep.inf file on page 130 **

 

You can change the administrative password by using Sysprep.inf only if the existing administrative

password is null. 

 

 

Setupcl.exe

 

The Setupcl.exe file processes Sysprep.inf to determine pages for the Mini-Setup wizard and start the

Mini-setup wizard.

 

NOTE:  The combination of Sysprep.exe and Setupcl.exe can be used to replace the Rollback.exe

tool used in previous versions of Windows NT.

 

 

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 13                                                     2001/01/12

 

 

 

 

Mini-Setup Wizard

 

The Mini-wizard starts the first time a computer boots from a disk that has been duplicated by using the

Sysprep tool.  The wizard gathers any information needed to further customize the target computer. 

 

The screens that the Mini-Setup wizard can display include the following:

 

·        EULA

·        Regional options

·        User name and company

·        Computer name and administrator password

·        Network settings

·        Server licensing

·        Time zone selection

·        FinishRestart

 

*** page 132 see the chart ***

 

 

Because Setup detects optimal settings for display devices, Display Settings is no longer a screen

seen during Setup or during the Mini-Setup wizard.  You must provide the specific networking

information in Sysprep.inf.  If enabling DHCP on all adapters is sufficient and installing Microsoft

Client for Microsoft Networks, TCP/IP, and File and Print Sharing for Microsoft Networks on all

adapters is sufficient, there is nothing additional you need to specify in Sysprep.inf.

 

 

Running Sysprep

 

There are two ways to run the Sysprep utility, manually or automatically.

 

 

Running Sysprep Manually

 

transfer to other similarly configured computers.  Then run Sysprep without the

reboot command line switch. 

computers.

 

 

How to prepare Windows 2000 Server installation for duplication:

 

Preparing the Sysprep folder.  A Sysprep folder must be created at the root of the drive.  The

Sysprep.exe, the Setupcl.exe, and if applicable, the Sysprep.inf files should be copied to the Sysprep

folder.

 

Running the Sysprep utility.  The Sysprep utility should be run from a command prompt within the

Sysprep folder. 

 

 

======================================================================

 

winser3.html                                                   PAGE 14                                                     2001/01/12

 

 

 

 

Running Sysprep without the –reboot switch.  When a message appears saying that the computer

should be shut down, selecting the Shut Down command from the Start menu.  A third-part disk-imaging

utility can now be used to create an image of the installation.

 

Running Sysprep with the –reboot switch.  The computer reboots automatically and the Mini-Setup

wizard runs.  The wizard’s prompts should be verified.

 

 

NOTE:  You can add a Cmdlines.txt file to the Sysprep folder to be processed by Setup.  This file will

run post-Setup commands, including those required for application installation.

 

 

Running Sysprep Automatically

 

The [GuiRunOnce] section of the answer file contains commands to be executed after Setup completes. 

You can use the [GuiRunOnce] section to create an installation that competes Setup, automatically logs

on the computer, runs Sysprep in quiet mode, and then shuts down the computer.

 

 

Using Sysprep to Extend Disk Partitions

 

Windows 2000 is designed to extend a partition of GUI mode.  This new functionality allows you to create

images that can be extended to take full advantage of hard disk that might have more space than the

original hard disk on the master computer.

 

To extend a hard disk when using a third-party imaging product that supports NTFS, you should first

configure the partition on the master computer hard disk to the minimum size required to install Windows

2000 Server with all the desired components and applications.

 

 

Using Systems Management Server

 

You can use System Management (SMS) to perform managed upgrades of Windows 2000 Server to

multiple systems, especially those that are geographically dispersed.  Note that SMS is used only for

installations to computers that contain a previously installed operating system and are running the SMS

client responsible for receiving software installation instructions.

 

The primary advantage of using SMS is upgrade that you can maintain centralized control of the upgrade

process.  For example, you can control when upgrades take place (such as during or after training, after

hardware verification, and after user data is backed up), which computers will be upgraded, and how

you will apply network constraints.

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 15                                                     2001/01/12

 

 

 

 

Using a Bootable CM-ROM

 

You can use the bootable CD-ROM method to install Windows 2000 Server on a computer whose BIOS

allows it to boot from a CD-ROM.  This method is useful for computers at remote sites with slow links and

no local information technology (IT) department.  The bootable CD-ROM method runs Winnt32.exe,

which allows for a fast installation.

 

NOTE:  You can use the bootable CD-ROM method only for clean installations.  To perform upgrades,

you must run Winnt32.exe from within the existing operating system.

 

To ensure maximum flexibility for setting up Windows 2000 Server, set the boot order in the BIOS as follows:

 

Network Adapter for PXE-compliant read-only memory (ROM),  this option can be used to support

operating system installation from a RIS server.

CD-ROM for bootable CD-ROM operating system installation.

Hard Disk for Sysprep or Syspart prepared local disk-based operating system installation.

Floppy Disk for floppy disk based operating system installation.

 


To use a bootable CD-ROM for a fully automated operating system installation, the

following criteria must be met:

 

(no emulation mode) format.

 

The following information provides an overview of how to install Windows 2000 Server by using a

 bootable CD-ROM drive:

 

Booting the system.  After the Windows 2000 Server CD has been inserted into the CD-ROM drive,

the system should be rebooted.

Loading the Winnt.sif file.  After the system reboots, the blue Text mode screen for Windows 2000

Setup appears.  The floppy disk that contains the Winnt.sif file should be inserted into the floppy drive. 

Once the computer reads the floppy drive, the floppy drive should be removed.  Setup will not run

from the CD-ROM drive as specified by the Winnt.sif file.

 

NOTE:  The bootable CD-ROM method required that all necessary files be on the CD-ROM,

Uniqueness Database Files (UDFs) cannot be used with this method.  UDFs are not usable because

the unique identifier is called for each installation when specifying the UDF file from Winnt.exe or

Winnt32.exe

 

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 16                                                     2001/01/12

 

 

 

 

Lesson Summary:

 

There are four methods available for automating the installation of Windows 2000 Server.

 

1.  Run the Winnt32.exe command along with the Syspart parameter.  This is used if the target computer

     has dissimilar hardware from the master computer. 

 

2.  If the hardware is similar, you can use the Sysprep utility to perform an unattended installation. 

 

3.  Use SMS to perform managed upgrades of Windows 2000 Server to multiple systems, especially

     those that are geographically dispersed.

 

4.  Bootable CD-ROM.  This method is useful for computers at remote sites with slow links and no

     local IT department.

 

 

Lesson 3:  Automating the Installation of Server Applications

 

You can use two methods of automate the installation of server applications:  using the Cmdlines.txt

file or using the answer file. 

 

The Cmdlines.txt file contains a list of commands that are executed during the GUI mode phase

of the Windows 2000 installation. 

 

The answer file, which allows you to run an un attended installation of Windows 2000 Server,

includes the [GuiRunOnce] section.

 

 

 

Using the Cmdlines.txt File

 

The Cmdlines.txt file contains the commands that are executed during the GUI mode phase of the

installation process.  If you plan to use Cmdlines.txt, you need to place the file in the \$OEM$

subfolder of the distribution folder.  If you are using Sysprep, place Cmdlines.txt in the

\$OEM$\$1\Sysprep subfolder.

 

You should use the Cmdlines.txt in the following circumstances:

 

Microsoft Office 95, or it is designed to be installed by one user and to replicate user-specific

information.

 

 

 

======================================================================

 

winser3.html                                                   PAGE 17                                                     2001/01/12

 

 

 

 

When you want to log on as a service and you want your changes replicated to all users.

 

The syntax for the Cmdlines.txt file is as follows:

 

[Commands]

“<command_1>”

“<command_2>”

 

 

 

 

“<command_x>”

 

 

 

Using the Answer File

 

The [GuiRunOnce] section of the answer file contains a list of commands that are executed the

first time a user logs on to the computer after Setup runs.

 

 

NOTE:  You need to run Sysprep from [GuiRunOnce] so that you can replicate settings to all users.

 

Another alternative is to place a command for a tool or application that forces a reboot at the end of a

set of RunOnce commands.  This also requires that before rebooting you add additional RunOnce

entries to the registry so that after the reboot, Windows 2000 processes the next set of commands. 

You can have the first command that RunOnce executes be a registry edit command:

 

            Regedit^/s^<filename.reg>

 

You can set the AutoAdminLogonCount parameter to log on automatically as administrator to the

computer.  An automatic logon supports the multiple reboots that might be required.  (Up to 99 reboots

are supported.)

 

 

Applications that use the same type of installation mechanism might not run properly if a /wait command

is not used.

 

 

Installing Applications

 

You can use two methods to install applications through the [GuiRunOnce] section of the answer file: 

using application installation programs and using a batch file.

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 18                                                     2001/01/12

 

 

 

 

Using Application Installation Programs

 

The preferred method for preinstalling an application is to use the installation routine supplied with the

application.  You can do this if the application you are preinstalling is able to run in quiet mode

(without user intervention).  Quiet mode usually requires a /q or /s command line switch.

 

Note that this command uses its own installation program:

 

<path^to^setup>\Setup.exe^/q

 

 

Using a Batch File to Control How Multiple Applications are Installed

 

If you want to control how multiple applications are installed, you can create a batch file that

contains how individual installation commands and uses the Windows 2000 Start command

with the /wait command line switch.

 

The following information provides an overview of how to create the batch file, install the application,

and then remove all references to the batch file after installation is complete:

 

Creating the Batch file.  The batch file should contain command lines similar to the following example:

 

Start^/wait^<path>\<setup^file><command^line^parameters>

 

Start^/wait<path>\<setup^file><command^line^parameters>

Exit

 

            Where:

 

                        The <path> placeholder is the path to the executable file that starts the

                        Installation.  This path must be available during Setup.

 

                        The <setup file> placeholder is the name of the executable file that

                        Starts the installation.

 

                        The <command line parameter> placeholders are any available quiet-

                        Mode parameters appropriate for the application you want to

                        Install.

 

Copying the batch file.  The batch file should be copied to the distribution folder or to another

location that can be accessed during installation.

 

Adding the batch file to the answer file.  An entry for the batch file should be added to the

[GuiRunOnce] section of the answer file.

 

Copying the .Ink file to the source computer.  The .Ink file should be copied from the source

computer to the $OEM$\$1\documents and settins\all users\start menu\programs\startup folder.

 

 

 

 

======================================================================

 

winser3.html                                                   PAGE 19                                                     2001/01/12

 

 

 

 

Lesson Summary:

 

of the installation process.

with the application, or you can create a batch file that contains the individual installation commands.