When you are deploying Windows 2000 Professional over a very large or geographically disparate set of systems, one of the most efficient methods is to use remote installation. You can perform remote installations of Windows 2000 Professional if you have a Windows 2000 Server infrastructure in place and the computers in your network support remote boot.
For more information about installing and configuring Windows 2000 Server, see Section II, Chapter 8, "Installing Microsoft Windows 2000 Server" in this book.
After this lesson, you will be able to
Estimated lesson time: 40 minutes
To be able to install RIS and to create a boot floppy for network interface cards that are not equipped with a Pre-Boot Execution Environment (PXE) boot ROM, or for systems with BIOSs that don't support starting from the PXE boot ROM, you must have a computer running one of the Windows 2000 Server family of products. You must also have either the CD-ROM or access to a network source of files used to install the Server product. For more information, see the section "Examining the Prerequisites" below.
Remote installation is the process of connecting to a server running Remote Installation Services, called the RIS server, and then starting an automated installation of Windows 2000 Professional on a local computer. Remote installation enables administrators to install Windows 2000 Professional on client computers throughout a network from a central location. This reduces the time administrators spend visiting all the computers in a network, thereby reducing the cost of deploying Windows 2000 Professional.
RIS provides the following benefits:
Before beginning a mass installation of Windows 2000 Professional using RIS, become familiar with the prerequisites for the service and install the service using the Remote Installation Services Setup wizard.
RIS is available only on computers running one of the Windows 2000 Server family of products. The RIS server can be a domain controller or a member server. Table 1.5 lists the network services required for RIS and their RIS function. These network services don't have to be installed on the same computer as RIS, but they must be available somewhere on the network.
Table 1.5 Network Services Required for RIS
|Network service||RIS function|
|DNS Service||RIS relies on the DNS server for locating both the directory service and client computer accounts.|
|DHCP Service||Client computers that can perform a network boot receive an IP address from the DHCP server.|
|Active Directory directory services||RIS relies on the directory services based on Active Directory technology in Windows 2000 for locating existing client computers as well as existing RIS servers|
Remote installation requires that RIS (included on the Windows 2000 Server CD-ROM) be installed on a volume that is shared over the network. This shared volume must meet the following criteria:
When your network meets the prerequisites for RIS, you can run the Remote Installation Services Setup wizard, which does the following:
When installation of RIS is complete, you can configure it using the server's computer object in the Active Directory Users And Computers snap-in.
The RIS server stores the RIS images used to automatically install Windows 2000 Professional on client computers that are enabled for remote boot. The RIS server can be a domain controller or a standalone server that is a member of a domain containing Active Directory directory services.
In this practice, you install Windows 2000 Remote Installation Services from a Windows 2000 Server CD-ROM.
To complete this exercise, you must have a Windows 2000 Professional CD-ROM or access to a shared folder that contains the Windows 2000 Professional installation files. You must also have a drive on the computer running one of the Windows 2000 Server family of products on which you installed RIS that is formatted with NTFS version 5 or later and that contains enough room to hold the Windows 2000 Professional installation files. You must have available on your network a DHCP server, a DNS server, and a domain.
In this exercise, you install Remote Installation Services on a computer running Windows 2000 Server.
The Add/Remove Programs window appears.
The Windows Components page of the Windows Components wizard appears.
Setup installs and configures RIS.
The Completing The Windows Components Wizard page appears.
The System Settings Change dialog box appears, indicating that you must reboot before the new settings will take effect.
In this exercise, you configure RIS.
The Microsoft Windows 2000 Configure Your Server screen appears, indicating that you have selected components that require additional configuration.
If the Microsoft Windows 2000 Configure Your Server screen doesn't appear after you restart and log on as Administrator, open Control Panel, double-click Add/Remove Programs, and click Add/Remove Windows Components. Under Set Up Services, you should see the Configure Remote Installation Services item with an associated Configure button. Skip step 2 that follows and proceed with step 3.
The Add/Remove Programs window appears, indicating that you now need to configure Remote Installation Services.
The Remote Installation Services Setup wizard appears.
The Remote Installation Folder Location page appears.
Notice that the drive on which you create the Remote Installation folder can't be the system drive and must be formatted with NTFS version 5 or later.
Enter a path that is appropriate for your system. The folder should not exist; it will be created as part of the configuration process. Remember that the drive must be on the computer on which you installed RIS, must be formatted with NTFS version 5 or later, and must have about 300 MB of space available to hold the Windows 2000 Professional installation files.
The Initial Settings page appears.
By default, the RIS server doesn't support client computers until you configure it to do so.
The Installation Source Files Location page appears.
If you were using a Windows 2000 Professional CD-ROM in the CD-ROM drive of the server on which you were configuring RIS, you would enter x:\i386, where x is the drive letter for the CD-ROM drive.
The Windows Installation Image Folder Name page appears.
The Friendly Description And Help Text page appears.
The Review Settings page appears.
The default description is "Microsoft Windows 2000 Professional." The help text is "Automatically installs Windows Professional without prompting the user for input."
It will take several minutes for the following tasks to be completed:
Client computers that support remote installation must have one of the following configurations:
The Net PC is a highly manageable platform that can perform a network boot and manage upgrades and prevents users from changing the hardware or operating system configuration. Additional requirements for the Net PC are the following:
The Administrator group doesn't have the right to log on to a batch job by default and thus needs to be assigned this right before attempting a remote installation.
Computers that don't directly meet the Net PC specification can still interact with the RIS server. You can enable remote installation on a computer that doesn't meet the Net PC specification by doing the following:
If the network interface card in a client isn't equipped with a PXE boot ROM or the BIOS doesn't allow starting from the network interface card, create a remote installation boot disk. The boot disk simulates the PXE boot process. Windows 2000 Professional ships with the Windows 2000 Remote Boot Disk Generator that allows you to easily create a boot disk (see Figure 1.7).
Figure 1.7 The Windows 2000 Remote Boot Disk Generator dialog box
Start the Windows 2000 Remote Boot Disk Generator by running Rbfg.exe. The Rbfg.exe file is located in the RemoteInstall\admin\i386 folder on the Remote Installation Server. These boot floppies support only the PCI-based network adapters listed in the Adapter List. To see the list of the supported network adapters, click the Adapter List button shown in Figure 1.7. A partial listing of the supported network adapter cards is shown in Figure 1.8.
Figure 1.8 Network adapters supported by boot floppies
In this practice, you create a remote boot disk.
The Run dialog box appears.
Your path to Rbfg.exe might vary. See step 6 in Exercise 2, "Configuring Remote Installation Services," in the previous practice.
The Windows 2000 Remote Boot Disk Generator dialog box appears.
If your computer has more than one floppy disk drive, make sure you select the appropriate floppy disk drive you will be using when you are choosing the drive in the Windows 2000 Remote Boot Disk Generator dialog box.
A Windows 2000 Remote Boot Disk Generator dialog box appears, prompting you to create another boot floppy.
In this lesson, you learned that if you have a Windows 2000 Server infrastruc-ture in place, and the computers in your network support remote boot, the most efficient method of deploying Windows 2000 Professional is to use remote installation. Remote installation is the process of connecting to an RIS server and then starting an automated installation of Windows 2000 Professional on a local computer. Remote installation enables administrators to install Windows 2000 Professional on client computers throughout a network from a central location. This reduces the time that administrators spend visiting all the computers in a network, thereby reducing the cost of deploying Windows 2000 Professional.
You also learned that client computers that support remote installation must have one of the three following configurations: a configuration meeting the Net PC specification, for which the network interface card must be set as the primary boot device within the system BIOS; a network interface card with a PXE boot ROM and BIOS support for starting from the PXE boot ROM; or a supported network interface card and a remote installation boot disk.
Finally, you saw that the user account that is to be used to perform the installation must be assigned the user right "Log on as a batch job," and users must be assigned permission to create computer accounts in the domain that they are joining. The domain is specified in the advanced settings on the RIS server.