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

sync: auto-sync from HOWARD-HOME at 2026-07-03 17:00:12

Browse Source 
Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-07-03 17:00:12
This commit is contained in:
Howard Enos
2026-07-03 17:00:47 -07:00
parent 78f794a924
commit e0e3dd0d82
9 changed files with 478 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
.claude/memory/project_av_migration_bitdefender_to_edr.md Normal file
View File

@@ -0,0 +1,24 @@
---
name: project_av_migration_bitdefender_to_edr
description: AV strategy — migrate all clients from Bitdefender to Datto EDR, except Glaztech and Dataforth
metadata:
type: project
---
Standing AV direction (set by Howard 2026-07-03): ACG is moving endpoint AV/security
from **Bitdefender GravityZone -> Datto EDR** for **all clients EXCEPT Glaztech Industries
and Dataforth Corp** (those two stay on Bitdefender / handled separately).
**Why:** consolidate on Datto EDR as the security plane; Bitdefender is being retired
fleet-wide (Glaztech + Dataforth are the two exceptions — both have large established
Bitdefender footprints: Glaztech ~242 endpoints, Dataforth managed separately).
**How to apply:** whenever setting up or reconciling a client's endpoints (e.g. the
GPS->GuruRMM coverage audit), the target end-state per machine is: GuruRMM agent +
Datto EDR agent, and Bitdefender **removed**. Do NOT deploy new Bitdefender coverage.
Use existing Bitdefender inventory only as a discovery source for which machines exist
(its company names carry the Syncro CID `_NNNNN`, handy for mapping). Deploy Datto EDR
via `[[datto-edr]]` (create-group -> mint-key -> deploy-cmd, pushed through `/rmm`).
Related: GPS->RMM audit tracker `projects/gps-rmm-audit/tracker.md`. Exceptions = Glaztech +
Dataforth (leave their existing AV alone; do not migrate them to EDR in this effort).