I have spent many, many hours creating and testing this ADMX. If it helps you please consider buying me a Coffee :)
Tip
Coming soon: ADMX Pro. Ready-to-import Intune & GPO profiles (Security Hardened · STIG-aligned · No Nags & Upsells), re-tested against every vendor release, plus an email alert when a vendor changes or breaks a setting. Join the waitlist → (free, no spam, one email when it launches)
Detailed policy reference pages, changelogs, and curated guides live under Documentation/.
| Adobe DC Settings (Device) | Machine-scope Acrobat + Reader policies |
| Adobe DC Settings (User) | User-scope Acrobat + Reader policies |
| Browser Extension Settings | Chrome and Edge extension managed-storage policies |
| Suppress Nags & Upsells | Nag and upsell controls (Device and User) |
| Security Hardening | Recommended security configurations (Device and User) |
| Screenshots | GPMC and Intune screenshots |
| ADMX Upgrade | Replace an imported ADMX in Intune (backup, delete, re-upload) |
| Changelog (Combined) | Combined device + user version history |
| Changelog (Retired) | Legacy device-only and user-only ADMX version history |
| Contributors | Community contributors and acknowledgements |
These ADMX/ADML templates (v4.2) provide Group Policy and Intune management of Adobe Acrobat DC and Adobe Reader DC on Windows. A single AdobeDC.admx/ADML pair covers machine-level (HKLM) and user-level (HKCU) policies.
AdobeDC.admx + ADML |
Adobe DC (Computer + User) | 828 (310 machine + 518 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"]
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 310 machine policy entries (158 unique Adobe machine settings after removing non-ADMX
tBuiltInPermList; architecture-specific non-policy settings are emitted separately for x64 and x86; plus 12 browser extension entries). Overall template: 310 machine + 518 user = 828 policy entries.
Counts are product-scoped: settings that apply to both Reader and Acrobat are listed under each product. The ADMX contains 518 user policy entries.
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 v4.2.
Convert them first with Helper_Scripts/Convert-AdobeDcIntuneExportToCombinedV3.ps1, then re-import.
See the ADMX install guide for migration steps. Upgrading from combined v3.0/v3.1/v3.2/v3.3/v3.4/v3.5 to v4.2 keeps the same namespace and policy names for existing settings. v3.4+ releases are additive-only except where a changelog entry documents a one-time control-type correction - re-upload preserves existing Intune/GPO bindings for all other settings.
| 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). |
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.