Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • GitHub
  • Windows 11
  • About the author
CCMEXEC.COM – Enterprise Mobility

Deploy Edge Chromium using MEMCM and PowerShell executionpolicy

Posted on January 14, 2020January 14, 2020 by Jörgen Nilsson

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!

  • Edge Chromium
  • Edge Deployment
  • MEMCM
  • 8 thoughts on “Deploy Edge Chromium using MEMCM and PowerShell executionpolicy”

    1. Freshner Fresnido says:
      January 14, 2020 at 6:14 pm

      Good day, Will this stop edge chromium being updated on all machines being handled by configman?

      Reply
      1. Jörgen Nilsson says:
        February 7, 2020 at 5:22 pm

        Yes, If you use the builtin wizard to deploy it then yes, automatic updates will be disabled.
        Regards,
        Jörgen

        Reply
    2. Ram says:
      January 17, 2020 at 4:38 pm

      Can you share the PS script

      Reply
      1. LomM says:
        January 22, 2020 at 9:19 am

        The Script can be found in the download folder that was specified during the installation.

        Reply
    3. Pingback: System Center Ocak 2020 Bülten – Sertaç Topal
    4. Blixa says:
      February 7, 2020 at 3:30 pm

      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”…

      Reply
    5. Andrew says:
      May 6, 2020 at 12:17 pm

      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?

      Reply
    6. Patrick says:
      August 22, 2020 at 4:08 pm

      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

      Reply

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
    All code is provided "AS-IS" with no warranties.

    Recent Posts

    • Community tools demoed at WPNinjas 2023
    • PowerShell script to keep Personal Teams away in Windows 11
    • Windows 11 Multi-App kiosk – a first look
    • Playing around with Driver Updates in Intune
    • MMUGSE – Summer Meetup 8th of June 2023

    ©2023 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    Non-necessary
    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
    SAVE & ACCEPT