Internet Explorer 10 has finally been released for Windows 7 SP1, but it brings a few headaches with it. Downloading the standalone installer works pretty well for individual installs, but as part of the install it will look for particular prerequisites and attempt to download them if they are not present.
That’s all well and good, but in an enterprise environment we don’t want to rely on the installer going out to download updates from the internet, and it would be really great to be able to evaluate ahead of time which machines don’t meet the requirements.
Microsoft has released a Knowledge Base article, KB2818833, specifically outlining the prerequisites for installing Internet Explorer 10 on Windows 7 SP1. It lists the following five requirements:
- 2729094 An update for the Segoe UI symbol font in Windows 7 and in Windows Server 2008 R2 is available
- 2731771 An update that provides new APIs for conversion between local time and UTC in Windows 7 or in Windows Server 2008 R2 is available
- 2533623 Microsoft Security Advisory: Insecure library loading could allow remote code execution
- 2670838 A platform update is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
- 2786081 Internet Explorer 10 does not save credentials for a website after you log off or restart a computer that is running Windows 7 SP1 or Windows Server 2008 R2 SP1
With a little digging, you’ll quickly find that 2533623 is actually superseded by 2731771…which is itself now superseded by KB2758857. This is important to know for the simple fact that neither 2533623 nor 2731771 typically show up in Software Updates for ConfigMgr 2012 SP1, while 2758857 does show up (assuming you sync updates with the “Security Updates” classification). Likewise, 2786081 will typically show up in SUP under the “Critical Updates” classification.
That leaves two more updates…2729094 and 2670838…and unfortunately these are not so easy. Brandon Linton has provided an excellent explanation of “how to deploy phantom updates” in ConfigMgr 2012. Update 2670838 is actually classified as a “Feature Pack” so you will need to update your SUP configuration to sync those updates. Following Brandon’s method, you can pull down these two updates from the Microsoft Update Catalog, import them into WSUS, and sync them to ConfigMgr 2012.
So, this should provide us with the four specific updates we need as prerequisites for Internet Explorer 10 on Windows 7 SP1:
Now that we have these updates, we can create a Software Update Group and Deployment Package for our prereqs, and deploy it to our Windows 7 SP1 workstations in preparation for Internet Explorer 10 deployment. Your method may vary, but a quick option is to navigate to the All Software Updates node, click the Add Criteria dropdown, select Article ID and click Add. Repeat this three more times to give four total fields, then enter the four Article IDs above.
Highlight the updates (eight total, four for each platform) and click Create Software Update Group.
Now navigate to the Software Update Groups node, right-click on the newly created SUG, and click Download.
Walk through the wizard to create a new Deployment Package…
…adding it to the appropriate Distribution Points and so forth.
After the download has completed, we can right-click on the SUG again and click Deploy to create a test deployment and verify the updates come down successfully on Windows 7 SP1 machines, and then eventually deploy them out to our Windows 7 SP1 workstations.
Once we have successfully deployed the prerequisites, it’s time to download the Internet Explorer Administration Kit (IEAK) for IE10 to create a customized, deployable installation in a fully supported Windows 7 environment!