You need to configure your domain controller to support the RIS server that provides operating system installation services. You also need to configure your network infrastructure to support RIS-based operating system installations.
To configure your domain controller, you need to acco 22222y2412w mplish the following:
Install the appropriate hardware on your domain controller to support the RIS environment and then install the Windows Server 2003 operating system.
Ensure that you have the software required to support RIS, including:
DHCP installed and activated on your domain controller, unless you are using a third-party application on a member server.
A configured DNS server to provide name resolution services for the domain.
Add a RIS installation account to your domain to enable autologon. Use the Active Directory Users and Computers snap-in to create this account.
To configure your network infrastructure, you need to accomplish the following:
Make any necessary changes to your network topology to provide support for the minimum data transmission rate of 10 Mbps (100 Mbps is highly recommended). See "Assessing the Network Infrastructure" earlier in this chapter.
Ensure that you have the necessary components in your network to support RIS, including a domain controller running Windows Server 2003 with DHCP and Active Directory services, and a DNS server. See "Assessing RIS Server Software Requirements" earlier in this chapter.
Install your RIS servers at suitable network installation points See "Evaluating Network Installation Points" earlier in this chapter.
Set the NTLM authentication level you require on the network. See "Evaluating the NTLM Authentication Level" earlier in this chapter.
Set up standard security measures for your network, including auditing and monitoring, securing physical access to the network, and enforcing a strict password policy. See "Assessing the Security of the PXE Environment" earlier in this chapter.
To configure production clients in preparation for RIS-based operating system installations, you need to accomplish the following:
Install new client computers that use the correct hardware to support RIS installations in the appropriate locations on your network. See "Evaluating RIS Client Hardware" earlier in this chapter.
Install the correct hardware on existing clients to support RIS installations. See "Evaluating RIS Client Hardware" earlier in this chapter.
Update any existing client computers that have incorrect HAL types for the Riprep images they are to receive. For more information about verifying the RIS client remote boot configuration, see "Evaluating Remote Boot Capabilties of RIS Clients" earlier in this chapter.
Run the BIOS information script to determine client BIOS compatibility with network adapter booting. For more information about verifying the RIS client remote boot configuration, see "Evaluating Remote Boot Capabilties of RIS Clients" earlier in this chapter.
|
|
|
Note Before running the BIOS information script, you must ensure that the computer running the script has ADSI and WMI installed and that client computers have WMI installed |
Create RIS boot floppy disks for non-PXE enabled clients. For more information about verifying the RIS client remote boot configuration, see "Evaluating Remote Boot Capabilties of RIS Clients" earlier in this chapter.
Migrate user state. For more information about migrating user state, see "Auditing Existing Clients" earlier in this chapter.
Obtain client computer UUIDs, using either Systems Management Server, OEM listings, or run the BIOS information script. For more information about obtaining client computer UUIDs, see "Evaluating the RIS Client Prestaging Process" earlier in this chapter.
For PXE-enabled clients receiving an automated installation, configure the boot sequence in the BIOS to boot from the hard disk first and the network adapter second.
For non-PXE enabled clients receiving an automated installation, configure the boot sequence in the BIOS to boot from the hard disk first and the floppy disk second.
Disable all active boot partitions on the hard disk of all client computers receiving an automated installation by using a tool such as Diskpart.exe with the /S:disablepart.txt argument.
Erase the hard disks of client computers using a management application such as Systems Management Server.
For more information about defining the boot configuration, also see "Fully-Automated Installation Design Tasks" earlier in this chapter.
|
