How to Audit and Remove Stale Endpoints from Your Caisey Console

Every MSP knows the feeling: you log into your remote support console and see dozens of devices you haven’t touched in months. Some belong to former clients, others are test VMs that were decommissioned years ago, and a few are duplicates from re-enrollments. These ghost devices clutter your view, slow down searches, and—worst of all—create a security surface if they ever reconnect unnoticed.

Caisey gives you a clean way to audit and remove stale endpoints directly from the console. No API scripting required, no manual database queries. Here’s how to keep your device list lean and accurate.

The Problem with Ghost Devices

When endpoints go dark, they don’t always disappear. A machine that was reimaged or retired might still show as “enrolled” in your remote support tool. Over time, these phantom entries pile up:

• Confusion during dispatch – A technician sees a device listed but can’t connect, wasting time.
• Security risk – An old, unpatched device could reconnect unexpectedly and be used as a foothold.
• Billing and reporting errors – Stale endpoints inflate license counts and skew usage reports.

Traditional RMMs often require custom scripts or manual API calls to find and remove these devices. Caisey builds the audit directly into the interface.

How Caisey Surfaces Stale Endpoints

Caisey’s device dashboard shows every enrolled endpoint with key metadata columns that make stale detection obvious:

| Column | What it tells you | |--------|-------------------| | Device Name | Hostname or alias | | Last Connected | Timestamp of the most recent Caisey session or heartbeat | | Client Group | The client or site the device belongs to | | Runtime Version | Version of the Caisey AI runtime installed | | Enrollment Status | “Active” or “Disconnected” (based on last check-in) |

You can sort or filter by Last Connected to see devices that haven’t checked in for 30, 60, or 90+ days. Caisey also flags endpoints where the runtime version is several releases behind—another sign the machine may be offline or abandoned.

Step-by-Step: Auditing and Removing Stale Endpoints

Here’s the workflow we recommend for a quarterly cleanup:

1. Open the Devices tab in the Caisey console.
2. Filter by Last Connected – Set a threshold (e.g., > 30 days ago).
3. Review the list – Check the Client Group column to confirm the device belongs to an active client.
4. Verify with the client – If you’re unsure, reach out to the client contact. For devices in critical groups (e.g., “Production Servers”), Caisey requires an approval step before removal.
5. Select the device(s) and click Remove. Caisey will prompt you to confirm and, if the device is in a protected group, request an approval from an admin.
6. Confirm removal – The device is immediately de-enrolled. The Caisey runtime on that machine will stop attempting to connect.

That’s it. No need to SSH into a server or write a PowerShell script. The entire process is point-and-click.

What Happens After Removal?

• The device disappears from your active device list.
• All pending sessions and approval requests for that endpoint are cancelled.
• The runtime on the device will show a “decommissioned” state in its local logs.

If the same machine is ever re-enrolled (e.g., after a fresh OS install), it will appear as a new device entry. The old entry is gone for good.

Audit Trail and Accountability

Every removal is recorded in Caisey’s IT support audit trail. The log shows:

• Who initiated the removal
• Which device was removed
• Timestamp of the action
• Any approval that was required and granted

This is critical for MSPs that need to demonstrate compliance (e.g., SOC 2, HIPAA) or simply want to track changes to the endpoint inventory. You can export the audit log at any time.

Comparison: Caisey vs. Traditional RMM Cleanup

Let’s look at how Caisey stacks up against a common tool like ScreenConnect (now ConnectWise Control):

| Feature | Caisey | ScreenConnect / Traditional RMM | |---------|--------|----------------------------------| | Built-in stale device detection | Yes – sort/filter by last seen | No – relies on custom scripting or third-party add-ons | | Approval-based removal | Yes – for critical client groups | No – any admin can delete without oversight | | Audit log of removals | Yes – full trail with user and timestamp | Limited – may require separate logging | | Bulk removal | Yes – select multiple devices | Usually yes, but often via API | | Client group awareness | Yes – removal respects group permissions | Varies by tool |

Caisey’s approach reduces the friction of keeping your console tidy. You don’t need to build a custom cleanup script or remember to run a cron job.

Keep Your Console Lean

Ghost devices are a silent drain on MSP efficiency. With Caisey, you can audit and remove stale endpoints in minutes, not hours. The combination of clear metadata, approval workflows, and a permanent audit trail means your device list stays accurate and secure.

For more on managing endpoint enrollment and permissions, see our installation and connection guide and permissions and settings documentation.

Start your next quarterly cleanup today—your dispatchers will thank you.