/build/static/layout/Breadcrumb_cap_w.png
Internet Explorer has 1 inventory records, 74 Questions, 6 Blogs and 26 links. Please help add to this by sharing more!

Deployment Tips (19)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 3 ratings
Most Commonly Reported Deployment Method
Windows Installer with Custom Transform (MST)
123
Command Line
Available switches:

[/help] [/passive] [/quiet] [/update-no] [/no-default] [/nobackup] [/ieak-full:<path>|/ieak-branding:<path>] [/norestart|/forcerestart] [/log:<path>]


/help = Display this message.

Setup Modes:

/passive = Run the installation without any input from the user.
/quiet = Identical to /passive, but do not show any user interface.

Setup Options:

/update-no = Do not look for Internet Explorer updates.
/no-default = Do not make Internet Explorer the default browser.
/nobackup = Do not backup the files that would later be required to uninstall Internet Explorer.
/ieak-full:<path> = Reserved for Internet Explorer Administration Kit use.
/ieak-branding:<path> = Reserved for Internet Explorer Administration Kit use.

Restart Options:

/norestart = Do not restart when installation is complete.
/forcerestart = Restart after installation.

Miscellaneous Options:

/log:<path> = Create log file at <path>.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
123
Command Line
A nice workaround:

You need:

* exeScript
* PopulateMSI
* a full install package of ie7

The way:

1. unzip the ie7 package an store it

2. create a share or a folder, that contain the ie7 install files

3. with exescript: create a script to launch the iesetup.exe - example: \\server\share\ie7setup\update\iesetup.exe /passive /quiet /forcerestart /update-no

4. compile this script to exe and copy it in your c:\program files\ie7installer\installer.exe

5. create a regfile: hklm - runonce - [path] installer.exe

6. create a project with populateMSI - don´t forget to integrate the regfile!

7. make your msi

and now?

you can deploy this msi package - after the next reboot will the ie7 installed silent and the machine reboots again...

enjoy it.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
123
Command Line
A nice workaround:

You need:

* exeScript
* PopulateMSI
* a full install package of ie7

The way:

1. unzip the ie7 package an store it

2. create a share or a folder, that contain the ie7 install files

3. with exescript: create a script to launch the iesetup.exe - example: \\server\share\ie7setup\update\iesetup.exe /passive /quiet /forcerestart /update-no

4. compile this script to exe and copy it in your c:\program files\ie7installer\installer.exe

5. create a regfile: hklm - runonce - [path] installer.exe

6. create a project with populateMSI - don´t forget to integrate the regfile!

7. make your msi

and now?

you can deploy this msi package - after the next reboot will the ie7 installed silent and the machine reboots again...

enjoy it.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
122
Note

If you receive the error 'unable to find BRANDING.CAB' during the package creation phase of the IEAK, check your TEMP environment variables. This error will occur if there are any spaces in the variable (for example, the default TEMP path is 'C:\Documents and Settings\username\Local Settings\Temp'. Change it to 'C:\temp' and all is well).

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
118
Command Line
I downloaded IEAK7 on 11/2/07. Went through the wizard for first test deployment. Help files showed that for installation from a network share, I should use the files from the FLAT folder (created by the IEAK wizard).
I copied the IE7Setup.exe to the network share and tried launching using the command line options listed above, such as:

start /wait \\SERVER\SHARE$\IE7\IE7Setup.exe /quiet /passive /norestart /update-no /nobackup

This DOES NOT LAUNCH. You will get "command line option syntax error"

I scoured the net for few min and found MSKB article: 934381, which says: "When you use Internet Explorer Administration Kit 7 (IEAK 7) in certain license modes, you cannot use command-line setup switches such as /quiet and /norestart .."

So the workaround is a command line such as:

start /wait \\SERVER\SHARE$\IE7\IE7Setup.exe /C:"IE7Setup.cmd /quiet /passive /norestart /update-no /nobackup"

THIS WORKED FOR ME. Maybe I chose a wrong option in the IEAK wizard? Anyhow, if you're beating your head against the wall with command line option errors, this might be the case for you too.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
118
Note
Proxy Exception List gotcha.

Problem: Once we deployed IE7 (or beta 8 for that matter), users could not make any changes to the proxy settings and have those settings saved.

Solution: It turns out that our Group Policy added an address that began with a "." (period). Apparently, you cannot preceed any addresses with a period.

For example, "www.company.com;120.23.2.203" works but ".company.com;120.23.2.203" doesn't and prevents anything from being saved as far as changes go.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
To Deploy IE 7 using Active Directory and Group Policy

1) Get the IE setup msi wrapper. It was originally used for MS PSS customers but is now freely available. It's called iexsetup.zip. Download it here http://www.installsite.org/files/iswi/IeXsetup.zip

2) You will then need to edit the .msi so that it recognises the new IE7 setup routine. Microsoft supplies an msi editing tool called Orca which you can download here. http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/msisdk-common.3.0.cab

Extract Orca_Msi.FD66E721_5AA0_41BC_AA26_1EC8F7FA1175 and rename it orca.msi. Then install it.
3) Run Orca and open ie7setup.msi and edit the following rows:
Table: CustomAction
Remove the rows "IE5MSI", "RunUninstall", "SetUninstallPath"
Edit "RunSetup" = "/quiet /forcerestart"
Edit "MySetPath" = "[SourceDir]IE7-WindowsXP-x86-enu.exe"

Table: Properties
You can edit this to reflect the later version of IE.
Save the .msi.
4) Download IE7-WindowsXP-x86-enu.exe
and place into your desired network location. Place the newly created ie7setup.msi in the exact same folder. You are ready for deployment but you're not done yet!
5) To get the new IE7 .adm files, install IE7 on a test machine. Navigate to c:\windows\inf and you will find the updated inetres.adm among other .adm's. Launch Active Directory Users & Computers and then create a new GPO or modify an existing one. Click on Administrative Templates and add the new inetres.adm from your inf folder.

To disable the first run webpage which runs for every user, you will need to navigate to Administrative Templates\Windows Components\Internet Explorer. Enable "Prevent Performance Of First Run Customize Settings". You might want to customize those settings which you have now stopped your users from seeing at the first run webpage though.

6) Finally, create a new package for IE7. Remember to ASSIGN the ie7setup.msi package to your COMPUTER CONFIGURATION section of your GPO. Don't try and put this in the user configuration, it will likely fail or give unpredictable results and/or require admin privileges to complete.

So much for an easy update but it works and I have not had a single failure yet on my corporate network.

Neilson.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
What IÂ’m trying to do:

Install IEAK (v.7) created package of IE7 during unattended install of XP Pro SP2. I am calling the setup from cmdlines.txt which gets executed at the end of GUI phase of XP Setup. The problem was that the IE 7 setup was trying to connect to the proxy to complete the Windows Genuine Advantage (WGA) check which is mandatory for the IE7 install. Because the IE7 setup was being called in the security context of the local system account, it did not have the relevant permissions at the proxy and would prompt the user for authentication details thus “breaking” the unattended install.

How to fix it:

Install the standalone WGA patch (KB905474) prior to the install of IE7.

You have to extract it and use the switches:

WGANOT~1.EXE /quiet /passive /norestart

Same with the IE7 package:

IE7-Setup.exe /quiet /passive /norestart /update-no /nobackup
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
Unfortunately, Microsoft hasn't released MUI-Packs for IE7 so far.

However, it's pretty easy to do it 'by hand'. To do it for eg. german, you have to download the native german IE7-setup first. Start the setup on any machine, it first unpacks to a temporary directory on the root drive. After the that, you get an error message about the wrong language. Don't OK. this message! Go to the temporary dir and sort it by type. Copy all the files with the .MUI extension to a new folder. Rename this folder de-DE (for the correct name of your languages folder, go to the MS Global Dev HP, at: http://www.microsoft.com/globaldev/nlsweb/default.mspx). After that, OK. the error message and the temp folder gets removed. As a final step, copy the 'de-DE' folder to the %windir%\system32 folder. That's all.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
The above info about the MUI isn't true anymore.
MS has released the MUI pack. you can get it here:
IE7MUI-x86-enu.exe.

For those who are using WSUS: It comes down also to the clients automatically, if you approve IE7.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
Upon first-run after restart, you see the following:
"Your current security settings put your computer at risk"

This is controlled on a per-user basis here:

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Security

"DisableSecuritySettingsCheck" - add a DWORD value of 1

Or, in Group Policy under User Configuration > Administrative Templates> Windows Components > Internet Explorer

Enable "Turn off the Security Settings Check"

This is only available in the new IE7 adm file available from Microsoft.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note

If you need to change the TEMP environment variable becuase of the branding error, make sure you change the TMP as well.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
116
Note
What I’m trying to do:

Install IEAK (v.7) created package of IE7 during unattended install of XP Pro SP2. I am calling the setup from cmdlines.txt which gets executed at the end of GUI phase of XP Setup. The problem was that the IE 7 setup was trying to connect to the proxy to complete the Windows Genuine Advantage (WGA) check which is mandatory for the IE7 install. Because the IE7 setup was being called in the security context of the local system account, it did not have the relevant permissions at the proxy and would prompt the user for authentication details thus “breaking” the unattended install.

How to fix it:

Install the standalone WGA patch (KB905474) prior to the install of IE7.

You have to extract it and use the switches:

WGANOT~1.EXE /quiet /passive /norestart

Same with the IE7 package:

IE7-Setup.exe /quiet /passive /norestart /update-no /nobackup
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
2
Note
I had a little trouble removing the RunOnce Window even after setting up a Group Policy for almost all the settings. I was still getting a window that asked if I wanted to keep my homepage. :( But I found this registry edit that resolved it! :)

I created a .reg file with the following information.


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]
"RunOnceComplete"=dword:00000001
"RunOnceHasShown"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main]
"RunOnceComplete"=dword:00000001
"RunOnceHasShown"=dword:00000001


