On Tue, Feb 14, 2012 at 6:16 PM, Matthew W. Ross <[email protected]> wrote: > How do I use Group Policy to assign a .MSI file to an OU, while also > passing command line options?
You can't pass command-line options to MSIEXEC from a GPO. Fortunately, everything can almost always be done with an MST. > setupfile.msi PROXY_SERVER=<server> PROXY_SERVER_PORT=<port> > ENABLE_PROXY=<true|false> SKIP_READINESS=<true|false> /qn All of those ALL_CAPS options are, in fact, setting MSI Properties. Every MSI has a list of Properties. Kind of like environment variables, but specific to each package. Your typical MSI file includes a bunch. The ones you specify on the MSIEXEC command-line get merged with those. > I found that I could make a .MST file (a transform?) Yes. MSI = package. MST = transform. An MST is essentially a set of changes vs an MSI. So you do up your changes in an MST, and then apply that at install time. > I see a spot for it in the Group Policy editor under the Modifications Tab You got it. > So, how do I make a custom .MST? I use ORCA. > Further googling pointed me to Orca and InstEd, MSI database editors > with the ability to make MST files. The only problem is that, thus far, > how to go about doing this is as clear as mud. From within ORCA, open the MSI file. Then go to the "Transforms" menu, and do "New". Now make your changes to the MSI tables. When done, do "Generate". That will build the MST with your changes. Hope this helps, -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
