The Remote Installation Service-ris of Windows is used to manage and distribute windows professional image files. When Remote-guided RIS are enabled, they can connect to the RIS server (which can be a controller or standalone server), receive a list of available image files, and then perform network-based installation.
RIS needs a service to run:
DHCP --- assign IP addresses to RIS customers
DNS --- Locate Directory Service
Active Directory --- locate RIS server and other existing RIS customers
Once RIS runs, the following services also run together:
1. Boot Information Negotiation layer (binl)
Monitors customers' Remote Installation requests and RIS Management
2. Single Instance store (SIS)
It is used to manage image files, eliminate duplicate files, and reduce the image size. When duplicate files exist, the original files are copied to the SIS store, and the others are only linked to the SIS store.
3. Trivial File Transfer Protocol (TFTP)
Download the client Installation Wizard to start the Remote Installation Process
RIS Working Process:
1. The RIS client obtains the IP address from DHCP and requests the IP address of the RIS server.
2. RIS customers contact RIS Server
3. The RIS server queries Active Directory to check whether the customer is pre-staged.
4. Active Directory allows the RIS server to respond to requests or forward requests to other RIS servers
5. The RIS server sends an image file list to the client.
Install the RIS server by taking the following steps:
Copy the files required for installation from the CD
The first image file will be installed when you install and start the RIS service.
Authorize RIS (to respond to customer requests)
Assign appropriate licenses to users on the RIS server (Log on as a batch job and add workstation to domain)
Start Remote Installation:
You need a PXE or a network card that can simulate PXE.
Create a Remote Installation Boot board (rbfg.exe)
Start with this floppy disk and press F12
Modifying the configuration of RIS includes the following:
1. Configure the name format of the RIS client computer and the location where the account is created
2. Add an OS image or associate an answer file with an existing image
3. Restrict customer installation options, including automatic, M, restart, tools, etc.
4. Restrict operating system options, such as setting NTFS licenses for answer files and assigning licenses to specified users or groups. This restricts the list of image files used by users.
5. Configuration maintenance diagnostic tools (external settings provided by isV and OEMProgram)
6. Activate Customer Service
7. Pre-staging client computers to prevent unauthorized computers from being remotely installed
The RIS service has two types of image files:
Disk-based Image
Simply copy the installation file to the RIS server, which is similar to common installation. Compared with riprep, the installation file is faster and occupies less disk space. It can be installed on different Hal, additional management is required.
Riprep Image
The fully-configured image can be used directly after installation (including applications). However, each Hal must have an independent riprep image, and the existing image configuration cannot be modified, unless you create an image file again
RIS allows you to specify installation parameters in the setup information answer file (SIF) file to reduce user interaction. You can also associate multiple answer files with an image file to customize different installation versions. You can use Setup Manager to create an answer file on the \ support \ reskit \ deploy \ setupmgr.exe disk.
Use of riprep:
Install Windows2000 Professional on a computer and configure components and applications. This computer is called the reference computer and uses riprep to create image files. Riprep will:
1. delete some unique settings, such as Sid, computer name, and registry setting.
2. Specify a shared directory on the RIS server to save the image file.
3. Create an image file and add it to SIS automatically