Rouletteload900

New Edge, Credge, Edgium or Credgium – no matter what you call it, the Edge browser based on chromium was released on Jan 15th 2020.

• Sccm Edge Update
• Edge Chromium Sccm Server
• Edge Chromium Sccm Task Sequence
• Sccm Microsoft Edge Browser Profiles

To deploy the new versions using SCCM 1910 (or above)

Jun 21, 2020 Learn how to Install Microsoft Edge Browser Using ConfigMgr. I have a blog post to explain Deploy Microsoft Edge Patches with SCCM Software Updates. This is all about the chromium based edge version. For more information, see Monitor applications from the System Center Configuration Manager console. End-user experience Users who have PCs that are managed by Configuration Manager and are running Windows 10 of the specified processor architecture, will see a message telling them that they must install the Microsoft Edge Dev application. Mar 01, 2020 If Edge Chromium is their default browser, they can still open legacy websites in Chromium but we can force the website to use the IE engine to address compatibility issues. We will cover this in more detail later but you can easily recognise if a website is being displayed in IE Mode by looking for the IE symbol in the address bar.

• Add “Microsoft Edge” a product that is sync’ed in your software update point component properties
  • Somewhat confusingly, the product is under the sub-category of “Windows”

• Then navigate to Software Library > Microsoft Edge Management | All Microsoft edge update

• Right click and select “:synchronise software updates”
• You can follow the progress of this process by checking wsyncmgr.log – the same log as you use to follow all software update sync’s
• At this stage – you can wait for anywhere from 5 minutes (for an environment that has sync’ed relatively recently) to hours (if this is your first sync)
• Once completed, you can refresh by hitting F5 – and you should see some content update for Edge in the right-hand pane
• Now right-click on the top node “Microsoft Edge Management” (yes, this is not intuitive) and select “Create Microsoft Edge application”
  • Select and name and a source directory to be used
  • Select a channel, or specific version that you wish to deploy. If you’re not sure here – use “stable” and “latest”
  • Deploy to a collection, select your DP’s etc – all pretty standard stuff here
• You’ll notice that an application is created for you under the “applications” node – this is different to other software updates which are created as Software Update groups (SUG’s)
• Personally, i’d prefer to see it all managed under the one node – however, its still a good feature overall – as simplifies deployment of edge greatly – but still allows the admin to go and edit properties of the deployment if… for the invetiable situation of where the Microsoft pre-defined install doesn’t meet your orgs needs

Once completed, as per any deployment – monitor your deployment via the “deployments” area in the monitoring tab.

*Update 28/02/2020 *

When installing, you may get the following error (or similar)

Sccm Edge Update

App install failed.
Install application action failed: ‘APP.Edge.Latest’. Error Code0x80004005
Sending StatusMessage
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest – URL: SCCM01.company.com.au:80 CCM_POST /ccm_system/request
Not in SSL.
Request was successful.
hrInstallation, HRESULT=80004005 (installapplication.cpp,989)
pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=80004005 (main.cpp,284)
Install application action cannot continue. ContinueOnErrorFlag is set to false.
Install Static Applications failed, hr=0x80004005

This is due to the powershell policy…. to get around this, modify the command line from this

powershell -File “.Install-Edge.ps1” -MSIName “MicrosoftEdgeEnterpriseX64.msi” -ChannelID “{56eb18f8-b008-4cbd-b6d2-8c97fe7e9062}”

to this

powershell -executionpolicy bypass -File “.Install-Edge.ps1” -MSIName “MicrosoftEdgeEnterpriseX64.msi” -ChannelID “{56eb18f8-b008-4cbd-b6d2-8c97fe7e9062}”

Symptoms

When creating a new Microsoft Edge application an error resembling the following is displayed in the Microsoft Edge Client Installation Wizard.

Failed to download artifact
http://.../MicrosoftEdgeEnterpriseX64.msi for Microsoft Edge version xx.x

Edge Chromium Sccm Server

The URL and version number in this error vary. The PatchDownloader.log indicates a successful download just prior to the error appearing onscreen.
An updated version of the Install-Edge.ps1 PowerShell script is available to resolve this issue.

Resolution

Microsoft Download Center

The following PowerShell script to resolve this problem is available for download from the Microsoft Download Center:

Virus-scan claim

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

After you download the Install-Edge.ps1 script, use the following steps to replace the original script on any affected computers with the Configuration Manager console installed.

1. Close the Configuration Manager console.

2. Backup the existing {Configuration Manager console installation directory}binscriptsInstall-Edge.ps1

3. Copy the new Install-Edge.ps1 script over the old version.

4. Create a new Microsoft Edge application.

Prerequisites

This script is only intended for computers with the Microsoft Endpoint Configuration Manager, version 1910 console installed.

File information

Edge Chromium Sccm Task Sequence

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File attributes for Microsoft Endpoint Configuration Manager current branch, version 1910

Sccm Microsoft Edge Browser Profiles

References