Internet Explorer 7 Deployment Notes
We recently deployed IE7 to the Client PCs using Software Delivery Solution and I wanted to share few things regarding IE7 Deployment.
We used standard installation package from Microsoft, but you can use Internet Explorer 7 Administration Kit to modify installation package.
We created target deployment collection by checking if the IE7 record is present in Add/Remove Programs.
In effect we have two collections:
Collection One: Computers with IE7 installed,
with filter
Inv_AeX_OS_Add_Remove_Programs is populated by machine inventory, we run machine inventory twice a day.
Collection Two: Computers targeted for IE7 deployment
This collection includes All Windows XP PCs and excludes Collection One: Computers with IE7 installed
I know that target collection may be build with single SQL query, but I have found this way easier and more manageable.
Below are the installation notes:
- IE7 can be installed silently, without a reboot and without any user interaction
Command line is: IE7-WindowsXP-x86-enu.exe /quiet /update-no /norestart switch /update-no will make installation faster, as IE7 will not try to download updates from Microsoft
- IE7 is installed using 'pre-stage' technology: user is able to use IE6 until PC is rebooted and only then files are replaced and installation is complete.
We have found one slight issue with this: after IE7 is pre-staged, but PC has not been rebooted yet, favourites in IE6 stop working.
- IE7 installation keeps all users settings: home page, favourites, browser history, recently typed urls, secure certificates.
- Installation package is 14.7 Mb and actual installation takes about 5 minutes.
- IE7 can be uninstalled and PC can be reverted back to IE6, but only if additional MS updates for IE7 have not been applied.
This is one of the reasons we used switch /update-no
- After installation, when IE7 is run for the first time, user must answer two questions on two pages and then IE7 is ready for use. Initial configuration cannot be suppressed, as it is there by design, and runs once for every user on a PC. We had to send an e-mail to users with screen shots.


The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments 5 Comments • Jump to latest comment
My group deployed IE7 a month or so ago. It would have been really nice to have this information. We ended up creating a WISE package to prevent the computer from rebooting. Also we did find a way to prevent the "Initial configuration page" but because I didn't create the package, I dont know how it was done, but I do know it is possible.
The Internet Explorer 7 Administration Kit lets you suppress the initial config, as well as lets you do a lot more customization, pretty much anything you would want. You can also use it to create an install that is silent with no restart.
I have used IEAK 7 to customize IE7 and deployed it to a wide user base. It works fine. You can customize home page, disable the Run On First use screen. It is pretty handy.
IEAK 7 Download and Release Documentation
http://technet.microsoft.com/en-us/ie/bb219543.aspx
Thanks for the information 'tkight'.
VM
Guys,
If you want to add IE7 hotfixes along with IE7, there is restriction in IEAK7 especially naming convention of the hotfix.
Look at my article to know more about this:
http://juice.altiris.com/article/4861/internet-exp...
Thanks, Eshwar
Thanks for the replies guys,
Sorry if I *was a bit misleading,
We were rushed into IE7 deployment and I did not have time to use IEAK 7.
My post is more relevant if you deploying standard Microsoft package.
But if you plan your deployment accordingly and have plenty of time, by all means use IEAK 7 or other tools to customize installation.
Andrey Shipov
Manchester, UK
Andrey Shipov
IS Infrastructure Senior Engineer
Manchester, UK
Would you like to reply?
Login or Register to post your comment.