Export (0) Print
Expand All
0 out of 2 rated this helpful - Rate this topic

Running Setup in Batch Mode

The Internet Explorer 6 Customization Wizard enables you to control functionality and user experience of Windows Update Setup. You can further control the setup process by using a batch file, command-line switches, or a combination of the two. You can use these methods whether Microsoft Internet Explorer is installed alone or with Microsoft Office.

In most cases, the batch-file method gives you more control over the installation of individual components and involves fewer steps. The command-line switches are provided for backwards compatibility and to support custom solutions.

Creating a Batch File

To create a batch file, use a text editor such as Microsoft Notepad, and name the file IEbatch.txt. If you plan to call the batch file with command-line switches, you can use a different name for the batch file, as long as you reference the correct file name in your command-line syntax. For more information, see Batch File Syntax. For an example, see Sample Setup Batch File.

Using the Batch File to Distribute Internet Explorer

If you distribute Internet Explorer over the Internet or an intranet, you can post the batch file to the site where users download Internet Explorer. If you distribute Internet Explorer on other media, such as a compact disc or floppy disk, you can add the batch file to the disk. Place it in the same folder as the IE5Setup.exe file.

You might want to keep the batch file in a separate location if the file was not available when you prepared your IEAK package, or if you want to temporarily or permanently change the setup options that you specified in your custom IEAK package.

Running Setup Using Command-line switches

If you are bundling Internet Explorer and any associated components with your product, you typically use command-line switches to install an IEAK package as part of your setup program. If you want to modify setup using command-line switches, you can use the IExpress Wizard, which is included with the IEAK, or you can use another program to package your setup files.

For more information, see Internet Explorer Batch-mode Setup Switches and IExpress Batch-mode Setup Switches.

Reasons for Running Setup from a Command Line or Batch File

Here are some reasons you might want to place additional controls on Windows Update Setup:

Implement hands-free installation

If you are a corporate administrator, you might want to distribute Internet Explorer to your users after standard working hours. Although the IEAK helps you set up a "silent" or "quiet" installation that requires little user interaction, perhaps you want to further control this process. By using settings in the batch text file or command-line switches, you can determine which messages the user sees and whether the computer restarts at the conclusion of setup.

Redistribute Internet Explorer

If you are an independent software vendor (ISV), you can host Internet Explorer within your application and install Internet Explorer without the icons or browser interface. To do so, use a batch file with the Redist option or the /X switch. For more information, see Internet Explorer Batch-mode Setup Switches.

Gain more control over specific components

Using a batch file enables you to install and control components, regardless of whether you included those components in your IEAK package. You can also restrict the setup modes (such as Standard or Minimal) available to your users. Use the ComponentID, a string such as NetMeeting, to identify components. You can find ComponentID information in the Iesetup.cif file.

Change setup options without rebuilding your IEAK package

Perhaps you need to set up Internet Explorer in a particular way, and you don't want to rebuild your IEAK package. You can use a batch file or switches to change settings you previously specified in the Internet Explorer 6 Customization Wizard when you built the package.


Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.