ADML and ADMX
Where to find the Group Policy templates.
EasyCC ships ADMX and ADML files for managing the app via Active Directory Group Policy. This page links to the files and covers how to install them.
The files
| File | Where |
|---|---|
windows-gpo-easycc.admx | docs/enterprise/windows-gpo-easycc.admx |
windows-gpo-easycc.adml (en-US) | docs/enterprise/windows-gpo-easycc.adml |
Download both. They're plain XML and small (a few KB each).
Installing in the Central Store
If your domain has a Group Policy Central Store (most do), drop the files in:
\\<domain>\SYSVOL\<domain>\Policies\PolicyDefinitions\windows-gpo-easycc.admx
\\<domain>\SYSVOL\<domain>\Policies\PolicyDefinitions\en-US\windows-gpo-easycc.admlIf your domain doesn't have a Central Store yet, create one:
# On a DC, copy the local PolicyDefinitions to SYSVOL
robocopy "$env:windir\PolicyDefinitions" "\\$env:userdnsdomain\SYSVOL\$env:userdnsdomain\Policies\PolicyDefinitions" /EThen drop the EasyCC files in.
Installing on a single machine (no Central Store)
For lab use, copy to the local PolicyDefinitions folder:
C:\Windows\PolicyDefinitions\windows-gpo-easycc.admx
C:\Windows\PolicyDefinitions\en-US\windows-gpo-easycc.admlGPMC on that machine will pick up the templates. Note: this only affects local Group Policy on this one machine.
What the templates contain
The ADMX defines policy categories that mirror EasyCC's managed-policy field groups:
| Category | Fields |
|---|---|
| EasyCC → General | release_channel, dev_mode, minimize_to_tray, agents_root |
| EasyCC → Updates | update_endpoint, max_update_deferral_hours, force_update_after_hours |
| EasyCC → Safety scanner | safety_deep_check_enabled, safety_sensitivity, safety_judge_mode, safety_block_mode, safety_custom_model_url_base |
| EasyCC → Token efficiency | The 5 token-efficiency fields |
Each field has:
- A user-friendly name (read from the ADML)
- A description (read from the ADML)
- An "Enabled / Disabled / Not Configured" tri-state
- A value editor (text, number, dropdown)
Enforced vs Recommended via ADMX
GPMC's ADMX UI separates each setting into:
- EasyCC → Enforced — values the user can't override
- EasyCC → Recommended — defaults the user can change
This matches the underlying registry split (HKLM\Software\Policies\EasyCC vs HKLM\Software\Policies\EasyCC\Recommended).
When you configure a setting under "Enforced," GPMC writes to the enforced subkey. When you configure under "Recommended," GPMC writes to the Recommended subkey. EasyCC reads both.
Using GPMC
Open Group Policy Management Console
Run gpmc.msc on a Windows admin workstation.
Pick a GPO
Pick an existing GPO that targets your fleet, or create a new one.
Edit
Right-click the GPO → Edit.
Navigate
Computer Configuration → Policies → Administrative Templates → EasyCC → category
You'll see categories matching the field groups above.
Configure
Pick a setting, click Enabled, set the value. Save.
Apply
GPOs apply on:
- Domain logon (slow-link policy)
- Periodic refresh (default: every 90 minutes ± 30)
- Manual:
gpupdate /force
Localization
The shipped ADML is en-US. For other locales:
| Locale | Status |
|---|---|
| en-US | ✅ Shipped |
| All others | Not shipped in v1 |
If you need a localized ADML, you can author one yourself based on the en-US template. Drop it in the appropriate locale subdirectory of PolicyDefinitions.
For partner-published localized ADMLs, contact us.
When the ADMX needs updating
When EasyCC adds new managed-policy fields (typically with each major release), the ADMX changes too. You'll need to:
- Download the new ADMX + ADML
- Replace the files in your Central Store
- Wait for the next GPMC refresh
Existing policy values for unchanged fields keep working. New fields appear in GPMC after the refresh.
Troubleshooting
| Symptom | Cause |
|---|---|
| EasyCC category doesn't appear in GPMC | The ADMX/ADML aren't in PolicyDefinitions, or you're using an older GPMC that hasn't refreshed. |
| Setting appears but says "Not Configured" everywhere | You haven't configured it yet (this is normal). |
| Value set in GPMC doesn't reach the device | GPO hasn't applied yet. Run gpupdate /force on the device. |
| Value reaches registry but EasyCC ignores it | Field name typo (use Reference → Policy fields) or wrong type. |
For deeper troubleshooting, see A policy isn't applying.
Why ADMX and not just the registry?
You can write to HKLM\Software\Policies\EasyCC directly (via PowerShell, regedit, or a script policy). The ADMX is a convenience:
- GPMC UI for browsing and editing
- Built-in descriptions per field
- Validation of value types
- Familiar to AD admins
For non-domain deploys (Intune, Jamf, SCCM), use the per-MDM patterns instead — see Deploy.
How is this guide?