Howard's personal MSP client documentation folder imported into shared
ClaudeTools repo via /import command. Scope:
Clients (structured MSP docs under clients/<name>/docs/):
- anaise (NEW) - 13 files
- cascades-tucson - 47 files merged (existing had only reports/)
- dataforth - 18 files merged (alongside incident reports)
- instrumental-music-center - 14 files merged
- khalsa (NEW) - 22 files, multi-site (camden, river)
- kittle (NEW) - 16 files incl. fix-pdf-preview, gpo-intranet-zone
- lens-auto-brokerage (NEW) - 3 files (name matches SOPS vault)
- _client_template - 13-file scaffold for new clients
MSP tooling (projects/msp-tools/):
- msp-audit-scripts/ - server_audit.ps1, workstation_audit.ps1, README
- utilities/ - clean_printer_ports, win11_upgrade,
screenconnect-toolbox-commands
Credential handling:
- Extracted 1 inline password (Anaise DESKTOP-O8GF4SD / david)
to SOPS vault: clients/anaise/desktop-o8gf4sd.sops.yaml
- Redacted overview.md with vault reference pattern
- Scanned all 160 files for keys/tokens/connection strings -
no other credentials found
Skipped:
- Cascades/.claude/settings.local.json (per-machine config)
- Source-root CLAUDE.md (personal, claudetools has its own)
- scripts/server_audit.ps1 and workstation_audit.ps1 at source root
(identical duplicates of msp-audit-scripts versions)
Memory updates:
- reference_client_docs_structure.md (layout, conventions, active list)
- reference_msp_audit_scripts.md (locations, ScreenConnect 80-char rule)
Session log: session-logs/2026-04-16-howard-client-docs-import.md
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.1 KiB
2.1 KiB
Step 6: Synology Transition (~2 hours, remote)
6.1 — Verify drive mappings
On each machine via ScreenConnect:
net use
Confirm mapped drives (S:, department drives) point to \\CS-SERVER\... and files are accessible.
Do not proceed until all users have working drive mappings.
6.2 — Remove Synology Drive Client
On each machine via ScreenConnect:
- Right-click Synology Drive Client in system tray → Quit
- Settings → Apps → Synology Drive Client → Uninstall
- Verify user can access files via mapped drives (not Synology)
Or via PowerShell:
# Find and uninstall Synology Drive Client
$synology = Get-WmiObject Win32_Product | Where-Object { $_.Name -like "*Synology Drive*" }
if ($synology) {
$synology.Uninstall()
Write-Host "Synology Drive Client uninstalled"
} else {
Write-Host "Synology Drive Client not found"
}
6.3 — Disable Synology Drive Server sync
- Log into Synology DSM at
https://192.168.0.120:5001 - Open Synology Drive Admin Console
- Disable all sync tasks
- Optionally disable Synology Drive Server package (don't uninstall yet)
6.4 — Repurpose Synology as backup-only
- Verify Active Backup for Business is backing up CS-SERVER nightly (set up in Step 1)
- Configure offsite backup:
- Install Hyper Backup from Package Center
- Create task → Backblaze B2 or Wasabi (~$3/mo for offsite copy)
- Schedule: daily after ABB completes (e.g., 5:00 AM)
- Retention: 30 daily + 12 monthly
6.5 — Archive SynologyDrive folder
Run scripts/phase4-archive-synology.ps1 on CS-SERVER:
Rename-Item "D:\Shares\SynologyDrive" "D:\Shares\_SynologyDrive_ARCHIVE_DeleteAfter30Days"
Do NOT delete immediately — keep 30 days as safety net. Set a calendar reminder to delete after 30 days.
Rollback
- Rename archive folder back:
Rename-Item "D:\Shares\_SynologyDrive_ARCHIVE_DeleteAfter30Days" "D:\Shares\SynologyDrive" - Re-enable Synology Drive Server sync
- Reinstall Synology Drive Client on workstations