Automatically update installed "available" Win32 (intunewin) apps on devices
- You create a Win32 app in Intune.
- You assign the app to a group of users as "available for enrolled devices".
- User clicks and installs app via Company Portal.
- You as an admin update the app binaries for the App in Intune (you replace the .intunewin file with a new version)
- NOW THE APP SHOULD AUTOMATICALLY UPDATE/REINSTALL ON USER DEVICES USING THE NEW PACKAGE
This is mandatory. This will make or break a 10k+ Intune deployment. We need this functionality ASAP, or we'll have to go with Chocolatey + AWS S3.
I realize with "required" apps, you can simply create a new app to supersede the old, but most apps are self-service via the Company Portal and installed by the user as-needed. These apps will need updated, and will need to update on user devices.
This should be a feature. Apps needs to be updated and the current behavior makes that painful. There are a few workarounds. Either you deploy the app twice and use custom pre-requistes so that it only installs if it detects that the previous version is already installed or you create a group that is updated via some form of automation whenever a user installs an app. Both are more burdensome than it needs to be.
Timothy Gruber commented
I did end up implementing a work around a while back and had forgotten about this suggestion, but it requires two Intune apps for each app. In the end, you end up with an "Available" app that shows up in the Company Portal to install on-demand, and a "Required" app.
The required app is assigned to everyone as required that the "Available" app is assigned to as available, however, the required app uses a custom detection script that will only apply to devices that have the "Available" app installed.
It works well, but if you aren't automating the creation and deployment of Intune apps, I can see it being very time consuming.
See attachment for example:
This is a problem we encounter with many of our customers. Therefore we made a solution to fill the void.
I am attempting to do this as well and just updated an older version of an app with a new version. I set it to assume installed if the exe file was present. I am guessing that it does not read the version number of that exe as it is telling me that the app is already installed. However, it is the old version of the app that is installed. It would be so useful if it would read the version number and if not current auto update.
Quinten DC commented
There is a perfect way to do this using chocolatey auto update script.
Next to that you can also check out patchmypc. If you want to read more about this and have a full guide on how to use patchmypc I highly recommend the cloud-boy guide for patchmypc
I hope this might solve your problem.
Pete Mitchell commented
Wow, no response to this yet? Seems like something that should have been included when Win32 app support was added.
Thomas Kurth commented
This is one of the main concern customers currently have and therefore stay on MEMCM because of better handling options.
Totally agree with this.
Please add this feature.
This has to be implemented as a standard feature. Create a new app object for every version just isn't practical.
Checkout this new Modern MDM tool we are using, they allow you to install any apps you wish, .EXE, .MSI, pre-packaged, custom, powershell, modern, chocolatey and etc packages either in a sequence or with API. You don't have to worry about converting Win32 apps again, You can also check auto update and auto package so when there's a new version available, your engineers never have to worry about keeping them up to date, the AI will do it for them.
A solution to this issue could be the ability to create dynamic device groups based on installed software, and deploy a required software to that group.
This is how I'd do it in SCCM
Marios Andreou commented
Agree! This is one of the most important features in my opinion. I've looked into so many different approaches, from editing detection rules (to check versioning), to trying to create Dynamic Groups based on users that have installed an app, to even playing with APIs. It's just a pain getting users to update their apps manually instead of having the ability to update them automatically.
I tried to work with dependencies and requirement logic to see if I could create a new w32app to update the existing w32app, but wasn't able to get this to work either. I was then pointed to this feature request forum... Isn't updates for software deployment one of the key features of a MDM?
Anyone have any workaround solutions for now?
Same, Same! We really need a fully supported process to update a Win32_App deployed with Intune.
[Deleted User] commented
We are deploying the Azure WVD Client via Intune. The updates aren't deployed.
Agreed, absolutely essential mechanism for optional self-serve apps.
Hey same problem here as well, I hope they will implement it soon...