Run a silent install
Install EasyCC unattended on a clean test machine.
For the lab walkthrough, prove that EasyCC installs without any user interaction. You'll use the same flags your MDM will use in production.
Windows
The Windows installer is NSIS-based and supports the standard NSIS silent flags.
Uninstall any prior copy
You want a clean slate. Run the uninstaller from %LOCALAPPDATA%\EasyCC\uninstall.exe, or from Add/Remove Programs.
If you previously installed v0.8.0 or v0.8.1-beta.2, the uninstaller lives at
%ProgramFiles%\EasyCC\uninstall.exeinstead — that release series shipped briefly as a machine-wide install. v0.8.1-beta.3 reverted to per-user; uninstall the old machine-wide copy first, then install fresh.
Run the silent install
EasyCC-Setup.exe /SFor a custom install path:
EasyCC-Setup.exe /S /D=C:\Users\<you>\AppData\Local\EasyCCThe /D flag must be the last argument and the path must not be quoted (NSIS quirk).
Launch with --silent-first-run
& "$env:LOCALAPPDATA\EasyCC\EasyCC.exe" --silent-first-runThis tells EasyCC it's being launched by a deploy tool, so it can skip interactive onboarding when a service-provider bundle or managed policy already satisfies setup. If setup isn't satisfied, the wizard runs anyway — we never wedge the user on a blank screen.
macOS
Unattended Mac install isn't supported yet. EasyCC ships a .dmg today, not a .pkg — and the .dmg needs a drag-to-Applications step that doesn't work unattended. For lab testing, install the .dmg by hand. For fleet deploy, hold on Mac rollout or have users install interactively. See macOS .pkg installer for status.
For a manual lab install on Mac:
Uninstall any prior copy
sudo rm -rf /Applications/EasyCC.appInstall from the .dmg
Open EasyCC.dmg and drag EasyCC.app to /Applications/. (This is the same interactive flow an end user goes through.)
Confirm the bundle landed
ls -d /Applications/EasyCC.appLaunch with --silent-first-run
/Applications/EasyCC.app/Contents/MacOS/EasyCC --silent-first-run &Once the .pkg ships, you'll wire this into a LaunchAgent on login instead.
What --silent-first-run does
It signals "this app was launched by a deploy tool, not a user." Two things change:
- First-run interactive screens are skipped when a managed policy or bundle already satisfies them (provider, agents folder, Sage onboarding).
- If setup is incomplete, the wizard still runs. The user is never left staring at an empty window.
Sign-in is always interactive — a deploy tool can't sign a user in.
See Silent install flags for every flag the installer accepts.
Updater behavior
Per-user installs to %LOCALAPPDATA% don't require elevation, so the auto-updater runs silently for every user — no UAC prompt (v0.7.x behavior, restored in v0.8.1-beta.3).
If your change-management process requires gating updates, point update_endpoint at a mirror you control and only publish there after each release is approved. See Self-hosted mirror.
Next
How is this guide?