In most situations, configuring Microsoft Edge to update automatically is the best choice. Configuration Manager now supports the option to allow Microsoft Edge to automatically update the client, on the end user’s device (supported as of Configuration Manager version 2002).
Watch the video below for a quick overview of configuring the deployment package in Configuration Manger to enable automatic updates in Microsoft Edge.
For a broad majority of users, updating Microsoft Edge automatically is the preferred. However, there are situations where specific builds and versions are needed for testing and validation.
Microsoft Edge Control build levels and targeted versions
New ADMX-based policies allow IT administrators to limit Microsoft Edge to specific, targeted versions. This approach allows for greater control by letting organizations test specific builds before deploying to more users. Administrators can download the new ADMX policies.
Check out the video below to see how to download the ADMX templates and deploy them within an organization.
As you saw, you can limit the build level of Microsoft Edge to specific versions using the new ADMX-based policies. In addition, there are other policies that provide an even greater level of control, allowing administrators to configure which Microsoft Edge channel to use with opening sites that are redirected from Internet Explorer.
For more information on Microsoft Edge update policies, see Microsoft Edge – Update policies.
In the next unit, you’ll see how to configure side-by-side installations of Microsoft Edge.
Microsoft Edge installations & Configure
While most users will only need a single installation of Microsoft Edge, there are some instances such as testing and validating capabilities, that require multiple versions installed side-by-side.
Side-by-side experience with Microsoft Edge Stable Channel and Microsoft Edge Legacy
Installing the Stable Channel of the next version of Microsoft Edge at the system-level will cause the current version (Microsoft Edge Legacy) to be hidden. If you want to let your users see both versions of Microsoft Edge side by side in Windows, you can enable this experience by setting the Allow Microsoft Edge Side by Side browser experience group policy to Enabled.
To do this, follow these steps:
- Install the Policy Definitions from Microsoft Edge for Business.
- Pick the CHANNEL/BUILD and PLATFORM you want to use, and then choose GET POLICY FILES.
- Extract the zipped files.
- Copy msedge.admx and msedgeupdate.admx to the ‘C:\Windows\PolicyDefinitions’ directory.
- Copy msedge.adml and msedgeupdate.adml to the ‘C:\Windows\PolicyDefinitions\[APPROPRIATE LANGUAGE/LOCALE]’ directory.
- Open the Group Policy Editor (gpedit.msc).
- Under Computer Configuration, go to Administrative Templates > Microsoft Edge Update > Applications.
Note
If you don’t see the Microsoft Edge Update folder, verify that step 1 was completed correctly.
- Under Applications, double-click Allow Microsoft Edge Side by Side browser experience.
Note
By default, this group policy is set to “Not configured”, which results in Microsoft Edge Legacy being hidden when the new version of Microsoft Edge is installed.
- Select Enabled and then select OK.
Setting this policy will set the following Registry Key to ‘00000001’:
- Key: ‘Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\EdgeUpdate’
- Value Name: ‘Allowsxs’
- Value Type: ‘REG_DWORD’