Use EndpointWorks with Intune
Intune delivers the agent and runs epw on the device. EndpointWorks still decides every install. Nothing in the Intune kit lets Intune bypass your approvals, rings or limits.
Before you begin
Section titled “Before you begin”- Plan: Business or higher for Intune onboarding. Premium for the Intune kit.
- Permission: View packages and View devices (
packages:readanddevices:read). - Intune Remediations need the Intune licensing that includes them.
Onboard devices
Section titled “Onboard devices”- Go to Devices & Access › Connect devices and open Intune onboarding.
- Create an enrollment token if you don’t have one. See Deploy the agent.
- Import the ADMX and deliver the server URL and enrollment token by policy.
- Create the Win32 app for the agent with the Install command, Uninstall command and Detection rule on the page.
- Assign the app. Then use Check the first inventory to confirm devices report.
Download the Intune kit
Section titled “Download the Intune kit”The kit is a ZIP with ready-made scripts:
| In the kit | What it does |
|---|---|
| Remediations detection script | Runs epw healthcheck. Exits 1 when the device isn’t compliant or healthy |
| Remediations remediation script | Runs ew-agent repair, then epw rebaseline --queue --no-wait |
| Compliance discovery script | Reads the agent’s verdict for Intune custom compliance |
| Compliance rules file | EwState IsEquals compliant and EwVerdictAgeHours LessEquals 24 |
Run the Remediations pair as System. Conditional Access can then use the custom compliance result.
Deploy a baseline as a Win32 app
Section titled “Deploy a baseline as a Win32 app”Each published baseline revision has its own kit, with these settings:
| Setting | Value |
|---|---|
| Install command | install.cmd, which runs epw.exe baseline install <slug> --timeout 50 --quiet |
| Install behavior | System |
| Installation time required | 60 minutes |
| Requirements | x64 and arm64, Windows 10 22H2, epw.exe present |
| Dependency | The EndpointWorks agent Win32 app |
| Detection | Custom script, detection.ps1 |
| Return codes | 0 success, 3010 soft reboot, retry on 1618, 4, 10, 25 and 29 |
Package it with IntuneWinAppUtil.exe. The kit includes the exact command.
Rings still apply. Publishing a new revision doesn’t make every device reinstall at once.
Who owns an app
Section titled “Who owns an app”One owner per app. A package you declare Intune-owned is never installed or removed by EndpointWorks. An MSI that Intune tracks as a line-of-business app is skipped and flagged.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Fix |
|---|---|
| The kit shows a plan notice | The Intune kit needs Premium. |
| The kit warns that Intune can’t detect the baseline | The baseline isn’t available to the device group behind your Intune assignment. Assign it, or pick another group. |
| Remediation runs every time | Check epw healthcheck --json on a device. The error.code names the problem. |
| Scripts fail under 32-bit PowerShell | Call epw by absolute path, "$env:ProgramW6432\EndpointWorks\Agent\bin\epw.exe". The kit does this. |