Deploying IE 10 for Windows 7

2 Pages
←
1
2

You cannot start a new topic
You cannot reply to this topic

Deploying IE 10 for Windows 7

#21 Tripredacus

K-Mart-ian Legend

Group: Super Moderator
Posts: 8,670
Joined: 28-April 06
OS:Server 2012
Country:

Posted 08 March 2013 - 10:04 AM

Can't disable the first run wizard... so that is out. I have sent this problem along to MS, waiting for an answer. I have a sneaking suspicion that the answer will be to inject it into the image... :rolleyes:

#22 Rico.JohnnY

Member

Group: Members
Posts: 246
Joined: 02-June 04
OS:Windows 7 x64
Country:

Posted 10 March 2013 - 07:36 AM

This tweak works fine for me

;IE10 - Disable first run wizard: 1 to homepage, 2 to welcome page, to enable just to remove the value
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=-

#23 maxXPsoft

MSFN Master

Group: Developers
Posts: 2,748
Joined: 14-November 03
OS:Windows 7 x64
Country:

Posted 10 March 2013 - 10:01 AM

An install with IE10 injected and xml disabling those things writes to the reg here. Most things related in xml will be written here

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\ActiveSetup\DisableFirstRunWizard]
"DisableFirstRunWizard"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\ActiveSetup\DisableWelcomePage]
"DisableWelcomePage"=dword:00000001

#24 Domain

Group: Members
Posts: 8
Joined: 14-June 05

Posted 10 March 2013 - 04:38 PM

Hmm, good information, fully tested and working here now.

I don't bother with applying every single patch individually, based my testing only order required is to make sure prerequisites are handled first (otherwise it will fail during IE 10 steps), then Internet Explorer 10, then Hyphenation/Spelling, followed by everything else. My base image is now 6 packages (prerequisites), IE 10, 62 critical, and 31 optional updates to get a Windows 7 image requiring no Windows update patches (not counting KB2533552 and Malicious Software Removal Tool)

dism /Image:.\mount /Add-Package /PackagePath:.\updates\prereq
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Win7.CAB
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Hyphenation-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Spelling-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\crit
dism /Image:.\mount /Add-Package /PackagePath:.\updates\opt

As for welcome screen/first run, this is working fine (as it has since GA release for IE8/IE9/IE10)

<settings pass="specialize">
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64">
            <DisableFirstRunWizard>true</DisableFirstRunWizard>
            <Home_Page>about:blank</Home_Page>
</settings>

#25 gotenks98

Member

Group: Members
Posts: 141
Joined: 02-June 05

Posted 11 March 2013 - 09:31 AM

Domain, on 10 March 2013 - 04:38 PM, said:

dism /Image:.\mount /Add-Package /PackagePath:.\updates\prereq
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Win7.CAB
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Hyphenation-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Spelling-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\crit
dism /Image:.\mount /Add-Package /PackagePath:.\updates\opt

As for welcome screen/first run, this is working fine (as it has since GA release for IE8/IE9/IE10)

<settings pass="specialize">
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64">
            <DisableFirstRunWizard>true</DisableFirstRunWizard>
            <Home_Page>about:blank</Home_Page>
</settings>

This is what I am trying to do but I keep getting failures on the updates when it gets like 30+ updates in. It keeps saying the image is no longer serviceable. I have to basically start over if I get this.

#26 Domain

Group: Members
Posts: 8
Joined: 14-June 05

Posted 11 March 2013 - 03:10 PM

gotenks98, on 11 March 2013 - 09:31 AM, said:

I can't say exactly what the issue is here... there is significant patch overlap once you start integrating IE... I believe you can end up breaking the image by trying to push a patch that was for previous version of IE into an image that already has a newer version integrated. For reference, these are the current set of patches used in my image to bring it fully up to date (at least until patch Tuesday tomorrow):

Pre-Req:

Spoiler

Critical:

Spoiler

Optional:

Spoiler

#27 maxXPsoft

MSFN Master

Group: Developers
Posts: 2,748
Joined: 14-November 03
OS:Windows 7 x64
Country:

Posted 12 March 2013 - 12:44 AM

Also if you inject too many times you will get those errors. Start over with fresh install.wim.
I inject monthly updates but after 3-4 times I start fresh and inject all at once. I have 122 64 bit msu total now

#28 gotenks98

Member

Group: Members
Posts: 141
Joined: 02-June 05

Posted 12 March 2013 - 05:46 AM

Your listing of updates will come in handy. I think I have almost as many if separating them out like that. What I will do is put all the critical updates separate and save the images in sections, like 30 updates at a time.

#29 Tripredacus

K-Mart-ian Legend

Group: Super Moderator
Posts: 8,670
Joined: 28-April 06
OS:Server 2012
Country:

Posted 12 March 2013 - 08:48 AM

Well I got the answer I thought I would... And there seems no real way to make IE 10 not open itself at the end of setup... and the recommended method is to inject it in the image. This makes sense since it is required for certain parts of the channel to not even offer IE8 or 9 and use IE10 across the board.

#30 myselfidem

Member

Group: Members
Posts: 2,388
Joined: 06-January 10
OS:Windows 7 x86
Country:

Posted 12 March 2013 - 12:18 PM

I have no trouble if all prerequisite updates are integrated and IE10 integrated.
And add inside Autounattend.xml these values for Windows 7 x86:

<settings pass="specialize">
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DisableFirstRunWizard>true</DisableFirstRunWizard>
            <DisableWelcomePage>true</DisableWelcomePage>
        </component>

#31 Domain

Group: Members
Posts: 8
Joined: 14-June 05

Posted 12 March 2013 - 02:29 PM

maxXPsoft, on 12 March 2013 - 12:44 AM, said:

Ah... very true. I didn't really think about this, since the early days when I automated the process, I always copy in a fresh wim at the start, and run the entire thing from scratch. It takes awhile, but it can just churn away while I am working on something else.

Also in case anyone cares, the only update to my previous lists from above for today's patch release was windows6.1-kb2807986-x64.msu (assuming IE10 is integrated, otherwise there are more)

*Edit* I take that back

windows6.1-kb2791765-x64.msu also replaced windows6.1-kb2762895-x64.msu

This post has been edited by Domain: 12 March 2013 - 02:34 PM