Configure RIS Step-by-Step

RIS Step-by-Step

Published By :- Nandlal Rawani

This step-by-step article describes how to use Remote Installation Service (RIS) to install Windows Server 2003 on remote computers.
You can use RIS to remotely set up new Microsoft Windows Server 2003-based computers by using a RIS network shared folder as the source of the Windows Server 2003 files. You can install operating systems on remote boot-enabled client computers. Client computers are connected to the network, and are then started by using a Pre-Boot eXecution Environment (PXE)-capable network adapter or remote boot disk. The client then logs on with a valid user account.

RIS Hardware Requirements

The following is the minimum hardware that is required for the RIS server:

• The server must meet the minimum hardware requirements for the version of Windows Server 2003 that is installed.
• A four gigabyte (GB) drive that is dedicated to the RIS directory tree on the RIS server.
• A 10 or 100 megabit per second (Mbps) network adapter that supports TCP/IP. 100 Mbps is preferred.
  
  NOTE: Dedicate a whole hard disk or partition specifically to the RIS directory tree. SCSI-based disk controllers and disks are preferred.
  
  The drive on the server on which you will install RIS must be formatted with the NTFS file system. RIS requires a lot of disk space, and you cannot install it on the same drive or partition on which Windows Server 2003 is installed. Make sure that the chosen drive contains enough free disk space for at least one full set of the installation files for the operating system you plan to remotely install.

Client Hardware Requirements

The following list describes the minimum hardware that is required for RIS client computers:

• Meet the minimum operating system hardware requirements.
• PXE DHCP-based boot ROM version 1.00 or later network adapter, or a network adaptor that is supported by the RIS boot disk.
  
  NOTE: Always contact the manufacturer of your network adapter to obtain the latest version of the PXE DHCP-based boot ROM.

Software Requirements

Several network services must be active and available for RIS. You can install the following services either on the RIS server or on other servers that are available on the network:

• Domain Name System (DNS Service)
• Dynamic Host Configuration Protocol (DHCP)
• Active Directory "Directory" service

Prerequisites for Client Installations

Make sure that the client computer's network adapter has been set as the primary boot device in the computer BIOS. If the network adapter is configured as the primary boot device, the client requests a network service boot from the RIS server on the network when the client starts. After the client contacts the RIS, the client is prompted to press the F12 key to download the Client Installation Wizard. Do not press F12 unless you need a new operating system installation or access to maintenance and troubleshooting tools.
After the client operating system has been installed by using RIS, you can ignore the prompt to press F12 during future client computer startups. You can also reset the client BIOS so that the primary boot device is the floppy disk drive, the hard disk, or the CD-ROM drive.
To use the remote boot disk to start the installation, insert the boot disk into the floppy disk drive, and then start the client computer. The floppy disk drive must be set as the primary boot device in the client BIOS. After the computer starts from the disk, you are prompted to press F12 to start the network service boot process. You must remove the boot disk after you press F12 and before the text-mode portion of the operating system installation completes.
NOTE: You may have to press F12 on some Compaq computers during startup. In this case, you must press F12 on the Compaq startup screen, and then press F12 again when you are prompted by the RIS server.

Install Windows Server 2003 RIS

1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Click to select the Remote Installation Services check box, and then click Next.
   
   NOTE: If you are prompted for the Windows Server 2003 installation files, put the Windows Server 2003 CD-ROM in the CD-ROM drive, and then click OK. After you do so, you may receive a message with options for upgrading the operating system. Click No.
4. Click Finish, and then click Yes to restart your computer.

Set Up RIS

1. Log on as a user with administrative privileges.
2. Click Start, click Run, type risetup.exe, and then click OK to start the RIS Setup Wizard.
3. When the "Welcome" screen appears, click Next.
4. Type the drive letter and folder in which the RIS files are stored, and then click Next. For example, you might type E:\RemoteInstall, and then click Next.
5. After the RIS Setup Wizard copies the files, you are be prompted to enable or disable the RIS service, and the options are:
• Respond to client computers requesting service. If you select this option, RIS is enabled, and it will respond to client computers that are requesting service.
• Do not respond to unknown client computers. If you select this option, RIS only responds to known client computers.
6. Click Respond to client computers requesting service, and then click Next.
7. You are then prompted for the location of the client operating system installation files. Put the client operating system CD-ROM in the server CD-ROM drive, and then click Next.
   
   NOTE: Microsoft only supports the use of Microsoft media when creating a client operating system image. The use of non-Microsoft media is not supported.
8. Type the folder name for the client operating system installation files on the RIS server, and then click Next.
9. Type a friendly description for the operating system image. This is displayed to users after they start a remote client and run the Client Installation Wizard.
10. Click Next, click Finish, and then click Done.

Authorize RIS in Active Directory

After you install RIS, the RIS server must be authorized in Active Directory. Authorization determines control of which RIS servers can serve client computers on the network. If the RIS server is not authorized in Active Directory, client computers that request service cannot contact the RIS server.
NOTE: To authorize a RIS server in Active Directory, you must be logged on as an enterprise administrator or a domain administrator of the root domain.

