Forum Discussion
Updating Edge via Software Update (SCCM)
Hi there,
Will administrators be able to deliver updates the new Edge via Software Update in SCCM? From all the documentation that I have read so far, it seems that the only update mechanism is the built in auto-update. Ideally, I would like to be able to control the updates via SCCM, as this will allow is to perform pilot testing using our current pilot method that we use for Windows and Office patches.
Keep up the great work!
Thanks!
RazaanKhoja check out the roadmap link and it explains how managed updates will be handled:
https://blogs.windows.com/msedgedev/2019/07/16/microsoft-edge-enterprise-evaluation-roadmap"Customers will be able to control the flow of updates, either by leveraging our general updating mechanisms and using policies to pause updates at a particular version while testing compatibility with a small set of pilot users, or by using the provided offline installers (MSIs and PKGs) to push updates directly to their managed devices on their own schedule.
For those customers using System Center Configuration Manager (SCCM) or Microsoft Intune, we’re working to make the deployment and configuration experience as easy as possible. We will also work with third parties, ensuring that deploying and configuring Microsoft Edge is a great experience with those tools as well."
lexcyn Are there plans to make local update agent work with an internal update file share? Like O365 updates (https://docs.microsoft.com/de-de/deployoffice/deploy-office-365-proplus-from-a-local-source).
I couldn't find anything related to an internal update server so I don't think that is an option. You'd have to either use SCCM/WSUS or the automatic updates.
lexcyn Thanks! I actually missed that!
Hello,
Can you clarify this :
"Customers will be able to control the flow of updates, either by leveraging our general updating mechanisms and using policies to pause updates at a particular version while testing compatibility with a small set of pilot users, or by using the provided offline installers (MSIs and PKGs) to push updates directly to their managed devices on their own schedule."
Ok, let's assusme that I deploy the enterprise MSI. By default, edge will be automatically updated. Is this correct ?
I checked the policies and cannot see any setting to pause update at a particular version.
Google Chrome has the GPO setting : "Target version prefix override" but I do not find equivalent setting for Edge.
And anyone else looking for how to control updates - please see the following Edge deployment guide: https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-update-policies
This section explains how to enable or disable auto updates via the built in updater: https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-update-policies#updatedefault
If you're using SCCM to push updates manually, you would want to disable the built in updater to control the version in your environment.
Finally found the answer in this new article :
https://docs.microsoft.com/en-us/DeployEdge/deploy-edge-plan-deployment
Define your update strategy and policies
You also want to determine how you want to do updates after you deploy Microsoft Edge:
Allow Microsoft Edge to update itself (default). If you choose to allow automatic updates of Microsoft Edge, then Microsoft Edge will automatically update itself at the pace determined by the channel(s) you deployed.
Update Microsoft Edge at your own pace. If you prefer to have explicit control over when updates are deployed, you can disable automatic updates and deploy it yourself (see the Update Policy reference.) After you disable automatic updates you can deploy updates for each channel using one of the following tools:
the deployment tool of your choice.
Regardless of your update strategy, we recommend leveraging a ringed deployment strategy. With automatic updates, this means having a representative sample of users running the Beta Channel, to identify issues with what will become the Stable Channel. With manual updates, this might also include additional validation of a pilot group after a new Stable Channel build is released. This is followed by broad deployment.
