How to Compare System State Across Devices in Caisey to Identify Outliers

When you support a fleet of endpoints for a client, the hardest problems aren't the ones that scream for attention. It's the quiet outlier—the one machine that missed a security patch, the device running an outdated driver, or the endpoint that's slowly drifting from the baseline. By the time that outlier causes a user-facing issue, you're already in reactive mode. Caisey's multi-device view changes that. Instead of checking machines one by one, you can run the same diagnostic across the entire fleet, compare the results side by side, and spot the device that doesn't match. Here's how to put that into practice.

Why Fleet-Wide Comparison Matters

A single device issue is rarely an isolated event. If one machine is missing a critical update, chances are others are too—or that machine is the canary in the coal mine for a deployment failure. By comparing system state across all enrolled endpoints, you can identify patterns and anomalies before they become user-facing problems. This proactive approach cuts troubleshooting time because you're not waiting for a ticket; you're finding the issue while it's still small.

Caisey is built for this. The cloud UI gives you a unified view of every enrolled device, and because each session preserves machine context and history, you can compare not just the current state but also how devices have changed over time. That's the difference between a snapshot and a story.

Running a Bulk Diagnostic in Caisey

Start by selecting the group of devices you want to compare. In Caisey, you can organize endpoints into client groups, so you might pick a specific client's fleet or a subset like "all laptops in the sales department." Once you've selected your group, you can run a bulk command across all of them simultaneously.

For example, let's say you want to check which devices are missing the latest security patches. You could run a command like Get-HotFix on Windows or softwareupdate --history on macOS. Caisey executes that command on every selected endpoint and collects the output in one place. No need to remote into each machine individually.

Sorting and Filtering Results to Spot Outliers

Once the bulk command finishes, you'll see a table of results—one row per device, with the command output in a column. This is where the comparison starts. You can sort by any column to bring the outliers to the top. For instance, if you're checking patch levels, sort by the date of the last installed update. The device with the oldest date is your outlier.

Here's a simplified example of what that table might look like:

| Device | Last Patch Date | OS Version | Status | |--------|----------------|------------|--------| | LAPTOP-01 | 2025-03-15 | Win11 23H2 | OK | | LAPTOP-02 | 2025-03-15 | Win11 23H2 | OK | | DESKTOP-03 | 2025-01-22 | Win10 22H2 | Outlier | | SERVER-01 | 2025-03-14 | Server 2022 | OK |

In this case, DESKTOP-03 is clearly behind. But you can also filter for other criteria—like OS version mismatches, disk space below a threshold, or specific error codes. Caisey's interface lets you filter the results dynamically, so you can narrow down to exactly the devices that need attention.

Drilling Into a Device's Session History

Identifying an outlier is only the first step. The real value comes from understanding why that device is different. Caisey preserves session history for every endpoint, so you can click into DESKTOP-03's record and see what's been happening. Was there a failed update attempt? Did the user decline a reboot? Did a previous troubleshooting session leave something in a weird state?

For example, you might see that DESKTOP-03 had a session last week where an update was attempted but failed due to a disk space error. That context tells you the fix isn't just "install the patch"—it's "free up disk space first." Without session history, you'd be troubleshooting blind.

This drill-down capability is part of Caisey's remote-troubleshooting approach. You're not just looking at a static snapshot; you're seeing the full narrative of that device's interactions.

Using Approvals and Audit Trails for Accountability

When you decide to take action on an outlier—like pushing a patch or running a repair script—Caisey requires explicit approval from the user or an admin, depending on your settings. This isn't just a safety feature; it's also a way to keep a clean record. Every command, approval, and result is logged in the session history, which you can later share with the client as a transparent report.

For MSPs, this audit trail is gold. It shows the client exactly what you found and what you did about it. And because Caisey's approval-based remote support is built into the workflow, you never have to worry about making changes without consent.

Best Practices for Proactive Troubleshooting

Fleet-wide comparison isn't a one-time activity. To get the most out of it, make it a regular habit. Here's a checklist to incorporate into your routine:

• Schedule recurring diagnostics for critical checks like patch levels, disk space, and service status.
• Set a baseline for what "normal" looks like for each client group, so you can spot deviations faster.
• Review session history for any device that shows up as an outlier more than once—it might indicate a recurring issue.
• Use client groups to compare similar devices (e.g., all Windows 11 laptops) rather than mixing different OS versions.
• Document your findings in the transcript share feature, so the client can see the evidence.

By following these practices, you turn Caisey from a reactive tool into a proactive monitoring platform.

Conclusion

Comparing system state across devices in Caisey is a simple yet powerful way to identify outliers before they become problems. Running bulk diagnostics, sorting results, and drilling into session history gives you the full picture. And with approval-based actions and a complete audit trail, you can act confidently and keep your clients informed. Start using Caisey's multi-device view today, and you'll spend less time firefighting and more time preventing fires.

For more on how Caisey can streamline your MSP workflow, check out our MSP device troubleshooting guide.