Internet Explorer 10 was released for Windows 7 in February 2013, and like the previous versions you can create a customized IE 10 application using the Internet Explorer Administration Kit (IEAK). You then configure MDT to install that application as part of your reference image build. Here is a guide that walk you trough the steps:
Update 2013-11-22: For adding Internet Explorer 11 to Windows 7 SP1, check this article: https://deploymentresearch.com/Research/tabid/62/EntryId/124/Adding-Internet-Explorer-11-to-your-Windows-7-SP1-reference-image.aspx instead.
Step-by-Step Guide
Anyway, the overview steps to add IE 10 to your Windows 7 SP1 reference image are the following:
- Download the IE 10 prerequisites and add as OS packages in MDT
- Create the IE 10 package using IEAK 10, and add as an application in MDT
- Add the application to your MDT Windows 7 SP1 task sequence
Note: Once you have created the reference image, you also need to update the Unattend.xml file for the task sequence used to deploy it. This is because the native template in MDT contains settings that are not compatible with IE 10. See the "Deploying a Windows 7 image with Internet Explorer 10" section later in this post for details.
Download the IE 10 prerequisites and add as OS package in MDT
- On the MDT01 server, create a folder named D:\Setup\IE10 PreReqs
- Download the following files to the D:\Setup\IE10 PreReqs folder
- In Deployment Workbench, in the Packages node, create a folder named Windows 7 SP1 x64.
- Expand the Packages node, right-click the Windows 7 SP1 x64 folder and select Import OS Packages.
- On the Specify Directory page, in the Package source directory text box, browse to D:\Setup\IE10 PreReqs and complete the wizard.
Note: If you are deploying multiple operating systems in your MDT deployment share, use selection profiles to limit what OS packages that are injected during deployment.


Create the Install – Microsoft IE 10 for Windows 7 SP1 – x64 Application
In these steps, I assume that you have downloaded IEAK 10 to your machine.
- Install IEAK 10 with the following settings:
- Choose License Type: Internal Distribution via a Corporate Intranet
- Organization name: ViaMonstra
- Start the IEAK 10 wizard (Internet Explorer Customization Wizard), and use the following settings:
- Destination Folder: C:\Setup\IE10 – ViaMonstra Build
- Target Platform: Windows 7 Service Pack 1 Systems (x64-Based)
- Target Language: English (United States)
- Package Type: Full Installation Package
- Feature Selection:
- Click Synchronize
- Note: The synchronize option may display the “Run” dialog box behind the window, so watch the taskbar.
- Custom Components:
- Browser User Interface:
- Search Providers: Click Import to add any search providers from your local machine.
- Important URLs – Home page and Support
- Remove the default home page, and add http://www.viamonstra.com.
- Clear the Retain previous Home Page (Upgrade) check box.
- Accelerators:
- Favorites, Favorites Bar and Feeds:
- Browsing Options:
- First Run Wizard and Welcome Page Options:
- Compatibility View:
- Connection Manager:
- Connection Settings:
- Proxy Settings:
- Root Certificate:
- Programs:
- Navigate to the C:\Setup\IE10 – ViaMonstra Build\FLAT\AMD64_WIN7\EN-US folder and copy the IE10-Setup-Full.exe file to your MDT server (mine is named MDT01, and I copied the package to D:SetupInstall – Microsoft IE 10 for Windows 7 SP1 – x64)
- Add the IE 10 Package to Deployment Workbench, by completing the New Application Wizard using the following settings:
- Application with source files
- Publisher:
- Application name: Install – Microsoft IE 10 for Windows 7 SP1 – x64
- Version:
- Source Directory: D:\Setup\Install – Microsoft IE 10 for Windows 7 SP1 – x64
- Specify the name of the directory that should be created: Install – Microsoft IE 10 for Windows 7 SP1 – x64
- Command Line: IE10-Setup-Full.exe /c:"IE-REDIST.EXE /quiet /norestart /update-no"
Note: The /norestart switch is critical, otherwise the IE 10 installation will reboot on it’s own and break the MDT task sequence.
- Working directory:

Edit the Task Sequence
In these steps, you add the Install – Microsoft IE 10 for Windows 7 SP1 – x64 application to your Windows 7 SP1 x64 task sequence.
- Right-click your Windows 7 Enterprise x64 SP1 task sequence, and select Properties.
- On the Task Sequence tab, configure the task sequence with the following settings:
- State Restore. After the Tattoo action, add a new Group action with the following setting:
- Name: Windows 7 Applications
- State Restore / Windows 7 Applications. Add a new Install Application action with the following settings:
- Name: Install – Microsoft IE 10 for Windows 7 SP1 – x64
- Install a Single Application: Install – Microsoft IE 10 for Windows 7 SP1 – x64
- State Restore / Windows 7 Applications. After the Install – Microsoft IE 10 for Windows 7 SP1 – x64 action, add a Restart Computer action.
- State Restore. After the Tattoo action, add a new Group action with the following setting:
- Click OK.

