Discussion Locked

IE Deployment using W2K, AD and MSI

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm trying to deploy IE across my organization which has over 250 users with OSs spanning from XPPro, 2K & NT. Most users do not have admin rights.

After consulting a number of MSFT's KB articles I tried solutions from logon scripts[2] to command line parameters[3]. I've also tried deploying some applications using MSI packages and W2K's Active Directory and Group Policy[1]. Some packages were successful but not IE.

I can control the policies, restrictions and browser appearance through the GP but still need to deploy the custom package in order to update older version of the browser.

I've created a URD Package using IEAK[4] and am using the MSI Wrapper[5] to run the setup.

The GP is working ok but the MSI wrapper isn't executing the package I create, even after updating the "IE6SetupPath" property to the path to the shared distribution folder referring to file "ie6sp1gp.exe" as informed on the MSI Wrapper Administrators Guide[5].

I've created a folder on the network \\server\share\ (example). The MSI files are on the root of that folder and the custom made package is at \\server\share\FLAT\WIN32\EN and \\server\share\INS\WIN32\EN.

What am I doing wrong? Why isn't the MSI wrapper executing my package?

Also article 810011[5] says "Installation Behavior: When a client computer restarts, Group Policy runs Ie6sp1gp.msi, which then starts Ie6sp1gp.exe to run Setup to install Internet Explorer 6 SP1.". But article 314934[1] says "Publishing Software: You can publish a program distribution to users. When the user logs on to the computer, the published program is displayed in the Add/Remove Programs dialog box, and it can be installed from there.". Which one is it then?

Tks,
AD

1.http://support.microsoft.com/?id=314934
2.http://support.microsoft.com/?id=296702
3.http://support.microsoft.com/?id=200007
4.http://www.microsoft.com/windows/ieak
5.http://support.microsoft.com/?id=810011

3 replies

by cg it

there's 2 methods of deployment advertised and published. and in advertised you assign the program either to a user or a computer [assigned to user the program follows the user around regardless of which computer they use. Assigning it to a computer anyone that uses it gets the program.

Publishing displays the program in the add/remove programs applet in control panel. User then can if they so choose install it and subsequently uninstall it. both methods advertised and publish require .msi packages.
now if your trying to customize the installation of Internet Explorer which will include the critical updates for IE I would suggest you go with Software Update Services in lieu of creating your own package and trying to distribute it out from a distribution point.
Also if your going to deploy the O/S AND security updates you can use the SDK tools [will continue with comments post. have to go find the SDK tools link].

by ad

Thanks for your answer.

I already knew the difference between the Publish and Assign methods and the computer and user assignment.

However, I'll take a look at the SUS (Software Update Services). I only want to update IE to the most up-to-date version so there's really no need for a custom made package.

I do, however, appreciate ideas and comments from other members.

Tks,
AD

This discussion is closed to new replies.