Forum Discussion
Installing MicrosoftEdgeBetaEnterpriseX64.msi - Error 1722 when EdgeUpdate Policy is configured
Gunnar-Haslinger How do you plan to distribute updates/patches? Do you think every single update/fix well be available as MSI package? How do you organize test deployment rings for new releases?
Thilo Langbein Microsoft didn't publish information how the Lifecycle of the final product is planned. But as there are the EdgeUpdate Policies I guess this is part of the final product too (wouldn't make sense to create EdgeUpdate Policies only for beta-phase).
Sure, offline MSI-Package-Deployment is the preferred way. Planning to deploy Edge based on Chromium as every other software package by our internal fully-managed enterprise deployment. Seems there is no need for separate "Updates/Fixes" because the full MSI-Package of Edge itself is not very large and can be used to update to the most current version.
Based on the reg keys that were set it looks like "install default" is the culprit and this experience would be by design (though we should look into having a more descriptive error message in this scenario).
Essentially with InstallDefault set that way the machine is being told "don't allow the next version of Edge to be installed" so when you try to install the next version of Edge it recognizes that there is policy set saying "don't allow installation" and it is respecting that.
Presetting the Update policies (UpdateDefault) should work as you expect and not block installation. Doing this would be the intended way to prevent Auto-update from running after you install using the MSI.
Hope that helps!
-Steve
