Mass Distribution for Microsoft Edge Chromium with SCCM

Introduction

This document provides step-by-step instructions for the deployment of Apty Extension on Edge Chromium Browser via SCCM.

CONTENTS

Step 1: Downloading Files for Chromium Edge

  •  Make sure that you have access to the following Apty installation files:
    1.  install.bat
    2. ChromiumEdge-AptyStore
  • Save the files in your shared directory which will be accessible to other users

Step 2: Configuration via SCCM

  • In the Software Library\Overview\Application Management\Applications create an application.
  • Select Manually specify the application information as shown on the screen below: 

  • Specify Application Information. For example, EdgeExtensionAptyStore

  • Create New Deployment Type. Select Script Installer and Manually specify the deployment type information.

  • Specify general information.

  • Enter the Content Location and Installation Program details.
NOTE: Select the “install.bat” file for Installation Program.

  • Select Add Clause in the Detection Method Page

  • Select “Registry” in the Setting Type. Enter Values as shown in the table an d on the screen below:
Hive:HKEY_LOCAL_MACHINE
Key:SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallSources
Value:3
This registry key is associated with 32- and 64-bit systems”Enable
Data Type:String
This registry setting must satisfy the following ruleSelect
Operator:Equals
Value: https://apty-assist-production-s3.s3.amazonaws.com/* 
  • Click OK to proceed

  • Click Next

  • In the Specify user experience settings for the application screen define the following:
Installation behaviour
Install for System
Logon requirement
Whether or not a user is logged in
Installation program visibilityHidden
Maximum allowed run time (minutes)20

  • Click Next and create the package.
  •  Deploy the package

Step 3: Check Your Chromium Edge Policies

  • On a target client device, open Edge Browser and navigate to edge://policy to see all policies that are applied. 
  • You can also check your extension by navigating to edge://extensions and ensuring your extensions are being forcefully installed.


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.