/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hello Package Experts
With the native Windows Server 2003 Group Policy and *.msi / *.mst Files, i have installed some Software Distribution in smaller environments with success. With "repackaging", i could also distribute som "non-native-msi" Applications.
But what i want is to distribute and launch "unattended installation" on behalf of native group policies. The *.zap File is not a solution, because it runs in user context and only to publish software.
Exists a solution to use GPO's Software distribution with Applications installable only by "setup.exe /... " e.g. by launch the setup-command within a *.msi?
Thanks and regards.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
Sounds like you want a wrapper to uninstall an legacy setup through a MSI?
Answered 08/04/2005 by: AngelD
Red Belt

Please log in to comment
0
Hello AngelD
A Wrapper Yes, but not to uninstall. I want to automate the installation of a legacy application with native GPO Tools. So the solution should "insert" the files from the application in a msi, distribute this to cliets using GPO and then kick-off the installation on the clients with the silent-install command like Setup.exe /s.
Regards hbru
Answered 08/04/2005 by: hbru
Yellow Belt

Please log in to comment
0
Why not repackage the whole thing?
Answered 08/04/2005 by: AngelD
Red Belt

Please log in to comment
0
Hello AngelD
For some Applications is repackaging OK. But for others, we have to look on the restrictions, how they are described in http://support.microsoft.com/?id=264478. At the moment, we distribute these applications placing it in a shared folder and using a startup script with the silent install command like setup.exe /s. But with this, we have some apps to distribute with GPO and *.msi like described in the scoolbook from Microsoft and the others with pure scripting. This ist not the way we want to do it.
Regards
hbru
Answered 08/04/2005 by: hbru
Yellow Belt

Please log in to comment
0
Well what you can do is to create an MSI template (file) which you have to generate a new GUID for each application you want to have this as a installation mechanism for legacy setups.

MSI "template" should contain:
1. "InstallLegacy" CA that take a property as installation command, that runs if "NOT Installed".

2. "UnInstallLegacy" CA that take a property as uninstallation command that runs if "REMOVE = ALL".

Is that what you want so that you can use the MSI for distributin through Active Directory?
Answered 08/04/2005 by: AngelD
Red Belt

Please log in to comment
0
Hello AngelID
Because i'm not yet the packaging senior, i need some detailed explanations to your last idea, how to implement it.
Thanks and regards
hbru
Answered 08/07/2005 by: hbru
Yellow Belt

Please log in to comment
0
Have a look at http://www.wise.com/Library/CustomActionsWithKiXtart.pdf
This will describe how you can manage this.
Answered 08/08/2005 by: AngelD
Red Belt

Please log in to comment