Endpoint Log Monitor reads the client logs on any Windows device. It pulls out the errors that need action and gives your techs the troubleshooting steps next to each one.
One Windows EXE for techs and admins. Reads local and remote devices. No expiry on the free version. Nothing leaves your network.
| Severity | Issue | Fix | Log | Count |
|---|---|---|---|---|
| Error | App installed but detection method did not find it (0x87D00324) | Yes | AppEnforce.log | 3 |
| Error | WSUS group policy conflicts with Configuration Manager | Yes | WUAHandler.log | 12 |
| Error | Installer returned an exit code that isn't mapped on the Win32 app | Yes | AppWorkload.log | 2 |
| Warning | App retry held by the 24-hour GRS window | Yes | AppWorkload.log | 6 |
Patches, apps, security baselines and compliance all reach the device through the ConfigMgr client or the Intune Management Extension. When that agent is unhealthy, nothing arrives, and the device often still looks fine in the console.
Most teams only look at client health after a failed rollout or a vulnerability report. By then the answer is buried in more than 150 log files, and a tech has to know which one to open.
Endpoint Log Monitor reads those logs for you. It groups repeated errors, hides known harmless noise and matches each problem to steps your team can follow.
09:31:07 Prepared command line: "setup.exe" /S 09:31:52 Process 6140 terminated with exitcode: 0 09:31:52 Looking for exit code 0 in exit codes table... 09:31:53 +++ Discovered application [AppDT_Id: ScopeId_…/DeploymentType_…] 09:31:53 Method EnforceApp failed (0x87d00324). 09:31:53 CAppEnforcer::Enforce failed (0x87d00324)↓ Endpoint Log Monitor
Repeated errors collapse into one line with a count and first and last seen times. Known issues are listed first.
Why it happens, what to check and which log to open, for dozens of common ConfigMgr and Intune failures.
Type a computer name to read its logs over the admin share. No agent to install on the endpoint.
Harmless messages are filtered out of the box. Right-click anything else to hide it for the whole team.
Trigger policy, app evaluation or update scans, repair the client, restart services and sync Intune.
Export the action items and fixes as an HTML report or CSV to attach to a ticket or send to another team.
Add a list of computers and scan them together. Each row shows a color, the top issue and the counts. Double-click one to open it.
Save a snapshot before a fix, scan again after, and export an evidence report that shows what is resolved, still happening or new. Copy a ticket summary in one click.
Search by date and time, with several words, exact phrases, exclusions or regex, and pick which logs to search.
It reads CMTrace-format, legacy SMS and plain-text logs. Refreshes only read the new lines, so auto-refresh stays fast on busy clients.
C:\Windows\CCM\LogsAppEnforce, CAS, LocationServices, PolicyAgent, WUAHandler and every other client logC:\Windows\ccmsetup\LogsClient installs and upgradesC:\ProgramData\Microsoft\IntuneManagementExtension\LogsWin32 apps, scripts, RemediationsDeviceManagement-Enterprise-Diagnostics-Provider/AdminEnrollment and configuration profile (CSP) resultsAAD/Operational · User Device Registration/Admin · ModernDeployment-Diagnostics-ProviderSign-in and token problems, Entra join and registration, AutopilotWindowsUpdateClient/Operational · AppXDeployment-Server/OperationalWindows Update and Store or MSIX app install errorsC:\WindowsAzure\Logs · AzureConnectedMachineAgent\LogAzure VM agent and extensions, Azure Arc agentAny folder you add, plus PSADT's C:\Windows\Logs\SoftwareCustom paths work on this computer and on remote onesThe app includes an error code lookup that understands hex, signed decimal and MSI exit codes. Here is a small sample of it.
A single Windows app with nothing else to install. Run it portable or deploy it with ConfigMgr or Intune.
It reads log files and event logs. Nothing is sent to us or anyone else.
Add fixes for your environment in one shared file. Upgrades never overwrite it.
The free version never expires. Pro is $500 per technician per year, with team and enterprise pricing.
The free version scans ConfigMgr, Intune and MDM logs on any computer you can reach, with troubleshooting steps for each error. Pro adds tools for deeper insight and faster, clearer troubleshooting and analysis: the multi-device view, evidence reports, advanced search, more log sources and Connect as.