The information in this article applies to:
 - Microsoft Internet Explorer Administration Kit version 5.0
   on the following platforms: NT, winnt, x86
 - Microsoft Systems Management Server version 2.0

This article describes how to use Systems Management Server 2.0 to deploy Microsoft Internet Explorer 5 to Microsoft Windows NT clients when the user is not an administrator on the local computer.

You must have Administrator rights to complete an Internet Explorer Setup installation on computers running Windows NT. The Systems Management Server Advertised Programs Manager (APM) agent delivers the first phase of the Internet Explorer installation and restarts the client. 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 to complete the installation.

Before you start the following procedure, obtain the Iesetup.zip file. This file contains a Systems Management Server Installer script file named Iesetup.ipf, and the Shutdown.exe command-line tool. For more information, including an overview of Systems Management Server Installer, please review chapter 13 of the
Administrator's Guide for Systems Management Server 2.0.

You can download the .zip file from the following Microsoft Web site:

   http://www.microsoft.com/windows/ieak/en/deploy/sms

For additional information about downloading files from the Microsoft Software Library, click the article number below to view the article in the Microsoft Knowledge Base:

   Q119591 How to Obtain Microsoft Support Files from Online Services

Step 1: Setting Up The Server

Systems Management Server 2.0 offers greater control and flexibility in software distribution than in previous versions of the product. Built-in functionality includes the option to force a package to run using a specified account with administrative rights on the target computer. This is necessary when distributing to clients who either are not logged on or when the logged on user does not have local Administrator rights on the computer.

To specify the account that you want software distribution to use when clients are not logged on, perform the following steps on the site server:

1. Click Start, point to Programs, click System Management Server, and then double-click SMS Administrator Console. This starts Microsoft Management  Console (MMC).

2. In the left pane, expand the Site Database tree, and then expand the Site  Hierarchy node under Site Database.

3. Right-click the site, and then click Properties.

4. On the Accounts tab, click the Set button next to the SMS Client Remote   Installation Account box. Specify the account that you want to use to perform    the software installation. The account needs to have domain Administrator    rights as well as local Administrator rights on the workstations. The Remote Client Installation component primarily uses this account, but software distribution also uses the account to run packages on computers that are
not logged on to the network.

Step 2: Customizing and Compiling the Script


The following steps describe how to customize the Systems Management Server Installer script (Iesetup.ipf) and how to 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 1.2, you can install the Systems Management Server Installer during the Systems Management Server site installation.

Iesetup.ipf 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:

   Q97597 How to Enable Automatic Logon in Windows NT

You must modify the Installer script to use it within the network environment.For the script to operate properly, you must configure the Windows NT domain, domain administrative account, and password within the script. All network information is compiled into the new executable file, which prevents users from obtaining the account information.

To customize the script:

1. Open Iesetup.ipf using Systems Management Server Installer.

2. Scroll down to the first occurrence of the SET DOMAIN ADMIN ACCOUNT NAME
HERE entry. Open the Set Variable script item below this entry. Change this to the    account you specified in step 4 of the "Step 1: Setting Up the Server"    section of this article. You can also use another account with local Administrator rights.

3. Directly below that, open the Set Variable script item below it. Change the    password for the SET DOMAIN ADMIN'S ACCOUNT PASSWORD entry to the password
   you specified for the account in the previous step.

4. The next entry is SET DOMAIN NAME HERE. Open the Set Variable script item
and type the name of the domain in which the Administrator account belongs.

\*
\* MSONLY:
\* In the previous steps, there are references to the SET DOMAIN ADMIN
ACCOUNT NAME \* HERE, SETUP DOMAIN ADMIN'S ACCOUNT PASSWORD, and SET DOMAIN NAME HERE
entries.
\* This information is not passed in clear text across the network. After
the .exe
\* file is compiled, this information cannot be extracted readily. The only
way to
\* obtain this information is to gain access to the .ipf file where this
\* information is in clear text.

5. Save the file.

6. On the Systems Management Server Installer menu bar, click Installation/Compile. An .exe file that has the same name as the Installer script is created. In this case, it is Iesetup.exe. Put the Iesetup.exe file in the same folder where the Internet Explorer 5 installation files are    located.

If you use the Internet Explorer Administration Kit (IEAK) for a silent installation, you do not need to make additional configurations to the installer script. The script contains the following syntax for silent installation:
   ie5setup.exe /q:a /c:"ie5wzd /s:""#e"" /q /r:n"

NOTE: When using the IEAK to create a customized installation of Internet Explorer for a silent installation, you must click to select the Install Silently check box.

If you do not configure the package for silent installation, you must not choose the Install Silently option within the IEAK when you create a customized installation. You must also modify the "Execute" script item under Section Two.
The script is displayed as the following example:

   execute %IENT_PATH%\ie5setup.exe /q:a /c:"ie5wzd /s:""#e"" /q:c /r:n"

You must remove command-line syntax so that the line is shown as follows:

   Execute %IENT_PATH%\Ie5setup.exe

The following list shows the command-line switches you can use to control Internet Explorer Setup:

 - /q - Specifies Quiet "hands-free" mode. The user is prompted for information
   that is not specified.

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

 - /q:a - Specifies Quiet mode with no user prompts.

 - /q:c - Specifies Quiet mode. The Cancel button is not displayed, so the user cannot cancel Setup. The Internet Explorer Customization wizard uses this switch if you select the the Install Silently option when you perform the installation 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 you want installed, regardless of the installation mode. Use this switch to specify components that are not part of the installation type you specified in the Customization wizard. This switch also overrides settings in the batch text file, if you used one. The <ComponentID> value 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>"" value 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. Make sure to
   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 associations.

 - /p - Reports the required component and disk space cost for an installation  so you can see how much disk space is available, based on the installation options you select.

 - /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.