1. Click Start, point to Administrative Tools, and then click DHCP.
2. In the left pane, right-click DHCP, and then click Manage Authorized Servers.

3. If your server is not listed, click Authorize, type the name or the IP address of the RIS server, and then click OK.

NOTE: If you are prompted to confirm the RIS server, verify the name and IP address, and then click OK.

4. Click Close, and then quit the DHCP console.

Set User Permissions

With RIS, clients can install their own client operating system. The users must also be granted permissions for creating computer accounts in the domain. To make it possible for users to create computer accounts anywhere in the domain:

1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. In the left pane, right-click your domain name, and then click Delegate Control.
3. In the Delegation of Control Wizard, click Next.
4. Click Add.
5. Type the name of the group that requires permission to add computer accounts to the domain, and then click OK.
6. Click Next.
7. Click to select the Join a computer to the domain check box, and then click Next.
8. Click Finish.

Install Clients By Using RIS

This section describes how to install a client operating system on a computer that contains a network adapter that supports PXE DHCP-based boot ROM. To install a client operating system:

1. Make sure that the network adapter is set as the primary boot device in the computer BIOS.
2. Restart the client computer from the network adapter.
3. When you are prompted to do so, press F12 to start the download of the Client Installation Wizard.
4. At the "Welcome" screen, press ENTER.
5. Type a user name that has permissions to add computer accounts to the domain, and then type the domain name and password for this user.
6. Press ENTER.
7. When you receive a warning message that states that all data on the client computer hard disk will be deleted, press ENTER.
8. A computer account and a global unique ID for this workstation are displayed. Press ENTER to start Setup.
9. If you are prompted to do so, follow the instructions on the screen to complete the client operating system installation.

Remote Installation Boot Disk Option

You can use the remote installation boot disk with computers that do not contain a network adapter that supports PXE DHCP-based boot ROM. The boot disk is designed to simulate the PXE startup process.
Rbfg.exe is a utility for creating network installation disks, and it is located in the RemoteInstall\Admin folder on every RIS server.

Creating a Boot Disk By Using the Windows Remote Boot Disk Generator

To create a remote installation boot disk:

1. Locate the drive:\RemoteInstall\Admin\I386 folder on the RIS server, where drive is the drive on which RIS is installed.
2. Double-click the Rbfg.exe file.
3. Put a floppy disk in the floppy disk drive, and then click Create Disk.
4. When you prompted to create another disk, click No, and then click Close.

NOTE: To view a list of supported network adapters, click Adapter List. You cannot add network adapters to this list.

Creating an installation image with RIPrep

Updated: January 21, 2005

Creating an installation image with RIPrep

With the Remote Installation Preparation (RIPrep) Wizard, you can create an image of an existing installation and replicate that image to an available Remote Installation Services (RIS) server on the network. To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. You must also have permission to write to the RIS folders on the RIS server (the default name for the folder that contains all the RIS folders is RemoteInstall).One way to ensure that you have permission to write to the RIS folders on the RIS server is to be explicitly assigned the permission. Another way is to have membership in the local Administrators group on the RIS server. For more information, see Default local groups and Default groups.

1. It is recommended that you start by using RIS to install the operating system that you have chosen for the installation image. RIPrep can be used to create images only for the particular operating systems it supports, however. For complete information on which operating systems RIPrep supports, see Operating systems supported by Remote Installation Services.
   It is not necessary to install the operating system using RIS; you can install it from the CD instead.
2. After you have installed the operating system, you should install the client computer applications that you want to deploy with clients.
   Important
• If you want to install applications that do not comply with the Windows Installer technology, this is the step at which you should do so. You can also install applications that do comply with the Windows Installer technology.
3. After you have installed the appropriate client computer applications, you should configure the source computer to conform to any required company desktop standards. For example, you might want to define specific screen colors, set the background bitmap to a company-based logo, remove any games installed by the base operating system, or configure Internet Explorer proxy settings. To save your desktop configuration, copy to the Default User profile the profile of the user who was logged in while the configuration changes were made. For instructions on how to copy user profiles, see Copy a user profile.
   Important
• Before starting the Remote Installation Preparation Wizard, be sure to remove all confidential information from the source client computer.
4. You should then close all applications and run the Remote Installation Preparation Wizard. For more information, see Create a Remote Installation Preparation Wizard image.
5. The wizard configures the source computer to a generic state, removing anything that is unique to the client installation, such as the computer's unique security identifier (SID), computer name, and any registry settings unique to the client source computer.
6. The wizard then prompts you for the installation information required by the image-creation process. This information includes the location where the client installation image should be replicated, the name of the directory it should be copied to on the server, and a friendly description and associated Help text that will describe the installation image to users who run the Client Installation Wizard.
   Because of memory limitations during the remote boot process, there are limits to the total text you can provide for a set of installation image choices. With a relatively large number of installation image choices, the friendly descriptions and Help text must be limited in length; with fewer choices, the friendly descriptions and Help text can be longer. It is not unusual to encounter these limits to total text when the number of installation image choices for client computers reaches approximately 12 to 16.
