azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from HOWARD-HOME at 2026-07-15 13:59:09

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-07-15 13:59:09
This commit is contained in:
Howard Enos
2026-07-15 13:59:40 -07:00
parent 3bab0de9c3
commit 4e3cf71851
12 changed files with 210 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
projects/gps-rmm-audit/client-contact-list-2026-07-15.md Normal file
View File

@@ -0,0 +1,35 @@
# MSP360 Stale-Backup Client Contact List — 2026-07-15
Machines whose MSP360 backups stopped because the endpoint went silent (last plan run
succeeded, then no further check-ins). None are remotely reachable — not enrolled in
GuruRMM, or enrolled but offline. Each needs a client conversation: is the machine still
in service? If yes → power on / reconnect / reinstall agent. If retired → remove from
MSP360 so we stop carrying and billing a dead endpoint.
| Priority | Client | Machine | Last good backup | Silent | Ask the client |
|---|---|---|---|---|---|
| **HIGH** | Tucson Safety and Medical | TSAM-SERVER | 2026-02-25 | 140d | A SERVER with no backup for 4.5 months. Is it still running? If yes, agent is dead — needs on-site/remote session to fix. If replaced, what took over its data? |
| **HIGH** | Glaztech Industries | GTI-INV-VMHOST | Image 2025-10-26, Hyper-V 2025-10-28 | ~260d | VM host was pushing 60+ GB images, silent since Oct 2025. Retired? Replaced? If in service, its VMs have no image/Hyper-V protection. |
| MED | Len's Auto | DESKTOP-BMBTQLI | Image plan NEVER ran | — | Plan was created (next start was 2026-05-03) but never executed once. Does this desktop still exist? Not in RMM. |
| — | Len's Auto | ~~LAB-SVR~~ RETIRED | — | — | Replaced by LAB-SERVER (per Howard). Cleanup item, not a contact item: remove stale LAB-SVR plans/user from MSP360 and the dead agent record from GuruRMM. Note: no LAB-SERVER backup plans appear in MSP360 monitoring — confirm where the replacement server backs up. |
| MED | Desert RV | DESKTOP-9T0UAON | Local Backup 2026-05-07 | 69d | Off/disconnected; consistency check stuck "Running". Still in service? |
| LOW | Tedards | DESKTOP-SUFJR0J | 2025-07-12 (51 MB files) | 368d | Silent a full year — almost certainly retired. Confirm, then remove from MSP360 + purge/retain B2 data per retention policy. |
## Related (tracked separately, same effort)
- **Tucson Coin / Seth-PC** — backs up daily but plan references a phantom E:\ drive that
does not exist on the machine (1 SSD, CD at D:, printer at F:). Decision needed:
remove E:\ from plan config vs. reconnect a drive. Machine currently offline; probe queued.
- **ACG-Internal / NEPTUNE** — Exchange backup fixed 2026-07-15 (service account
ACG\svc-msp360 with Exchange RBAC); verification run in progress.
- **Air Pros** — user diegobuilder300@gmail.com DISABLED in MSP360 2026-07-15 and flagged
for removal. 418.7 GB still stored in B2 (MSPBackups20200311 destination) — final
delete-user (which purges the data) awaits explicit direction.
## Notes
- Status source: MSP360 monitoring feed (authoritative). All six rows above show
Status=Success on their last run — the plans are fine, the machines went away.
- Removal from MSP360 = `delete-user`/company cleanup via the msp360 skill (gated), after
the client confirms. B2 data retention is a per-client decision — do not purge without
explicit direction.