How RIS Deployed Windows XP Across Networks

Remote Installation Services (RIS), introduced in Windows 2000 Server and extended in Windows Server 2003, provided network administrators with an automated mechanism to deploy Windows XP without physical media. By leveraging Preboot Execution Environment (PXE) technology, Dynamic Host Configuration Protocol (DHCP), Trivial File Transfer Protocol (TFTP), and Active Directory, RIS enabled client computers to boot over a local area network, authenticate against domain controllers, and execute unattended installations of Windows XP from centralized server repositories.

Network Boot and DHCP Discovery

The deployment process began when a client machine initialized a PXE-enabled Network Interface Card (NIC). The client broadcasted a DHCP discover packet across the local network requesting an IP address and PXE boot server information. The DHCP server responded with standard IP configuration details along with DHCP options pointing to the RIS server: Option 66 (Boot Server Host Name) and Option 67 (Bootfile Name, typically startrom.com or oschoice.exe).

TFTP Transfer and Client Initialization

Once the client acquired network configuration, it contacted the RIS server using TFTP to download the bootstrap code. The server transmitted the Client Installation Wizard (CIW), which executed directly in memory before any operating system was loaded.

The CIW presented a text-based interface to the user or technician, requiring Active Directory domain credentials. This authentication step prevented unauthorized network installations and determined which operating system images the user had permission to install based on Access Control Lists (ACLs) defined in the RIS configuration.

Active Directory Integration and Computer Staging

After successful authentication, the RIS server queried Active Directory. RIS checked whether the computer was prestaged—a process where an administrator pre-created a computer account using the client machine's Globally Unique Identifier (GUID) derived from its BIOS or network card.

If prestaged, the computer joined the domain under the preconfigured name and Organizational Unit (OU). If not prestaged, RIS used automated naming formats (such as user initials combined with sequential numbers) defined in the server's configuration to generate a new computer account in Active Directory.

Image Types and Deployment Execution

RIS supported two distinct image formats for deploying Windows XP:

CD-Based Images (Flat Images): Created using the risetup.exe utility, these were direct copies of the Windows XP installation media stored on the RIS server. Deployment functioned like a standard unattended installation driven by a Setup Information File (.sif). The installation booted into text-mode setup, partitioned the hard drive, formatted it (usually with NTFS), and copied files over Server Message Block (SMB/CIFS) shares.
Remote Installation Preparation (RIPrep) Images: Created using the riprep.exe tool, these were customized system-state images taken from a fully configured reference machine running Windows XP. RIPrep stripped machine-specific identifiers (such as Computer Names and Security Identifiers, or SIDs) and hardware abstraction layer (HAL) dependencies. When deployed, the image cloned the operating system, applications, and desktop settings, then generated unique SIDs during the initial boot phase.

Finalizing the Installation

Once the base files were copied and the client machine rebooted, the standard Windows XP mini-setup executed in GUI mode. It read the corresponding .sif file to silently populate settings such as regional options, network configurations, product keys, and display resolutions. The machine then completed domain join operations and applied Group Policies upon its first administrative login.