[Download Group Policy Templates For New Microsoft Edge Chromium Browser

0 views

Skip to first unread message

Oludare Padilla

unread,

Jun 12, 2024, 3:07:33 PM6/12/24

to lobspanlofi

You can use group policy objects (GPO) to configure policy settings for Microsoft Edge and managed Microsoft Edge updates on all versions of Windows. You can also configure policies via the registry for:

Download Group Policy Templates for new Microsoft Edge Chromium browser

Download ○○○ https://xiuty.com/2yEzJr

To configure Microsoft Edge with group policy objects, install administrative templates that add rules and settings for Microsoft Edge to the group policy Central Store in your Active Directory domain. Alternatively, add these rules and settings to the Policy Definition template folder on individual computers and then configure the specific policies you want to set.

You can use Active Directory group policy to configure Microsoft Edge policy settings if you prefer to manage policy at the domain level. This approach lets you manage policy settings globally. You can target different policy settings to specific OUs, or use WMI filters to apply settings only to users or computers returned by a particular query. To configure policies on individual computers, you can use Local Group Policy Editor on the target computer. This approach lets you apply policy settings that only affect the local device.

Microsoft Edge supports mandatory and recommended policies. Mandatory policies override user preferences and prevent the user from the policy. Recommended policies provide a default setting that the user can override. Most policies are only mandatory but there's a subset that is mandatory and recommended. If both versions of a policy are set, the mandatory setting takes precedence. A recommended policy only takes effect when the user hasn't modified the setting.

There are two administrative templates for Microsoft Edge, both can be applied with common group policy management tools such as Local Group Policy Editor for application on an individual computer or the Group Policy Management Console for Microsoft Windows domain networks. These templates are:

If you want to configure Microsoft Edge policy settings in Active Directory, download the files to a network location you can access from a domain controller or a workstation with the Remote Server Administration Tools (RSAT) installed. To configure on an individual computer,download the files to that computer.

On a domain controller or workstation with RSAT, go to the PolicyDefinition folder (also known as the Central Store) on any domain controller for your domain. For older versions of Windows Server, you might need to create the PolicyDefinition folder. For more information, see How to create and manage the Central Store for Group Policy Administrative Templates in Windows.

Copy the msedge.adml file to the matching language folder in the PolicyDefinition folder. Create the folder if it doesn't already exist. (Example: %systemroot%\sysvol\domain\policies\PolicyDefinitions\EN-US)

To confirm the files loaded correctly, open the Group Policy Management Editor from Windows Administrative Tools and expand Computer Configuration > Policies > Administrative Templates > Microsoft Edge. You should see one or more Microsoft Edge nodes as shown below.

You can set mandatory or recommended policies to configure Microsoft Edge with the Group Policy Editor for both Active Directory and individual computers. You can scope policy settings to either the Computer Configuration or User Configuration by selecting the appropriate node as described below.

On a target client device, open Microsoft Edge and go to edge://policy to see all policies that are applied. If you applied policy settings on the local computer, policies should appear immediately. You might need to close and reopen Microsoft Edge if it was open while you were configuring policy settings.

For Active Directory group policy settings, policy settings are sent to domain computers at a regular interval defined by your domain administrator. Target computers might not receive policy updates right away. If you want to manually refresh Active Directory group policy settings on a target computer, run the following command from a command prompt or PowerShell session on the target computer:

You can also use REGEDIT.exe on a target computer to view the registry settings that store group policy settings. These policy settings are located at this registry path: HKLM\SOFTWARE\Policies\Microsoft\Edge.

You can download the Microsoft Security Compliance Toolkit for the recommended security configuration baseline settings for Microsoft Edge. For more information see the Microsoft Security Baselines Blog.

Starting in Microsoft Edge version 116, certain policies will not be applied to a profile that is signed in with a Microsoft account. For more information, please check an individual policy for details on whether it applies to a profile that is signed in with a Microsoft account.

If you enable this policy, all navigations from Edge, including navigations to untrusted sites, will be accessed normally within Edge without redirecting to the Application Guard container. Note: this policy ONLY impacts Edge, so navigations from other browsers might get redirected to the Application Guard Container if you have the corresponding extensions enabled.

If you enable or don't configure this policy, Application Guard will add an extra HTTP header (X-MS-ApplicationGuard-Initiated) to all outbound HTTP requests made from the Application Guard container.

Setting the policy lets you make a list of URL patterns that specify sites for which Microsoft Edge can automatically select a client certificate. The value is an array of stringified JSON dictionaries, each with the form "pattern": "$URL_PATTERN", "filter" : $FILTER , where $URL_PATTERN is a content setting pattern. $FILTER restricts the client certificates the browser automatically selects from. Independent of the filter, only certificates that match the server's certificate request are selected.

Define a list of sites, based on URL patterns, that are allowed to perform multiple successive automatic downloads.If you don't configure this policy, DefaultAutomaticDownloadsSetting applies for all sites, if it's set. If it isn't set, then the user's personal setting applies.For more detailed information about valid URL patterns, see =2095322.

Define a list of sites, based on URL patterns, where multiple successive automatic downloads aren't allowed.If you don't configure this policy, DefaultAutomaticDownloadsSetting applies for all sites, if it's set. If it isn't set, then the user's personal setting applies.For more detailed information about valid URL patterns, see =2095322.

To allow third-party cookies to be set, specify a pair of URL patterns delimited by a comma. The first value in the pair specifies the third-party site that should be allowed to use cookies. The second value in the pair specifies the top-level site that the first value should be applied on. The first value in the pair supports * but the second value does not.

Cookies created by websites that don't match the pattern are controlled by the DefaultCookiesSetting policy (if set) or by the user's personal configuration. This is also the default behavior if you don't configure this policy.

This policy enables Data URL support for SVGUseElement, which will be disabledby default starting in Edge stable version 119.If this policy is Enabled, Data URLs will keep working in SVGUseElement.If this policy is Disabled or left not set, Data URLs won't work in SVGUseElement.

Set whether websites can perform multiple downloads successively without user interaction. You can enable it for all sites (AllowAutomaticDownloads) or block it for all sites (BlockAutomaticDownloads).If you don't configure this policy, multiple automatic downloads can be performed in all sites, and the user can change this setting.

Control whether websites can create cookies on the user's device. This policy is all or nothing - you can let all websites create cookies, or no websites create cookies. You can't use this policy to enable cookies from specific websites.

If you don't configure this policy, the default 'AllowCookies' is used, and users can change this setting in Microsoft Edge Settings. (If you don't want users to be able to change this setting, set the policy.)

