Using Sysprep and FBReseal in POSReady

2/16/2009

You can prepare your Windows Embedded POSReady 2009 installation for duplication by using Sysprep and you can reseal your image by using Sysprep or FBReseal.

Sysprep is a utility that can be used to prepare a POSReady installation for duplication and customization. You can run Sysprep from the command line or by using the GUI, and it can be fully automated by specifying information in the Sysprep.inf file. Sysprep generates a unique Security ID (SID) to make your POSReady installation unique.

FBReseal is a utility that can be used to reseal a customized installation, and you can run it from the command line. Like Sysprep, FBReseal generates a unique SID but can only be run one time.

Sysprep is useful in scenarios when you have access to your POSReady product key, and also provides additional customizing functionality over FBReseal. FBReseal does not require a product key, but it does not have as many features as Sysprep, and it can only be run one time. If you do not have access to your POSReady product key, you must use FBReseal.

Preparing Your POSReady Installation for Sysprep Duplication

If you want to create a master POSReady installation for cloning purposes, there is important information that you must know.

• The master computer and destination computers must have compatible hardware abstraction layers (HALs).
• The mass-storage controllers must be identical between the master and destination computers unless you modify your Sysprep.inf file to provide additional drivers.
• Plug and Play devices can be different between the master and destination computers.
• The size of the destination computer's hard disk must be at least as large as the hard disk of the master installation.

How to prepare a master installation for cloning by using Sysprep

1. Install and configure POSReady on drive C of your master computer that has all of your 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 specify your desired command-line options. These options are listed later in this section. For example: C:\sysprep –reboot –reseal starts Sysprep, automatically restarts the computer, and seals the installation for deployment.

Using a Sysprep.inf File

You can fully automate the changes that are made by Sysprep upon initial startup by specifying information in the Sysprep.inf file. A Sysprep.inf file can automatically populate a new image with user information, a password, geographical data, networking configuration, and so on. The following is an example of Sysprep.inf:

[GuiUnattended]
OemSkipRegional=1
TimeZone=10
AdminPassword=Password
OemSkipWelcome=1

[UserData]
FullName=User1234
OrgName=Woodgrove-Bank
ProductKey="ABCDE-12345-FGHIJ-67890-KLMNO"
ComputerName=Kiosk1234

[Networking]
InstallDefaultComponents=Yes
[Identification]
JoinWorkgroup=WoodgroveBank1

How to automate Sysprep by using a Sysprep.inf file

1. Install and configure POSReady on drive C of your master computer that has all of your 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. Create a new text file that is named Sysprep.inf and add your desired information.

1. Start sysprep.exe from your C:\sysprep folder and specify your desired command-line options. The Sysprep.inf file will automatically be accessed upon initial startup of the sealed image.

Sysprep Command-Line Options

You can use the following command-line options with Sysprep.

Option	Description
-activated	Use this option only if you have activated the Windows installation previously.
-audit	Restarts the computer into Factory mode without generating new SIDs or processing any items in the [OEMRunOnce] section of Winbom.ini. Use this command-line option only if the computer is in Factory mode.
-bmsd	If the [SysprepMassStorage] section header exists in Sysprep.inf, and you run the command Sysprep -bmsd, then Sysprep populates the [SysprepMassStorage] section with the Plug_and_Play_ID = path_to_device_inf_file entries that correspond to the Plug and Play IDs of mass-storage devices specified in Machine.inf, Scsi.inf, Pnpscsi.inf, and Mshdc.inf. Sysprep builds only the list of mass-storage devices. It does not install these devices in the critical device database or do any other processing. After you use the Sysprep -bmsd command to generate the entries of the [SysprepMassStorage] section, you can delete items from this section before you run Sysprep -reseal or Sysprep -factory on this installation. Installing a smaller number of items in the critical device database reduces the time that is required for this image to restart into the operating system. Do not use the -bmsd command-line option with any other command-line options.
-clean	Clears unused mass-storage drivers added by the [SysprepMassStorage] section of Sysprep.inf, and removes phantom devices created by Plug and Play.
-factory	Restarts in a network-enabled state without displaying Windows Welcome or mini-Setup. This option is useful for updating drivers, running Plug and Play enumeration, installing applications, testing, configuring the computer that has customer data, or making other configuration changes in your factory environment. For companies that use disk imaging (or cloning) software, Factory mode can reduce the number of images required. When you have finished your Factory mode tasks, run the Sysprep -reseal option to prepare the computer for delivery.
-forceshutdown	Shuts down the computer after Sysprep finishes. Note: Use this option with computers that have an ACPI BIOS that do not shut down correctly with Sysprep's default settings.
-mini	Configures the computer to use mini-Setup.
-noreboot	Modifies registry keys (SID, OemDuplicatorString, and so on) without the system restarting or preparing for duplication. This option is used mainly for testing, specifically to see whether the registry is modified correctly. This option is not recommended because making changes to a computer after Sysprep may invalidate the preparation done by Sysprep. Do not use this option in a production environment.
-nosidgen	Runs Sysprep without generating new SIDs. You must use this option if you do not duplicate the computer, or if the computer is a domain controller.
-pnp	Runs the full Plug and Play device enumeration and installation during mini-Setup. Use -pnp only to detect and install legacy, non-Plug and Play devices. Do not use -pnp on computers that use only Plug and Play devices. Otherwise, you will increase the time that is required for the first-run experience without providing any additional benefit to the user.
-quiet	Runs Sysprep without displaying on-screen confirmation messages. This is useful if you automate Sysprep. For example, if you plan to run Sysprep immediately after unattended Setup, add Sysprep -quiet to the [GuiRunOnce] section of the Unattend.txt file.
-reboot	Forces the computer to restart automatically and then start mini-Setup or Factory mode, as specified. This is useful when you want to audit the system and verify that the first-run experience operates correctly.
-reseal	Clears the Event Viewer logs and prepares the computer for delivery to the customer. If you run the command Sysprep -factory, you must seal the installation as the last step in your preinstallation process, either by running the command Sysprep -reseal or by clicking the Reseal button in the Sysprep dialog box.

Using FBReseal in POSReady

To use the fbreseal command, type the following syntax at the command prompt:

fbreseal [-autologon | -keepall | -keepdomain | -keepmounted | -keepnet | -keepuser]

You can use the following command-line options with FBReseal.

See Also

Tasks

Installing POSReady by Using Remote Deployment