In this article, I will show you how to deploy Microsoft Edge updates using SCCM ADR (Automatic Deployment Rule). With SCCM ADR, you can deploy MS Edge updates to update the Edge browser to the latest version.
With SCCM, you can deploy updates to Microsoft Edge browser using two ways: Manual deployment and Automatic Deployment. Both the methods have pros and cons and I feel using ADR to deploy MS Edge updates is easier than manual updates deployment.
Microsoft recently made an announcement about Internet Explorer announcing its end of support. With Microsoft Edge capable of assuming this responsibility, the Internet Explorer 11 desktop application will be retired and go out of support on June 15, 2022, for certain versions of Windows 10. Therefore, you can now look to disable Internet Explorer using group policy.
Microsoft Edge has Internet Explorer mode built in, so you can access those legacy Internet Explorer-based websites and applications straight from Microsoft Edge.
We know that Configuration Manager makes it easier to deploy software updates including third-party updates. With Automatic Deployment Rules, you can define the rules for patching MS Edge browsers in SCCM.
Table of Contents
Why use ADR to deploy MS Edge Updates?
Automatic Deployment Rules are the best way to deploy MS Edge updates. Utilizing an ADR helps you save a lot of time because you only need to create one with all the settings defined once, and it runs according to the schedule.
If you are new to ADR, refer to the detailed guide on how to create Automatic Deployment Rules in SCCM.
Unlike the manual updates deployment where you select and deploy set of software updates in the ConfigMgr console, the SCCM ADR will automatically deploy MS Edge updates based on the criteria and rules that you specify in the ADR.
Keeping the Microsoft Edge browser updated to latest version is important. Microsoft advises using the most recent version of Edge browser on production machines.
Creating MS Edge Application in Configuration Manager
An essential feature introduced in SCCM 1910 allows you to create MS Edge application and deploy it to your endpoints. Creating an MS Edge application in SCCM is easy and takes only a few minutes of your time.
Once the MS Edge application is created, the MS Edge can be deployed to a device collection and the deployments can be monitored from the Configuration Manager console.
After you have deployed the MS Edge application to computers, you can create a device collection for Microsoft Edge in SCCM. You can have multiple device collections for Microsoft Edge based on versions.
Now I’ll go over the steps of creating an SCCM ADR to deploy MS Edge updates. If you are looking to deploy Microsoft Edge using Microsoft Intune, have a look at Edge Browser deployment with Intune.
Prerequisites to Deploy MS Edge Updates
Before we deploy MS updates using SCCM ADR, let’s have a look at the prerequisites.
- This guide assumes that you already have the Microsoft Edge browser deployed to all the machines.
- Ensure you have installed and configured the Software Update Point role.
- Most of all, if you don’t see Microsoft Edge updates in the console, ensure you have enabled the Updates classification under Software Update Point properties > Classifications. In addition to that, under Software Update Point properties > Products, select the Microsoft Edge product for synchronization. If it’s already selected, proceed with the deployment.
In the next section, I will demonstrate how to deploy the latest updates for the Edge browser using SCCM ADR.
Create an Automatic Deployment Rule for Microsoft Edge
Before you deploy MS Edge updates, create an SCCM ADR (Automatic Deployment Rule) using the following steps.
- Launch the Configuration Manager console.
- Go to Software Library > Overview > Software Updates.
- Right-click on Automatic Deployment Rules and click Create Automatic Deployment Rule.
On the General page of the Create Automatic Deployment Rule Wizard, specify the name for the ADR. For example, specify the ADR name as Microsoft Edge Updates or something similar.
You may add a brief description about this ADR. Configuration Manager comes with set of built-in templates that has predefined configuration settings for the deployment. Click the drop-down and select Patch Tuesday as the Template.
Click Browse button and select a target collection to deploy MS Edge updates. This device collection should have at least few computers so that ADR run and patch updates to Edge browser.
You have the option to add new updates discovered by this rule to an existing Software Update Group or to create a new Software Update Group each time it runs. I prefer to create a new software update group for every product. Select Create a new software update group and click Next.
On the Deployment Settings page, choose the detail level as Only success and error messages. Next, select Automatically deploy all software updates found by this rule and approve any license agreements. Click Next.
Software Updates Property Filters and Search Criteria
This section here – Software Updates, is important. A subset of the filter criteria is displayed on this page, where you select and define the criteria for finding the updates for inclusion in the update deployment.
I am going to select the following property filters. In your case, you may alter the criteria based on your requirements.
- Date Released or Revised – Last 2 weeks (14 days)
- Product – Microsoft Edge
- Update Classification – Updates
After you make the above selection, click Preview.
Based on the property filters and search criteria that you defined above, in the preview updates window you can see the applicable or relevant Microsoft Edge updates. Since you have specified only Microsoft Edge as the product, it lists the updates for Beta, Dev, and stable channels. When you deploy Microsoft Edge updates using SCCM, only the relevant build updates will be deployed.
MS Edge Updates ADR Evaluation Schedule
On the Evaluation Schedule page, you need to define the schedule for ADR. I am going to select the option “Run this rule on a schedule“. In the Custom Schedule box, select the recurrence schedule to “Monthly,” and it will recur every 1 month. To be more precise, I want to run this SCCM ADR on every second Wednesday of the month.
We know that Patch Tuesday is always the second Tuesday of every month, and that’s when Microsoft releases updates. It is also referred to as Update Tuesday. So let’s assume that we have a patch Tuesday update released for MS Edge, and we deploy the same updates the very next day.
Note: You can choose the ADR schedule and set it according to your requirements. If you want to avoid deploying MS Edge updates very often, you can alter the schedule and adjust it. Not every organization would want to immediately implement the Patch Tuesday updates. Since I am testing the MS Edge ADR Updates deployment in my SCCM lab setup, I am going to go with the above configuration.
Click OK to save the changes and click Next to continue to the next step.
ADR Deployment Schedule for MS Edge Updates
On the Deployment Schedule page, set the Time based on to Client Local Time. Select the Software Available Time to As Soon as possible and the Installation deadline to 7 days (this is by default). However, 7 days is a lot of time, so I am going to select As soon as possible. Click Next.
User Experience: On the User Experience window, you can configure user visual experience, deadline behavior, Device restart behavior. Choose the settings as shown in the below screenshot and click Next.
Create Microsoft Edge Updates Deployment Package
The deployment package contains the MS Edge software updates that is deployed to computers. I recommend creating a new deployment package for Microsoft Edge updates because you can later verify the updates included in the deployment package.
Select Create a new deployment package and specify a Name and Description. Next, specify the package source which is a folder location on your server or a shared location. When the SCCM ADR runs, it downloads the MS Edge updates to this folder. Click Next.
Click the Add button and specify the distribution point or DP groups to host this content. When you deploy MS Edge updates to SCCM clients, the updates are downloaded from the local distribution point server. Therefore, it is important to distribute the updates to all the required distribution points. Click Next.
In this step, you specify the download location for the SCCM ADR and define where to download the Microsoft Edge updates from. Select Download software updates from the internet and click Next.
In the Language Selection window, you can specify the update languages for the Microsoft Edge updates. Click Next.
On the Download Settings page, click Next.
Finally, on the Summary page, verify all the settings that you have configured to deploy MS Edge updates. You may save the settings as a template, and you can use this template next time you create an ADR. Click Next.
This completes the steps to create an SCCM ADR to deploy MS Edge updates. Wait for the ADR to run, evaluate and deploy the Edge updates to your computers.
Verify MS Edge Updates Download
When the SCCM ADR runs, it downloads the Microsoft Edge updates and stores them in the folder specified in the Deployment Package step.
Monitor Microsoft Edge Updates Deployment in SCCM
In order to speed up the MS Edge update deployment, I altered the deployment schedule and triggered this ADR manually. As per our settings, whenever the ADR runs and downloads the updates, it puts them into a new Software Update Group.
If you visit Monitoring > Overview > Deployments, you should see the new ADR deployment entry. Right-click the software update deployment and click View Status. In my case, the ADR has successfully done its job, and we can see that all the machines within that device collection show as Compliant.
You may go to any of the client computers and open the WUAHandler.log file. Take a look at all the SCCM log files for reference. When I deployed the MS Edge browser using SCCM, it was deployed as a stable build and the version was 79.0.309.68.
In the log file you can clearly see that new build 80.0.361.62 is deployed over the existing build. The update ID here is ddaec3b6-3757-4951-81c4-cd4117876d11.
1. Update (Missing): Microsoft Edge-Stable Channel Version 80 Update for x64 based Editions (Build 80.0.361.62) (ddaec3b6-3757-4951-81c4-cd4117876d11, 201) WUAHandler Async installation of updates started. WUAHandler Update 1 (ddaec3b6-3757-4951-81c4-cd4117876d11) finished installing (0x00000000), Reboot Required? No WUAHandler Async install completed. WUAHandler Installation of updates completed. WUAHandler
From the above screenshot, we see the ADR has patched the Microsoft Edge browser to the latest build. In this step, we will launch the Edge browser on the client computer and check the version. Launch the Microsoft Edge browser and check the version to determine if you are running the latest build.
SCCM Reports for MS Edge Updates Deployment
SCCM comes with 400+ built-in reports and there are several reports to monitor and get information on software update deployments. Now that we know the ADR has deployed the Edge browser updates, you can also find more information about this deployment by visiting the Reports section.
Go to Reports > Software Updates – B Deployment Management. Click Management 3 – Updates in a deployment.
In the report, select the deployment, and you will find more details about the MS Edge updates in this deployment. Note that only Edge stable channel updates were deployed to 4 of my computers. And for the rest of the builds, it is listed as not required.