The overview comes first. If you’ve arrived with a remediation misbehaving in production, the index at the end starts from what the portal shows you and points at the post that covers it.
Intune runs my scripts in Windows PowerShell 5.1, from system32, often as SYSTEM. My console is none of those, so I built a module that tests scripts the way the agent will, from what real devices did.
Microsoft’s sample detection for expired certificates returns a count before its exit 1, so it exits 0 and the remediation never runs. My linter flags that, and every rule cites the device test behind it.
My remediation prints success and exits 0 over a Set-ItemProperty error, and Intune calls it Failed. My harness runs scripts the way the agent does, as me, as SYSTEM or as another account, and now agrees.
A file rule set to “does not exist” saves in the portal and Graph, and the Intune agent never counts the app as installed. My harness checks Win32 detection, requirements and installs the way devices did.
Microsoft’s own cpuArchitecture filter example saves without complaint and drops every x64 Windows device, which reports amd64. My command checks a rule locally the way the service parsed and matched it.
The Enrollment Status Page closes while my user’s blocking app is still InProgress, and only AppWorkload.log records it. IntuneScriptLab reads the agent’s four CMTrace logs as objects and timelines.
I set runRemediationScript to false, Graph reads it back that way, and both devices still run the fix every hour. IntuneScriptLab audits what the tenant holds against rules, git and what devices report.
I run Invoke-ScriptAnalyzer -Severity Error with IntuneScriptLab’s rules loaded, and every Intune record disappears, Errors included. The wrapper puts those rules in PSScriptAnalyzer’s own pass.
My uptime detection returns 1 at script scope, so it exits 0, and its runtime test passes. The static check fails it on line 5. IntuneScriptLab’s gate and Pester assertions put both in a pull request.
REM-RETURN-EXIT has run hourly for three weeks, and its probe file holds 168 records, all detections. My validation kit deploys experiments like it to Proxmox VMs and reads them back.
My Widget detection exits 0 with nothing on stdout, so Intune installs the app, can’t find it and reports 0x87D1041C. This index maps each portal symptom to the IntuneScriptLab command behind it.