Hi Guys,

I have created a package of IE7 and trying to deploy it via GPO and I am unsuccessful.

I have used IEAK7 to create IE7Setup.exe. Now copied this in my package folder (Internet_Explorer_7.0_b01)

Now I have created an .msi wrapper and used a custom action in that to call this IE7Setup.exe from SourceDir.

When I run my msi manually it successfully install IE7 on my machine but when I try to install this msi via GPO, .msi fail to call the IE7Setup.exe.

What could be the reason.

Any suggestions please.

Thanks,
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Could this be a problem that .msi fail to call the IE7Setup.exe from a network location.

I mean to say that GPO call the .msi from a UNC path \\abc\dfs\Internet_Explorer_7.0_b01

and .msi and IE7Setup.exe is located in Internet_Explorer_7.0_b01 folder

But I have tried another way as well which also fails.

I have tried to first copy the IE7Setup.exe in c:\windows\temp folder

and then run it from there instead of Sourcedir

Even this is not working via GPO....while manual installation on machine works fine..
Answered 01/15/2010 by: djain3
Second Degree Blue Belt

Please log in to comment
0
Why not leave the IE7 update to WSUS/Windows Update?
Answered 01/15/2010 by: VBScab
Red Belt

Please log in to comment
0
Hi Vbscab,

I know that is the best way...but client want it to be packaged and delivered it this way to their 100 of users...

please advise what could be causing problem in its deployment via GPO.

Regards,
DJ
Answered 01/17/2010 by: djain3
Second Degree Blue Belt

Please log in to comment
0
You have, of course, consulted AppDeploy's Package KB? See the 'Notes' section.
Answered 01/17/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity