> 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.
Ah, Properties. When I first opened the MSI in orca, I was lost in the forest of tables I could edit. I didn't know where the settings I wanted to change were. Thanks for pointing out the Properties table, that's exactly where I needed to look. > 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. This was the other detail lost to me. Now that I know how to generate the transforms, I'm wondering about other MSI's I can play with... Sm:)e. > Hope this helps, It helped a ton. Thanks again, Ben. --Matt Ross Ephrata School District ----- Original Message ----- From: Ben Scott [mailto:[email protected]] To: NT System Admin Issues [mailto:[email protected]] Sent: Tue, 14 Feb 2012 17:16:53 -0800 Subject: Re: MSIs, MSTs and custom installs. > 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 > > ~ 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
