Windows 2000 Remote OS Installation via RIS

Microsoft Windows 2000 uses Remote Installation Services (RIS) to automate the deployment of operating system images to client computers across a local area network without requiring physical media. By integrating core infrastructure services—such as the Preboot Execution Environment (PXE), Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory—RIS provides a centralized framework to deploy standardized desktop configurations. This article breaks down the foundational architecture of RIS and explains the sequential process Windows 2000 follows to initiate, authenticate, and complete remote network installations.

Key Infrastructure Components

A functional Windows 2000 RIS deployment relies on several interconnected network services:

  • Active Directory: Authenticates users, authorizes RIS servers, and correlates client hardware using Globally Unique Identifiers (GUIDs).
  • DHCP Server: Allocates IP configuration to client machines and directs PXE-enabled clients to the RIS server.
  • DNS: Resolves server names and network resource locations across the Active Directory domain.
  • Boot Information Negotiation Layer (BINL): A specialized Windows 2000 service that responds to client boot requests, checks Active Directory for pre-staged computer accounts, and delivers appropriate boot parameters.
  • Trivial File Transfer Protocol (TFTP): A lightweight protocol used to transfer initial boot files and network drivers to the client before the full network stack is initialized.
  • Single Instance Storage (SIS): A file-system filter driver that minimizes disk space usage on the RIS server by eliminating duplicate files across multiple OS images.

The Remote Installation Execution Process

The remote installation workflow proceeds through six distinct stages:

1. PXE Initialization and DHCP Discovery

The target machine powers on, and its PXE-enabled Network Interface Card (NIC) broadcasts a standard DHCPDISCOVER packet containing PXE-specific option flags (Option 60). The network's DHCP server responds with a standard IP address, subnet mask, and default gateway.

2. BINL Discovery and Contact

Simultaneously, the RIS server's BINL service detects the client's PXE discovery broadcast. BINL replies to the client on UDP port 4011, providing the IP address of the RIS boot server and the name of the Network Bootstrap Program (NBP), typically Startrom.com.

3. Bootstrap and Boot File Transfer via TFTP

Using the network parameters obtained during DHCP negotiation, the client connects to the RIS server via TFTP. It downloads the initial bootstrap program into RAM:

  • If the client is configured to prompt the user (such as pressing F12 to network boot), Startrom.com waits for user confirmation before proceeding.
  • The bootstrap loader then requests and downloads Oscfilter.n12 and the Client Installation Wizard (CIW) files via TFTP.

4. Active Directory Authentication and Image Selection

The client executes the Client Installation Wizard (OS Chooser), which provides a text-based interface. The user is prompted to enter Active Directory domain credentials.

Upon entry, the BINL service validates the credentials against Active Directory. Based on the user's group policies and permissions, BINL returns a customized menu listing available RIS images. Windows 2000 RIS supports two types of images:

  • CD-based Images: Standard Windows 2000 Professional installations generated using the RIS Setup (Ristndrd.sif) script.
  • RIPrep Images: Customized, pre-configured desktop images that include installed applications and desktop settings, captured using the Remote Installation Preparation (RIPrep) tool.

5. Kernel Loading and Setup Initialization

Once an image is selected, the client downloads Setupldr.exe and the Windows 2000 kernel files through TFTP. Setupldr.exe switches the processor into 32-bit protected mode, creates a temporary RAM disk, and loads the native network card driver embedded within the RIS image.

Once the network driver initializes, the client transitions away from TFTP and establishes a standard Server Message Block (SMB) connection directly to the RIS server’s REMINST share.

6. Operating System Deployment and Finalization

Depending on whether a CD-based or RIPrep image was chosen, Windows 2000 executes the installation:

  • For CD-based installations: Standard Windows 2000 Setup partitions and formats the target disk, copies the installation files over SMB, and processes unattended answers provided by the RIS template.
  • For RIPrep installations: The imaging engine copies the pre-captured disk contents and applies unique System Identification (SID) generation routines.

After copying all required files, the client computer restarts, completes the automated hardware detection and Plug and Play phases, joins the Active Directory domain, and boots to the Windows 2000 desktop.