You can design your RIS-based operating system deployment to use either the interactive or fully-automated mode. Interactive mode requires the user to respond to predefined options presented during installation at the client computer; the fully-automated mode requires no user intervention other than turning on the client computer and providing logon credentials.
You might want to provide interactive installations for more
knowledgeable users who can
easily provide the user input you require. For users that are less
knowledgeable, you can provide fully-automated installations that require
little or no input. This ensures that installation on these clients goes
smoothly and does not require your presence at the client computer.
If you want to provide a combination of interactive and fully automated installations to RIS clients, you can prestage your client computer accounts in Active Directory by using the prestaging script along with an input file that specifies wh 14414m1223o ich Startrom.com boot file each prestaged client must use. To find the prestaging script, see the Remote Installation Scripts link on the Web Resources page http /www.microsoft.com/windows/reskits/webresources.).
|
|
|
Note The RIS deployment mode design process is closely associated with the CIW design process. For further details, see the job aid "Designing the RIS Deployment Mode and CIW Process" (ACIRIS_08.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Designing the RIS Deployment Mode and CIW Process" on the Web at https://www.microsoft.com/reskit). |
An interactive installation requires users at client computers to press the F12 key to initiate a network service boot. This occurs automatically when you use the default Startrom.com boot file for RIS installations. After the client initiates the network service boot and obtains an IP address from DHCP, the CIW downloads to the RIS client. At this point, the information gathering and option choosing process of the CIW begins.
You can configure the CIW to display numerous required user input fields on a menu of installation options. You can also configure the CIW to present specific operating system installation options, such as a list of Risetup or Riprep images. These capabilities enable you to control the user input necessary to enable the installation and to designate who can access predefined installation configurations.
For example, you might allow one group of users to have access to all predefined operating system installation options, but restrict another group of users to a single installation option. You can achieve this type of control over the installation process by using Group Policy and ACL configuration.
When designing an interactive installation, your primary tasks are to choose the following:
The information you require users to input to the CIW.
The operating system installation options you want to make available to different users via the CIW.
Which users receive specific RIS setup options that you configure in Group Policy.
For a job aid to record your design decisions for an interactive installation, see "Designing the RIS Deployment Mode and CIW Process" (ACIRIS_08.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Designing the RIS Deployment Mode and CIW Process" on the Web at https://www.microsoft.com/reskit).
You can configure the user information that is required as input to the CIW. For example, the first screen presented by the CIW is the Welcome screen. You can modify this screen to include multilanguage choices or additional information such as a company message. The next screen is the Logon screen, which requires the user to provide logon credentials, including user name, password, and domain name. You can also build custom CIW screens to prompt the user for specific input information. For more information about defining the CIW configuration, including customizing CIW screens with language options and input prompts, see "CIW Design Tasks" later in this chapter.
At this point in your interactive installation design process, you might need to further analyze your user input requirements. If this is the case, you can wait until you review the section "Designing the CIW Process" later in this chapter before recording your design decisions. Otherwise, use the "Required User Input" section of job aid "Designing the RIS Deployment Mode and CIW Process" (ACIRIS_08.doc) to record the choices you make for required user input. You can also specify the users or user groups from which you require the input, under "Applicable User Groups."
You can define which operating system images the CIW allows specific users to install, and you can limit the images the CIW displays to specific users by configuring ACLs. By providing ACEs on the answer files associated with a RIS installation image and by providing ACEs on the RIS server operating system image folder, you can determine which clients get to view and install a particular image.
For example, to enable a particular user group to install a RIS image, you must configure the group with Read permissions on the answer file and Read permissions on applicable RIS server operating system image folder. This causes the operating system images associated with that answer file to display in the CIW as installation options for the user group. If you specify Read permissions only on the answer file and not on the image folder, the option to install the image displays in the CIW, however, the image does not install due to the lack of Read permissions on the image folder. When configuring ACEs on the operating system image folder on your RIS server, use the following directory path:
\\RISServerName\RemoteInstall\Setup\Language\Images\ImageName\
You can also set an answer file permission configuration to Deny Read access to a particular user group. This causes all operating system images associated with that answer file to not display in the CIW as installation options for that user group.
When enabling access to operating system images, you will probably want to simplify administration. Therefore, the best approach might be to enable Read permissions for all users on the image folder and then use answer files to provide Read permissions to specific user groups. However, note that by configuring ACEs on the image folder, you can explicitly prevent certain users and groups from being able to view an installation option for a particular operating system image located on your RIS server.
For this part of your interactive installation design process, use job aid "Designing the RIS Deployment Mode and CIW Process" (ACIRIS_08.doc) on the Windows Server 2003 Deployment Kit companion CD (or see "Designing the RIS Deployment Mode and CIW Process" on the Web at https://www.microsoft.com/reskit) to record your choices for the operating system installation options you want to provide, along with the user groups that can or cannot receive them. In this job aid, you can specify the following under the "Operating System Installation Access" section:
Answer file name.
Operating system image associated with the answer file.
Users or groups of users granted or denied access to operating system images based on the answer file ACL.
Users or user groups denied access to specific images based on the image folder ACL.
If you need to record this information for multiple operating system images, make an additional copy of the job aid for each operating system image. You might also make more copies of this job aid for recording information that applies to automated installations.
|
