Deploy Microsoft Edge and Manage Edge Updates using SCCM or Intune

Benoit LecoursSCCM37 Comments

Microsoft announced that the general availability of the new Microsoft Edge Chromium on January 15, 2020. SCCM and Intune are already ready for this launch as both products include a feature to deploy and manage updates for Microsoft Edge. This blog post will describe how to deploy the Microsoft Edge browser to your computer using both SCCM and Intune and manage Edge Updates.

You can download and install Edge Chromium from the Microsoft website. It’s available for Windows, macOS, iOS and Android. If you need to do SCCM Edge Deployment Update in Enterprise, continue to read our post.

SCCM Edge Deployment Update Requirements

The first step to SCCM Edge Deployment Update is to ensure that you have SCCM version 1910 or higher. Version 1910 brings a new feature to deploy Microsoft Edge, version 77 and later. Intune is already ready to deploy Edge.

Also ensure that PowerShell Execution Policy are not set to Restricted.

When Microsoft Edge is deployed to a computer, automatic updates are automatically turn off to point to SCCM. You can change this using Group Policy.

You will also need to have a functioning Software Update Point to deploy Microsoft Edge Updates.

Deploy Microsoft Edge using SCCM

It’s also possible to create an application using the downloadable MSI from the Microsoft Edge Insider web page but this blog post will not describe this option as we find that the built-in feature is doing a simpler job handling it.

  • In your SCCM Console
  • Navigate to Software LibraryMicrosoft Edge Management
  • Right-click Microsoft Edge Management and select Create Microsoft Edge Application
SCCM Edge Deployment Update
  • On the first pane, enter a Name and Path where you want the build to be downloaded. The path must be an empty directory. Click Next
SCCM Edge Deployment Update
  • Select an Update Channel and Version. You can select Dev, Beta and Stable. Click Next.
SCCM Edge Deployment Update
  • Starting with SCCM 2002, you can create Edge to receive automatic updates rather than having automatic updates disabled. This allows choosing to manage updates for Microsoft Edge with SCCM or allow Microsoft Edge to automatically update.
  • When creating the application, select Allow Microsoft Edge to automatically update the version of the client on the end user’s device. If you previously used Group Policy to change this behaviour, Group Policy will overwrite the setting made by SCCM during Edge installation.
  • In SCCM 2010, the product group also add an option to bypass the PowerShell Execution policy on the user machine
SCCM Edge Deployment Update
  • The next screen permits you to create your deployment or wait at a later time. For this blog post, we will create it now. Click Next
SCCM Edge Deployment Update
  • As for any other application deployment, select a Collection, Content Destination, Distribution Settings (Available or Required), Scheduling, User Experience and Alert
SCCM Edge Deployment Update
  • Complete the Wizard. It will take a couple of seconds to complete since SCCM is downloading the files in the background.
SCCM Edge Deployment Update
  • In the folder you specified in the first screen, you’ll see the downloaded bits for both X86 and X64
  • If you’re curious and wonder at that’s inside the PS1 file, it’s basically a script to install Edge and a registry value set for future updates.
  • You can now log on a computer that is a member of your deployment collection and initiate the Edge deployment from Software Center. For now, the “regular” version of Edge is retained on the computer.
  • Use the usual AppEnforce.log file to monitor the deployment

SCCM Edge Deployment Updates

Starting with SCCM 1910, it is possible to deploy Edge Updates using the SCCM console (As for Office 365) – Under Microsoft Edge Management / All Microsoft Edge updates.

To Enable Edge updates to show up, you need to enable the product on your Software Update Point.

  • Go to Administration / Site Configuration / Sites
  • On the Top ribbon select Configure Site Components and select Software Update Point
  • In the Classification Tab, ensure that Updates is checked
  • In the Product tab, select Microsoft Edge under the Windows product
  • Go back to the Software Library node, right click the All Microsoft Edge Updates node and select Synchronize Software Update
  • Wait for the sync to complete and refresh the All Microsoft Edge Updates node, you should see Microsoft Edge Update appear
  • You can now deploy Microsoft Edge updates like any other software update. You can also use automatic deployment rule to deploy them.

Microsoft Edge Management Dashboard

Beggining with SCCM 2002, a new dashboard is available in the SCCM console. You can consult that Microsoft Edge Management dashboard to see the usage of Microsoft Edge and other browsers.

  • To see the Dashboard, click Software Library / Microsoft Edge Management. You can filter the dashboard based on a specific collection

Deploy Edge using Intune

If you’re using Intune to manage your devices, you can also find the same deployment mechanism in your Intune console. This feature is currently in Preview mode but in our test, it worked out great!

  • In the Intune Console, go to Manage / Client Apps
  • Select Apps
  • At the top, select Add
  • In the App type dropdown, Under Microsoft Edge, version 77 and later, select Windows 10
SCCM Intune Edge Chromium
  • Click App Information and enter your desired information
  • Click App Settings and select the desired update Channel.
  • Click the Add button at the bottom to add the application. You’ll see a confirmation on the top right.
  • You’ll be in your Edge Chromium application screen. The only thing left is to assign the app to a group. Go in the Assignment tab and select your group

We hope that this post was useful. Now that Edge Chromium hits general availability there’s no reason not to manage SCCM Edge Deployment Updates.

