Verify the deploy
Confirm policy + install both took on the test machine.
The last step of the walkthrough is to prove that everything you pushed is actually in effect. Six checks — they take about three minutes.
On the test machine
EasyCC binary is in the expected location
| Platform | Path |
|---|---|
| Windows | %ProgramFiles%\EasyCC\EasyCC.exe |
| macOS | /Applications/EasyCC.app/Contents/MacOS/EasyCC |
EasyCC launches and signs in
Open the app. Sign in. Confirm the Command Center appears.
Open Settings → About
Confirm three things:
- Version matches what you installed.
- Update source URL is what you expect (the default GitHub-hosted manifest, or your mirror if you set
update_endpoint). - Signing key fingerprint is a short SHA-256 hash. Every machine on your fleet should see the same value — if one differs, that machine is on a tampered build.
Open Settings → Advanced
Find the field you set in Push your first policy. It should:
- Show its enforced value (the one you pushed)
- Be visually disabled — the user can't edit it
- Have a small lock icon
- Show the tooltip "Managed by your organization — you can't change this." on hover
If the field shows the user's own value instead, the policy didn't apply. See A policy isn't applying.
Confirm the policy was logged
EasyCC writes a structured log on launch. The line includes the policy fields it read.
| Platform | Log path |
|---|---|
| Windows | %LOCALAPPDATA%\com.easycc.app\logs\ |
| macOS | ~/Library/Logs/com.easycc.app/ |
Look for the most recent log file and search for managed policy. You should see one line per field that was applied.
Confirm the installer is detectable by your MDM
Run your MDM's detection rule from the Detection rules page. Confirm it reports EasyCC as installed.
You're done with the walkthrough
If all six checks pass, your deploy pipeline works end-to-end. From here:
Browse all deploy recipes
Per-MDM how-tos with copy-paste config.
Configuration reference
Every managed-policy field, with the enforced/recommended split.
Service-provider bundles
Pre-seed agents, skills, MCP servers, and branding.
Cleaning up the lab
If you want to take the test machine back to a clean state:
Windows (PowerShell):
Remove-Item -Path 'HKLM:\Software\Policies\EasyCC' -Recurse -Force
& "$env:ProgramFiles\EasyCC\uninstall.exe" /SmacOS:
sudo rm /Library/Managed\ Preferences/com.easycc.app.plist
sudo rm -rf /Applications/EasyCC.app
rm -rf ~/Library/Application\ Support/com.easycc.appThe user's per-agent files (under ~/EasyCC/) stay put unless you remove them too.
How is this guide?