Set whether websites can track users' physical locations. You can allow tracking by default ('AllowGeolocation'), deny it by default ('BlockGeolocation'), or ask the user each time a website requests their location ('AskGeolocation').

Disabling the JavaScript JIT will mean that Microsoft Edge may render web content more slowly, and may also disable parts of JavaScript including WebAssembly. Disabling the JavaScript JIT may allow Microsoft Edge to render web content in a more secure configuration.

Set whether websites can display desktop notifications. You can allow them by default ('AllowNotifications'), deny them by default ('BlockNotifications'), or have the user be asked each time a website wants to show a notification ('AskNotifications').

Setting the policy to "BlockWindowManagement" (value 2) automatically denies the window management permission to sites by default. This limits the ability of sites to see information about the device's screens and use that information to open and place windows or request fullscreen on specific screens.

Setting the policy to "AskWindowManagement" (value 3) by default prompts the user when the window management permission is requested. If users allow the permission, it extends the ability of sites to see information about the device's screens and use that information to open and place windows or request fullscreen on specific screens.

Setting the policy lets you list the URL patterns that specify which sites can ask users to grant them read access to files or directories in the host operating system's file system via the File System API.

If you set this policy, you can list the URL patterns that specify which sites can't ask users to grant them read access to files or directories in the host operating system's file system via the File System API.