Installing Internet Explorer 5 to Windows NT 4.0 Using SMS 1.2

This article was previously published under Q223371
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes a procedure to deploy Microsoft Internet Explorer versions 4.x and 5.0 through Microsoft Systems Management Server version 1.2 to Microsoft Windows NT-based clients, when the user is not an administrator on the local computer.
Internet Explorer Setup requires administrator rights to complete its installation on computers running Microsoft Windows NT. The Systems Management Server Package Command Manager (PCM) service can deliver the first phase of the Internet Explorer installation and restart the client. However, after the client is restarted, Internet Explorer Setup continues running instructions from the RunOnce section of the registry. The processes running from the registry require Administrator rights in order to complete the installation.

Before beginning, first obtain the file. This file contains a Systems Management Server Installer script file named Iesetup.ipf, and the Shutdown.exe command line utility.
This .zip file can be downloaded from the following Microsoft Web site: For additional information about downloading files from the Microsoft Download Center, click the article number below to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
The procedures outlined in this article require that the Windows NT clients run the Systems Management Server Package Command Manager as a service. The PCM service requires a user account that meets the following requirements:
  • Domain administrator privileges on the client computer.
  • Domain user authority to read a PCM instruction file on the Systems Management Server logon server and to run a setup program in the package directory on the Systems Management Server distribution server.
Because PCM as a service uses a user account with local administrative privileges, the PCM service can perform tasks that the PCM application cannot. For example, it can install files into secured folders or make changes to secured registry keys. For additional information about installing the Package Command Manager service, click the article number below to view the article in the Microsoft Knowledge Base:
167114 SMS: PCM Service Now Available for Windows NT Clients

Part 1 - Customizing and Compiling the Script

The following steps explain how to customize the Systems Management Server Installer script, Iesetup.ipf, and create the Iesetup.exe file. The Iesetup.exe file is generated when the Iesetup.ipf script is compiled by Systems Management Server Installer. Unlike version 2.0 of Systems Management Server, the Systems Management Server Installer can not be installed during the site installation but must be installed separately. If the script has been previously compiled with an older version of the Systems Management Server Installer, it must be recompiled using the Systems Management Server Installer version or later.

The Iesetup.ipf file is a sample script that modifies the client registry to enable automatic logon on the Windows NT clients with an Administrator account. To prevent compromising security, the script also disables the mouse and keyboard to prevent the local user from interrupting the script while the computer is logged on with administrative rights. For additional information about enabling automatic logon, click the article number below to view the article in the Microsoft Knowledge Base:
97597 How to Enable Automatic Logon in Windows NT
It is necessary to modify the installer script for use within the network environment. The Windows NT domain, domain administrative account and password must be configured within the script to operate properly. All network information will be compiled into the new executable file preventing users from obtaining the account information.

Customizing the Script

  1. Open the Iesetup.ipf script using the Systems Management Server Installer.
  2. Locate the first occurrence of *SET DOMAIN ADMIN ACCOUNT NAME HERE*, and then open the "Set Variable" script item below it. Change this to be an account with local administrator rights on the client computers.
  3. Directly below that, open the "Set Variable" script item below it. Change the *SET DOMAIN ADMIN'S ACCOUNT PASSWORD* to the password for the account you specified in step 2.
  4. Next is *SET DOMAIN NAME HERE*. Open the "Set Variable" script item and enter the name of the domain under which the administrator account belongs.
  5. Save the file.
  6. On the Systems Management Server Installer Installation menu, click Compile. This creates an executable (.exe) file with the same name as the Installer script. In this case, Iesetup.exe. Place the Iesetup.exe file into the same folder as the Internet Explorer 5 installation files.
If the IEAK package was created for a silent installation, no additional configurations will need to be made to the Installer script. The script has the syntax needed for a silent installation:
IE5SETUP.EXE /Q:A /C:"ie5wzd /S:""#E"" /Q /R:N"
When using the IEAK to create a customized installation of Internet Explorer for a silent installation, it is necessary to check the "Install Silently" option.

If the package will not be configured for a silent installation, this option must remain unchecked within the IEAK when creating a customized installation. Also modify the "Execute" script item under Section Two from
Execute %IENT_PATH%\Ie5setup.exe /Q:A /C:"ie5wzd /S:""#E"" /Q:C /R:N"
to remove the command line syntax. The line should then read:
Following is a list of the command line switches that can be used to control the installation of Internet Explorer:

/Q - Specifies a quiet "hands-free" mode. The user will be prompted for information that has not been specified.

/B:iebatch.txt - Specifies the batch script file to use.

/Q:A - Specifies a quiet mode with no user prompts.

/Q:C - Specifies a quiet mode with the Cancel button not displayed, so the user cannot cancel Setup. The Internet Explorer Customization wizard uses this switch if you select the "Install package silently" option when you are installing as a corporate administrator.

/M:[0|1|2|3...] - Specifies the installation mode. For customized IEAK packages, 0 refers to the first installation choice, 1 refers to the second choice, and so on (for example, 0=minimal, 1=typical (default), 2=full).

/E:ComponentID,ComponentID - Specifies extra components to be installed regardless of the installation mode. Use this switch to specify components that aren't a part of the installation type you specified in the Customization wizard. This switch also overrides settings in the batch text file, if used. The ComponentID is a string that uniquely identifies a component; you can find the corresponding string in the component sections of the Iesetup.cif file.

/S:""#e"" - Designates the source path of Ie5setup.exe. The ""#e"" refers to the full path and name of the .exe file. Note that two pairs of double quotation marks must surround the path.