7. After the replication is complete, the installation image is automatically added to the list of available operating system installation options and is available to client computers that use the remote boot technology. When you create new images using RIPrep, the image is available only to client computers that have the same type of Hardware Abstraction Layer (HAL). Images that were created using RIPrep are available to all clients that are authorized to view them.
   Note
• A remote boot-enabled client computer need not contain hardware that is identical (other than the HAL) to that of the source computer used to create the installation image. The Remote Installation Preparation Wizard uses the Plug and Play feature to detect any differences between the source and destination computers' hardware during the image installation process. This ensures that, for any Plug and Play device, the correct device driver is installed.
8. You can control the installation choices available to clients by setting access control permissions on the installation image .sif files or, for greater control, on the folders that contain the installation image. For more information, see Allow or prevent the installing of a RIS image by a user or group and Allow or prevent the viewing and installing of a RIS image by a user or group.

Factors to consider when planning for RIPrep

The following sections describe factors to consider when planning to create an installation image with RIPrep. These include:

• Requirements for the RIPrep replication process
• Installation images, the product identification number, and licensing
• Disk characteristics on the source client computer and the destination computers

Requirements for the RIPrep replication process

When planning to run RIPrep, it is important to understand requirements that must be met by the source client computer, the image, and the medium onto which the image is replicated.

• The Remote Installation Preparation Wizard currently supports the replication of a single disk and a single boot partition of an installation to a single RIS server. This means that the operating system and all of the applications that make up the standard installation image must reside on a single partition of the source client computer.
• The files on the source client computer must not be encrypted. Replication of encrypted files is not supported.
• Modifications to replicated installation images are not supported.
• The wizard allows source image replication only to available RIS servers. Currently, source replication to alternate drives or media types is not supported.

Installation images, the product identification number, and licensing

• When you use the Remote Installation Preparation Wizard (RIPrep) to create an installation image of a client computer that was originally installed using a retail version of the operating system, you must modify the RIS unattended setup answer file (sif) to include the product identification number (PID). The PID is the unique identification number specific to each copy of the operating system.
  If the PID is not entered in the .sif file, the installation process will stop and prompt the user for the product identifier information during the installation of that RIPrep image. To prevent prompting your users for the PID, add the product identifier to the [UserData] section of the .sif file associated with this installation image.
  For example, you would type the following (including the dashes and quotation marks) into the [UserData] section of the .sif file:
  ProductKey = "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
  For more information about product activation, see Windows Product Activation.
• The source client computer will shut down when the image replication process is complete. The abbreviated Setup program runs automatically when the source computer restarts. You must complete the setup process if you want to use this client computer to create another installation image. You can create additional installation images only three times if you are using a Retail PID. A volume licensing PID permits you to create installation images more than three times, however.
• All copies of Microsoft software made or installed using RIS must be properly licensed. All copies of non-Microsoft software made or installed using RIS must also be properly licensed; it is the licensee's obligation to ensure that non-Microsoft software is licensed to make any such copies.

Disk characteristics on the source client computer and the destination computers

When planning to run RIPrep, it is important to study the disk configuration that exists on the source client computer and then compare it to the disk configurations on the client computers on which the image will be installed. The following requirements apply:

• The destination computer's disk capacity must be equal to or greater than that of the source computer.
• The RIPrep installation image maintains the volume and partition characteristics of the disk on the source computer.
  The following example illustrates this, but describes the use of the file allocation table (FAT) and FAT32 file systems, which are not recommended. The recommended file system for RIS is the NTFS file system. The example is as follows. If you create an installation image from a source computer with a 2-gigabyte (GB) FAT volume, and you then install the image on a client computer with a 4-GB drive, the resulting installation will format the drive as a 4-GB volume using FAT32. The change in the destination computer file system type is dictated by the limits of the FAT file system. This type of change in the destination computer file system type (from FAT to another file system) does not work if the destination volume is larger than 32 GB. For destination volumes larger than 32 GB, the source computer must use the NTFS file system. For more information about file system compatibility and limitations, see Choosing a file system: NTFS, FAT, or FAT32.
• Disk preparation of the destination computer must be identical to that of the source computer; any remaining disk capacity on the destination computer will be formatted unless you follow the instructions in the next item in this list. For example, if the source computer's disk capacity is 1 GB and the disk capacity of the destination computer is 2 GB, the entire 2 GB will be formatted on the destination computer.
• You can change the information in the .sif file associated with an installation image to restrict the disk reformatting so that it will be the same as that which the source computer used to create the installation image. For example, open the Riprep.sif file located in the \\Server_name\REMINST\Setup\Applicable language\Images\Applicable image name\I386\Templates\Riprep.sif folder and modify the UseWholeDisk parameter to equal NO. When a client computer installs this image, the disk will be formatted to match the capacity of the source computer, and the remainder of the destination computer's disk will be unformatted.