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.0 KiB
2.0 KiB
DHCP Configuration
DHCP Server
- Server Name: ISP Router
- Server IP: 10.0.0.1
- Failover Partner: None
Note: The Windows Server DHCP role is installed on SERVER (10.0.0.5) but has zero scopes configured. All DHCP is handled by the ISP router.
Scopes
Scope - LAN (ISP Router)
- Subnet: 10.0.0.0/24
- Range Start: Unknown — need to check ISP router admin interface
- Range End: Unknown
- Subnet Mask: 255.255.255.0
- Default Gateway: 10.0.0.1
- DNS Servers: Unknown — critical to verify (should be 10.0.0.5 for AD)
- Lease Duration: Unknown
Reservations
No reservations documented. Need to check ISP router for any existing DHCP reservations.
| Device Name | MAC Address | IP Address | Scope | Notes |
|---|---|---|---|---|
| SERVER | — | 10.0.0.5 | LAN | DC — should be reserved or static |
| UniFi Switch | 0C:EA:14:8A:8D:7F | 10.0.0.122 | LAN | Should be reserved |
DHCP Relay
- Not applicable — single subnet, DHCP server on same segment
Issues
- DHCP on ISP router instead of server — Less control over DHCP options (DNS, NTP, lease times). Cannot manage reservations centrally via Windows tools. ISP router may hand out ISP DNS instead of the DC's DNS (10.0.0.5), which would break AD name resolution.
- Windows DHCP role installed but unused — Creates confusion. Either uninstall or migrate DHCP to the server.
Recommendations
- Migrate DHCP to Windows Server — Provides centralized management, AD-integrated DNS updates, DHCP reservations via PowerShell, and logging.
- Create reservations for: SERVER (10.0.0.5), UniFi switch (10.0.0.122), printers, and any other infrastructure.
- Set DNS option — Ensure DHCP hands out 10.0.0.5 as the primary DNS server.
TODO
- Log into ISP router and document DHCP scope, range, DNS settings, and any reservations
- Verify what DNS servers DHCP clients receive
- Plan DHCP migration from ISP router to Windows Server
- Create DHCP reservations for infrastructure devices