The MS approach is that you must use transform files (.mst) to modify the package. There are apps which will let you work with these (Orca and InstEd both spring to mind) but there is no way to directly enter command line switches in AD. Peter On 16/03/2009, bugzilla-daemon at bugzilla.wpkg.org < bugzilla-daemon at bugzilla.wpkg.org> wrote: > > http://bugzilla.wpkg.org/show_bug.cgi?id=141 > > > > > > > --- Comment #4 from Tomasz Chmielewski <mangoo at wpkg.org> 2009-03-15 > 14:01:44 --- > I think we could do it. > > Although it's really hard for me to believe that Active Directory really > does > not allow setting parameters to MSI packages it deploys via GPO. > > What a system for deploying MSI packages it is if it can't really deploy > MSI > packages? > > Every second MSI installer has such parameters - activation key, inf file > with > settings, other options. > > > Did anyone try asking at a Windows-specific mailing list if such parameters > are > somehow settable via GPO? > > > > -- > Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the QA contact for the bug. > ------------------------------------------------------------------------- > wpkg-users mailing list archives >> > http://lists.wpkg.org/pipermail/wpkg-users/ > _______________________________________________ > wpkg-users mailing list > wpkg-users at lists.wpkg.org > http://lists.wpkg.org/mailman/listinfo/wpkg-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090316/cd09df93/attachment.html> |