You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The packages get updated with the new certificate and publisher information as checked using the get-appxpackage cmdlet; however the publisherid is not substituted in the msix package name as per the MSIX Packaging Tool default naming standard when saving msix packages, so these have needed to be renamed with another powershell script afterwards.
Could this option be made available and potentially include the option to update the minor version of the package, as some issues have been seen with supersedence in MECM where increasing the version is the only way to get supersedence to work against the same package with an older certificate.
The text was updated successfully, but these errors were encountered:
As per thread opened on the MSIX Community thread MECM Supersedence issues.
The packages get updated with the new certificate and publisher information as checked using the get-appxpackage cmdlet; however the publisherid is not substituted in the msix package name as per the MSIX Packaging Tool default naming standard when saving msix packages, so these have needed to be renamed with another powershell script afterwards.
Could this option be made available and potentially include the option to update the minor version of the package, as some issues have been seen with supersedence in MECM where increasing the version is the only way to get supersedence to work against the same package with an older certificate.
The text was updated successfully, but these errors were encountered: