How to configure IEAK 7, IEAK 8 or IEAK 9 to deploy Internet Explorer 7, 8 or 9 with the menu bar visible without using Group Policy

System Requirements:

  • IEAK 7, 8, 9
  • Windows Vista, 7
  • Windows Server 2008, 2008 R2

The Problem:

The current version of IEAK allows you to configure the visibility of the command bar, the status bar and the tool bar however the option to make the menu bar (file, edit view etc) visible on the default install appears to be missing from the current revision of IEAK 9.

You can enforce the visibility of the menu bar through registry changes or through group policy, but the former is a headache requiring application during log-in and the latter does just what it says on the tin – it enforces it. Part of the design ideology of IE 9 was to reduce the UI of the browser to the simple necessities. While many users, particularly novice users will want the menu bar, some of your users may simply want to change all of their settings back to the IE 9 defaults.

“The web the way you want it”

More Info

If there is an option for configuring the menu bar visibility in IEAK 9, I can’t see it. Perhaps it is an oversight on the version that I’ve been building against and perhaps it’ll appear in a service release. For the time being, it’s just not there.

The Fix

The fix is to modify the custsec.inf that is generated by IEAK and then applied to the deployments default security context at package build time (.exe or .msi).

  1. Create your IEAK profile with all customisation’s, modifications and settings. Build it once (create the .exe or .msi)
  2. Exit IEAK
  3. Re-open IEAK and progress through the wizard until you arrive on the File Locations screen. Here, before continuing select the ‘Advanced Options…’ button
    IEAK 9 Advanced Options Button
  4. Now browse for the INS file that was created by IEAK during its first pass – note you are looking for the INS file associated with the pass, not the INF file that you edited in step 4. It will be located in the same folder
    IEAK 9 Browse for INS file
  5. Once located, click OK to return to the wizard and re-run through all of the options. IEAK should have remembered all of your preferences.
  6. Stop once you arrive at the ‘Wizard Complete’ screen
    IEAK 9 Pre-build Wizard Complete Screen
  7. Leaving IEAK running in the background. Open the build path’s INS folder in Windows Explorer. If you are building for Windows 7 / 2008 R2 x86 in English then by default this is something along the lines of:
    C:\builds\12232011\INS\WIN32_WIN7\ENU
    If you are building for Windows Vista / 2008 x64 in English then by default this is something along the lines of:
    C:\builds\12232011\INS\AMD64_VISTA\ENUNote that you are going into the INS folder, not FLAT or any of the others which have a similar structure.
  8. Locate and open the custsec.inf file in Notepad. This contains the security context data that will be built into the deployment package.
  9. Somewhere under the [AddRegSection.HKCU] section add:
    HKCU,”Software\Microsoft\Internet Explorer\MINIE”,”AlwaysShowMenus”,0x10001,1,0,0,0This will enable the menu bar by default when new IE profiles are created as part of Windows user profile generation on the local machine. To disable the menu bar simply change it to:
    HKCU,”Software\Microsoft\Internet Explorer\MINIE”,”AlwaysShowMenus”,0x10001,0,0,0,0
  10. Save and exit Notepad
  11. Return to the IEAK wizard and press the Next button. IEAK will now build the customised installer files
  12. Note that if you re-run IEAK it will overwrite your modifications to custsec.inf as it exits the ‘Additional Settings’ screen. Consequently you will have to reapply them from step 7.

If you wanted the custsec.inf modifications for the other toolbar options they are:

  • HKCU,”Software\Microsoft\Internet Explorer\MINIE”,”LinksBandEnabled”,0x10001,1,0,0,0
  • HKCU,”Software\Microsoft\Internet Explorer\MINIE”,”CommandBarEnabled”,0x10001,1,0,0,0
  • HKCU,”Software\Microsoft\Internet Explorer\MINIE”,”ShowStatusBar”,0x10001,1,0,0,0

Make sure that you test your installers before deploying with this as clearly it is unsupported.

Deploying Internet Explorer 7.0 from a Slipstreamed Windows XP CD

System Requirements:

  • Windows XP Home Edition
  • Windows XP Professional Edition

The Problem:

This article follows on from my integrating Windows XP SP3 with Windows Media Player 11 guide. The aim of the article is to discuss the simplest way to deploy Internet Explorer 7.0 from the CD, automatically and without using third-party software.

 

More Information:

Yes, there are automated, third party integration methods for this, but you wouldn’t use them in a commercial environment (sensibly).

If you want IE7 to install, and are not fussed about it being ‘integrated’ then the following will get you to where you want to go under both XP Home and Professional Edition. It should also work with the soon to be released Internet Explorer 8 come its RTM towards the end of the year.

