Manage Microsoft Edge Application using SCCM Software Updates

Using Configuration Manager 1910, you can not only create and deploy Microsoft Edge application but you can also manage Edge updates. Yes you can now deploy Microsoft Edge updates using SCCM 1910 and this is really a good thing.

In this post I will cover the steps to create Microsoft Edge Application. We will deploy it to test device collection. We can then look at managing Microsoft Edge updates using SCCM.

The Microsoft Edge browser has been in preview since a long time. But then the Admins could still deploy Edge as an application using Configuration Manager 1910. However one thing that was lacking was deploying Edge browser updates using SCCM.

Previously if you had to download Edge, you could pick the Beta, Dev, or Canary channel, along with a version of the Microsoft Edge client to deploy. With the release of Edge stable build, the Canary channel is now gone. You can read more about these channels here.

Configuration Manager 1910 allows you to create Edge application and deploy it to your clients. If you want to manually download the stable version of Edge and package it in SCCM, you can do that as well. To download the stable version of Edge browser, click here.

Note – Before you deploy Edge via SCCM, ensure the PowerShell Execution Policy is not set to Restricted on the client computers. If it is set to Restricted, then the deployment will fail.

Create Microsoft Edge Application Using SCCM

To create a new Microsoft Edge application using SCCM

• First of all, launch Configuration Manager console
• Go to Software Library > Overview > Microsoft Edge Management
• Right-click Microsoft Edge Management and click Create Microsoft Edge Application

The Microsoft Edge client installation wizard lets you create and deploy Edge application. On the Application Settings page, specify the application name and content location. Click Next.

Under Microsoft Edge client settings, you should find three channels.

• Dev
• Beta
• Stable

Select Stable and version as Latest. Click Next.

On the Deployment page, select Yes if you want to deploy the application after you close this wizard or select No to deploy it later. I will select Yes here. Click Next.

Specify the collection to which you want to target the Edge deployment. Click Next.

On the content page, select the distribution point. Click Next.

On the Deployment page, since I selected Yes under “do you want to deploy the application now”, I can see the Purpose is set to Required. Click Next.

Click Next on rest of the pages and finally on Completion page click Close.

Microsoft Edge Application Deployment Report

After you deploy the Microsoft Edge application, you may want to check the application deployment status. You can run the report All application deployments (basic) located under Software Distribution > Application Monitoring.

Select the Microsoft Edge application and the device collection. The report should show you the deployment summary. In addition to that, you may use other built-in reports to get the similar data.

Manage Microsoft Edge Updates with SCCM

To get Microsoft Edge updates in the console, ensure you have enabled the Updates classification under Software Update Point properties > Classifications. If it’s already selected, proceed to next step.

Under Software Update Point properties > Products, select the Microsoft Edge product for synchronization.

Tip – If you don’t see Microsoft Edge product in the list, synchronize software updates once and check the products tab.

After you perform the above steps, click Synchronize Software Updates. Wait for the sync to complete and now check All Microsoft Edge Updates. You should the Microsoft Edge Updates for all the 3 channels – Beta, Dev and Stable.

Now that you have got the Edge Updates in the SCCM console, you can manage and deploy Microsoft Edge updates like any other update. For example you can add them to a Software Update Group and deploy. Or add them to your automatic deployment rule.