Introducing Eido 26.8: Your Intune Devices, Live

When a user reports that their laptop is slow, an application keeps crashing or something simply is not working, IT needs to know what is happening now, not what the device looked like hours ago.

Microsoft Intune provides essential management data, but its reporting intervals can leave engineers investigating yesterday’s version of a problem. By the time a ticket reaches the service desk, the CPU spike may have disappeared and the user may no longer be able to reproduce the issue.

Eido 2026.8 changes that with Live Device Intelligence.

The latest release gives IT teams a live view of their Intune-managed Windows devices, bringing current performance, historical behavior, detailed inventory, significant events and remote remediation tools together on one device page.

See what is happening right now

Live Device Intelligence captures performance data every three seconds and retains seven days of history.

Engineers can investigate CPU utilization, memory pressure, disk activity, network behaviorf, GPU utilization, running processes, Windows services, event logs, application crashes, Intune errors and overall device health.

This makes it possible to see what is happening now, and what was happening when the original problem began.

There is no need to wait for another Intune sync, ask the user to reproduce an intermittent issue or piece together evidence from multiple tools.

Turn troubleshooting into evidence

A current snapshot only shows what a device looks like at one moment. Eido provides the history needed to understand how it reached that state.

More than 3,000 Windows performance counters can be graphed using data sampled every three seconds. Engineers can identify CPU spikes, sustained memory pressure, abnormal disk activity, network issues and changes in GPU utilization.

Instead of guessing why a device became slow, the service desk can inspect the relevant period. Instead of assuming an application crashed, engineers can find the corresponding event.

Troubleshooting becomes evidence-based rather than dependent on guesswork.

See the complete device

Effective troubleshooting also depends on understanding what is installed, configured and running on a machine.

Eido collects more than 350 inventory data points from each device, providing visibility across hardware, software, security, networking and operating-system health.

From the device page, engineers can inspect:

• Installed applications, runtimes and browser extensions
• Battery, memory, disk and system information
• Certificates, Defender, firewall and Secure Boot status
• Local users, profiles and startup items
• Network adapters, Wi-Fi, proxy and VPN-related settings
• Intune, MDM, Office, OneDrive and operating-system health
• Windows 11 readiness, Windows features and WSL status

This reduces the need to jump between portals, scripts and specialist utilities simply to understand the current state of a device.

Open the device. Get the answer.

Investigate what happened before the ticket arrived

Intermittent problems are often the hardest to diagnose. Everything may appear normal by the time an engineer starts investigating, even though the user experienced a genuine failure.

Eido records important events as they occur, including Blue Screens of Death, unexpected shutdowns, application crashes and hangs, installation failures, Intune and MDM errors, and Eido Client logs.

This history provides evidence for problems that might otherwise be difficult to reproduce or diagnose.

Diagnose and remediate from one place

Visibility is only half of the troubleshooting process. Once an engineer identifies a problem, they need a practical way to resolve it.

Eido brings ten remote troubleshooting and remediation tools directly into the device page:

• Intune Doctor diagnoses MDM enrollment health, displays recent errors and triggers an on-demand Intune resync.
• Process Explorer and Services let engineers inspect processes and control Windows services remotely.
• Registry Explorer and File Explorer provide controlled access to registry keys, drives and folders.
• Print Queue and Logged-In Users help resolve print problems and manage active user sessions.
• Event Viewer and Network Tools support remote log analysis, ping, traceroute, DNS lookups and connection inspection.
• AI Diagnostics runs pre-approved and verified diagnostic or remediation scripts with individual access controls.

Together, these tools allow engineers to move from detection to diagnosis and remediation without repeatedly switching between systems.

From “something is wrong” to resolution

Live Device Intelligence changes the troubleshooting workflow for Intune-managed Windows devices.

Instead of reconstructing a problem across multiple tools, IT teams can access device data, performance history, inventory, events and remediation controls in one place.

The conversation changes from:

“Something is wrong with this device.”

To:

“This is what happened, this is what is happening now and this is how we are going to fix it.”

The result is fewer guesses, fewer follow-up calls, fewer requests for users to reproduce problems and a faster path to resolution.

More improvements in Eido 26.8

The release also includes:

• Redesigned Trends V2 charts with clearer health-band visuals
• Refreshed admin pages and device detail views
• Improved dark mode support
• Faster, more reliable inventory synchronisation
• Layout and readability improvements
• Fixes for enrollment, certificate handling and query filtering

Bring your Intune estate to life

Intune tells you what happened. Eido shows you what is happening.

With real-time performance data, seven days of history, detailed inventory, event evidence and remote remediation tools, Eido 2026.8 gives IT teams the context they need to resolve device issues with confidence.

Your Intune estate just went live.

See Live Device Intelligence in action

Want to improve visibility and troubleshooting across your Intune-managed devices?

Request a personalised Eido demo and explore Live Device Intelligence with our team.

‍