ALTE DOCUMENTE
|
||||||||
When designing a Risetup-based installation, your primary tasks are to choose the following:
· 242p1524c 242p1524c The operating systems you want to image.
· 242p1524c 242p1524c The software applications you want to include on your distribution share.
· 242p1524c 242p1524c The special hardware drivers you want to include on your distribution share.
· 242p1524c 242p1524c The operating system configuration settings or components you want to provide.
For a job aid to record your design decisions for Risetup images, see "Defining Risetup Images" (ACIRIS_07.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Defining Risetup Images" on the Web at https://www.microsoft.com/reskit).
To begin defining your operating system images, make a copy of job aid "Defining Risetup Images" (ACIRIS_07.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Defining Risetup Images" on the Web at https://www.microsoft.com/reskit) for each operating system you want to deploy. Under "Operating System Image," create an identifier for each image and enter it under "Image ID Number." Also enter the product name and the full version number of the operating system for each Risetup image.
For Windows Server 2003 and Windows XP Professional operating systems, you can find the version number by viewing the properties of the file Ntdll.dll located in the i386 folder on the operating system CD. You can locate the version number on the Version tab of the Properties dialog box. The version number is in the format 5.1.XXXX.Y, where XXXX is the build number. Be sure you include the build number in the job aid.
In many cases, you can use a modified Ristndrd.sif answer file to automatically install and configure software applications after installing a Risetup image. The answer file provides the information necessary to do this at the end of Mini-Setup or after Mini-Setup finishes, which follows initial image installation on the client. To enable application installation at these times, you need to create an \$OEM$ folder at the same level as the i386 folder for the appropriate image in your RIS directory structure, and place your applications and related support files in a folder you create with a name such as Applications. The path to such a folder is as follows:
RemoteInstall\Setup\Language\Images\ImageName\$OEM$\$1\Applications
By staging your applications in this location and then using answer files to install the applications on the client, you can minimize the number of images you need to manage and simplify the modification of software configurations as group needs change. However, you need to maintain separate answer files that define the unique application installation configurations. The methods available to define these configurations in your answer files include:
· 242p1524c 242p1524c Pointing to Cmdlines.txt
· 242p1524c 242p1524c Specifying the appropriate entries in the [GuiRunOnce] section
Using these methods enables you to maintain a single image from which you derive multiple application (or driver) configurations that you can provide as installation options to meet varying client needs. You provide these options to the client by associating each answer file with the Risetup image and then configuring access control entries (ACEs) on each answer file to define which clients can receive specific image-answer file sets. For more information about defining operating system installation options, see "Interactive Installation Design Tasks" later in this chapter.
|
|
|
Note For application installation, you can also use Group Policy to configure computer or user deployments of applications. For more information about Group Policy-based software deployment, see the Distributed Services Guide of the Windows Server 2003 Resource Kit (or see the Distributed Services Guide on the Web at https://www.microsoft.com/reskit). |
If you intend to stage your applications, use job aid "Defining Risetup Images" (ACIRIS_07.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Defining Risetup Images" on the Web at https://www.microsoft.com/reskit) to record your pool of applications under "Applications Staged in \$OEM$ Folder." Also, record the staging path to your applications under "Staging Path for Applications," using the name of the new folder you plan to create to contain them. In addition, use the "Answer File Versions" section of job aid ACIRIS_07.doc to record your answer file names and software configuration for each answer file. In job aid ACIRIS_07.doc, you can identify your Risetup answer files with any suitable names, such as Ristndrd01.sif and Ristndrd 02.sif.
To create the answer files, you can copy and modify the default Risetup answer file (Ristndrd.sif) from the following location after you create a Risetup image:
RemoteInstall\Setup\Language\Images\ImageName\i386\Templates\
To create new answer files or to modify existing answer files, you can use Setupmgr.exe or a text editor such as Notepad.
For further information about configuring answer files, see the Deploy.cab file in the \Support\Tools folder on your Windows XP Professional or Windows Server 2003 operating system CD. This file contains a complete reference to the entries you can add or modify for the [Unattended] section. However, be aware that not all sections and entries you find in Deploy.cab apply to RIS.
|
|
|
Tip Consider testing your answer file configurations with an actual operating system installation in your RIS test environment. This ensures proper functioning before performing RIS installations in your production environment. |
It is unnecessary to create separate answer files that specify installation of hardware drivers for groups of computers on which hardware is automatically detected by Plug and Play. However, you might have special hardware on certain groups of computers in your organization that Plug and Play does not detect. To ensure that the drivers for this hardware are properly detected, you need to add the drivers and any support files to your RIS distribution share in an \$OEM$ folder you create, and point to this location in your answer files. For storing your driver files, you can create a subfolder with a name such as "Drivers" in the following path within your RIS directory structure:
RemoteInstall\Setup\Language\Images\ImageName\$OEM$\$1\Drivers
|
|
|
Note You can also structure the Drivers folder with subfolders; Mini-Setup searches all the subfolders when attempting to detect drivers for your hardware. |
For this part of your Risetup image design process, you need to identify all the unique hardware driver and support files that you want to provide to clients. For each unique configuration, you must create a separate answer file that provides the commands to install the specific drivers. You can record the hardware driver and support file information in job aid "Defining Risetup Images" (ACIRIS_07.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Defining Risetup Images" on the Web at https://www.microsoft.com/reskit) under "Hardware Drivers Staged in \$OEM$\$1\Drivers Folder." You can record the answer file names with the hardware driver configurations that they install under "Answer File Versions" in job aid "Defining Risetup Images" (ACIRIS_07.doc).
|
|
|
Note If you have a large number of special drivers, you can include them all in your Drivers folder. After installing the Risetup image on a group of client computers, you can have your answer file call Cmdlines.txt, which you can preconfigure with commands to remove the unused hardware drivers for that user group. |
For special or legacy hardware that requires drivers that Plug and Play cannot detect, you can use your Ristndrd.sif answer file to add a new device search path. This path enables Mini-Setup (and each subsequent Plug and Play detection sequence on client computers) to find the special hardware drivers.
As with Riprep images, you can specify the path to special hardware drivers by including the registry entry OemPnpDriversPath in your Ristndrd.sif answer file in the [Unattended] section as follows:
OemPnPDriversPath=Drivers\Audio; Drivers\Video
For more information about defining the path to special hardware drivers in Riprep answer files, see "Riprep Image Design Tasks" earlier in this chapter.
If you have multiple hardware configurations for different user groups that use the same Risetup image, you can create different answer files with different search paths to the required hardware drivers. In each answer file, add the [Unattended] section and OemPnpDriversPath entries to specify the different paths.
For this part of the image design process, identify the path(s) to your special hardware drivers using the new folder(s) you plan to create, and record this information in job aid "Defining Risetup Images" (ACIRIS_07.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Defining Risetup Images" on the Web at https://www.microsoft.com/reskit) under "Staging Paths for Hardware Drivers."
|
