Microsoft KB Archive/305311

= How to Customize Winbom.ini Sections for the Windows Preinstall Environment (WinPE) =

Q305311

Formal product support for Microsoft Windows XP will be available from Microsoft beginning October 25, 2001. Until then, you can consult with your counterparts, peers, and Microsoft Most Valuable Professionals (MVPs) by using our online newsgroups. Access to the Microsoft newsgroups is available from the following Microsoft Web site: "http://communities.microsoft.com/newsgroups/default.asp"

-

The information in this article applies to:


 * Microsoft Windows XP Professional
 * Microsoft Windows XP Home Edition

-

SUMMARY
This article lists and describes the sections of the Winbom.ini file that can be customized for the Windows Preinstall Environment (WinPE).

NOTE: This article is intended for Select Corporate, MCS, and OEM customers.

MORE INFORMATION

 * [DiskConfig]: Includes entries for configuring and partitioning one or more physical hard disks.

EXAMPLE

[DiskConfig]

Disk1 = first.config
 * [description.Config]: Includes entries for configuring and partitioning a particular physical hard disk.

EXAMPLE

[first.config]

Size1 = 10,100

FileSystem1 = FAT32

SetActive1 = Yes

PartitionType1 = Primary

Size2 = *

PartitionType2 = Extended

Size3 = *

PartitionType3 = Logical


 * [Factory]: Includes entries for performing a factory preinstallation.

EXAMPLE

[Factory] AutoDetectNetwork = yes

DoDeviceIDScanOnError = yes

EndUserComputerName = *

FactoryComputerName = *

Logfile = c:\winbom.log

logging = yes


 * if file below exists, its used instead of this one

NewWinBOM = a:\newwinbom.ini

RebootAfterComputerName = no

reseal = yes

resealmode = mini
 * [PnPDriverUpdate]: Includes entries for updating drivers on the installed image before you install the drivers with Plug and Play.

EXAMPLE

[PnPDriverUpdate]

Domain = Domain

EncryptedPassword = yes

Password = *

Username = username
 * [PnPDrivers]: Lists all the updated drivers to be copied onto the computer.

EXAMPLE

[PnPDrivers]


 * DriverSourcePath is a directory located on the local computer in


 * %windir%\OEMDrivers.


 * If the specified path does not already exist, it is created.


 * To copy drivers starting at the root of %windir%\OEMDrivers,


 * specify a single dot (.) for the DriverSourcePath.


 * driverssourcepath = target path under %winroot%\oemdrivers

a:\video\vodoo2000=Vodoo2000

\\server\share\video\ati\allinwonder=AllinWonder

FLOPPY:\audio=audio

CDROM:\drivers=.
 * [NetCards]: Includes entries for configuring the network adapter (NIC) on the target computer, if a network connection is required.

EXAMPLE

[NetCards]


 * If this section does not contain any entries, the Sysprep -factory


 * command scans all present .inf files for a NET class driver that matches


 * the network adapter present on the computer.


 * If no driver is found, the Sysprep -factory command logs a failure.

NICPnPID = path to inf
 * [UpdateSystem]: Includes entries for controlling the update of external answer files by the Sysprep -factory command.

EXAMPLE

[UpdateSystem]

AddReg = UpdateSystem.AddReg

DelReg = UpdateSystem.DelReg

CopyFiles = UpdateSystem.CopyFiles

RenFiles = UpdateSystem.RenFiles

DelFiles = UpdateSystem.Delfiles

Example section that corresponds to the preceding &quot;UpdateSystem.AddReg&quot; entry:

[UpdateSystem.AddReg]

HKLM, &quot;Software\Test&quot;,&quot;String Value&quot;,, &quot;Value&quot;

HKLM, &quot;Software\Test&quot;,&quot;Number Value&quot;,0x00010001, 10
 * [UserAccounts]: Includes entries for controlling the creation of user accounts on the target computer.

EXAMPLE

[UserAccounts]

Mom

Dad

Son
 * [name.Account]: Includes entries for the creation of a specific user account.

EXAMPLE

[Mom.Name]

Description=Mom's Account

Password=Mom's Password

Alias=Mom

Passport=Mom@hotmail.com

[Dad.Name]

Description=Dad's Account

Password=Dad's Password

Alias=Dad

Passport=dad@passport.com

[Son.Name]

Description=Son's Account

Password=Son's Password

Alias=Son

Passport=son@passport.com
 * [OEMRun]: Includes entries for controlling the running of external programs and command shell scripts during the running of the Sysprep -factory command. Commands are processed asynchronously. Each program runs in the order listed in this section, but the program does not wait for an earlier program to finish before it runs.

These executable files or command shell scripts represent the last processing done by the Sysprep -factory command.

EXAMPLE

[OEMRun]

&quot;Run Near the End&quot;, &quot;c:\windows\near.exe&quot;

