I have been playing around with a AdminStudio and trying to repackage this but am having some trouble. Mainly it looks like it cant replace some locked .dll files.
How have you deployed this in your org.


0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


We used WSUS for one customer as the 3.1 version is required for the WSUS agent/client to work.
SMS for another customer.

Do not repackage this.
Use the original media or you could try an msi wrapper but I have never tried that.
Answered 09/12/2006 by: AngelD
Red Belt

Please log in to comment
I just finished deploying windows installer 3.1 on a dozen or so machines. I used ZenWorks which ran WindowsInstaller-KB893803-v2-x86.exe from a network drive. I used the /passive switch to disallow user interaction. The conditions were basically if the file version of C:\windows\system32\msi.dll was lower then 3.1 to run this package.

Please note: Installing XP Service Pack 2 includes installer 3.1. I also had a few computers who had some issues with it and I had to run WindowsInstaller-KB893803-v2-x86.exe /uninstall then WindowsInstaller-KB893803-v2-x86.exe /passive.

Hope that helps.


Answered 09/15/2006 by: tyler
Yellow Belt

Please log in to comment