Installing POSReady by Using Remote Deployment

2/16/2009

You can deploy Windows Embedded POSReady 2009 by using Remote Installation Services (RIS) or its successor, Windows Deployment Services (WDS). RIS and WDS enable administrators to set up, configure, and install operating system images on networked computers. They are especially useful when you want to deploy POSReady to many clients.

To install POSReady by using RIS, you must have the following:

  • A correctly configured RIS server that is running Windows Server 2000 or Windows Server 2003 SP1 or earlier
  • Your installation disk or a prepared POSReady image
  • Pre-Boot Execution Environment (PXE) capable network adapters on the destination computers, or those that are supported by drivers on the RIS start disk

To install POSReady by using WDS, you must have the following:

  • A correctly configured WDS server that is running Windows Server 2003 SP2 or Windows Server 2008 (Native mode only)
  • Your installation disk or a prepared POSReady image
  • Pre-Boot Execution Environment (PXE) capable network adapters on the destination computers

The following steps describe how to create a POSReady image on your RIS or WDS (Legacy mode) server. The image can then be deployed over the network to install POSReady.

There are two things that you must know before you continue with a RIS or WDS Legacy mode deployment:

  • POSReady does not use .sif files such as RIStndrd.sif or RIPrep.sif to configure user-specific settings. These settings must be provided by using the POSReady Setup Wizard or by creating an unattended answer file. For more information about how to create an unattended answer file, see Creating a POSReady Answer File.
  • POSReady Setup Wizard automatically calculates the estimated installation size depending on which installation type and components you choose. However, the estimate that is displayed during RIS and WDS installations does not account for caching of setup files during remote deployment. You must add an additional 500MB to the estimated installation size that is displayed in the Setup Wizard.

  1. In the \\server_name\RemInst\Setup\language\Images folder, create a new folder named POSReady.

  2. Browse to the installation media location that contains your POSReady files, and copy the following folders and files into the POSReady folder:

    • \I386 folder
    • \Setup folder
    • Win51
    • Win51is
    • Win51.pos
    • Winbom.ini
  3. In the POSReady\I386 folder, create a \Templates folder.

  4. Copy the following files to the \Templates folder:

    • Startrom.com from the \Templates folder of an existing Windows Server 2003 RIS image.
    • RIStndrd.sif from any other RISetup images on the RIS server.
    • Ntdetect.com from the \I386 folder.
    • Ntldr (from the \I386 folder, copy Setupldr.exe to \Templates, and rename Setupldr.exe to Ntldr).
  5. Open the RIStndrd.sif file in a text editor such as Notepad. Under [SetupData], on the line that begins with OSLoadOptions, add the /minint option. For example:

    [SetupData]
    OsLoadOptions = "/noguiboot /fastdetect /minint"
    
  6. Copy the .inf files for network adapters, or all the contents, from the POSReady\I386\inf folder to the POSReady\I386 folder.

  7. Copy the .sys files for network adapters, or all the contents, from the POSReady\I386\System32\Drivers folder to the POSReady\I386 folder.

  8. (Optional) Create an unattended answer file that is named Unattended.xml and copy it to the POSReady\Setup folder. For more information about how to create unattended answer files, see Creating a POSReady Answer File.

The following steps describe how to create a POSReady image for WDS Native mode deployment. These steps assume that you have already created a WDS captured image. The image can then be deployed over the network to install POSReady. Steps 1-3 involve using Sysprep, a utility available on your POSReady installation media. For more information about Sysprep, see Using Sysprep and FBReseal in POSReady.

  1. Install and configure POSReady on drive C of your master computer that has all desired applications, devices, updates, and so on.

  2. Browse to the \Utilities\sysprep folder on your POSReady installation media and copy the folder and its contents to the root of drive C.

  3. Start sysprep.exe from your C:\sysprep folder and enter the following at the command prompt:

    C:\sysprep –mini –reseal -reboot
    

    Sysprep automatically restarts the computer.

  4. When the computer restarts, press F12.

  5. In Windows Boot Manager, choose a capture image, and then click Next.

  6. Choose your desired drive and provide a name and description for the image. Choose Next to continue.

Dd458824.note(en-US,WinEmbedded.20).gifNote:
You will only see POSReady if you have completed step 3. Windows Boot Manager will only display POSReady if it has been prepared by Sysprep.
  1. Choose Browse and select the location where you want to store the captured POSReady image. You must specify a location to prevent data loss if there is a network issue while you deploy the capture image.
  2. Enter a name for the image and choose Save. You must use a .wim file name extension.
  3. Choose Upload image to WDS server.
  4. Enter the name of the WDS server and choose Connect. You may be prompted for access credentials. If this is the case, provide a user name and password for an account that has sufficient credentials to connect to your WDS server.
  5. On the Image Group list, select your desired image group, and choose Finish.

Adding Network Drivers for RIS and WDS Legacy Mode

When you install POSReady by using RIS and WDS, your computer's network adapter becomes the startup device. If third-party drivers are required for your network adapter, you must copy the following files to the specified folder on your server's POSReady image:

  • .sys files to the \I386 and \I386\system32\drivers folders
  • .inf files to the \I386 and \I386\inf folder
  • All other files to the \I386\system32 folder
  • Copying the driver files to these locations makes them available when you try to startup from your network adapter.
Show: