SMS: How to Deploy Internet Explorer 4.0 to Windows NT 4.0

Last reviewed: February 1, 1999
Article ID: Q185339


The information in this article applies to:
  • Microsoft Systems Management Server version 1.2

SUMMARY

This article describes a procedure to deploy Microsoft Internet Explorer version 4.0 through Microsoft Systems Management Server to Microsoft Windows NT clients, when the user is not an administrator on the local computer.

Internet Explorer 4.0 Setup requires Administrator rights to complete its installation on computers running Windows NT. The Systems Management Server Package Command Manager (PCM) service can deliver the first phase of the Internet Explorer 4.0 installation and restart the client.

The problem is that after the client is restarted, Internet Explorer 4.0 Setup continues running instructions from the RunOnce section of the registry. The processes running from the registry require Administrator rights to complete the installation.

MORE INFORMATION

To successfully use Systems Management Server to install Microsoft Internet Explorer 4.0, perform the steps listed under "Phase 1" below. Then the sequence of events listed under "Phase 2" and "Phase 3" will occur automatically. These steps involve using three Systems Management Server Installer scripts (Ie401nt1.ipf or Ie401nta.ipf, Ie401nt2.ipf, and Ie401nt3.ipf) and the Shutdown.exe file from the Windows NT Resource Kit.

CAUTION: Microsoft provides script, macro and other code examples for illustration only, without warranty either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. This script is provided 'as is' and Microsoft does not guarantee that the following script, macro or code can be used in all situations. Microsoft does not support modifications of the script, macro or code to suit customer requirements for a particular purpose.

While Microsoft support engineers can help explain the functionality of a particular script function, macro or code example, they will not modify these examples to provide added functionality, nor will they help you construct scripts, macros or code to meet your specific needs. If you have limited programming experience, you may want to consult one of the Microsoft Solution Providers. Solution Providers offer a wide range of fee-based services, including creating custom scripts. For more information about Microsoft Solution Providers, call Microsoft Customer Information Service at (800) 426-9400.

NOTE: The procedures described below require that the Windows NT clients run the Systems Management Server Package Command Manager service. For additional information about installing the Package Command Manager service, please see the following article in the Microsoft Knowledge Base:

   Q167114 SMS: PCM Service Now Available for Windows NT Clients

Before beginning, you should obtain and run the Ie4.exe file. This file contains the Ie401nt1.ipf, Ie401nt2.ipf, and Shutdown.exe files. The Ie401nt1.exe (or Ie401nta.exe), the Ie401nt2.exe, and the Ie401nt3.exe executable files are generated when the Ie401nt1.ipf (or Ie401nta.ipf), Ie401nt2.ipf, and Ie401nt3.ipf scripts are compiled by Systems Management Server Installer.

The following file is available for download from the Microsoft Software Library:

~ Ie4.exe (http://support.microsoft.com/download/support/mslfiles/Ie4.exe)

For additional information about downloading files from the Microsoft Software Library, please see the following article in the Microsoft Knowledge Base:

   Q119591 How to Obtain Microsoft Support Files from Online Services


PHASE 1

  1. The Ie401nt1.ipf or Ie401nta.ipf files are sample scripts that modify the client registry to enable automatic logon on the Windows NT clients with an Administrator account. Use Ie401nta.ipf if you are using Systems Management Server Installer version 1.0.34.00 or lower. For Systems Management Server Installer version 1.0.35.00 and higher, use Ie401nt1.ipf.

    For additional information about enabling automatic logon, please see the following article in the Microsoft Knowledge Base:

    Q97597 How to Enable Automatic Logon in Windows NT

  2. Use Systems Management Server Installer to compile Ie401nt1.ipf or Ie401nta.ipf, Ie401nt2.ipf, and Ie401nt3.ipf.

  3. Use the files from the Internet Explorer CD or use a customized CD installation file set that was created with the Internet Explorer Administration Kit (IEAK) to create a Systems Management Server package. Make sure the Silent Installation option, which allows Setup to run in quiet mode, is selected when generating the Internet Explorer 4.0 files. Include Ie401nt1.exe or Ie401nta.exe, Ie401nt2.exe, Ie401nt3.exe, and Shutdown.exe as source files of the package.

    For additional information about the IEAK, please see the following article in the Microsoft Knowledge Base:

    Q176323 SMS: How to Install Internet Explorer 4.0 with SMS

  4. Create a mandatory job to run Ie401nt1.exe or Ie401nta.exe as a background task. You can use the package definition file (PDF file) generated by the Systems Management Server Installer when Ie401nt1.ipf or Ie401nta.ipf was compiled. The PCM service executes the job.

    Ie401nt1.exe performs the following tasks:

    a. Modifies the registry to enable automatic logon.

    b. Disables the keyboard and mouse services.

    c. Captures the UNC path to the Systems Management Server distribution server

          where the script is being executed from, as well as the package ID.
    

    d. Adds Ie401nt2.exe to the RunOnce section of the registry.

    e. Adds UNC path to the Systems Management Server distribution server and the

          Ie4setup command line to the RunOnce section of the registry.
    

    f. Calls Shutdown.exe to restart the client computer.

    g. Writes to the registry that Setup is in Phase 1.

PHASE 2

  1. The client restarts with automatic logon enabled, and with the keyboard and the mouse disabled. At this point, everything will be running under the context of the Administrator account.

  2. Internet Explorer 4.01 Setup starts from the registry in "quiet" mode.

  3. Ie401nt2.exe is started through the RunOnce section of the registry. It updates the registry to indicate that Setup is in Phase 2 and writes Ie401nt3.exe to the current user "load=" section of the registry.

  4. Ie401nt3.exe starts, finds that Setup is in Phase 2, updates the registry to Phase 3, and then closes.

  5. Internet Explorer 4.01 Setup finishes the first phase of its installation and restarts the client computer.

PHASE 3

  1. Ie401nt3.exe starts again but this time it finds that Setup is in Phase 3. It disables automatic logon, removes the Administrator account and password from the registry, and enables the keyboard and mouse services.

  2. Ie401nt3.exe deletes Ie401nt1.exe or Ie401nta.exe, Ie401nt2.exe, and itself, and then calls Shutdown.exe with a 60-second timer. After that, it deletes Shutdown.exe from the client. You may need to adjust the 60 second Shutdown.exe timer to allow sufficient time for Microsoft Internet Explorer 4.01 to finish its configuration. At this point, Internet Explorer 4.01 is completely installed, but it must configure itself for the Administrator account that is running these procedures. You can adjust the Shutdown.exe timer by editing the line that calls Shutdown.exe in the Ie401nt3.ipf file. For more information on Shutdown.exe switches, type "shutdown /?" (without the quotation marks) from a command prompt.

  3. The client is restarted and is ready for the user to log on.


Additional query words: prodsms IE reboot reboots rebooted ntfs

Keywords : kbfile kbSMS120
Version : winnt:1.2
Platform : winnt
Issue type : kbhowto kbinfo


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 1, 1999
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.