Extend MDM MSI deployment
I would like the MDM MSI deployment (to MDM enrolled Win8.1+ clients) to be extended. Currently, only single MSI's are supported, I'd like this to include MSI's with .cab's, MSP files to patch installed MSI apps, and to be able to deploy .exe installers.
+1, and another feature I think is missing is the ability to deploy a file or set of files alongside a software installation. This feature was available in the Classic portal (include files/folders), but is no longer present in the Azure portal.
That said, I came across the Intune Management Extension the other day and it seems that this feature will be rolling to Prod in the near future?
This may solve a lot of these problems for us, if we can do a little scripting to close the gaps. Am I wrong?
@Thomas Kurth - thank you for sharing your information. I will look into that.
We have done some testing utilizing the 'Desktop Bridge' provided by Microsoft, transforming elder software including subfolders to .appx applications. From there we add the applications to the Windows Business Store and distribute via Intune.
Works fine so far. But we have only tested a number of software packages. There might be problems with very old or complicated setup configurations.
So far so good... :-)
I do think this will be the official answer from Microsoft at some point. But that is my take and not an official statement.
Thomas Kurth commented
We had the same issues in our Intune Projects, therefore we created a solution on Syntaro which gives us the needed features like (multi file, other executables, BranchCache and Chaining of Packages) for Intune.
Perhaps it helps you to realise more projects with Intune.
Steve Crookston commented
WE can push out apps that .msi but not .exe
When customers want a new windows 10 based solution with azure ad joined devices. Software deployment is the biggest problem we experience. Customers are too small to use SCCM. And the Intune Agent is also not an option because of the lack of policies that can be used when using that agent. This is a realy big showstopper in most projects.
+1 for Multiple file MSI installs, and to support EXE (Powershell scripts would be awesome)
If you look at the MDM competitors for other desktop platforms (like "Jamf Pro" for Macs), they offer to install multiple "packages" (in their case PKG files) in one "policy rule", or multiple bash shell scripts, which can in turn, trigger manually other "policy rules".
This offer a chain of actions, that are well-controled by the MDM/scripting IT admins.
Aaron Marks commented
Please allow us to deploy software to MDM enrolled Windows 10 computers with the same controls that are available to deploying software to SCCM enrolled PCs. In the field/real-world this feels like the most valuable features Intune could implement.
I would like MDM MSI and Intune client support chained package, one MSI with multiple MSI packages inside. I have some prerequisite MSI packages (VC++2017 Redistributable) need to be installed after the main package.
Justin Howard commented
This is something that is proving very problematic for us as we are essentially unable to deploy updated versions of software at the moment as we cannot deploy .exe's or an .Msi with multiple files like CABs or certificates.
I too would like this feature - but until then I have developed a work around that will allow me to deploy complex MSI packages, EXE based installations and even execute PowerShell scripts (in system context). I create a PowerShell wrapper script to do what I want - Install MSI with MSP, install EXE file etc. and then convert that to a .EXE.... Then I use an MSI creation tool to create a single MSI with all required files and to execute the .EXE version of my PowerShell script..... It all works well, but there are some issues that prevent wider scale adoption. Each package is listed twice in Add/Remove Programs (once for the Installer wrapper I create and once for the actual application that gets installed) and InTune only monitors the Installer Wrapper to determine if an app is still installed. - Nearly there, but not quite
Alan Dooley commented
A good example of where this is a problem. Microsoft Visual C++ redistributables. All of these are provided in .exe. I've got a number of .msi packages which need visual C++ install first. I cannot do this with the MDM approach.
Alan Dooley commented
This would make the MDM Windows 10 option far more viable and remove the need for the Intune agent.
@Chad, good idea, I will merge these. Thanks!
It would be a highly appreciated feature implementing the full .exe and .msi software distribution possibility from the 'Windows Installer' to the 'Windows Installer through MDM Installer'?
This is very important for how we distribute packaged applications in our organization to Windows 10 PC's utilizing MDM instead of the Intune client.
Hope you can look into this feature request at some point. This is the last major barrier for us to go full-blown Win10 management with the native MDM feature.
Thanks Chad - I will do that. Didn't see it on my initial search.
Chad Simmons commented
I recommend consolidating this Idea with the more popular one "https://microsoftintune.uservoice.com/forums/291681-ideas/suggestions/17309767-extend-mdm-msi-deployment"
Chad Simmons commented
+1 (but out of votes)
Multiple file MSI installs are a must. There are a few 3rd party tools that will wrap an install in an MSI, but this is both cumbersome and problematic.
Jos Anoniem commented
You're misunderstanding, to MDM enrolled W10 devices, only the lowest option ("Windows Installer through MDM (*.msi)") is available.
According to the below website, most of what you're asking for here is already included. Or am I misunderstanding?
I second this vote! Many software packages consist of multiple files and are not all MSI installers. Being able to deploy single MSI files only is very limiting.