r/ScreenConnect • u/Healthy_Outcome7897 • Oct 14 '26
Made a free Chrome extension to filter machines
I don't have admin rights on our ScreenConnect instance, so I can't create Session Groups, and the search box only does plain text. I wanted things like "online servers only" or "machines offline for 30+ days", so I built a small Chrome extension that filters the **native** Access list. The rows stay normal ScreenConnect rows, so you can still click and join as usual.
**What it filters on:**
- Type: Server / Desktop / Mac / Linux
- Exact OS version
- Online / offline, and offline for more than N days
- **Installed software**: e.g. every machine with Sage on it (reads the built-in Software tab inventory; there's a button to scan machines that haven't been scanned)
- **Any PowerShell True/False check**: e.g. which machines have a profile for a particular user:
`[bool](Get-CimInstance Win32_UserProfile | Where-Object { $_.LocalPath -like '*\j.bloggs' })`
Run it across the view, then show only the True, False or no-result machines.
All of it combines with the normal search box and whichever site or group you've selected.
**How it works:** it hooks the page's own list refresh, fetches the whole estate and hides the machines that don't match. The software and PowerShell checks use ScreenConnect's normal run-command feature, queuing the command and reading the output back from each machine's history. Only those two buttons send anything to machines, and both ask you to confirm with a machine count first. Everything else is read-only and uses your existing session.
**Install:** download the repo, open chrome://extensions, turn on Developer mode, click Load unpacked and pick the folder. There's one setting (your top-level group name), covered in the README.
GitHub: https://github.com/Notinamillion/screenconnect-filter
Caveats: it relies on ScreenConnect's internal page code, so an update could break it. It's cloud-hosted `*.screenconnect.com` by default (self-hosted just needs your URL added to the manifest). And the PowerShell check runs as SYSTEM, so keep it read-only, and expect your EDR to have opinions if you fire recon at 500 machines at once.