Good afternoon. I've been asked to deploy a package to specific labs, and the software developer was kind enough to provide a .MSI installer.
I want to use Group Policy to push this out to the labs. Group Policy deployment has been extremely useful for us, and I want this to continue. Unfortunately, the MSI installer has a few defaults that I want to change. How do I use Group Policy to assign a .MSI file to an OU, while also passing command line options? Essentially, I can instal this silently with my options this from the command line using the following command: setupfile.msi PROXY_SERVER=<server> PROXY_SERVER_PORT=<port> ENABLE_PROXY=<true|false> SKIP_READINESS=<true|false> /qn ==== So, I've been doing my GoogleFu, and I found that I could make a .MST file (a transform?) to apply my options to the MSI at the time of install (I see a spot for it in the Group Policy editor under the Modifications Tab). See: http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/b3e7bacd-1c33-4d72-a9c6-5a641968c7b1/ So, how do I make a custom .MST? 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. Could anybody give me a few pointers or point me in the right direction to complete this? Thank you in advance. --Matt Ross Ephrata School District ~ 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
