Deploying Applications and .Sdb Files During Image-based Installations

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Three primary methods are available for deploying applications and .sdb files during an image-based installation:

  • You can install and configure your applications and .sdb files on the master installation and then create a disk image of the master installation. The master installation is the reference computer that contains the operating system, software applications, and configuration settings that you plan to install on destination computers in your organization. When you copy the disk image to a destination computer, and then start the destination computer, the applications and .sdb files will be installed, configured, and ready for use by an end user on the destination computer.

  • You can install applications and .sdb files by using a Sysprep.inf file to automate Mini-Setup. Mini-Setup is a subset of Windows Setup that gathers and configures user-specific information when a user starts a destination computer for the first time. This method uses a Cmdlines.txt file and the [GuiRunOnce] section of the Sysprep.inf file.

  • You can use the Factory mode feature of Sysprep, and a Winbom.ini file, to attach or detach applications and run Sdbinst.exe on each destination computer. When you attach or detach applications, your application files and .sdb files exist on your disk image, but the applications and .sdb files are not installed. Then, when you copy the disk image to a destination computer and start the destination computer, you can use a Winbom.ini file to attach (install) or detach (remove) your application files and .sdb files.

The first and second methods are used most commonly in corporate environments in which a single standard software configuration is deployed. The Factory mode method is most often used in factory environments or corporate environments where several different software configurations are being deployed.

Installing and Configuring Applications and .Sdb Files on a Disk Image

To deploy installed and configured applications and .sdb files on a disk image:

  1. Install and configure your applications on your master installation.

  2. Copy your .sdb files to your master installation. Usually, .sdb files are saved in the systemroot\AppPatch\Custom folder, but you can save the files in any folder.

  3. Run Sdbinst.exe on your master installation to install and register your .sdb files.

  4. Run the Sysprep tool on your master installation.

  5. Run your disk imaging program, and save the disk image in a shared folder or on some type of removable media.

  6. Use your disk imaging tool to copy the disk image to your destination computers.

This is only a summary of the tasks that you need to perform to deploy installed and configured applications and .sdb files on a disk image. For more information about designing and performing an image-based installation, see "Designing Image-based Installations with Sysprep" in Automating and Customizing Installations of this kit.

Installing and Configuring Applications and .Sdb Files During Mini-Setup

To install and configure applications and .sdb files during Mini-Setup:

  1. Copy your application files to the Sysprep folder on your master installation. Do not install the applications.

  2. Copy your .sdb files to your master installation. Usually, .sdb files are saved in the systemroot\AppPatch\Custom folder, but you can save the files in any folder.

  3. Create and configure your Cmdlines.txt file as described in "Deploying Applications and .Sdb Files During Unattended Installations" earlier in this chapter. Save the file in the Sysprep folder on your master installation.

  4. Specify the path to your Cmdlines.txt file by configuring the InstallFilesPath entry in the [Unattended] section in your Sysprep.inf file.

  5. Create and configure the [GuiRunOnce] section of your Sysprep.inf file in the same way you created and configured the [GuiRunOnce] section of your unattended installation answer file. For more information about configuring the [GuiRunOnce] section of Sysprep.inf, see "Deploying Applications and .Sdb Files During Unattended Installations" earlier in this chapter.

  6. Configure any other sections and entries in your Sysprep.inf file, and save the file in the same location as Sysprep.exe and Setupcl.exe, which are usually in the systemdrive\Sysprep folder on your master installation.

  7. Run the Sysprep tool on your master installation.

  8. Run your disk imaging program, and save your disk image in a shared folder or on some type of removable media.

  9. Use your disk imaging tool to copy the disk image to a destination computer.

This is only a summary of the tasks that you need to perform to deploy applications and .sdb files during Mini-Setup. For more information about designing and performing an image-based installation, see "Designing Image-based Installations with Sysprep" in Automating and Customizing Installations of this kit.

Installing and Configuring Applications and .Sdb Files in Factory Mode

To install and configure applications and .sdb files by using the Factory mode feature of Sysprep:

  1. Copy your application files to your master installation. Do not install the applications.

  2. Copy your .sdb files to your master installation. Usually, .sdb files are saved in the systemroot\AppPatch\Custom folder, but you can save the files in any folder.

  3. Create a Winbom.ini file by using Notepad or any other text editor, and save the Winbom.ini file on a floppy disk, on a CD, or in the same folder as the Factory.exe program (usually, the systemdrive\Sysprep folder).

  4. Configure the [OEMRunOnce] section of the Winbom.ini file. This section contains the list of commands to be run while the computer is running in Factory mode. For example, you can attach (install) or detach (remove) applications, and run Sdbinst.exe.

  5. Configure the WinbomType entry in the [Factory] section of the Winbom.ini file. This entry specifies how the Winbom.ini file is processed; it is required.

  6. Run the Sysprep tool, with the /factory parameter, on your master installation.

  7. Run your disk imaging program, and save your disk image in a shared folder or on some type of removable media.

  8. Use your disk imaging tool to copy the disk image to a destination computer.

  9. Start the destination computer.

  10. After the computer processes your Winbom.ini file and installs your applications and .sdb files, run Sysprep with the /reseal parameter.

This is only a summary of the tasks that you need to perform to deploy applications and .sdb files by using the Factory mode feature of Sysprep. Although Factory mode lets you install and configure applications quickly and efficiently, using it requires substantial planning and design. For more information about planning, designing, and implementing image-based installations with Factory mode, see "Designing Image-based Installations with Sysprep" in Automating and Customizing Installations of this kit.