Windows 2000 RIS Automated OS Deployment

Remote Installation Services (RIS) in Microsoft Windows 2000 provides an integrated framework that enables administrators to deploy operating systems to client computers remotely over a local area network. By combining Preboot Execution Environment (PXE) technology, Active Directory, DHCP, and DNS, RIS eliminates the need for physical media like CDs or floppy disks during desktop rollouts. This article examines the core architecture, essential infrastructure prerequisites, and the sequential process by which Windows 2000 utilizes RIS to achieve standardized, hands-free client installations.

Core Infrastructure Prerequisites

To function, RIS depends on several Windows 2000 network services working in tandem:

  • Active Directory: Locates RIS servers, stores computer account objects, and enforces security policies to determine which users can deploy operating systems.
  • Domain Name System (DNS): Resolves service locations and domain controller addresses required during domain join operations.
  • Dynamic Host Configuration Protocol (DHCP): Leases IP addresses to booting PXE clients and points them to available RIS servers via specific DHCP scope options.
  • Dedicated NTFS Volume: RIS requires a dedicated, non-system NTFS partition to store installation images, maintaining file security and Single Instance Storage (SIS) to eliminate duplicate files across images.

The Deployment Process

Automated OS deployment via Windows 2000 RIS follows a multi-step execution cycle:

  1. PXE Network Boot: The client machine powers on and executes its PXE-enabled Network Interface Card (NIC) firmware. It broadcasts a standard DHCP discover packet containing a PXE client identifier.
  2. DHCP and BINL Negotiation: The DHCP server issues an IP address, while the RIS server's Boot Information Negotiation Layer (BINL) service detects the PXE request and responds with its own IP and the name of the network bootstrap file (startrom.com).
  3. Bootstrapping via TFTP: The client downloads the boot file and the Client Installation Wizard (OSChooser) using Trivial File Transfer Protocol (TFTP).
  4. Authentication and Image Selection: OSChooser prompts the user for domain credentials. Once authenticated against Active Directory, RIS presents an installation menu listing the specific OS images the user has permissions to deploy.
  5. Unattended Installation: After selecting an image, the client downloads the Windows setup files. RIS passes an automated answer file (.sif, such as ristndrd.sif) to the installer. This script pre-configures computer names, product keys, regional settings, and domain-join parameters, completing the Windows 2000 installation without requiring human intervention.

RIS Image Types

Windows 2000 RIS supports two primary image formats to accommodate different deployment scenarios:

  • CD-Based Images: Created directly from the original Windows 2000 Professional installation media using the RIS setup tool (risetup.exe). These provide a clean, standard operating system base that runs through a scripted installation process.
  • Remote Installation Preparation (RIPrep) Images: Created using the RIPrep utility (riprep.exe) on a reference computer that has already been configured with local settings, desktop customizations, and core line-of-business applications. RIPrep strips machine-specific identifiers (such as Security Identifiers, or SIDs) and replicates the disk state onto the RIS server, allowing for faster, fully configured deployments.