Automating Tasks Before Mini-Setup
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
You can automate some installation and configuration tasks before Mini-Setup runs by using a special Sysprep feature known as Factory mode. Factory mode is a network-enabled state that uses an answer file to automate installation and configuration tasks before you prepare the computer for final delivery to an end user. Factory mode is commonly used in a manufacturing environment where every computer requires some customization prior to final delivery to an end user; however, it is also useful for corporate deployments. Use Factory mode if you want to customize individual computers or groups of computers after you have copied a disk image onto a destination computer but before Mini-Setup runs.
To automate installation tasks in Factory mode, you need to configure a Winbom.ini file (short for "Windows bill of materials"). Winbom.ini is the answer file for Factory mode. Using Wimbom.ini is a completely automated process. You prepare a master computer by using the -factory parameter with Sysprep, and then create a disk image of the master computer. You then copy the image onto a destination computer. The first time the destination computer starts, it starts in Factory mode and automatically searches for Winbom.ini. The computer then automatically performs the installation and configuration tasks you specified in Winbom.ini. When the destination computer finishes all of the tasks listed in Winbom.ini, you must run Sysprep with the -reseal parameter, which prepares the computer for delivery to an end user. To do this, use the Reseal and ResealMode entries in the [Factory] section of Winbom.ini. Factory.exe must be present in the Sysprep\I386\$OEM$ folder with Sysprep.exe and Setupcl.exe in order for Factory mode to work.
Note
- You cannot manually install and configure software and system components when a computer is in Factory mode. You must use a Winbom.ini file to install and configure software and system components when a computer is in Factory mode.
For corporate deployments, where you typically do not need to create a unique Winbom.ini file for every computer, you can create Winbom.ini files manually by using a text editor.
Use Factory mode and a Winbom.ini file to automate installation tasks before Mini-Setup if you need:
Network connectivity. You can access resources in shared folders, such as data files, device drivers, and applications.
Choice of security context. You can choose a user account under which to run automated installation tasks.
Staged installation support.You can stage the installation of software, which is the fastest method of installing and configuring applications after you copy a disk image onto a destination computer. For more information about staging the installation of applications, see "Preinstalling Applications" in the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy.chm). Deploy.chm is included in the Deploy.cab file in the Support folder on the Windows Server 2003 operating system CD.
Windows Installer support.You can use Windows Installer (.msi) packages to install programs.
Disk configuration support.You can create partitions and format disks on a destination computer, but only if you use Factory mode with the Windows Preinstallation Environment.
Synchronous and asynchronous program execution.You can run programs, scripts, and batch files synchronously by using the [OEMRunOnce] section of Winbom.ini, or asynchronously by using the [OEMRun] section of Winbom.ini. During synchronous execution, each program does not run until the previous program finishes running. During asynchronous execution, programs start one after the other without waiting for the previous program to finish running.
Faster uptime for end users.You can reduce the number of installation tasks that need to be performed after a computer is delivered to an end user.
Auditing support.You can perform auditing tasks after a destination computer has been started in Factory mode.
Device driver installation support. You can use the [PnPDrivers] and [PnPDriverUpdate] sections of Winbom.ini to connect to a server and download device drivers. By comparison, when you use the [OEMPnPDriversPath] section of Sysprep.inf, you can only copy device drivers from the local hard disk.
There are some limitations to automating installation tasks before Mini-Setup runs. You cannot use Factory mode and a Winbom.ini file to do the following:
Perform installation and configuration tasks that publish information in Active Directory.
Install and configure Cluster service and domain controllers.
Perform installation and configuration tasks that rely on the computer name or the computer’s SIDs.
To design automated installation tasks that occur before Mini-Setup, you must identify:
The installation tasks you want to automate.
The configuration files you need to use.
The settings you need to configure for each configuration file.
Identifying Automated Installation Tasks You Can Perform Before Mini-Setup
You can use each copy of the "Disk Image Worksheet" (ACISYS_1.doc) to identify the installation tasks you need to perform after each of your disk images is copied onto a destination computer. If you have not created a worksheet for each of your disk images, identify the installation and configuration tasks that need to be performed after each of your disk images is copied onto a destination computer.
Next, use Table 3.5 to determine which installation tasks to automate before Mini-Setup. Try to automate as many installation tasks as possible.
Table 3.5 Installation Tasks You Can Automate Before Mini-Setup
| Installation Task | Comments |
|---|---|
Install Windows components |
These include all Windows components listed in Add or Remove Programs in Control Panel, such as accessories, games, media services, and networking services. |
Install and configure software |
This includes Windows Installer (.msi) packages as well as staged software. Software installation must run in quiet mode, which means the installation must be fully automated and cannot rely on user interaction. Usually, when you run an installation program in quiet mode, you must provide an answer file. |
Configure computer settings |
These include power management and display settings. |
Run programs, scripts, and batch files |
Programs, scripts, and batch files must be fully automated and cannot rely on user interaction, which means you must provide an answer file for any programs, scripts, or batch files you are running, and you must be able to run the programs, scripts, or batch files in quiet mode. |
Update device drivers |
Device driver files are copied onto the destination computer and the device driver location is added to the device path, which is stored in the registry. (The device path tells the Plug and Play module where drivers are stored). The Plug and Play feature installs the drivers the next time the computer starts. |
Configure shell settings |
These include desktop themes, Windows Messenger, and the appearance of the Start menu. |
Enable an Internet connection firewall |
Enables the firewall feature in Windows XP and Windows Server 2003. |
Configure the list of most frequently opened or accessed applications |
The list of most frequently opened or accessed applications can be configured for specific users. |
Update registry and file settings |
Uses directives based on Windows .inf file processing standards. For information about .inf file sections and directives, see the Driver Development Kits link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources. |
Configure user accounts |
This includes user name, .NET Passport, password, and description settings. |
Update files |
This includes renaming, deleting, or copying files in addition to updating the contents of .inf and .ini files. |
Extend a primary partition |
Extends the primary partition that the Windows operating system is installed on. |
Configure Internet Explorer Enhanced Security Configuration |
This includes configuring Internet Explorer Enhanced Security Configuration for members of the User and Guests groups, and the Administrators group.* |
* For more information about Internet Explorer Enhanced Security Configuration settings, see "Internet Explorer Enhanced Security Configuration" in Help and Support Center for Windows Server 2003. For more information about answer file settings related to Internet Explorer Enhanced Security Configuration, see the Readme.txt file in Deploy.cab. Deploy.cab is in the Support folder on the Windows Server 2003 operating system CD.
You can perform other automated installation tasks with a Winbom.ini file if you are using Factory mode with the Windows Preinstallation Environment. For more information about these tasks, see the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy.chm). Deploy.chm is included in the Deploy.cab file in the Support folder on the Windows Server 2003 operating system CD.
Identifying Configuration Files to Use Before Mini-Setup
You might have to configure several answer files or configuration files if you automate installation tasks before Mini-Setup. Table 3.6 describes these answer files and configuration files, and explains where you need to save them.
Table 3.6 Configuration Files Used to Automate Tasks Before Mini-Setup
| Configuration File | Description | Where to Save the Configuration File |
|---|---|---|
Winbom.ini |
Answer file for Factory mode. |
Any of the following locations:
|
filename.txt* |
Answer file for programs or scripts that run during Factory mode. This includes answer files for software installation (setup) programs. |
Any location you specify in the [OEMRun] or [OEMRunOnce] section of Winbom.ini. |
filename.theme* |
Configuration file for desktop themes. |
Any location you specify in the [Shell] section of Winbom.ini. |
* Where filename can be any valid file name you choose.
For more information about how to configure an answer file for a program or script, see the documentation for the program or script. For more information about configuring a .theme file, see the Core Software Development Kit (SDK). To download the Core SDK, see the Microsoft Platform SDK link on the Web Resources page at https://www.microsoft.com/windows/reskits/webresources.
Identifying Configuration File Settings for Winbom.ini
Use Table 3.7 to match an installation task with a specific section in a Winbom.ini file.
Table 3.7 Installation Tasks and Corresponding Winbom.ini Section Names
| To Automate This Task | Configure These Sections of Winbom.ini |
|---|---|
Install Windows components |
[Components] |
Install and configure software |
[OEMRun], [OEMRunOnce] |
Configure computer settings |
[ComputerSettings] |
Run programs, scripts, and batch files |
[OEMRun], [OEMRunOnce] |
Update device drivers |
[PnPDrivers], [PnPDriversUpdate] |
Configure shell settings |
[Shell] |
Enable an Internet connection firewall |
[SetupHomenet] |
Configure the list of most frequently used applications |
[StartMenuMFUlist] |
Update registry and file settings |
[UpdateSystem] |
Configure user accounts |
[UserAccounts] |
Update files |
[UpdateSystem] |
Extend a primary partition |
[ComputerSettings] |
For more information about specific configuration file settings, including procedural and reference information about creating, formatting, and configuring a Winbom.ini file, see the Microsoft Windows Corporate Deployment Tools User’s Guide (Deploy.chm). Deploy.chm is included in the Deploy.cab file in the Support folder on the Windows Server 2003 operating system CD.