Professional Documents
Culture Documents
In Windows 2000, Remote OS Installation is part of change and configuration management. Remote
OS Installation simplifies the task of installing the Windows 2000 Professional operating system on
PXE-based remote boot–enabled client computers throughout the organization. It allows computers
to connect to a networked server during initial start-up, and then it allows the server to perform a
local installation of Windows 2000 Professional.
Remote Installation Services (RIS) is the technology that is used during initial start-up before the
resident operating system loads. RIS supports clients without an initial operating system or failed
computers that need to have the operating system restored. RIS allows computer hardware
connected through a LAN to find a networked RIS server and request installation of a new copy of
Windows 2000 Professional appropriately configured for the user and computer. Remote OS
Installation cannot be used to upgrade an existing operating system.
Remote OS Installation uses these key technologies to install Windows 2000 Professional on a
computer:
• Active Directory
• Group Policy
• Using a bootable CD
These methods are not discussed in detail in this chapter. For more information about installing and
upgrading an operating system by using these methods, see "Automating Server Installation and
Upgrade," "Automating Client Installation and Upgrade," and "Using Systems Management Server to
Deploy Windows 2000" in the Microsoft ® Windows ® 2000 Server Resource Kit Deployment
Planning Guide . For more information about upgrading Windows 2000 on an existing Windows 2000
Professional client, see "Software Installation and Maintenance" in this book.
Hardware Requirements
Ensure that both your server and client hardware meet the minimum installation hardware
requirements for Windows 2000. For more information about Remote OS Installation hardware
requirements and compatible computers or network adapters, see the Hardware Compatibility List
link on the Web Resources page at
http://windows.microsoft.com/windows2000/reskit/webresources .
In addition, be sure that your server and client hardware meet the requirements in the following
sections.
• Pentium or Pentium II 200 megahertz (MHz) or faster processor (Pentium 166 MHz minimum).
96 to 128 megabytes (MB) of random access memory (RAM) needed to run when services such
•
as Active Directory, DHCP, and DNS are installed.
• 2-gigabyte (GB) disk drive for the Remote Installation Services servers folder tree.
RIS Components
The following are the various components that you use to install, configure, and implement RIS
within your organization:
Remote Installation Services Setup (RISetup.exe) You can install RIS at the same time or
after you install Windows 2000 Server by using Add/Remove Programs in Control Panel .
Remote Installation Preparation Wizard (RIPrep.exe) RIPrep allows you to create a
customized image of a Windows 2000 Professional computer. Imaging Windows 2000 Professional
means creating a replica of a hard disk that you can then install on other computers in your
organization. You can use this wizard to prepare an existing Windows 2000 Professional installation
image and to replicate that image to an available RIS server on the network. The image can include
the operating system alone or it can be a preconfigured desktop image, including the operating
system and standard locally-installed desktop applications.
Client Installation Wizard (OSChooser) OSChooser is the client-side (the part that is
downloaded to the client) text-based program that communicates with the RIS server. The Client
Installation Wizard is a default set of screens that the Boot Information Negotiation Layer (BINL),
the server-side service, sends to the client to guide the user through the remote installation
process. Users of remote boot–enabled clients use the Client Installation Wizard to log on and select
from operating system installation options. You can customize the setup screens to meet the needs
of your organization.
RIS Services
RIS comprises individual services that have been combined to enable the remote installation of
Windows 2000 Professional. The Remote Installation Setup Wizard (RISetup) configures and starts
the following services:
Boot Information Negotiation Layer (BINL) This service listens for and answers DHCP (PXE)
requests. It also services Client Installation Wizard requests. BINL directs the client to the files
needed to start the installation process. This service also checks Active Directory to verify
credentials, determine whether a client needs service, and whether to create a new or to reset an
existing computer account object on behalf of the client.
Trivial File Transfer Protocol Daemon (TFTPD) A RIS server uses TFTP to download the initial
files needed to begin the remote installation process to the client. This includes the Client
Installation Wizard and all files needed to start Windows 2000 Setup. The first file downloaded to
the client using TFTP is Startrom.com. Startrom is a small bootstrap program that displays the
Press F12 for Network Service Boot prompt. If F12 is pressed within three seconds, the Client
Installation Wizard (OSChooser) is downloaded to begin the remote installation process. When it
resides on the server side, it is called the Trivial File Transfer Protocol Daemon (TFTPD), and when it
resides on the client, it is called Trivial File Transfer Protocol (TFTP).
Single Instance Store (SIS) SIS services consist of an NTFS file system filter and a service that
acts on the volume on which the RIS images are kept. SIS services reduce the storage requirements
needed to store these images by combining duplicate files.
Installing RIS
You can install Remote Installation Services either on a Windows 2000 server that is already on a
network or on a stand-alone server that you want to add to the network.
To install the RIS component
1. From the Start menu, point to Settings , and then point to Control Panel .
2. Double-click Add/Remove Programs, and then click Add/Remove Components.
3. Check the box for Remote Installation Services .
4. Click Next .
5. Click Finish , and then Restart your server. After the server has restarted, complete the
Configure Remote Installation Services wizard.
RISetup locates the first NTFS volume that does not contain the system volume (boot.ini file) or the
boot volume (%windir%). You then define image properties such as directory name, friendly
description, and Help text for the end user. None of these properties can contain any non-ASCII
characters. For more information about the Client Installation Wizard variables, see "OSCML and
Client Installation Wizard Variables" in this book. This process also creates the RIS directory
structure and copies the files required for a CD-based "flat" installation image of Windows 2000
Professional. This process also copies the default Client Installation Wizard screens and configures
and starts all of the services required for RIS (BINL, SIS filter, SIS Groveler, and TFTP).
For more information about installing and configuring RIS servers and DNS, see Windows 2000
Server Help. Windows 2000 Server Help also provides instructions for promoting a stand-alone
server to a domain controller and installing and configuring the DHCP service.
For more information about the Client Installation Wizard, see "Client Installation Wizard" later in
this chapter.
%# Incremental number
GUID Format
Valid characters for the client GUID are restricted to the hexadecimal characters 0-9 and A-F
(uppercase or lowercase). You can enter the GUID in either "pretty print" or "raw byte order"
format. However, combining the two formats causes RIS to not recognize the client.
Top of page
Pretty Print
Pretty print format is as follows:
{dddddddd-dddd-dddd-dddd-dddddddddddd}
where d is a hexadecimal character. For example, {921FB974-ED42-11BE-BACD-00AA0057B223}.
The dashes are optional and spaces are ignored.
Top of page
• Read permissions
Create computer
•
objects
Users can also install an operating system image on their prestaged client if they have been granted
the ability to read and write all properties on the specific computer object (not the container) that
was created when the client was prestaged. The user also requires the ability to reset and change
password rights on the computer object. (An administrator might need to reset the user account.)
• Easy to use.
RIPrep Considerations
If you plan to use RIPrep to create operating systems in your organization, keep the following
considerations in mind:
RIPrep supports replication of a single disk, single partition (the boot partition, which is usually
•
drive C) of Windows 2000 Professional. Because of this, the operating system and all of the
applications that make up the standard installation must reside on the boot partition prior to
running the RIPrep wizard. By creating a RIPrep image, you can install and configure the
operating system, locally-installed applications and configuration settings once for deployment to
many clients.
RIPrep-based images generally use more hard disk space than CD-based images because they
•
contain an uncompressed copy of the client system's hard disk stored on the server. CD-based
flat images still contain the compressed installation files that the CD contains.
To store a RIPrep image on a server, you must also have a CD-based image that is the same
•
version and default language stored on the same RIS server. This is because the answer file used
for the RIPrep image also refers the client to the CD-based image for access to network adapter
and text-mode boot drivers, in case the drivers required for the client installing the RIPrep image
are different from those in the system used to create the RIPrep image. The text-mode setup
then does an advanced Xcopy of the client's image to the client's hard disk drive. (Text-mode
setup is the normal blue screen you see when installing Windows 2000 Professional that moves or
copies all the files over before the graphical user interface setup begins.)
One of the beneficial features of the RIPrep wizard is that the destination client, that is, the
•
computer that is installing the RIPrep image, does not need to contain identical hardware as that
of the source computer used to create the image. However, the hardware abstraction layer (HAL)
drivers must be the same. The RIPrep wizard uses the new Plug and Play support that is included
with Windows 2000 for detecting any differences between the source and the client hardware
during image installation.
To create a RIPrep image, a source computer is required. The source computer contains the
•
Windows 2000 Professional operating system, locally-installed applications, and any configured
system settings that represent a standard client configuration you want to deploy to the specific
clients. Carefully configure and test this image before running the RIPrep wizard to create the
RIPrep image. After the image is replicated to the RIS server, you cannot alter its configuration
without rerunning the RIPrep wizard against the existing image.
Top of page
• Network settings
• Security settings
• User settings
• Desktop settings
Configure the source computer to adhere to any company configuration policies. For example,
you might choose to define specific screen colors, set the background bitmap to a company-
based logo, and set intranet proxy server settings in Microsoft® Internet Explorer 5.
4. Install all applications that you want to be a part of this image. If you have applications that are
Windows Installer (.msi) packages and you want the applications to be installed in a managed
state, see the following section. Install all the applications from the location that should be used
when looking for updates or additional files, rather than a temporary location such as a local
CD-ROM drive that is not available on clients installing the RIPrep image. For example, you can
install Microsoft® Office 2000 and virus protection software for all users who require these
applications on the computer.
5. Test the source computer to ensure that the configuration is exactly how you want it to be for
the group of users who will access this image. RIPrep images cannot be modified after they are
created, so if your image fails your test process, you must recreate the image or restore the
existing RIPrep image, make the necessary adjustments, and run the RIPrep wizard again to
create a new image that contains the additional changes. If it is appropriate, you can overwrite
the existing image on the RIS server when you create the new image
6. Run the RIPrep wizard to create the RIPrep image on the server.
7. Configure user access to the image by setting permissions in the ristnrd.sif file in the Templates
folder of the new RIPrep image. For more information, see "Setting Security Permissions in
Answer Files" later in this chapter.
Top of page
-Or-
In Regedt32.exe, click the entry, click Edit , and then click the appropriate menu choice.
Caution
Do not use a registry editor to edit the registry directly unless you have no alternative. The registry
editors bypass the standard safeguards provided by administrative tools. These safeguards prevent
you from entering conflicting settings or settings that are likely to degrade performance or damage
your system. Editing the registry directly can have serious, unexpected consequences that can
prevent the system from starting and require that you reinstall Windows 2000. To configure or
customize Windows 2000, use the programs in Control Panel or Microsoft Management Console
(MMC) whenever possible.
The administrator restarts the computer, and Software Installation and Maintenance installs
Office 2000 (applications assigned to a computer install when the computer starts). After
Office 2000 installation is complete, the administrator can take the computer running Windows 2000
with Office 2000 installed, and use RIPrep to build a Remote OS Installation image and put the
image on a RIS server.
When the resulting RIPrep image is installed on destination clients, as long as the same Group
Policy objects are applied to the destination computers, the applications remain in a managed state
and can be managed, updated, or patched using the Software Installation and Maintenance
features. It is recommended that you use Software Installation and Maintenance to install, update,
and manage all applications that you install in RIPrep images.
For more information about software installation, see "Software Installation and Maintenance" in this
book.
Top of page