Group Policy and Intune ADMX/ADML templates for Adobe Acrobat DC and Adobe Reader DC on Windows. A single AdobeDC.admx/ADML pair covers machine-level (HKLM) and user-level (HKCU) policies, with policy reference pages, DISA STIG mapping tables, and curated hardening guides under Documentation/.
This is an independent, community-maintained fork of systmworks/Adobe-DC-ADMX, originally created by systmworks and licensed under CC BY-SA 4.0. The upstream template through v4.2 is the foundation of this work, and full credit for it belongs to its author. If it helps you, please consider supporting the original author.
The project now follows its own direction. What differs from upstream:
| Area | This project |
|---|---|
| Extra policies | ARM Legacy updater policies (8), a Machine-scope URL Access Permissions policy (iURLPerms) so Computer Configuration satisfies the STIG SCAP check, and removal of app-internal state flags that are not meaningful admin settings. |
| STIG documentation | Per-control mapping tables for the Acrobat Pro DC and Reader DC STIGs showing the GPMC/Intune category path, the exact Enabled/Disabled (or dropdown) selection to make, and the registry data written. |
| Hardening guidance | Recommendations are validated against real behavior. For example, Block PDF Link Actions is flagged because it breaks XFA-based forms. |
| Docs layout | Separate Acrobat and Reader settings pages per scope. No in-repo changelog or generated data files; version history lives in GitHub Releases. |
| Tooling | CI validation of the ADMX/ADML (scripts/validate.py), release automation, and Intune helper scripts for sandbox testing. |
| Versioning | Releases are tagged and published on GitHub and are independent of upstream's version numbers. The revision attribute inside the template files is a format revision, not a release number. |
Upstream changes are reviewed and brought in selectively rather than merged wholesale.
Warning
Migrating from v2.x or User ADMX v1.x is a breaking change. The combined namespace and re-organised tree mean Intune ADMX backups/exports from those versions will not import into the combined template.
Convert them first with Helper_Scripts/Convert-AdobeDcIntuneExportToCombinedV3.ps1, then re-import.
See the ADMX install guide for migration steps. Upgrades within the combined template keep the same namespace and policy names for existing settings. Releases are additive-only except where release notes document a one-time control-type correction - re-upload preserves existing Intune/GPO bindings for all other settings.
| Acrobat DC Settings (Device) | Machine-scope Acrobat DC policies |
| Acrobat DC Settings (User) | User-scope Acrobat DC policies |
| Reader DC Settings (Device) | Machine-scope Reader DC policies |
| Reader DC Settings (User) | User-scope Reader DC policies |
| Security Hardening (Device) | Recommended device security configurations |
| Security Hardening (User) | Recommended user security configurations |
| Reduce Nags & Upsells (Device) | Device-scope nag and upsell controls |
| Reduce Nags & Upsells (User) | User-scope nag and upsell controls |
| STIG: Acrobat Pro DC | DISA STIG controls mapped to ADMX policy, GPMC path, and exact setting |
| STIG: Reader DC | DISA STIG controls mapped to ADMX policy, GPMC path, and exact setting |
| Built-in Attachment Permissions helper | REG_BINARY deployment for tBuiltInPermList (not in ADMX) |
| Screenshots | GPMC and Intune screenshots |
| License | CC BY-SA 4.0 license |
AdobeDC.admx + ADML |
Adobe DC (Computer + User) | 840 (320 machine + 520 user) |
flowchart TD
ADMX["AdobeDC.admx + ADML"]
ADMX --> Computer["Computer Configuration (HKLM)"]
ADMX --> User["User Configuration (HKCU)"]
Computer --> AR["Acrobat & Reader DC<br/>Policies\\Adobe\\Adobe Acrobat\\DC (Acrobat x86/x64 + modern x64 Reader)"]
Computer --> R32["Reader DC (32-bit)<br/>Policies\\Adobe\\Acrobat Reader\\DC (legacy 32-bit Reader)"]
Computer --> NP["Non-Policy Settings<br/>architecture-specific non-Policies paths"]
Computer --> BE["Browser Extensions<br/>Chrome + Edge 3rdparty extension policy paths"]
User --> UA["Acrobat DC (User)"]
User --> UR["Reader DC (User)<br/>HKCU prefs; leaf names carry the (User) suffix"]
| x64 Reader (Unified Installer) is configured under Acrobat & Reader DC (Acrobat hive), not the Reader hive. Configure legacy 32-bit Reader under Reader DC (32-bit). |
Some machine settings write outside HKLM\SOFTWARE\Policies and appear under Adobe DC > Non-Policy Settings with architecture-specific sub-nodes (Acrobat & Reader DC (64-bit), Acrobat DC (32-bit), Reader DC (32-bit)). See curated guides for marked entries. |
| Browser extension settings write to each browser's 3rdparty extension policy path under Adobe DC > Browser Extensions (Google Chrome / Microsoft Edge). Values are REG_SZ strings, not DWORD. See Browser Extension Settings. |
Several bToggle* policies use inverted registry values (DWORD 0 = feature ON, DWORD 1 = feature OFF). |
Counts are product-scoped: settings that apply to both Reader and Acrobat are listed under each product, so Reader + Acrobat column totals are higher than the number of unique settings. The ADMX contains 320 machine policy entries (156 unique machine settings after removing non-ADMX
tBuiltInPermList; architecture-specific non-policy settings are emitted separately for x64 and x86). Overall template: 320 machine + 520 user = 840 policy entries.
Counts are product-scoped: settings that apply to both Reader and Acrobat are listed under each product. The ADMX contains 520 user policy entries.
Sharing & responsibility - Built for the community, shared with good intentions. Use at your own risk. The author accepts no responsibility for any outcomes resulting from the use of these files. Always verify registry paths and values, and test in a safe environment first. If you find an issue or have a suggestion, contributions are welcome.