Windows 2000 Remote Installation Services

Planning and Prerequisites

Remote Installation Services (RIS) is the Windows 2000 Server feature that lets administrators push the Windows 2000 Professional image out over a LAN without touching a floppy or DVD on every machine. The idea is simple: a client machine boots from the network, discovers an RIS host, downloads the OS files, and installs itself automatically. In practice, a well‑planned deployment saves hours of manual work, eliminates the need for media, and guarantees consistent images across the organization.

The foundation of a RIS setup is a combination of networking services and a dedicated storage area for the image files. Before you even start installing the component, make sure the following infrastructure is in place:

• DHCP – RIS relies on DHCP to assign an IP address and to point the client to the TFTP server that holds the boot files. A properly configured DHCP server also needs the “Boot File” option set to the name of the PXE boot program (usually “pxelinux.0” or “pxeboot.com”).
• DNS – The client must resolve the name of the RIS server. Make sure the server’s hostname is registered in the DNS zone that the client queries.
• Active Directory – RIS integrates with AD for computer account creation, security filtering, and delegation. A domain controller must be reachable from the client and the RIS host.
• NTFS Partition – RIS stores the Windows image files on a dedicated NTFS volume that is separate from the system partition. The volume should be at least 800 MB, but a 2 GB or larger drive is recommended if you plan to keep multiple images. The partition must be formatted beforehand; RIS will not format it for you.
• Network Boot Capability – The client NIC should support PXE (Preboot Execution Environment). If the NIC is not PXE‑ready, you can install a USB boot disk, but that defeats the purpose of a fully network‑based deployment.
• Administrative Rights – The account used to install and configure RIS needs full control over the server, DHCP, and AD. The same account will be used to delegate rights to other users later.

  Once these prerequisites are verified, you’ll have a clean slate to install RIS. In the next section you’ll walk through the actual installation, configuration, and initial authorization steps that turn the server into a functioning deployment hub.

  Installing and Configuring RIS

  The first step is to add the RIS component to Windows 2000 Server. Start by launching the “Add/Remove Windows Components” wizard from the Control Panel. Find the Remote Installation Services checkbox, click Next, and let the wizard finish installing the necessary files. If the installation media isn’t on a local drive, point the wizard to the folder that contains the files, such as a mapped network share.

  After the component is installed, reboot the server. On startup, the RIS service registers itself with the operating system but remains unconfigured. To begin the configuration process, open the “Remote Installation Services” console from Administrative Tools or run risetup.exe directly. The console presents a familiar wizard interface.

  In the first step of the wizard, you specify the source location for the Windows 2000 files. You can point this to the original installation media or to an existing folder on the server that already contains the OS files. The wizard will scan the folder and verify that the required files are present.

  The next prompt asks whether RIS should respond to client requests. Check “Respond to Client Requesting Service” to enable the service. If you have other RIS or BootP servers on the network, or if you only want trusted machines to install, you can limit the service to known or pre‑staged clients. “Known” clients are those that already have a computer account in Active Directory. “Pre‑staged” clients are those that have a computer object created but are not yet connected to the network.

  After setting the response filter, you’ll be asked to provide the destination for the installation files. Browse to the NTFS partition you prepared earlier, create a folder name that reflects the purpose of the image (e.g., “Win2000Pro”), and click Finish. The wizard will copy the OS files to the destination and perform final integrity checks. This process can take several minutes; don’t interrupt it.

  Once the wizard reports success, you must authorize the server for DHCP. Open the DHCP console, navigate to the server node, right‑click, and select “Manage Authorized Servers.” If the RIS server is not listed, click “Authorize,” type in the server’s IP address, and confirm. This step allows the server to issue DHCP leases that point clients to the RIS boot files.

  The last step in the wizard is optional delegation. If you plan to let other users run their own installations, open Active Directory Users and Computers, right‑click the domain root, and choose “Delegate Control.” Follow the wizard to grant the “Join a Computer to the Domain” permission to a group or individual. Those users can then create computer objects during the RIS deployment, which is essential for an unattended installation that automatically joins the domain.

  With these steps complete, the RIS server is fully operational and ready to accept client boot requests.

  Deploying Unattended Images and User Delegation

  To make a deployment truly unattended, you need a SIF file that tells the installer which product key to use, what domain to join, and how to configure networking. The Windows 2000 Server CD includes a Setup Manager utility that can create this file. Run setupmgr.exe from the support/tools/deploy directory on the disk and point it to an empty folder on the server. Copy the setupmgr.dll from the CD into that folder, then launch Setup Manager.

  During the wizard, select “Create a new SIF file” and follow the prompts. When the wizard finishes, you’ll have a file named unattend.txt. Rename the file to match the name of the image folder (for example, Win2000Pro.sif). Edit the file and add a line for the product key: ProductID=12345-67890-12345-67890-12345, replacing the placeholders with a valid Microsoft product key. The installer will prompt for the key only if it’s missing, so including it guarantees a fully automated install.

  Place the SIF file in the same folder that contains the OS files. When a client boots, RIS automatically looks for a SIF file that matches the image name. If found, the installer reads the configuration and proceeds without user interaction.

  For users who need to deploy machines on their own, delegate the “Remote OS Installation” permission in the RIS console. Right‑click the server node, choose “Delegate Control,” and add the users or groups who should be able to run installations. Grant them the “Respond to Client Requesting Service” permission so that they can trigger RIS from the client side. Once authorized, these users can boot a client, let it contact the RIS server, and have the machine automatically install Windows 2000 Professional, join the domain, and apply the settings specified in the SIF file.

  When the deployment is finished, you can verify that the computer accounts were created by checking Active Directory Users and Computers. The new objects should be under the Computers container and will have the correct properties set during the installation.

  Additional resources are available for advanced scenarios, such as creating multiple images, customizing the UI, or integrating third‑party tools. Microsoft’s “Technical Guide to Remote Installation Services” white paper offers deeper insight into the architecture and troubleshooting tips. For a more user‑friendly overview, the NetworkNewz Remote Install Guide provides step‑by‑step screenshots and common pitfalls to avoid.

  By following these steps, you’ll have a robust RIS environment that delivers consistent, unattended Windows 2000 installations across your network, saves time, and reduces the need for manual media handling.