<p>I have a product which has been traditionally shipped as an MSI file.  It is deployed through some sort of SMS push to thousands of desktops by our various clients.  The software we use to create these installers is getting long in the tooth and we are looking to replace it.  We have already standardized on InstallAnywhere for most of our products as we support many operating systems.  Unfortunately InstallAnywhere cannot produce MSI files.  </p>

<p>I am wondering if it is required that SMS use MSI files or if it can handle other installer types (.exe).  If not, are there any open source programmes for creating MSI files?  </p>

[{'answer_id': 21650, 'author': 'Chris', 'author_id': 2134, 'author_profile': 'https://Stackoverflow.com/users/2134', 'pm_score': 2, 'selected': False, 'text': '<p>If you want to create <code>MSI</code> files, try <a href="http://wix.sourceforge.net/" rel="nofollow noreferrer">WiX: Windows Installer XML (WiX) toolset</a>.</p>\n\n<p>It\'s an addon to Visual Studio 2005 and 2008, is open-source, and Microsoft developed.  You can use XML to specify and create MSI files.  There is a <a href="http://robmensching.com/blog/" rel="nofollow noreferrer">wealth</a> <a href="http://www.joyofsetup.com/" rel="nofollow noreferrer">of</a> <a href="http://blogs.msdn.com/astebner/" rel="nofollow noreferrer">resources</a> available on it, and <code>WiX 3.0</code> is, although in beta, is very complete.</p>\n\n<p>Also, note that you don\'t have to start from scratch, you can decompile an existing MSI using the WiX <code>Dark</code> utility, modify the XML in any way you like, and then recompile it into an MSI.</p>\n'}, {'answer_id': 21726, 'author': 'saschabeaumont', 'author_id': 592, 'author_profile': 'https://Stackoverflow.com/users/592', 'pm_score': 3, 'selected': True, 'text': '<p>If your clients are using SMS then you\'re in the clear... SMS supports EXE. You enter a command line when creating \'Programs\' and clients are probably already calling msiexec to launch the MSI. Also I\'m pretty sure SMS predates the MSI file format :)</p>\n\n<p>However if they\'re using <code>Active Directory / Group Policy Objects</code>.. then you\'re SOL as that does depend on MSI format for deployment.</p>\n\n<p>If you do want to stick with InstallAnywhere, there are a number of "MSI repackaging" tools available. Assuming you\'re looking at a basic application (device drivers might be an issue) then repackaging should be a fairly painless process.</p>\n'}, {'answer_id': 21775, 'author': 'Sören Kuklau', 'author_id': 1600, 'author_profile': 'https://Stackoverflow.com/users/1600', 'pm_score': 1, 'selected': False, 'text': "<p>Actually, with group policies, there's the <code>ZAP</code> file alternative, but I would recommend regardless that you learn <code>MSI</code>. It's not that hard, and very flexible.</p>\n"}]
['https://Stackoverflow.com/questions/21635', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/361/']