Done! You can now start your virtual machine, and run the build and capture task sequence.
Deploying a Windows 7 image with Internet Explorer 10
Once you have created the Windows 7 SP1 reference image with IE 10, you also need to update the Unattend.xml file for the task sequence you use to actually deploy it. If not, the deployment will fail with the infamous error: “Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist.”. This is because the native template in MDT contains settings that are not compatible with IE 10.
In these steps I assume you have created your reference image with IE 10 per the previous instructions, and imported into your production deployment share.
- Using Deployment Workbench, right-click the Windows 7 SP1 task sequence and select Properties.
- In the OS Info tab, click Edit Unattend.xml. MDT now generates a catalog file, which will take a few minutes, and then Windows System Image Manager (WSIM) starts.
- In Windows System Image Manager (WSIM), in the Answer File pane, expand the 4 specialize node, and select the amd64_Microsoft-Windows-IE-InternetExplorer_neutral entry.
- In the amd64_Microsoft-Windows-IE-InternetExplorer_neutral properties (right-hand window), right-click the IEWelcomeMessage property and select Revert Change.
- Save the Unattend.xml file, and close Windows System Image Manager.
- On the Windows 7 SP1 Properties window, click OK.


Happy Deployment
/ Johan
Hey Gordon,
The only things that comes to mind is using a script wrapper that does the needed configuration.
/ Johan
Hi, I work for a company that has offices across the globe. I was trying to do an SCCM application with the IEAK 10 to configure, setup IE for upgrades and well as current installs. I have been trying to set User Authentication to Automatic Logon with current user name and password as part of the IEAK deployment. The issue is that for the intranet sites, the employees get a popup. I would think the IEAK could set this and I do as part of setting up the IEAK. However, when it installs/reboot, the setting is not set, IE 10… Read more »
The MDT 2013 template is updated for IE10/11
/ Johan
Would this still apply to SCCM 2012/MDT 2013? Would I still need to make a change to the unattend.xml file?
Hi Danny,
I deleted the duplicated posts, no worries, and since you sent me an email as well, I will follow up offline.
/ Johan
FYI I am not using a captured image – Just a deployment
I have a two part question.
My first question is although I followed the instructions above IE installs through the application that has been added to the task sequence. I removed it from WSUS to insure it was installing it from the applications
However here is the problem all the modifications made for IE active x settings etc go back to default
Second question what is done with the packages that are imported into the packages on MDT do they just go there or am I supposed to do something else in the task sequence. Please explain
For WinPE you should always create a separate selection profile, so that only drivers and packages that are added to that profile are injected into the boot image… see this post for details: https://deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
The OS updates you add to packages are injected during deployment time.
/ Johan
So when you "Update Deployment Share".. does that try to inject all drivers and packages into your windows PE iso? as well as the actual windows 7 software?
I tried removing the IE10 PreReq's from "Packages", then WSUS wouldn't install IE10 on my reference task sequence anymore. I re-added the prereqs, updated deployment share, still get the errors about "software package not applicable" to windows PE environment, but I assume that still installs the patches to the Windows OS.
For updates, use the built-in Windows Update task in MDT. As long as IE 10 is installed before the Windows Update tasks run you're good.
/ Johan
As you know, just getting into deploying windows 7, I'm trying to patch the 'base/reference' image so users don't have to sit through updates. Found your post re: IE 10 in the reference image, as I watched all the IE8 patches apply from my WSUS server, then it installed IE10. Obviously, a waste of time.
I followed your above instructions and when I went to update the deployment share. Every KB file had an error 0x800f081e "specified package is not applicable".
Can't think of what I did incorrectly here.. 🙂 or if thats expected.
Hi!
Im using a similar method to this for deploying IE10 via SCCM 2007 with MDT integration, though having no luck.
Any tips for this method?
The additional command lines are not needed in IEAK 11, assuming you configure the new Internal Install settings in IEAK 11. I just posted an updated article on adding IE 11. https://deploymentresearch.com/Research/tabid/62/EntryId/124/Adding-Internet-Explorer-11-to-your-Windows-7-SP1-reference-image.aspx
/ Johan
Excellent read, many thanks!
Small question: I have used your guide to add IE11 to my Win7 builds. With the new IEAK for IE11 I have the possibility to specify "no reboot" and "totally silent" as part of the customization. In this case, would I still need the /c:"IE-REDIST.EXE /quiet /norestart /update-no" parameters you have used for IE10 deployment?
Cheers, Dan