Deploy Edge Chromium using MEMCM and PowerShell executionpolicy
Been testing Edge Chromium deployment a lot the last couple of days as the we are getting really close to release when I write this..
Configuration Manager 1910 has a builtin feature to deploy and update Edge Chromium which looks great, hard to test the update part as the Stable release and updates are not released yet.
When creating the deployment of Edge Chromium using the built- feature we select channel and version to deploy. Which is great as we most likely will have developers, testers that needs the Beta/Dev version as well for testing.
It will download the content and create a Application with two deployment types one for x64 and one for x86, both are deployed using a PowerShell script. The PowerShell script also turns off automatic updates so that they can be handled by MEMCM instead of using EdgeUpdater.
Detection Method for the Deployment types are configured automatically to allow for updating of Edge Chromium using MEMCM as the detection method checks registry value and is configured with the operator “Greater than or equal to” as shown below.
To be able to use the script the Powershell Execution policy needs to be set to RemoteSigned or Unrestriced.
Allsigned will timeout after 30 minutes
Restriced will result in immediate failure
Restriced is default in Windows 10 and if you are using that modifying the Install command will solve the problem for you by simply adding -ExecutionPolicy Bypass to the command line. Sample below
Sample original installation string:
powershell -File “.\Install-Edge.ps1” -MSIName “MicrosoftEdgeBetaEnterpriseX64.msi” -ChannelID “{2cd8a007-e189-409d-a2c8-9af4ef3c72aa}”
After adding -ExecutionPolicy Bypass
powershell -Executionpolicy bypass -File “.\Install-Edge.ps1” -MSIName “MicrosoftEdgeBetaEnterpriseX64.msi” -ChannelID “{2cd8a007-e189-409d-a2c8-9af4ef3c72aa}”
Let’s look at the PowerShell script as well to prove that is sets the AutoUpdate policy to “0” , it is set during deployment.
If you choose to deploy Edge Chromium in another way make sure you configure AutoUpdate using GPO/Intune according to your update plan and that your detection method can handle the way you choose to update it!
Stay tuned for more Edge Chromium posts the coming days as it goes live!
New in Application requests in SCCM 1906
Enable App-V and UE-V during OSD in Windows 10 1607
Endpoint Protection and additional scheduled scans
About Author
Jörgen Nilsson
Add a Comment
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Good day, Will this stop edge chromium being updated on all machines being handled by configman?
Yes, If you use the builtin wizard to deploy it then yes, automatic updates will be disabled.
Regards,
Jörgen
Can you share the PS script
The Script can be found in the download folder that was specified during the installation.
So if I want my user to be able to update Edge and configure the Group Policy options for this before I actually send out the application this installer will fail due to the part below “# If the value is not set to 0, auto update is not turned off, this is a failure”…
Why is the “This registry key is associated with a 32-bit application on 64-bit systems” checked by default? Surely when deploying Edge x64 onto Win10 x64 it’s a 64-bit application on a 64-bit system?
I notice the detection method is querying the WOW6432Node, but surely that’s only for 32-bit apps?
Hi, I was getting install failures, after I put in a GPO to allow users to self update ( which was recommended by microsoft in their GPO Templates) After doing this, my install script / package started failing. Sure enough after googling and found this article ( thank you ) found out why. My update value has changed.
I guess the default script package if you do it through sccm is to allow sccm to hand all updates? Cant I use both? I would like my users to update edge and SCCM can handle the straggler’s