windows-itpro-docs/browsers/edge/managing-group-policy-admx-files.md
illfated 67af30f4f1 chore: MarkDown Note marker compatibility spacing
Description:

This PR is a standalone attempt to standardize the MarkDown Note
bubbles by adding the recommended single space after the quote marker.
MarkDown codestyle consistency is the main goal here.

Changes proposed:
- Add single space between the quote marker and the text [!NOTE]
- Add the same spacing to the connected text line in the same bubble
- Apply the same standard to other nearby notes, e.g. [!IMPORTANT]
- Standardize on uppercase [!NOTE] instead of mixed casing ( [!Note] )
- Remove some of the obvious redundant spacing at end-of-file

Ticket reference or closure:

None that I know of (at least not yet).

Additional notes:
I have split this modification chore into sub-folder sections to keep
the number of files within a reasonably manageable amount.
2020-02-15 03:35:34 +01:00

28 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: Managing group policy ADMX files
description: Learn how to centrally administer and incorporate ADMX files when editing the administrative template policy settings inside a local or domain-based Group Policy object.
ms.assetid:
ms.reviewer:
audience: itpro
manager: dansimp
author: dansimp
ms.author: dansimp
ms.prod: edge
ms.sitesec: library
ms.localizationpriority: medium
ms.date: 10/19/2018
---
# Managing group policy ADMX files
>Applies to: Microsoft Edge on Windows 10
ADMX files, which are registry-based policy settings provide an XML-based structure for defining the display of the Administrative Template policy settings in the Group Policy Object Editor. The ADMX files replace ADM files, which used a different markup language.
> [!NOTE]
> The administrative tools you use—Group Policy Object Editor and Group Policy Management Console—remain mostly unchanged. In the majority of situations, you wont notice the presence of ADMX files during your day-to-day Group Policy administration tasks.
Unlike ADM files, ADMX files are not stored in individual GPOs by default; however, this behavior supports less common scenarios. For domain-based enterprises, you can create a central store location of ADMX files accessible by anyone with permission to create or edit GPOs. Group Policy tools continue to recognize other earlier ADM files you have in your existing environment. The Group Policy Object Editor automatically reads and displays Administrative Template policy settings from both the ADMX and ADM files.
Some situations require a better understanding of how ADMX files are structured and the location of the files. In this article, we show you how ADMX files are incorporated when editing Administrative Template policy settings in a local or domain-based Group Policy object (GPO).