Then ran it using regedit.exe /s "\\server\folder\file.reg"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Note
IEAK bug:
You cannot make the install silent or with minimal dialogs and present a reboot to the user. This is some sort of bug. If you try to do this, the reboot is forced without warning.

If you want to make the installation automated, you must either suppress the reboot completely or force the reboot.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Note
To remove the startup window is first opened IE7 for each new user implement the following key:

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main]
"RunOnceHasShown"=dword:00000001
"RunOnceComplete"=dword:00000001

[HKEY_LOCAL_MACHINE\Default_User\Software\Microsoft\Internet Explorer\Main]
"RunonceComplete"=dword:00000001
"RunOnceHasShown"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main]
"RunOnceHasShown"=dword:00000001
"RunOnceComplete"=dword:00000001

Submitted by: poojasri
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Virtualization
While not exactly a packaging note for deploying IE, this pertains to using it as a viewer for applications that need to open up webpages and/or raw *html files from within the virtual package.

Since AppV is used in lockdown scenarios, IE security settings might prevent some things from firing off correctly, like if an application consists entirely of *.html files, or perhaps might launch an *.html help file that uses an ActiveX control. In this case, it might not work correctly.

However, if IE or some other browser is being launched from within the virtual package, you can bake security settings into the package as long as they come in the form of registry values. For IE, this is mostly here:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl

So, by setting up the permissions as necessary on a clean machine, and then exporting this key, and importing the *.reg into an AppV package (which of course, I build with InstallShield), packages that need to kick off an *.html file are able to do so based on the permissions defined in the AppV package.

Browser windows launched from outside the virtual package will still use whatever security settings were pushed onto that machine by the SysAdmin, however. Only the AppV package that's running the browser will allow different security settings to be used.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
-1
Command Line
For Windows Internet Explorer 7 20070813.185237 I used the following...

Full Command Line: msiexec.exe /i /quiet "iesetup.msi"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
-4
Note
This reg file will delete the annoying stubs that run on every login of a new user. I'm suprised it hasn't been mentioned yet.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4383}]
"StubPath"=-

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\<{12d0ed0d-0ee0-4f90-8827-78cefb8f4988}]
"StubPath"=-

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\>{26923b43-4d38-484f-9b9e-de460746276c}]
"StubPath"=-

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\>{60B49E34-C7CC-11D0-8953-00A0C90347FF}]
"StubPath"=-

You may want to leave these in, if you don't want to update the default user registry hive for new users.

The default strings in those keys are internet explorer (twice), ie7 uninstall stub, and browser customizations.

Looks like a reboot is required between the install and any ie7 patches after that.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Internet Explorer

Version

20060823.002922

Uninstall String

"C:\WINDOWS\ie7\spuninst\spuninst.exe" "C:\WINNT\ie7\spuninst\spuninst.exe"

Questions & Answers (74)

Questions & Answers related to Microsoft Internet Explorer

2
ANSWERED
1
ANSWERS
1
ANSWERS
1
ANSWERS
1
ANSWERS
2
ANSWERED
3
ANSWERED
2
ANSWERS
0
ANSWERS
1
ANSWERS
2
ANSWERED
1
ANSWERED
1
ANSWERS
1
ANSWERS
1
ANSWERS
1
ANSWERED

Reviews (0)

Reviews related to Microsoft Internet Explorer

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