3 ms·
And people still use it over creating MSIs? Madness. I hate everything that's not an MSI as I deploy software in schools. Of course as soon as Office 2007 stopp
by mavhc 10y ago
And people still use it over creating MSIs? Madness. I hate everything that's not an MSI as I deploy software in schools. Of course as soon as Office 2007 stopped being a normal MSI all hope was lost. If Microsoft won't use it why would anyone else?
- cm3 10y agoMSI and the whole Microsoft setup engine ecosystem is very wrong and a waste of hardware resources and people's time. I get the benefits of MSI and MSM when managing a fleet of machines, but it exhibits the same issues as Microsoft's other installers and update engines. It takes ages to do anything and during that seemingly seeks around the disk or eats up cpu for no reason. Sometimes it takes minutes or an hour just to return a failure condition at the end. If you compare the update process of a Debian install, which can update before first boot, to a Windows installation, you cannot explain what Microsoft is doing. The only explanation I've heard is that Windows doesn't have the required info in their databases and thus has to seek around the disk for a very long time. Now, if you compare that to an NSIS installer, which admittedly doesn't support the Windows Domain deployment scenarios that MSI does, it's instant and you can understand where time is spent. I do not understand why Microsoft doesn't fix those shortcomings.
- flukus 10y agoMSI is absolutely awful to deal with when you've got automated deployments. Chocalatey is much nicer.