Step 3: Creating the Systems Management Server Package


You can use the following steps to create the Systems Management Server 2.0 package for deployment. This is not to be confused with the Internet Explorer package you created with the IEAK. This is the actual package that Systems Management Server uses for distribution.

1. Open the Systems Management Server console, right-click Packages, and click    New/Package.

2. On the General tab, type a name for the package.

3. On the Data Source tab, click to select the This Package Contains Source   Files check box, and then click Set.

4. Under Source Directory Location, click the type of connection to the set up files in the source directory, and then click OK.

5. On the Distribution Settings tab, in the Sending Priority box, click High, and then click OK. The package should now appear under the Packages node of the site tree within the console.

6. Expand the package under the Packages node.

7. Right-click Distribution points, click New/Distribution Points, and then click Next to begin choosing distribution points.

8. Click to select the check box by the server or servers that you want to be the distribution points for this package, and then click Finish. You are returned to the site tree.

9. Right-click Programs under this package, click New/Program, and then type a name for the program.

10. In the Command Line box, type the full path to the script executable file, or click Browse to locate the file.

11. On the Environment tab, click to clear the User Input Required check box.

12. Click to select the "Run with Administrative rights" check box, and then click OK.

   NOTE: You must click to select this check box for the package to run successfully. Internet Explorer Setup requires administrative rights to make modifications to the client's registry.

The Packages window now reappears and the newly created Systems Management
Server     package is displayed.

Step 4: Creating the Advertisement

Use the following steps to create the advertisement that offers the package
to the clients:

1. Create a collection of clients that are targeted to receive the distribution. You can base the collection on a query or direct membership rules.

2. Right-click the collection that will receive the package, and then click All    Tasks/Distribute Software.

3. The Distribute Software Wizard starts. Click Next.

4. Click "Distribute an existing package", click the Internet Explorer package, and then click Next.

5. Make sure the distribution point is selected, and then click Next.

6. Click the program you want to install, and then click Next.

7. Fill in the advertisement name if appropriate, and then click Next.

8. Specify any subcollections that should also receive this advertisement, and then click Next.

9. Confirm or change the time the advertisement is offered and specify if the advertisement should expire and when.

10. On the Assign Program page, click Yes to assign the program.

11. Click Next, and then click Finish.

Step 5: The Installation Process


The package is now offered to the specified clients. After the client recognizes a package is available, the installation process begins. The following section provides a brief overview of the installation process for the Internet Explorer 5 package.

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 is running under the context of the Administrator account you specified in step 4 in the "Step 1: Setting Up the Server" section of 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-second timer. You may need to adjust the timer to allow sufficient time for 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 processor speed, the amount of RAM, the size of the hard disk, and other factors, the 30-second countdown timer may not be sufficient. You need to take these factors into account during the testing phase of the deployment, and you should resolve any issues 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.

 - When the client is restarted and the user logs on, Internet Explorer performs   a user-specific configuration routine that is similar to the routine  performed in the previous step.

\*
\* MSONLY:
\* Microsoft's current policy (which is essentially verbal at this point) indicates
\* that we support the scripted install of Internet Explorer 5. This means that we
\* have an escalation path through CPR if needed.
\*
\* Support Professional responsibilities and case ownership:
\*
\* 1. A Systems Management Server Support Professional should take and retain\*    ownership of any case that comes into Systems Management Server. Onlya
\*    subcase is sent to the Internet Explorer team, not the original case.
\*
\* 2. Have the customer log on to the failing workstation using an
\*    Administrator-level account.
\*
\* 3. Run Iesetup.exe from the Systems Management Server distribution point
\*    specified during the package creation.
\*
\* 4. If this action is successful, the issue is related to the Systems Management
\*    Server distribution process and you should work on it from a Systems
\*    Management Server standpoint.
\*
\* 5. If this script does not run, request a screen capture of the command line
\*    (including all switches) the customer used when creating the Systems
\*    Management Server package. The command line should contain the Ie5setup.exe
\*    file. If it does not, the command line may be incorrect. Attach this
screen
\*    capture to the case.
\*
\* 6. Thoroughly document any error messages that occur during the troubleshooting
\*    process because you are dealing with two very different products.
\*
\* 7. Create a subcase to assign to an Internet Explorer Support Professional.
\*    Provide the screen capture when you transfer ownership of the subcase to the
\*    Internet Explorer Support Professional.
\*
\* 8. The Internet Explorer and Systems Management Server Support Professionals
\*    need to work together to determine if the command line is the problem and to
\*    test a resolution with the customer.
\*
\* 9. If you need Internet Explorer assistance, create a subcase to assign to an
\*    Internet Explorer engineer. You must provide the screen capture to the
\*    engineer when you give the subcase to the Internet Explorer Support
\*    Professional.
\*
\*
\*

Additional query words: sms,ie,ieak

\* MSONLY Document Information
\* ===========================
\*
Keywords          : kbsetup kbClient kbConfig kbMMC kbSecurity kbSMS200
kbAdvertisement kbCollections kbPCM kbPackage kbSMSAdmin kbSMSInst
kbSoftwareDist
Version           : WINDOWS:5.0; winnt:2.0
Platform          : WINDOWS winnt
Issue type        : kbhowto
 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.

@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited

[TOP] [HOME] [INDEX]