CHAPTER
15
DEPLOYING WINDOWS 2000 USING RIS
Using Remote Installation Services (RIS), you can set up new client computers remotely
without the need to physically visit each machine. Specifically you can install operating
ystems (Os) on remote boot-enabled client computers by connecting the computer to the
network, starting the client computer, and logging on with a valid user account.
Lesson 1:
RIS Overview
Remote OS Installation uses some of the exiting services that may already be deployed and in
use within your organization and it adds some services that you may or may not be familiar
with.
MUST HAVE:
· Active Directory
· Updated Dynamic Host Configuration Protocol (DCHP) server
· Compliant version of DNS.
Remote Install Server Components
When RIS is installed, these additional services are added to the server:
Boot Information Negotiation Layer (BINL). The BINL service is added during the
RIS installation process and provides overall management of the RIS environment.
Allows User LOGON.
Trivial File Transfer Protocol Daemon (TFTPD). This server-side TFTP service is
responsible for hosting specific file download request made by the client computer.
Trivial File Transfer Protocol Daemon (TFTPD) does not require logon, that is why
it is called trivial.
TFTPD uses UDP Protocol
FTP uses TCP Protocols
======================================================================
winads15.html PAGE
2 2002/03/06
Single Instance Store (SIS). SIS is the service responsible for reducing disk space
requirements on the volume used for storing RIS installation images.
SIS creates the links, it actually works as a dummy terminal with a Remote Boot Prom.
Remote Install Client Components
There are two types of remote boot-enabled client computers
boot ROMS
PXE Remote Boot Technology
Remote OS Installation uses the new PXE DHCP-based remote boot technology to initiate
the installation of an OS from a remote source to a client hard disk.
The Windows 2000 Professional OS is currently the only installation supported by RIS.
CD-based installation. The CD-based option is similar to setting up a workstation directly
rom the Windows 2000 Professional CD-ROM; however, the source files reside across
the network on available RIS servers.
RIPrep image format. The RIPrep imaging option allows a network administrator to
clone a standard corporate desktop configuration, complete with OS configurations,
desktop customizations, and locally installed applications.
RIPprep Image Format, will work well to install, user log ons, copies the image much
faster, if you can put an answer file, then you can do remotely without user intervention.
TERMINOLOGY
BINL. Boot Information Negotiation Layer, added to the RIS installation process and
provides user logons.
TFTPD. Trivial File Transfer Protocol Daemon. Does not require user to logon.
CIW. Part of the installation option, the CIW warns the users that the installation will
reformat his or her hard disk and previously stored information will be deleted, and then
prompts the user to start the Remote OS Installation. (page 558)
======================================================================
winads15.html PAGE
3 2002/03/05
PXE. Uses existing TCP/IP for companies along with DHCP to discover RIS servers
on the network. Remember DORA, Discover, Offer, Request and Acknowledge Process.
RIS. Must be installed on NTFS, does not work on FAT.
RIPrep Image format. Allows a network administrator to clone a standard desktop
configuration, complete with OS configurations, desktop customizations, and locally
installed applications.
*** See the diagram
on page 557, may be on exam ***
How the PXE Remote Boot Technology Works
PXE is a new form of remote boot technology that has been created within the computing
industry. PXE provides companies with the ability to use their existing Transmission Control
Protocol/Internet Protocol (TCP/IP) network infrastructure with DHCP to discover RIS
servers on the network.
PXE uses TCP/IP and DHCP to access the network (remember DORA). But, be careful,
everything is sent clear text, so do this type of install locally, not over a WAN link.
The user logs in and then presses F12 to start, ensure you send it to the proper machine.
When a PXE-enabled client computer is turned on, the PXE-based ROM requests an IP
address from a DHCP server using the normal DHCP discovery process.
After the network bootstrap program is sent to the client by the BINL service, the client-side
experience will be different, depending on the remote installation server vendor that is
responding to the client request for service.
*** see the diagram
on page 557***
The RIS Boot Disk
For computers that do not contain the PXE-based remote boot ROM, Windows 2000
provides the administrator with a tool to create a remote boot disk for use with RIS. The
RIS remote boot disk can be used with a variety of Peripheral Component Interconnect
(PCI)-based network adapter cards. Using the RIS boot disk eliminates the need to
retrofit existing client computers with new network cards that contain a PXE-based remote
boot ROM to take advantage of the Remote OS Installation feature.
======================================================================
winads15.html PAGE
4 2002/03/06
How the Remote OS Installation Process Works
The process of contacting an RIS server and selecting an OS image is accomplished in a
few steps. See the diagram page 558.
The Remote OS Installation Process
An RIS client connected to the network starts, and during the power up the computer
initiates a network service request. The DHCP server makes a request.
The RIS server (using the BINL) service must check in Active Directory for the existence
of a prestaged client computer account that matches this client computer. Once the RIS
server has checked for the existence of a client computer account, the CIW is downloaded
to the client computer.
Once the user logs on, the RIS server checks Active Directory for a corresponding user
account, verifying the password. If the user is only allowed a single installation option
and OS choice, the user is not prompted to select anything. Once the user confirms the
installation settings on the summary screen the OS installation
begins.
IMPORTANT: Because the CIW is running in a preboot execution environment, there is
no support for extended characters in either the text displayed or the input fields (user
name, password, domain, or any custom input parameters). Careful consideration
should be taken before creating user or domain names that contain extended characters
because they will be not usable with RIS.
RIS Server and Client Requirements
BOOK: Server hardware minimum requirements:
· Pentium or Pentium II 166 MHz recommended
· 64MB of RAM, but if Active Directory and DNS need 96-128MB
· 2GB hard disk or partition dedicated to the RIS
· 10 or 100MBps NIC, 100Mbps preferred
======================================================================
winads15.html PAGE
5 2002/03/06
MICROSOFT WEB SITE:
Server hardware minimum requirements:
· Pentium III MHz processor or faster
· 256MB of RAM minimum
· 5GB hard drive minimum.
· 100 Mbps or Fibre Optic.
· NTFS File System
· Active Directory
· DNS Installed and operational
· DHCP working
IMPORTANT: A separate partition from the system’s boot partition is required to
install the RIS. RIS cannot be installed on the same drive as the system volume. The
volume you choose to install RIS onto must be formatted with the Windows NT file
system (NTFS). RIS only supports PCI.
Server Software Requirements
The following services can be installed either on individual servers or on the same server
and must be active and available:
· DNS
· DHCP
· Active Directory
Client Hardware Requirements:
· Pentium 166 MHz or faster processor Net PC client computers
· 32 Mb RAM (64MB recommended)
· 800 MB hard disk drive
· Supported PCI Plug and Play NIC
· Optional: PXE-based remote boot ROM version, 99c or later
Network Cards Supported by RIS Boot disk
======================================================================
winads15.html PAGE
6 2002/03/06
The RIS boot disk supports the following NIC cards:
· 3C900 (combo and TP0)
· 3C900B
· 3C905
· 3C905B
· 3C905C
AMD Nic adapters: AMD PCNet and Fast PC Net
*** See page 561 for
the adapters **
NOTE: The RIS boot disk generator only supported PCI-based network cards.
Industry Standard architecture (ISA), Extended Industry Standard Architecture (EISA),
and token ring cards are not supported.
Lesson Summary:
RIS architecture Windows 2000 services that are required to take advantage of the
Remote OS Installation feature.
Lesson 2:
Implementing RIS
· Set up RIS
· Configure RIS
· Create an RIPrep image
· Create an RIS boot disk (optional)
· Verify the RIS configuration
Setting up RIS
RIS requires a two-stage setup process: adding the RIS component and installing RIS.
You must authorize the RIS Server in the DHCP snap-in menu.
Setting RIS Clients Installation Options
By setting the RIS client installation options, you can control the options presented to
different groups of user during the CIW. There are four client installation options that
can appear on the CIW:
======================================================================
winads15.html PAGE
7 2002/03/06
· Automatic Setup
· Custom Setup
· Restart a Previous Setup Account
· Maintenance And Troubleshooting
CHOICE OPTIONS PROPERTIES
Under these options when the Choice Options Properties is displayed, you can only
select from three choices: Allow, Don’t Care and Deny.
Automatic Setup
The Automatic Setup option is the client installation option that all users of the Remote
OS Installation feature have access to by default.
While restricting installation options, you can still allow users to choose the OS for
installation. Remote OS Installation allows you to provide a friendly description and
associated help text that describes the OS options so that an end user can choose the
most appropriate OS.
Custom Setup
Similar to automatic, but it provides you with the ability to set up a computer for another
person within the organization.
Restart a Previous Setup Attempt
This is provided in the event that the installation of the OS fails for any reason. The CIW
can be customized to ask a series of questions about the specific OS being installed.
Maintenance and Troubleshooting
This provides a third-party hardware and software vendor tools. These tools range from
system BIOS flash updates and memory virus scanners to a wide range of computer
diagnostic tools that check for hardware-related problems.
The answer file has the extension .sif.
======================================================================
winads15.html PAGE
8 2002/03/06
Create a RIPrep Image
To build and maintain standard desktops, many organizations use disk imaging or cloning
software that allows you to configure a client computer exactly how you want it, and then
make a copy of the image for installation on client computers on the network.
Creating a Source Computer
To create a source computer, use the Remote OS Installation feature to remotely install the
base Windows 2000 Professional OS.
Configuring the Workstation
When creating RIPrep images, it is important to understand the relationship of user profiles,
the changes made to an RIPrep source computer, and the desired result for users that log on
to computers that are installed using the RIPrep image.
NOTE: If the source computer contains a 1 GB disk drive and the destination computer
contains a 2GB disk drive, by default RIS will format the destination computer’s drive as a
2 GB partition in the same file system format as the source computer used to create the image.
RIPrep requirements
The destination computer (the computer that installs the image posted to the RIS server) is not
required to contain hardware identical to that of the course computer that was used to create
the images.
The destination computer’s disk capacity must be equal to or larger than that of the sources
computer.
All copies of Microsoft software made or installed using RIS must be properly licensed.
RIPrep Limitations
2000 Professional installation to an available RIS server.
======================================================================
winads15.html PAGE
9 2002/03/06
available RIS servers.
before running the Remote Installation Preparation Wizard are not maintained in the installation
image. Modifications to replicated installation images are not supported.
NOTE: If the PID is not entered in the RIPPREP.SIF file, the installation process will stop
and prompt the user for the PID information during the installation of that RIPrep image.
Lesson 3:
Administering RIS
Administering RIS includes the following tasks:
· Managing RIS client installation images
· Managing RIS client computers
· Managing RIS security.
Managing RIS Client Installation Images
Managing RIS client installation images includes the following tasks:
Adding new client OS installation images
Associating unattended setup answer files
Prestaging RIS Client Computers
Prestaging an RIS client computer is the process of creating a valid client CAO within Active
Directory. By prestaging the client computer account in Active Directory, you can configure the
RIS servers to only respond to prestaged client computers.
Finding RIS Client Computers
You can search Active Directory for RIS client computer accounts using their computer name
or GUID. The Show Clients feature searches for all clients computers that are prestaged for
this RIS server. The search process can include the entire Active Directory structure or be
limited to a specific domain. Locating the GUID for Client Computers
======================================================================
winads15.html PAGE
10 2002/03/06
The computer’s GUID appears in the following areas:
· A label on the side of the computer case
· A label within the computer case
· The BIOS of the client computer.
Managing RIS Security
Setting permissions for creating prestaged and user-created computer accounts.
Setting permissions for joining computers created in the Computers container and OUs to the
domain.
Lesson 4:
RIS Frequently Asked Questions and Troubleshooting
*** see pages 587-
591 ***