/R:N - Suppresses restarting the computer after installation. If you suppress restarting, your program should take care of restarting the computer. Internet Explorer is not configured correctly until the computer is restarted.

/D - Specifies that you want to download only the files for the current operating system.

/D:1 - Specifies that you want to download files for Microsoft Windows and Windows NT operating systems.

/G: - Runs specified installation sections in Iesetup.inf. Separate sections with commas.

/X - Installs Internet Explorer without the shell, icons, or links. This option is useful for hosting browser controls in your own application.

/X:1 - Installs Internet Explorer with the shell, icons, or links, but does not take over default browser or http protocol associations.

/P - Reports the required component and disk space cost for an installation. It enables you to see how much disk space will be used based on the installation options selected.

/F -(Fix) Reinstalls all items on the user's computer that are the same version or newer. Using the /F switch ensures that no component is replaced with an earlier version.

Part 2 - Creating the SMS Package

The following procedure outlines the steps needed to create the Systems Management Server package for deployment. This is not to be confused with the Internet Explorer package created with the IEAK. This is the actual package that Systems Management Server will use for distribution.
  1. Create the package in the Systems Management Server Administrator. On the File menu, click Open.
  2. Choose the Packages window, and then click OK. This opens the Packages window.
  3. On the File menu, click New to open the "Package Properties" window. Name the package, and then add a comment if needed.
  4. Click Workstations. In the source folder field, enter the path to the IEAK installation package location or use the "..." button to the right of the field to locate the source folder.
  5. Under "Workstation Command Lines", click New, and then specify a command name.
  6. For the Command Line, enter the location and file name of the compiled installer executable. For example, \\server name\share name\Iesetup.exe or C:\IE5\IESETUP.EXE, where server name is the appropriate server name, and share name is the appropriate share name.
  7. There will also be two check boxes available, one labeled "Automated Command Line" and the other is "System (background task)". Verify that both boxes are checked.
  8. In the "Supported Platforms" box, check the boxes next to the platforms that will be installing the Internet Explorer package. For this package, choose Windows NT (x86).
  9. Click OK, click Close, and then click OK.
The Packages window is now displayed again, and the newly created Systems Management Server package should now be visible.

Part 3 - Creating the Job

The following steps outline the creation of the Job to distribute the Internet Explorer Package to the clients:
  1. In the Systems Management Server Administrator, click Open on the File menu.
  2. Choose both Jobs and Sites by holding down the CTRL key and then clicking OK. This opens the Jobs window.
  3. In the Sites window, expand the tree so that the intended clients are displayed. If there are multiple clients that are already members of a machine group, open the machine groups window using the above steps.
  4. Drag the package from the Packages window and drop it onto the client in the Sites window or onto the machine group that will receive the package. This opens the job details dialog box.
  5. In the "Distribute Phase" section of the Job Details window are two check boxes. One called "Refresh Existing Distribution Servers", and the other is "Put On Specified Distribution Servers"; verify that both of these are checked.
  6. In the drop down list box, verify that "Default Servers" is selected.
  7. In the Run Phase section, confirm that the Run Workstation Command check box is selected. In the drop down list box below should be the name specified in the Command Name field of the Package Properties window.
  8. Click to select the Mandatory After check box, and then confirm that the date and time are the same as displayed in the "Offer After" field.
  9. Disable the Expires After option.
  10. Click OK to commit the settings. This returns the job properties dialog box.
  11. Click Schedule, and then change the priority to high.
  12. Click OK to close the Job Details window and to begin deployment.
The newly created job should now appear in the jobs window. The status should say pending. Watch the Jobs window refreshing status periodically for the job status to change to Active. Once the status has changed to Active, the package will be available to clients for installation.

Part 4 - The Installation Process

Phase 1

Iesetup.exe performs the following tasks:
  • Modifies the registry to enable automatic logon.
  • Disables the keyboard and mouse functionality.
  • Records the path to the Systems Management Server distribution point from which the script is executed.
  • Executes the Shutdown function from within Systems Management Server Installer to restart the client computer.

Phase 2

  • The client restarts with automatic logon enabled, and the keyboard and mouse are disabled. At this point, everything will be running under the context of the administrator account specified earlier in this article.
  • Iesetup.exe runs from the registry. It starts Internet Explorer Setup in "quiet" mode.
  • Internet Explorer Setup finishes the first phase of its installation.
  • Iesetup.exe calls the Shutdown function to restart the client computer.

Phase 3

  • Internet Explorer Setup continues with the final phase of the installation. Iesetup.exe makes one last call of the shutdown function with a 30 seconds timer. You may need to adjust the timer to allow sufficient time for Microsoft Internet Explorer to finish its configuration. At this point, the Internet Explorer installation is complete, but it must configure itself for the administrator account that is running these procedures.

    NOTE: Depending on the Central Processing Unit speed, the amount of RAM, hard disk type and other factors, the 30-second countdown timer may not be sufficient. These factors will need to be taken into account during the testing phase of the deployment and should be resolved prior to sending the package into production.
  • Automatic logon is disabled, the administrator account and password are removed from the registry, and the keyboard and mouse services are enabled.
  • The client is restarted and is ready for the user to log on.
  • Once the client is restarted and the user has logged on, they will also go through the configuration process the administrator account went through in the previous step.
sms ie

Article ID: 223371 - Last Review: 02/21/2014 00:35:08 - Revision: 3.2

  • Microsoft Internet Explorer Administration Kit 5.0
  • Microsoft Systems Management Server 1.2 Standard Edition
  • kbnosurvey kbarchive kbhowto kbpackage kbsoftwaredist kbadvertisement kbsetup kbsmsadmin kbcollections kbpcm KB223371