&quot;Run Next to Last&quot;, &quot;\\server\dir\next.exe&quot;

&quot;Run Last&quot;, &quot;c:\%windir%\last.bat&quot;


 * [OEMRunOnce]: Includes entries for controlling the running of external programs and command shell scripts during the running of the Sysprep -factory command. Commands are processed synchronously. Each program runs in the order listed, and each command must finish before the next command is run.

EXAMPLE

[OEMRunOnce]

&quot;Net Use Call&quot;, &quot;net use R: \\server\share&quot;

&quot;First Application Stage&quot;, &quot;App1.Stage&quot;, MSI

&quot;Second Application Stage&quot;, &quot;App2.Stage&quot;, MSI

&quot;Third Application Stage&quot;, &quot;App3.Stage&quot;, MSI

&quot;First Application Attach&quot;, &quot;App1.Attach&quot;, MSI

&quot;Second Application Detach&quot;, &quot;App2.Detach&quot;, MSI


 * [Section_name]: Includes entries for preinstalling programs.

EXAMPLE

[App1.Stage]

InstallType = Stage

StagePath = &quot;C:\App1_Temp&quot;

SetupFile = &quot;Application_One.msi&quot;

SourcePath = &quot;R:\App1&quot;

[App1.Attach]

InstallType = Attach

StagePath = &quot;C:\App1_Temp&quot;

SetupFile = &quot;Application_One.msi&quot;


 * [ComputerSettings]: Includes entries for controlling user settings on the target computer.

EXAMPLE

[ComputerSettings]

AuditAdminAutoLogon = yes

DisplayRefresh = 75

DisplayResolution = 800x600x256
 * [StartMenuMFUlist]: This contains the Most Frequently Used Program link for the Start menu.

EXAMPLE

[StartMenuMFUlist]

Link0=C:\Documents and Settings\All Users.WIN\Desktop\Windows Media Player.lnk

Link1=C:\Documents and Settings\All Users.WIN\StartMenu\Programs\Accessories\WordPad.lnk

Link2=C:\Documents and Settings\All Users.WIN\Desktop\Launch MSN Explorer.lnk

Link3=
 * [OemFolder]: Contains an OEM folder with any additional data or programs from the OEM manufacturer.

EXAMPLE

[OemFolder]

OemFolder=C:\Documents and Settings\All Users.WIN\Awesome Computers
 * [UserDefined]: A user-defined section that can contain branding information or any other data for other processes.
 * [WinPE]: Identifies the configuration set and Windows operating system that will be installed.

EXAMPLE

[WinPE]

ConfigSet=Config_Set_Name

Domain=DomainName

Lang=ENG

Password=Password

Quiet=Yes

Restart=No

SKU=PRO


 * Possible Values: PER, PRO, SRV, ADS, DTC, WBS

SourceRoot=\\Servername\Sharename


 * UNC path to the root directory containing the source files.

Username=Useraccnt


 * User name used to connect to the location specified by SourceRoot.


 * [WinPE.Net]: Controls the settings that WinPE uses when connecting to a network.

EXAMPLE

[WinPE.Net]

IPConfig=DHCP (Or the static IP address)


 * DHCP is ignored if the value for StartNet is No.

Gateway=xxx.xxx.xxx.xxx

StartNet=Yes

SubnetMask=xxx.xxx.xxx.xxx

When you start a computer by using WinPE, you are running the factory -winpe command, which processes these sections in Winbom.ini in the following order:


 * 1) [WinPE.Net]
 * 2) [DiskConfig]
 * 3) [OEMRunOnce]
 * 4) [OEMRun]
 * 5) [WinPE], except for the Restart entry
 * 6) [UpdateSystem]
 * 7) Then the Restart entry in [WinPE]

Initial Startup

WinPE uses the Windows Setup loader in the initial boot of WinPE. Setup Loader loads the mass-storage device drivers listed in Winpeoem.sif. If no drivers are listed in Winpeoem.sif, Setup Loader loads all of the mass-storage devices normally present in Windows XP Professional or Windows XP 64-Bit Edition.

Win32 Subsystem

When the Win32 subsystem starts, by default WinPE starts the Cmd.exe shell. If Factory.exe does not find a Winbom.ini file, either in the WinPE image or on a floppy disk, it stops running. The settings in Winbom.ini provide a wide range of preinstallation tasks. To perform tasks beyond the scope of Winbom.ini, create batch files to either replace or supplement Winbom.ini.

Additional query words:

Keywords : kbsetup kbtool

Issue type : kbhowto kbinfo

Technology : kbWinXPProSearch kbWinXPHomeSearch kbWinXPSearch

Last Reviewed: September 5, 2001

-

[mailto:MSDN@MICROSOFT.COM Send feedback to Microsoft]

© 2002 Microsoft Corporation. All rights reserved.