06-25-2020 08:42 AM
06-25-2020 08:42 AM
I've noticed a problem with installing Edge Stable (tested on 83.0.478.54) when attempting to install by with the MSI. We're applying the InstallDefault = 0 and UpdateDefault = 0 policies to prevent Edge from automatically updating. Our update strategy will be to deploy Edge periodically with SCCM.
As a work-around, I can remove the "InstallDefault" regedit, perform the install, then perform a group policy update.
06-25-2020 05:05 PM
@Jeffrey_Fronius Thanks for reaching out and reporting this. I'll loop in our Enterprise team and let you know if they have any insights to share.
Project & Community Manager - Microsoft Edge
06-25-2020 06:00 PM
The InstallDefault policy is probably blocking installation -- InstallDefault==0 corresponds to "don't allow Edge installation". The UpdateDefault policy is sufficient to prevent the browser from updating. If you set InstallDefault to "Not Configured" (or Configured/one of the allowed values) you should be good to go.
06-25-2020 06:50 PM
06-26-2020 09:53 AM
Agreed that the docs for InstallDefault need to be more clear about the behavior - I will follow up on that, thank you for the feedback. It's actually our installer (which is shared across all deployment types -- EdgeUpdate/MSI/WSUS/etc.) that reads the InstallDefault key. Let me know if you hit any additional issues.
06-26-2020 11:02 PM
The policy documentation seems to state this only impacts installing through edge update, not when installing through other methods. Perhaps I'm reading into it wrong. If we in fact don't need this to suppress automatic updating, then I'll look to remove it.
Edge MSI package bundle Microsoft Edge Update as well, and it's what's used to perform the installation
you can inspect MSI with Orca or InstEd and see InstallCommand
MicrosoftEdgeUpdateSetup.exe /silent /install "[ProductTag]" /installsource enterprisemsi[OptOmahaArgs] /appargs ..