Forum Discussion

michalkala123's avatar
michalkala123
Copper Contributor
Jul 04, 2019

Updating an MSIX application via SCCM

Hello,   My test scenario:   I have packaged two versions of Mozilla Firefox - 65.0.1.0 and 65.0.2.0 - they both have the same name so when I manually install 65.0.1.0 first and then double click...
TIMOTHY_MANGAN's avatar
TIMOTHY_MANGAN
MVP
Jul 12, 2019

michalkala123  In my testing, I found the following:

 

Locally installing, if I install the original version and leave it running, and then install the update version (with matching FamilyName), the update install will close the running app (without notice) and then install the update version.

 

Using SCCM and deploying as msix packages and using the higher-priority deployment type method, if the app is running the SCCM agent downloads the installer to the SCCM cache but holds off the installation.  The next time the evaluation cycle runs and the app is not in use it will be installed.  This is likely to be "by design" and would be consistent with other SCCM deployment types (except for App-V which is built to handle it).  

 

I also tested deploying the update  by adding into SCCM as a New Application that is marked to Supersede the old one. The new application may have a different name using this method, and you must not only add supersedence but mark the old deployment type to be uninstalled in the new application supersedence definition.   In this scenario, if the old app is running, it is killed and the new install happens right away.  This is probably not the behavior your users want.

 

michalkala123's avatar
michalkala123
Copper Contributor
Jul 12, 2019

TIMOTHY_MANGAN  closing the application without warning is of course not wanted and yes when I test local install and update I get the same result as you. I was hoping that I could deploy the update via SCCM without forcing users to close the app and it would prepare the update in the background and when user closes it, it will apply.

  • jvintzel's avatar
    jvintzel
    Former Employee
    Jul 15, 2019

    michalkala123 Feel free to request this with the ConfigMgr team as well.

     

    John.

  • Tim Mangan's avatar
    Tim Mangan
    MVP
    Jul 15, 2019

    jvintzel  ConfigMan has a checkbox for that, it just didn't seem to do anything (yet).

     

    Good to hear about upcoming deferral.  If app is in a partially deployed state, please also add a pending state to the PowerShell so we can detect this.

     

    Tim

  • michalkala123's avatar
    michalkala123
    Copper Contributor
    Jul 15, 2019

    jvintzel  great, I am looking forward to this!

     

    Shall I report this to ConfigMgr team or do you mean that they are aware already?

  • jvintzel's avatar
    jvintzel
    Former Employee
    Jul 12, 2019

    michalkala123 Its a discussion item for ConfigMgr to stage the package and not register it during a deployment.  We are looking to improve the overall download experience for MSIX in ConfigMgr in an upcoming release (TBD).  We are also adding functionality to the an upcoming version of Windows to stage the package and defer the installation if the app until the next launch if the app is in use to help with these scenarios.

     

    John.