Deploy to a Windows Fleet
You deploy two things: a small setup script that enrolls the PC with your workspace, and the signed Waxell MSI. The MSI installs the agent, registers the coding-agent hooks and force-installs the Waxell browser extension into Chrome, Edge and Firefox — no separate browser policy needed.
What you deploy
| Artifact | What it does |
|---|---|
Setup script — waxell-setup.ps1 (generated for your workspace) | Trusts your workspace certificate and writes the enrollment settings to HKLM\SOFTWARE\Waxell. Idempotent; safe to re-run. |
The app — WaxellSetup-x64.msi | Installs the Waxell services, the browser bridge, wax-hook, and force-installs the browser extension. Signed by CallSine LLC. Runs on x64 and on ARM64 under emulation. |
Both are on Endpoints → Setup.
Treat waxell-setup.ps1 as a secret and limit who can read it in your MDM or
RMM.
Deploy with Intune
1. Setup script
Devices → Scripts and remediations → Platform scripts → Add → Windows 10 and later:
- Script file:
waxell-setup.ps1 - Run this script using the logged on credentials: No
- Enforce script signature check: No (or Yes if you sign it)
- Run script in 64 bit PowerShell host: Yes
The script already trusts the workspace certificate, so a separate Trusted certificate profile is optional.
2. The MSI
Apps → Windows → Add → Win32 app — wrap the MSI as .intunewin with
Microsoft's Win32 Content Prep Tool first:
- Install command:
msiexec /i "WaxellSetup-x64.msi" /qn /norestart - Uninstall command:
msiexec /x {9F3A2B81-7C4E-4E1A-9D0B-5E6F1A2B3C4D} /qn /norestart - Install behavior: System
- Detection rule: MSI (auto-detected)
3. Assign and push
Assign both to the same device group. The script usually applies within minutes; the app on the next sync.
Deploy with an RMM
NinjaOne, ConnectWise, Datto, Kaseya and similar tools can deploy Waxell with the script on Endpoints → Setup. It downloads the current MSI, checks its SHA-256 against Waxell's release manifest, writes the enrollment settings and installs — run it as SYSTEM. No MDM is needed.
Application control (ThreatLocker, AppLocker, WDAC)
If your fleet runs an application allow-listing tool, approving the MSI is not enough. Allow these to run:
| Executable | Started by |
|---|---|
C:\Program Files\Waxell\Bridge\WaxellBrowserBridge.exe | Chrome / Edge / Firefox, through cmd.exe, every time the extension connects |
C:\Program Files\Waxell\Setup\wax-hook.exe | Claude Code, Cursor, Codex and other coding agents, before each action |
C:\Program Files\Waxell\Service\WaxellNetworkMonitor.exe | Windows service |
C:\Program Files\Waxell\PolicyDaemon\WaxellPolicyDaemon.exe | Windows service |
C:\Program Files\Waxell\Cowork\WaxellCoworkWatcher.exe | Starts at user sign-in |
PowerShell helper scripts in C:\Program Files\Waxell\Setup\ | The installer and services |
All Waxell executables are signed by CallSine LLC; a publisher rule is the simplest allow. If the bridge is blocked, the Health page shows the device as no ext and no browser captures arrive.
Verify
Within an hour of the next sync each PC appears in your workspace:
- Health — reports every 60 seconds. Hooks should read managed; Capture reads on after someone uses AI in a browser.
- Inventory → AI Apps — the AI apps found on the PC.
- Activity and Captures — AI use as it happens.
On the PC, sc query WaxellNetworkMonitor and sc query WaxellPolicyDaemon
should both be running, and chrome://extensions should list
Waxell AI Monitor as installed by your organisation.
For a whole fleet, Waxell's fleet diagnostic script (run as SYSTEM from your RMM or MDM) prints one summary line per PC — enrollment, credentials, browser bridge, last upload — which pinpoints most problems at once. Ask Waxell support for it.
Optional: turn off encrypted DNS in browsers
Browsers using DNS-over-HTTPS hide which AI sites they reach from the network monitor. Browser capture is unaffected, but if you rely on flow visibility, push the Disable DoH policy from Setup (GPO or Intune Settings Catalog). The Health page warns per device when DoH is on.
Memory Integrity (HVCI)
On PCs with Memory Integrity on, Windows blocks the packet driver Waxell uses to read HTTP/3 hostnames. Only that one metadata signal is affected; browser capture, hooks, policy and flow visibility work normally. No action is needed.
Uninstalling
Uninstall through your MDM or with the uninstall command above. Uninstall removes
the services, browser bridge registration and extension policy. The
HKLM\SOFTWARE\Waxell enrollment settings are left in place so a reinstall
re-enrolls the same device; remove the key if you are decommissioning.