Please note that the following is CASE SENSITIVE and should be followed to the LETTER:

  1. Open c:\integrated (from the XP SP3 + WMP11 Slipstream Guide) or substitute with your own folder with the CD files inside where applicable
  2. Create a new folder called:
    $OEM$
  3. Create a new .txt file in c:\integrated\$OEM$\ called:
    CMDLINES.TXT
  4. Open CMDLINES.TXT in notepad and add:
[Commands]
“rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\OPTIONS.INF”
“cmd /c start /min cmd /c .\AddOEM.bat”
  1. Create a new .bat file in c:\integrated\$OEM$\ called:
    AddOEM.bat
  2. Open AddOEM.bat in notepad and add:
mkdir %SystemDrive%\$Setup
copy .\IE7INST.exe %SystemDrive%\$Setup
  1. Download IE7-WindowsXP-x86-enu.exe (the IE7 installer) into c:\integrated\$OEM$\
  2. Rename IE7-WindowsXP-x86-enu.exe to IE7INST.exe
  3. Create a new .inf file in c:\integrated\$OEM$\ called:
    OPTIONS.INF
  4. Open OPTIONS.INF in notepad and add:
[Version]
Signature=$CHICAGO$[DefaultInstall]
AddReg=IE7Updt.AddReg

[IE7Updt.AddReg]
HKLM,”Software\Microsoft\Windows\CurrentVersion\RunOnceEx\1001″,”IE7 Update”,,”%30%\$Setup\IE7INST.exe /passive /nobackup /update-no /forcerestart”

  1. Open c:\integrated\i386
  2. If it does not already exist, create a new .txt file called:
    unattend.txt
  3. Open unattend.txt in notepad and enter the following, integrating or overwriting (recommended for novices) the entire file content with:

;SetupMgrTag

[Data]
MsDosInitiated=”0″
UnattendedInstall=”Yes”

[Unattended]
UnattendMode=ProvideDefault
OemPreinstall=No
TargetPath=\WINDOWS

  1. Burn the revised c:\integration folder to disc as normal to create a bootable slipstream CD

If you have followed these steps correctly then you will be able to install the integrated XP SP3 + Windows Media Player 11 package that I demonstrate how to build here and have IE7 installed by the time you first get to the desktop.
There will be an extra reboot involved as the updated Internet Explorer is applied during the initial post-install startup.

Should you wish to patch Internet Explorer 7.0 as part of this process, you will need to modify the AddOEM.bat, OPTIONS.inf and contents of the $OEM$ folder with the patch files, file copy commands and installation processes. Do remember to ensure that the RunOnceEx run number is > 1001 so that the patch is applied after the installation of IE7.

You will not be able to uninstall Internet Explorer 7 from the machine using these scripts. If you require uninstallation support for IE7 then remove “/nobackup” from the OPTIONS.INF file IE7Updt.AddReg line.

Known Issues

  1. This method causes a reboot before the completion of the first boot to a user desktop. There is a quirk involved in this which means that the account that you configure during setup (administrator under XP Professional) will ultimately load with luna, the Windows XP visual style disabled. You can re-enable this from Desktop in the Control Panel should you want to use Windows Luna.
  2. The folder $Setup will remain on the root of C:\ after the installation has completed. You can safely delete this folder.

Using IEAK 5.x under Windows XP or Internet Explorer 6 / 7

System Requirements:

  • IEAK 5.0
  • IEAK 5.01
  • IEAK 5.5

The Problem:

If you need to build an IEAK 5.0, 5.01 or 5.5 internal distribution for your organisation, or you are just playing with the older IEAK versions, then you will encounter a significant problem if you happen to be using Windows XP, or have upgraded your web browser to Internet Explorer 6.0 or 7.0.

IEAK configurations are designed to operate exclusively under the Internet Explorer release they are generating redistributable’s for, and will bluntly refuse to work if you attempt to fob it off with a greater IE version.

The Fix:

Pretty simple really. Like most of Microsoft’s application dependencies, it’s nothing more than observable madness, built in for some strange reason (presumably to force Internet Explorer 3/4 users to migrate to 5.x. Quite why it wasn’t deemed sensible to program IEAK…

if MSIE version <=4.01 SP2 then
Terminate
else
Proceed
End if

… is beyond me. Anyway. The fix is so extremely simple, you will wonder why you were reaching for a Windows install CD.

  1. Open up Regedit and navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer
  2. Find the string value called Version and edit the Major and Minor version to match the version of IEAK that you are attempting to install. For Example:
    Change 6.0.2900.2180 into
    5.5.2900.2180 for IEAK 5.5 or
    5.0.2900.2180
    for IEAK5.0x.

I don’t recommend that you fiddle with the build number, as you’ll probably forget it when you go to switch it back again. As soon as you have run IEAK for the first time, you can safely switch it back to whatever you had before.

It wont bother you again after that.