ALTE DOCUMENTE
|
|||||
To create a RIS server in your organization, you need to add the Remote Installation Services component to a computer running Windows Server 2003. You can do this in Control Panel under Add or Remove Programs. You must also configure your RIS server using Risetup.exe and you must create at least one operating system im 14114b114o age on the server.
You create a RIS server in the deployment phase of your RIS deployment process, but you need to do some preliminary analysis in the planning stage to assure good performance. As part of the planning process, you need to evaluate the following elements to ensure that your RIS server meets the necessary specifications:
Hardware requirements
Software requirements
Server placement
Server performance
In this part of your planning process, use job aid "Planning for RIS Servers" (ACIRIS_02.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Planning for RIS Servers" on the Web at https://www.microsoft.com/reskit) to record your planning decisions. At this point, you can specify which personnel you want to perform the task of creating RIS servers and initial installation images.
In general, RIS servers must meet the requirements of the product version of the Windows Server 2003 family you install. However, you are encouraged to increase those requirements to more efficiently support RIS image deployment in your organization.
You need to have at least two disk partitions available on the RIS server, one for booting the server operating system and another to contain the directory structure for the client operating system images. You need to allocate an entire separate partition to the RIS server directory tree because you cannot install RIS on the same drive as the system volume. Also, you need to format the RIS partition as NTFS.
The partition containing the images must be large enough to store one or more operating system images, depending on your requirements. A CD-based image for Windows XP Professional is 650 MB-700 MB in size. Most organizations store more than one operating system image to meet the needs of different clients.
For up-to-date hardware compatibility information, see the Windows Catalog link on the Web Resources page at: https://www.microsoft.com/windows/reskits/webresources.
For this part of your planning process, use job aid "Planning for RIS Servers" (ACIRIS_02.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Planning for RIS Servers" on the Web at https://www.microsoft.com/reskit) to record whether you require an upgrade to RIS server hardware. Also indicate the personnel you want to assign to the task.
Several software components are necessary to support the functioning of a RIS server in your network. You need to verify whether the Active Directory, DNS, DHCP services exist on your network before deploying RIS in your organization. You can find all of these services, including the RIS component, on a server running Windows Server 2003. However, you might also have the DNS or DHCP services provided by a third party. In any case, to assure that you do not have any performance degradation in your production environment, install these services on different servers and configure each server for the specific role of that service.
|
|
|
Note You can install all of these software components on a single RIS server when you create your test environment, as discussed in "Designing a Test RIS Environment" later in this chapter. |
RIS is an optional component of Windows Server 2003 that provides the services that enable you to automate the remote installation of an operating system, such as Windows XP Professional, on client computers in your organization.
RIS servers rely on DNS to locate the required Active Directory servers to facilitate domain operations. If you use Windows Server 2003 DNS, you have the benefit of dynamic updates for your DNS server. However, it is not a requirement to use Windows Server 2003 DNS for RIS to function. Whichever DNS server you use, it must support the SRV RR record type and the dynamic update protocol specified in RFCs 2052 and 2136, respectively. For more information about DNS, see "Deploying DNS" in Designing Network Services of this kit.
RIS servers require a DHCP server on the network which is authorized and has an activated scope. Remote boot-enabled clients must receive an IP address from a DHCP server before they can contact a RIS server to request an operating system installation. You can install Windows Server 2003 DHCP or you can use existing DHCP services provided with Windows 2000 Server. In addition, you can use a third party DHCP server. For more information about Dynamic Host Configuration Protocol (DHCP), see the Networking Guide of the Windows Server 2003 Resource Kit (or see the Networking Guide on the Web at https://www.microsoft.com/reskit).
You must install RIS on a computer running Windows Server 2003 in an Active Directory domain. For best results, configure this computer as a member server. Although you can install RIS on a domain controller, the heavy traffic load generated by RIS can impact the performance of the domain controller.
RIS uses Active Directory to locate RIS clients and other RIS servers. You can administer the RIS server from the Active Directory Users and Computers snap-in (dsa.msc) located on the RIS server. For more information about Active Directory, see the Directory Services Guide of the Windows Server 2003 Resource Kit (or see the Directory Services Guide on the Web at https://www.microsoft.com/reskit).
For this part of your planning process, use job aid "Planning for RIS Servers" (ACIRIS_02.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Planning for RIS Servers" on the Web at https://www.microsoft.com/reskit) to indicate whether you need to verify the existence of the software components required to support RIS, along with the personnel you want to assign to this task.
|
