Chapter 23, Deploying Windows 2000
Chapter 23, Deploying Windows 2000
Chapter 23, Lesson 1
Automating Installations
|1|1.Automating Installations by Using the Windows 2000 Setup Manager
A.Create setup scripts quickly and easily.
1.The computers in most networks are not identical, but have many similarities.
2.Installation scripts allow you to specify the variations in the hardware configurations.
B.Create and modify answer files and uniqueness database files (UDFs) with an easy-to-use graphical interface.
C.Include application setup scripts in the answer file.
D.Create the distribution folder that you use for the installation files.
|2|E.Setup Manager presents three options when started
1.Create A New Answer File
a.Windows 2000 unattended installation
b.Sysprep Install
c.Remote Installation Services (RIS)
2.Create An Answer File That Duplicates This Computer’s Configuration
3.Modify An Existing Answer File
2.Practice: Installing the Windows 2000 Installation Deployment Tools
Chapter 23, Lesson 2
Using Disk Duplication to Deploy Windows 2000
|3|1.Introducing Disk Duplication
A.To install Windows 2000 on several computers with identical hardware
1.Create a disk image of a Windows 2000 installation.
2.Copy the disk image to multiple computers.
3.This establishes a baseline you can use to quickly copy again to a computer having significant problems.
B.System Preparation tool (Sysprep.exe)
1.Helps prepare the master disk image
2.Helps prepare for mass installations
C.Third-party disk-imaging tools
|4|2.Examining the Disk Duplication Process
A.Install and configure Windows 2000 on a test computer.
B.Install and configure any applications on the test computer.
C.Install application update packs on the computer.
D.Run Sysprep.exe on the test computer.
|5|3.Installing the Windows 2000 System Preparation Tool
A.Extract the files from Deploy.cab.
1.Double-click Deploy.cab (located in the Support folder of the Windows 2000 installation files) to view the files it contains.
2.Select all the files.
3.Right-click a file and select Extract.
B.Copy the necessary files onto the test computer you are using to create the master image.
|6|4.Using the System Preparation Tool
A.Every computer must have a unique security ID (SID).
1.You can’t copy an existing disk image to all your computers because all the computers would have the same SID.
2.The System Preparation tool adds a system service to the master image that creates a unique local domain SID the first time the computer is started.
B.Every master image has a Mini-Setup wizard added to it.
1.The Mini-Setup wizard runs the first time the computer is started.
2.The Mini-Setup wizard guides a user through entering user-specific information.
a.End-user license agreement
b.Product ID
c.Regional settings
d.User name
e.Company name
f.Network configuration
g.Joining a workgroup or domain
h.Time zone selection
3.The Mini-Setup wizard can be scripted so the user-specific information is automatically entered.
C.Every master image forces the computer on which it is copied to run a full Plug and Play device detection.
D.Every computer on which the master image is copied (the destination computer) must have the same mass storage devices, ACPI support, and hardware abstraction layer (HAL) as the computer on which the master image is generated (the master computer).
5.Practice: Using the System Preparation Tool to Create a Master Disk Image
|7|6.Installing Windows 2000 from a Master Disk Image
A.Run Sysprep on your test computer.
B.Run a third-party disk image copying tool to create a master disk image.
C.Save the new disk image on a shared folder or CD-ROM.
D.Copy this image to the multiple destination computers.
E.Start the destination computers and the Mini-Setup wizard prompts the user for computer-specific variables.
F.Provide a Sysprep.inf file and the Mini-Setup wizard will be bypassed and Windows 2000 will be loaded without user intervention.
7.Practice: Using the System Preparation Tool to Install Windows 2000 Professional
Chapter 23, Lesson 3
Performing Remote Installations
|8|1.Understanding Remote Installation
A.The most efficient method of deploying Windows 2000 Professional.
B.The process of performing a remote installation consists of the following:
1.Connecting to a Remote Installation Services (RIS) server
a.A computer running one of the Windows 2000 Server products
b.A computer running Remote Installation Services
2.Starting an automatic installation of Windows 2000 Professional
|9|C.Remote Installation offers several benefits.
1.Enables remote installation of Windows 2000 Professional
2.Simplifies server image management
a.Eliminates the need for hardware-specific images
b.Detects Plug and Play hardware during setup
3.Supports recovery of the operating system and computer in the event of computer failure
4.Retains security settings after restarting the destination computer
5.Reduces Total Cost of Ownership (TCO) by allowing either users or technical staff to install the operating system on individual computers
2.Installing and Configuring Remote Installation Services
|10|A.Examining the prerequisites
1.RIS is available only on a computer running one of the Windows 2000 Server products.
2.RIS requires additional network services to be available on the network.
a.RIS relies on the DNS server for locating both the directory service and the client computer accounts.
b.Client computers that can perform a network boot receive an IP address from the DHCP server.
c.RIS relies on the Active Directory directory services for locating existing client computers as well as existing RIS servers.
3.RIS must be installed on a volume that is shared over the network.
a.The shared volume can’t be on the same drive that is running Windows 2000 Server.
b.The shared volume must be large enough to hold the RIS software and the various Windows 2000 Professional images.
c.The shared volume must be formatted with the Microsoft Windows 2000 File System (NTFS).
|11|B.Using the Remote Installation Services Setup Wizard
1.Installs the RIS software
2.Creates the remote installation folder
3.Copies the Windows 2000 Professional installation files to the server
4.Adds .SIF files, which are a variation of Unattend.txt files
5.Configures the Client Installation wizard screens that will appear during a remote installation
6.Updates the registry
7.Starts the required Remote Installation Services
3.Practice: Installing RIS
4.Understanding Client Requirements for Remote Installation
|12|A.Client computers that support remote installation must have one of the following configurations:
1.A configuration meeting the Net PC specification
2.An NIC (network interface card or network adapter) with a PXE boot ROM and BIOS support for starting from the PXE boot ROM
3.A supported network interface card and a remote installation boot disk
|13|B.Net PCs
1.Have the ability to perform a network boot
2.Manage upgrades
3.Prevent users from changing the hardware or operating system configuration
4.Additional requirements
a.The network adapter must be set as the primary boot device within the system BIOS.
b.The user account that will be used to perform the installation must be assigned the user right “Log on as a batch job.”
Note Administrators do not have the “Log on as a batch job” user right by default.
c.Users must be assigned permission to create computer accounts in the domain that they are joining.
|14|C.Computers Not Meeting the Net PC Specification
1.Install a network interface card with a PXE boot ROM.
2.Set the BIOS to start from the PXE boot ROM.
3.Assign the user right “Log on as a batch job” to the user account that will be used to perform the installation.
4.Assign users permissions to create computer accounts in the domain that they are joining.
|15|5.Creating Boot Floppies
A.You create a boot floppy
1.If the network interface card in a client isn’t equipped with a PXE boot ROM
2.If the BIOS doesn’t allow starting from the network interface card
B.You use the boot floppy, also known as a boot disk, to simulate the PXB boot process.
C.You use the Windows 2000 Remote Boot Disk Generator to create a boot disk.
D.You run Rbfg.exe to start the Windows 2000 Remote Boot Disk Generator.
Note These boot floppies support only the PCI-based network adapters listed in the Adapters List in the Windows 2000 Remote Boot Disk Generator.
6.Practice: Creating a Remote Boot Disk
Chapter 23, Lesson 4
Upgrading Previous Versions of Windows to Windows 2000
|16|1.Identifying Client Upgrade Paths
A.Upgrade Microsoft Windows 95 to Windows 2000 Professional.
B.Upgrade Microsoft Windows 98 to Windows 2000 Professional.
C.Upgrade Microsoft Windows NT Workstation 3.51 and 4 to Windows 2000 Professional.
Note Windows 2000 Professional also upgrades all released service packs for Windows NT Workstation 3.51 and 4.
D.Upgrade Windows NT 3.1 or 3.5 to Windows NT 3.51 or 4 first and then to Windows 2000 Professional.
|17|2.Identifying Hardware Requirements and Compatibility
A.Intel Pentium processor 166 MHz or higher
B.32 MB or more memory
C.650 MB or more free space on the boot partition
D.VGA or higher video card and monitor
E.CD-ROM or DVD-ROM drive for CD-ROM installations
F.Network interface card and related cables
G.Keyboard and mouse or other pointing device
|18|3.Generating a Hardware Compatibility Report
A.Use the Windows 2000 Compatibility tool.
1.Run Winnt32/checkupgradeonly.
2.Run the Chkupgrd.exe utility.
B.Review the report
1.Generated as a text document
2.Documents system hardware and software that is incompatible with Windows 2000
|19|4.Identifying Incompatible Software
A.Any third-party networking protocol that doesn’t have an update in the i386\Winntupg folder
B.Any third-party client software that doesn’t have an update in the i386\Winntupg folder
C.All antivirus applications because of changes in the NTFS file system
D.All disk quota software because of changes in the NTFS file system
E.Any custom power management software or tools because of Windows 2000 support for ACPI and APM
|20|5.Upgrading Compatible Windows 95 or Windows 98 Computers
A.Run Winnt32.exe.
B.Accept the license agreement.
C.Create a computer account for computers in the domain.
D.Provide any application upgrade packs.
E.Decide if you want to upgrade to NTFS.
F.Check the Compatibility report and continue if compatible.
|21|6.Installing the Directory Service Client
A.Install on incompatible computers currently running Windows 95 or Windows 98.
B.Provides support for the following Active Directory features on computers running Windows 95 or Windows 98
1.Using fault-tolerant Dfs
2.Searching Active Directory directory services
3.Changing your password on any domain controller
C.Install Microsoft Internet Explorer 4.01 or later on computers running Windows 95 and enable the Active Desktop or the Directory Services Client Setup wizard won’t run.
D.Run Dsclient.exe located in the Clients\Win9x folder on the Windows 2000 Server or Advanced Server CD-ROM.
|22|7.Upgrading Windows NT 3.51 and 4 Clients
A.Verify compatibility by running the Windows 2000 Compatibility tool.
B.Run Winnt32 and select Upgrade To Windows 2000 (Recommended).
C.No Directory Service Client is available for incompatible computers running Windows NT 3.51 or Windows NT 4.
Chapter 23, Lesson 5
Installing Service Packs
|23|1.Installing Service Packs in Previous Versions of Windows
A.You installed the operating system and then applied each required service pack.
B.Installing a service pack would often make it necessary to reinstall previously installed components.
C.Windows 2000 eliminates the need to reinstall components after applying a service pack.
|24|2.Slipstreaming Service Packs
A.Integrates service packs with the Windows 2000 Professional installation files
1.Allows you to keep one master image of the operating system
2.Installs the appropriate files from the service pack as part of the Windows 2000 Professional installation
3.Saves you the time of manually applying the service packs after you install Windows 2000
B.Apply new service packs by running Update.exe with the /slip switch.
|25|3.Deploying Service Packs After Windows 2000 Is Installed
A.Run Update.exe to replace the existing Windows 2000 files with the appropriate new files from the service pack.
B.Adding and removing services does not require service packs to be reapplied.
1.Windows 2000 automatically recognizes that a service pack has been applied.
2.Windows 2000 automatically copies the necessary files from either the Windows 2000 installation files or the service pack install location.
Outline, Chapter 231
Microsoft Windows 2000 Professional