Forum Discussion
Updating an MSIX application via SCCM
In SCCM, I would use a different approach to the upgrade. I would add the new version as a new Deployment Type of the original application, and reorder them such that the new version is a higher priority (lower priority number). If everyone gets the upgrade, you can remove the old DT, although I'd tend to want to wait a while before the removal.
Tim
Tim Mangan You are correct Tim, it worked with your approach, thanks!
I tested two scenarios here, first is that Firefox is not running when update is being deployed - then it worked fine and Firefox is updated.
Second scenario I tried is that Firefox is running during the update deployment - in that case deployment is successful, but Firefox is still displayed as older version when I re-open it (or reboot machine). Shouldn't it update the blocks in the background even when the app is running?
michalkala123 And by the way, to your original issue. I think you can deploy the upgrade as a separate application, but you need to remember to also assign the original application to an uninstall job. While MSIX knows that packages are related, SCCM doesn't and likely wants to reinstall the original. But the DT method I think is easier and more straightforward.
Tim Mangan "While MSIX knows that packages are related, SCCM doesn't"
Yes this is true. All I had to do is specifying a supersedence relationship between my two firefox packages (without forcing uninstall) and now when I deploy the second one, SCCM is aware that is it meant as upgrade and it works as I wanted. It also preserves user settings like homepage, which I am not sure it would do if I set the older application to uninstall.
I like the method of adding new deployment type, but I want to be able to first shoot out new package to couple testers on customer side for verification. If I would do it with the new DT method, SCCM would start distributing to all where it is deployed.
Regarding updating while the app is in use - I tried again (now with supersedence) and maybe I am just expecting it to be really quick, but I still see only the old version. I will do more extensive testing next week, because I also think it should work (it works when deploying via .appinstaller file solution)
Hello,
I've done multiple new tests but I am not able to update MSIX application via SCCM deployment while the application itself is running on the client. If it is not running then everything works well. If it is running I never see new version applied (even when SCCM says it is success)
Does anyone know if this is possible to achieve with SCCM? I am looking for similar update behavior like with App Installer solution as described here: https://techcommunity.microsoft.com/t5/Windows-Dev-AppConsult/Handling-application-updates-with-App-Installer-and-MSIX-in/ba-p/355389
Updates checks can be configured in two ways:
- Every time the application starts. In this case, the update will be automatically downloaded and installed when the application is closed.
- At a specific frequency (for example, every 6 hours). In this case, the update will be automatically downloaded and installed if the application is not running; otherwise, it will be installed as soon as the application is closed.
michalkala123 My recollection is that the update should succeed even if the app is in use, and closing all use of the app should result in the new version being seen. But honestly, I haven't tested that scenario in a long time.