Deploying Internet Explorer 11 … the proper way

Microsoft recommends using IEAK to create IE11 deployment package, however, based on my own (and my work colleagues) experience I know this is not the best way to create the deployment package. Due to the number of prerequisites it just loves to fail installing the browser that way.
Bellow method has been tested by me on 300+ machines (so far). There were couple of issues related to Enterprise Mode that I have identified, hence the patches added to the script. My work colleagues have tested this deployment method on if I remember correctly 2k+ machines with not a single issue. So to cut it short – it works.

Just a word, before I start.
Lets compare IE to other web browsers in terms of deployment method. How do you deploy Google Chrome? Its simple, all you need is an googlechromestandaloneenterprise.msi from here,  then you just package it with whatever deployment tool you prefer, SCCM, SMS, Altiris, PDQDeploy, AutoIT even PSExec, by simply adding /quiet /norestart (or just /qn) and ALLUSERS parameter, like this: msiexec.exe /i “googlechromestandaloneenterprise.msi” /qn ALLUSERS=2  – it just couldn’t be any easier.

Deploying Firefox in an enterprise environment is little bit more complicated, but still, its like a walk in the park comparing to IE. What you need is full redistributable installer and then you need a small .ini file with setup config where you can customize the installer. Quite straight forward to.

Internet Explorer is different :D

What do you need ?

– Prerequisites
– IE 11 installers
– Patches

Lets say we’ll be creating IE11 x86 and x64 package as we have a mix of 32 and 64-bit machines within our environment.
Create C:\IE11x86x64deploy folder – this will be your root folder.

You need to download the following prerequisites:

Download and place them all into PreReq folder within your IE11 root directory.

32-bit

–  Windows6.1-KB2533623-x86
–  Windows6.1-KB2639308-x86
–  Windows6.1-KB2670838-x86
–  Windows6.1-KB2729094-v2-x86
–  Windows6.1-KB2731771-x86
–  Windows6.1-KB2786081-x86
–  Windows6.1-KB2834140-v2-x86
–  Windows6.1-KB2882822-x86
–  Windows6.1-KB2888049-x86

64-bit

–  Windows6.1-KB2533623-x64
–  Windows6.1-KB2639308-x64
–  Windows6.1-KB2639308-x64
–  Windows6.1-KB2729094-v2-x64
–  Windows6.1-KB2731771-x64
–  Windows6.1-KB2786081-x64
–  Windows6.1-KB2834140-v2-x64
–  Windows6.1-KB2882822-x64
–  Windows6.1-KB2888049-x64

Download IE11 x86 and x64 standalone installers from here

Open command prompt and extract them into

IE11-Windows6.1-x86-en-us.exe /x:C:\IE11x86x64deploy\IE10_x86
IE11-Windows6.1-x64-en-us.exe /x:C:\IE11x86x64deploy\IE10_x64 

Download the following patches:

Download and place them all into Patches folder within your IE11 root directory.

KB292947 is an important one as it fixes an Enterprise Mode. Even though you enable Enterprise Mode via GPO, it won’t work without this patch.
Other two are cumulative security updates.

–  IE11-Windows6.1-KB2929437-x64
–  IE11-Windows6.1-KB2929437-x86 
–  IE11-Windows6.1-KB3078071-x64
–  IE11-Windows6.1-KB3078071-x86
–  IE11-Windows6.1-KB3087985-x64
–  IE11-Windows6.1-KB3087985-x86 

Now, above patches are already included in the script bellow, they are located AFTER IE11 install. If you prefer you can remove them from the script and install them separately.

Copy the script and place it into your IE11 root folder as IE11Installer-Win7.vbs
Once launched, the script will create  install log file in C:\Support\Logs .
You may wonder, why I added 3010 as a success code? There’s a suppressed reboot after IE11 install, therefore all patches will come with “3010 – restart required return code” once install is complete. Some deployment systems (ie. Altiris) see’s that as Install Failed and this will affect your compliance report.

 

 

Leave a Reply