Title: Automating Installations by Using the Microsoft Windows 2000 Setup Manager
1Automating Installations by Using the Microsoft
Windows 2000 Setup Manager
- Create setup scripts simply and easily.
- Create and modify answer files and UDFs with a
graphical interface. - Include application setup scripts in the answer
file. - Create the distribution folder used for the
installation files.
1
2Setup Manager Presents Three Options When Started
- Create A New Answer File
- Create An Answer File That Duplicates This
Computers Configuration - Modify An Existing Answer File
3Introducing Disk Duplication
- Install Windows 2000 on several computers with
identical hardware. - Create a disk image of a Windows 2000
installation. - Copy the disk image to multiple computers.
- Youll be able to reinstall computers quickly.
- Use the System Preparation tool (Sysprep.exe) to
create the image. - Use third party disk-imaging tools to distribute
the image.
4Examining the Disk Duplication Process
- Install and configure Windows 2000 on a test
computer. - Install and configure any applications on the
test computer. - Install any application update packs on the test
computer. - Run the System Preparation tool on the test
computer.
5Installing the Windows 2000 System Preparation
Tool
- Extract the files from Deploy.cab.
- Copy these files onto the test computer.
6Using the System Preparation Tool
- Every computer must have a unique SID.
- Every master image has a Mini-Setup wizard added
to it. - Runs the first time the computer is started
- Guides a user through entering user-specific
information - Enters the user-specific information
automatically if scripted - Every destination computer must match the master
computer.
7Installing Windows 2000 from a Master Disk Image
- Run Sysprep on your test computer.
- Run a third-party disk image copying tool.
- Save the new disk image on a shared folder or
CD-ROM. - Copy this image to the multiple destination
computers. - Start the destination computers and the
Mini-Setup wizard starts. - Provide a Sysprep.inf file to bypass the
Mini-Setup wizard.
8Understanding Remote Installation
- Remote installation is the most efficient method
of deploying Windows 2000 Professional. - The process of performing a remote installation
consists of - Connecting to a Remote Installation Services
(RIS) server. - Starting an automatic installation of Windows
2000 Professional.
9The Benefits of Remote Installation
- Enables remote installation of Windows 2000
Professional - Simplifies server image management
- Supports recovery of the operating system and
computer - Retains security settings after restarting the
destination computer - Reduces Total Cost of Ownership (TCO)
10Examining the Prerequisites
- RIS is available only with Windows 2000 Server
products. - RIS requires additional network services.
- DNS Service
- DHCP Service
- Active Directory directory services
- RIS is installed on a volume that is shared over
the network.
11The Remote Installation Services Setup Wizard
- Installs the RIS software
- Creates the remote installation folder
- Copies the Windows 2000 Professional installation
files to the server - Adds .SIF files
- Configures the Client Installation wizard screens
- Updates the registry
- Starts the required Remote Installation Services
12Client Computers That Support Remote Installation
- Meet the Net PC specification
- Have an NIC (network interface card or network
adapter) with a PXE boot ROM and BIOS support
for starting from it - Have a supported NIC and a remote installation
boot disk
13Net PCs
- Have the ability to perform a network boot
- Manage upgrades
- Prevent users from changing the hardware or
operating system configuration - Have additional configuration requirements for
RIS installations
14Computers Not Meeting the Net PC Specification
- Install a NIC with a PXE boot ROM.
- Set BIOS to start from the PXE boot ROM.
- Assign the user right Log on as a batch job.
- Assign the user permissions to create computer
accounts.
15Creating Boot Disks
- Create a boot disk
- If the NIC is not equipped with a PXE boot ROM.
- If the BIOS does not allow starting from the NIC.
- Use the boot disk to simulate the PXB boot
process. - Run Rbfg.exe to create a boot disk.
16Identifying Client Upgrade Paths
- Upgrade Microsoft Windows 95 to Windows 2000
Professional. - Upgrade Microsoft Windows 98 to Windows 2000
Professional. - Upgrade Windows NT Workstation 3.51 and 4 to
Windows 2000 Professional. - Upgrade Windows NT 3.1 or 3.5 to Windows NT 3.51
or 4 first.
17Identifying Hardware Requirements
- Intel Pentium processor 166 MHz or higher
- 32 MB or more of memory
- 650 MB or more free space on the boot partition
- VGA or higher video card and monitor
- CD-ROM or DVD-ROM drive for CD-ROM installations
- Network interface card and related cables
- Keyboard and mouse or other pointing device
18Generating a Hardware Compatibility Report
- Use the Windows 2000 Compatibility tool.
- Run Winnt32/checkupgradeonly.
- Run the Chkupgrd.exe utility.
- Review the report
- Generated as a text document
- Documents incompatible hardware and software
19Identifying Incompatible Software
- Third-party networking protocols without an
update in i386\Winntupg - Third-party client software without an update in
i386\Winntupg - All antivirus applications
- All disk quota software
- Custom power management software or tools
20Upgrading Windows 95 or Windows 98
- Run Winnt32.exe.
- Accept the license agreement.
- Create a computer account for computers in the
domain. - Provide any application upgrade packs.
- Decide if you want to upgrade to NTFS.
- Check the Compatibility report and continue if
compatible.
21Installing the Directory Service Client
- Install on incompatible computers running Windows
95 or Windows 98. - Provides support for Active Directory features
- Using fault-tolerant Dfs
- Searching Active Directory directory services
- Changing your password on any domain controller
- Install Microsoft Internet Explorer 4.01 or later
on computers running Windows 95 and enable the
Active Desktop. - Run Dsclient.exe.
22Upgrading Windows NT 3.51 and 4 Clients
- Run the Windows 2000 Compatibility tool.
- Run Winnt32 and select Upgrade To Windows 2000
(Recommended). - No Directory Service Client is available for
Windows NT 3.51 or Windows NT 4.
23Installing Service Packs in Previous Versions of
Windows
- You installed the operating system and then
applied required service packs. - You had to reinstall components after installing
a service pack. - Windows 2000 eliminates the need to reinstall
components.
24Slipstreaming Service Packs
- Integrates service packs with the Windows 2000
installation files - Allows you to keep one master image of the
operating system. - Installs the service pack files during the
Windows 2000 installation. - Saves time.
- Apply new service packs by running Update.exe
with the /slip switch.
25Deploying Service Packs After Windows 2000 Is
Installed
- Run Update.exe to replace the existing Windows
2000 files with the appropriate new files from
the service pack. - Adding and removing services does not require
service packs to be reapplied. - Windows 2000 automatically recognizes that a
service pack has been applied. - Windows 2000 automatically copies the necessary
files from either the Windows 2000 installation
files or the service pack install location.