37 Comments on “Deploy Microsoft Edge and Manage Edge Updates using SCCM or Intune”

  1. Thanks I followed the Intune route.
    Started to build two brand new devices and I get Error downloading content. (0x87D30068)

    Any ideas what to look for to solve this please? |If I run the download version its fine and it has installed Office, Adobe reader etc no problem.

    1. I’m seeing the same thing in Intune. We’ve deployed it as Available rather than required, but when a user tries to install using Company Portal, it spends about 30 seconds saying it’s downloading, then errors out. In Intune it shows up as a failed install with
      Error downloading content. (0x87D30068)

      It was working fine last time I tested it, about a month ago. Failing now on both Stable and Dev builds.

      1. Same here. Working great from intune 2-3 days ago, now consistently the 0x87D30068 error. I’m switching Edge to LOB for now to see if that makes a difference.

  2. Quickbooks Error support service helps you to get rid of the errors. You get instant and quality assistance in order to resolve your issues. Quickbooks Error support service is a reliable and on-demand service provider that helps you to sort issues. QuickBooks Error supports helps you provide all the necessary solutions to help keep your business running at peak.

  3. So your telling me that MECM automatically creates the deployment for Edge Chromium and none of their engineers can find an icon to make Software Center beautiful? Come on!

  4. Incase you guys get error 0x1(1), edit your deployment type and add -ExecutionPolicy Bypass into your program installion. It will fix if desktops has restricted Execution policy, and update your DPs and try installing again it should go fine.


  5. Hi Benoit,

    So I keep getting this error message : Failed to download artifact for Microsoft Edge Version 79.0.309.71

    Error: The SMS Provider reported an error.
    Application Settings
    • Application name: Edge Chromium
    • Administrator comments:
    • Content Location: \\x\d$\Sources\Applications\Microsoft\Edge_Chromium

    Deployment Settings
    • Channel: Stable
    • Version: 79.0.309.71

    Running Endpoint Configuration Manager. 1910

    Any idea ?

      1. Hi,
        anybody else with this issue? I got it also, but without any MSI in download folder. I’ve tried to search for this issue also, but with no luck.

        1. I’m also getting this and i’ve done some digging.. If you go to the profile’s Local AppData there is a SCCMReporting.log that has the same error mentioned. However there is another error that says:

          Microsoft.ConfigurationManagement.exe Error: 0 : Unable to copy file from D:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\scripts\Install-Edge.ps1 to \\*DFS-Share*\*version*\Install-Edge.ps1 with error: Invalid certificate for Powershell script, not copying

          Haven’t been able to figure anything about this.. I’ve changed the powershell execution policy on the machine to unrestricted and bypass without success. I’ve verified the Cert that has signed the script and all levels of that cert are trusted… I can copy the file manually…

          1. Nice find, i don’t seem to have that log file anywhere, all i have is PatchDownloader.log, where i can see it downloading the file and verifying the hash successfully, then copying it where i want it to go.

          2. We had to explicitly install the intermediate certificate in the local certificate store. After that, the error no longer occurred.

          3. Did you ever get a fix for this? I am having the same error and cannot resolve it.

            Which certificate needs explicitly installing I have tried all the ones I can see to no avail.

    1. Did you manage to resolve this? We’re getting the “Invalid certificate for Powershell script, not copying” in the SCCMReporting log file too.

  6. hi!,I love our writing very much! proportion we keep uup a correspondence extra approximately your article on AOL?

    I require an expert onn tjis space to solve my problem.
    May be that is you! Taking a look forward to peer you.

  7. After deploying using SCCM, the browser’s automatic updates seem to be disabled. When going to About – Microsoft Edge, it says “Your organization disabled updates.” Is there a way to prevent this, i.e. to let it update itself from Microsoft automatically?

  8. Getting “failed to create and establish connection to“. IE on our site server gets a “page not available”, but chrome on the same box displays the JSON file.

    Hate to have to create an MSI based install, but not seeing a reason for the above error.

    1. Rob, I’m at the same point as you. If I try through IE on the SCCM server I get a unsafe TLS warning. We are also behind a blackhole proxy, although that has an exception for both and so I have to think it’s a TLS issue with the page and possibly a policy we have blocking that version of TLS.

      1. Hi,

        Did you manage to solve this? And if so, what was the issue?
        As i’m facing the same thing.

        Chrome works, I.E. doesn’t.
        TLS protocols are checked.

  9. “For now, the “regular” version of Edge is retained on the computer.”

    Great, lets add another browser option (Edge, IE, Chrome) for my users to complain doesn’t load their outdated web-based application. smh

  10. Geek squad provides various tech assistance related services for there users as in case you face any issue in your tech assistance devices hardware and software you can contact Geek squad tech support and ask them for Geek squad support or in case you want to install the new hardware you can contact them and they will visit you at your place for assistance.

  11. Quickbooks provides best accounting services as through this you can create or manage your business accounts details and records of tax bills, payments, transactions, etc online in fast and easy and way and in case you need any help assistance you can contact Quickbooks premier support and ask them for premier support

      1. Are you sure it’s downloaded? It appears it’s copied from the SCCM install directory, specifically D:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\scripts If you remove the copy from this location, I haven’t found a method to get it to download a fresh copy. Which is annoying as the script signing certificate appears to have expired on May 2nd.

Leave a Reply