The normal way to do things with an MSI is any property in the property table who is named entirely with capital letters is considered a public external property. This means it is settable when you run the MSI from the command line. So if you work out how you want to flag your language choice, put a property in for it, and then you can link the installation of components or features inside the MSI to that flag/variable. So if you are not familiar with the concepts yet, check out components, features and properties of MSIs. You don't mention which MSI builder you are using - if you are using the one that comes with Visual Studio i don't know if it is capable of giving you access to the components and feature, but there are one or two low priced or free (i.e. Wix) alternatives out there that do (if you are using something proper like Wise or InstallShield then you have full control over all these things).
Edit: to a script that will extract a list of public properties for you (click on the text Get MSI-File properties.vbs to see the script). Alternatively, and may provide you some other options. The guys over on will probably be able to help a lot more with this, I know there are some Windows admin tools that allow you to disassemble and/or wrap up MSis but I can't remember what they are called. ( Note: I posted a variation of this response on a different StackExchange site for a similar question.) lessmsi is a great tool that certainly works here if you're willing to pop open its GUI and do some manual investigation.
The only thing I don’t like about CutePDF Writer is that it comes with a little bit of bloat with the Ask Toolbar and wanting to set your browser homepage to Ask.com but you can uncheck these options during the install. Rem install cutepdf writer, silent install. Program Files Acro Software CutePDF Writer. This method will create am msi that installs CutePDF Writer.
If you're looking for a quick fix, you can try: lessmsi l -tProperty Unfortunately, it is likely that the above command will not output the properties you're looking for (sidenote: the output is csv formatted). One way to essentially guarantee that you get all the possible properties is to actually perform either an installation, repair, or uninstall with the MSI file and log the process.
![Msi Msi](http://1.bp.blogspot.com/-h4yBmGxGSPw/UGHKllbXeII/AAAAAAAAADY/ULEl8xfg9lg/s1600/14.png)
The following command records only the properties and nothing else: /lp! The above command is equivalent to: msiexec /lp! /i My preferred method, however, is to not actually install/remove/repair (and to simply extract instead).
The advantages this method has over lessmsi is that it doesn't require a 3rd-party utility (i.e. Lessmsi), and it doesn't require you to mess with any installations. Given that you have enough disk space to actually install the program, you can do: msiexec /a /lp! TARGETDIR= Note that the can point to a nonexistent directory (the command will create the directories necessary or fail).
If you hate the installation UI for whatever reason you can append the /qr option, which will 'reduce' and possibly eliminate the UI without impairing the property logging process. Be warned however-if you go 'lower' than the reduced UI (viz. /qb /passive or /qn /quiet), your may be missing some properties. Once the process has finished, you simply open up the logfile and note the lines beginning with Property(S):/ Property(C).
Generally speaking, the parameters/properties that can be set for an install are logged in ALL CAPS; for example, ALLUSERS can be set ALLUSERS=1 so that the installation is for all users. So for the example just given, your unattended mode installation could look something like: msiexec /i /passive ALLUSERS=1.
Welcome to exemsi.com. We specialize in converting executable setup programs to MSI packages. System administrators often prefer MSI over a normal setup.exe. MSI packages are better suited for software distribution through Active Directory group policies. The target audience for this website is:. Software developers who have a setup.exe and want to offer an MSI that wraps their original setup.exe.
System administrators with a setup.exe they want to distribute as an MSI to client computers in their organization. Our MSI Wrapper is the tool that makes it easy to convert an executable setup program to an MSI package. We were looking for a MSI wrapper that would meet top restrictive enterprise requirements for a large customer:. The MSI package will report completion only when the internal setup exe installation process truly completes.
The MSI package will return error codes returned by the internal setup exe file. Works on XP and above, 32bit and 64bit architectures. Using MSI packagers (that re-create native MSI setup kit) was not an option (due to very complex installation scripts we have), so we had to test all the MSI wrapper tools we could put our hands on. We tested a few MSI wrappers, and the only MSI wrapper that met those requirements was MSI Wrapper from EXEMSI, and by that it saved us from working a few months re-writing the whole installation script with a new setup builder tool that creates native MSI files, not to mention the cost of the other setup builder tool.