Export (0) Print
Expand All

Deploying WEPOS from Remote Installation Services (RIS) Servers

Deploying WEPOS from Remote Installation Services (RIS) Servers

To speed production, OEMs and retailers can deploy WEPOS using Remote Installation Services (RIS) servers. RIS is an optional component of Windows 2000 Server and Windows Server 2003 operating systems.

Prerequisites

The following items are required for starting WEPOS Setup from RIS:

To deploy WEPOS from a RIS setup image for PXE boot, there are two methods, detailed below.

Method 1

  1. On the RIS server, open a command prompt and type RISetup.exe –add.
  2. When prompted for a source, point RISetup to the Windows XP Professional SP2 CD.
  3. Browse to the location where RISetup installed the image; for example, \\Server_name\RemInst\Setup\Language\Images.
  4. Open the subfolder for the image that you created; for example, \\Server_name\RemInst\Setup\Language\Images\WEPOS.
  5. Browse to the CD or network share containing your WEPOS files and open the folder.
  6. Copy the following WEPOS files into the Remote Install image folder that you just opened, overwriting all files if prompted.
    • \I386 (entire folder)
    • \Setup (entire folder)
    • \SDK (entire folder)
    • win51
    • win51s
    • winbom.ini
  7. Open the Templates folder in the platform folder that you copied WEPOS Setup into.
  8. Open the RIStndrd.sif file in a text editor, and on the line that starts with OSLoadOptions, add the /minint option.
  9. Create an unattended answer file named unattended.xml and copy it to the wepos\Setup folder.

Method 2

  1. In the \\Server_name\RemInst\Setup\Language\Images folder, create an image folder:
    • wepos
  2. Browse to the CD or network share containing your WEPOS files and open the folder.
  3. Copy the following WEPOS files into the Remote Install image folder that you just created:
    • \I386 (entire folder)
    • \Setup (entire folder)
    • \SDK (entire folder)
    • win51
    • win51s
    • winbom.ini
  4. Create this directory: wepos\i386\Templates.
  5. Copy the following files to the \Templates folder:
    • startrom.com from the RemoteInstall\OSChooser\I386 directory.
    • ntldr from the \Templates folder of an existing Server 2003 RIS Image.
    • RIStndrd.sif from any other RISETUP images on the RIS server.
    • Ntdetect.com from the \I386 folder.
  6. Open the RIStndrd.sif file in a text editor, and on the line that starts with OSLoadOptions, add the /minint option.
  7. Copy the .inf files for network cards, or alternatively, all of the contents, from the wepos\i386\inf folder to the wepos\i386 folder.
  8. Copy the .sys files for network cards, or alternatively, all of the contents, from the wepos\i386\system32\drivers folder to the wepos\i386 folder.
  9. Create an unattended answer file named unattended.xml and copy it to the wepos\Setup folder.

Note: Apply the hotfix described in KB 814199 after creating an image using either method.

Adding Network Drivers

When starting WEPOS Setup with RIS and third-party network adapter drivers, the network adapter acts as the boot device. You must add the necessary drivers to the image: i.e., \i386 directory for use by RIS. If the network adapter drivers are not installed properly, you may receive an error stating that the selected operating system image does not contain the drivers needed by your network adapter.

The third-party drivers must also be copied to the Windows PE image.

To add a third party driver to a WEPOS RIS Image:

  1. Copy the driver .sys and .inf files to the \i386 directory.
  2. Copy the driver .inf files to the \i386\inf directory.
  3. Copy the .sys file to the \i386\system32\drivers directory.
  4. Copy the remaining driver files to the \i386\system32 directory.

TIP: If RIS does not recognize drivers that are installed, check the third-party support site. Some third-party network cards require modifications to the driver .inf files or specific .inf files to work with RIS.

Adding Mass Storage Devices

To add a third party mass storage driver to the WEPOS RIS Image:

  1. Create a file named winpeoem.sif with the following contents:
[Version]
signature="$Windows NT$"

;
; Use this section to load pnp/non-pnp oem drivers
; in addition to the inbox driver list
;
; OemDriverRoot : Indicates the path relative to
;                 the system directory of WinPE. If 
;                 none, then specify ""
;
; OemDriverDirs : Specifies series of directories separated
;                 by comma. Each specified directory has the
;                 txtsetup.oem which has the information on
;                 what driver to load.
;
; e.g. OemDriverRoot = "" and OemDriverDirs = drv1, drv2
; indicates to the WinPE that under WinPE's system32 directory 
; there are two directories named drv1 and drv2. Each of these 
; directories contain txtsetup.oem file which lists which
; driver to load
;
[OemDriverParams]
OemDriverRoot=""
OemDriverDirs=storage
  1. Create the directory specified in the OemDriverDirs parameter in the \i386\system32\ directory.
  2. Copy all of the driver files including the txtsetup.oem supplied by the mass storage vendor to the \i386\system32\storage directory.

Adding Additional Drivers to RIS Image

See Adding Drivers to Be Installed by WEPOS Setup. Name the file driverinstall.xml and place it in the \Setup folder of the RIS Image so that setup will automatically load and use the file during a RIS setup.

RIS Settings and WEPOS

WEPOS does not use the .sif files, RIStndrd.sif or riprep.sif, that RIS uses to configure the computer name and other client-specific information provided by the user via the RIS user interface. This information must be provided through the WEPOS Setup wizard or by configuring an unattended.xml file used by WEPOS Setup. When specifying the computer name, use the wildcard "*" (asterisk) character. This will randomly generate the computer name and ensure that the RIS installation is completed without conflict.

RIPrep and WEPOS

RIPrep cannot be used with WEPOS in the same way it is used with other Windows versions. To generate an image of a WEPOS installation on a RIS server, perform the steps listed below.

First, use RIPrep to generate an installation image of Windows XP Professional SP2 from the same machine (hardware type) that you intend to create the WEPOS image for (For more information, see (KB article 842198). This will be used as the base on which the WEPOS image will be overlayed.

Second, create a cloned WEPOS image.

Third, on the RIS server, create the base directory structure for the WEPOS image folder:

  1. In \RemoteInstall\Setup\Language\Images, create two directories:
    • wepos
    • wepos\i386\Mirror1\UserData
  2. Copy BootCode.dat and IMirror.dat from the existing RIPrep Windows XP Pro SP2 image to the \Mirror1 folder.
  3. Create this directory: wepos\i386\Templates.
  4. Copy the following files from the existing RIPrep Windows XP Pro SP2 image \Templates folder to wepos\i386\Templates:
    • Ntdetect.com
    • ntldr
    • startrom.com
    • riprep.sif
  5. Edit riprep.sif to change the install information.

Finally, on the client machine, copy the WEPOS install to the WEPOS image folder on the RIS Server:

  1. Boot the client system using the WEPOS CD or a WEPOS RIS image.
  2. Press any key to display the Setup command prompt.
  3. Type factory –winpe and press Enter.
  4. Type net use letter:\\RISServer\Disk$\RemoteInstall\Setup\Language\Images\wepos and press Enter.
  5. Type XCOPY C:\*.* letter:\i386\Mirror1\UserData /chervyqi and press Enter.

You should end up with the following WEPOS image folder structure on the RIS Server:

WEPOS
I386
   Mirror1
      BootCode.dat
      IMirror.dat
      UserData
         Documents and Settings
         Program Files
         System Volume Information
         Windows
         Boot.ini
         Ntdetect.com
         ntldr
   Templates
      Ntdetect.com
      Ntldr
      Riprep.sif
      Startrom.com
© 2006 Microsoft Corporation. All rights reserved.



Show:
© 2015 Microsoft