Files
claudetools/verify-and-test-sync.ps1
Mike Swanson ba2ed379f8 feat: Add AD2 WinRM automation and modernize sync infrastructure
Comprehensive infrastructure improvements for AD2 (Domain Controller) remote
management and NAS sync system modernization.

## AD2 Remote Access Enhancements

**WinRM Configuration:**
- Enabled PowerShell Remoting (port 5985) with full logging
- Configured TrustedHosts for LAN/VPN access (172.16.*, 192.168.*, 10.*)
- Created read-only service account (ClaudeTools-ReadOnly) for safe automation
- Set up transcript logging for all remote sessions
- Deployed 6 automation scripts to C:\ClaudeTools\Scripts\ (AD user/computer
  reports, GPO status, replication health, log rotation)

**SSH Access:**
- Installed OpenSSH Server (v10.0p2)
- Generated ED25519 key for passwordless authentication
- Configured SSH key authentication for sysadmin account

**Benefits:**
- Efficient remote operations via persistent WinRM sessions (vs individual SSH commands)
- Secure read-only access for queries (no admin rights needed)
- Comprehensive audit trail of all remote operations

## Sync System Modernization (AD2 <-> NAS)

**Replaced PuTTY with OpenSSH:**
- Migrated from pscp.exe/plink.exe to native OpenSSH scp/ssh tools
- Added verbose logging (-v flag) for detailed error diagnostics
- Implemented auto host-key acceptance (StrictHostKeyChecking=accept-new)
- Enhanced error logging to capture actual SCP failure reasons

**Problem Solved:**
- Original sync errors (738 failures) had no root cause details
- PuTTY's batch mode silently failed without error messages
- New OpenSSH implementation logs full error output to sync-from-nas.log

**Scripts Created:**
- setup-openssh-sync.ps1: SSH key generation and NAS configuration
- check-openssh-client.ps1: Verify OpenSSH availability
- restore-and-fix-sync.ps1: Update Sync-FromNAS.ps1 to use OpenSSH
- investigate-sync-errors.ps1: Analyze sync failures with context
- test-winrm.ps1: WinRM connection testing (admin + service accounts)
- demo-ad2-automation.ps1: WinRM automation examples (AD stats, sync status)

## DOS Batch File Line Ending Fixes

**Problem:** All DOS batch files had Unix (LF) line endings instead of DOS (CRLF),
causing parsing errors on DOS 6.22 machines.

**Fixed:**
- Local: 13 batch files converted to CRLF
- Remote (AD2): 492 batch files scanned, 10 converted to CRLF
- Affected files: DEPLOY.BAT, NWTOC.BAT, CTONW.BAT, UPDATE.BAT, STAGE.BAT,
  CHECKUPD.BAT, REBOOT.BAT, and station-specific batch files

**Scripts Created:**
- check-dos-line-endings.ps1: Scan and detect LF vs CRLF
- convert-to-dos.ps1: Bulk conversion to DOS format
- fix-ad2-dos-files.ps1: Remote conversion via WinRM

## Credentials & Documentation Updates

**credentials.md additions:**
- Peaceful Spirit VPN configuration (L2TP/IPSec)
- AD2 WinRM/SSH access details (both admin and service accounts)
- SSH keys and known_hosts configuration
- Complete WinRM connection examples

**Files Modified:**
- credentials.md: +91 lines (VPN, AD2 automation access)
- CTONW.BAT, NWTOC.BAT, REBOOT.BAT, STAGE.BAT: Line ending fixes
- Infrastructure configs: vpn-connect.bat, vpn-disconnect.bat (CRLF)

## Test Results

**WinRM Automation (demo-ad2-automation.ps1):**
- Retrieved 178 AD users (156 enabled, 22 disabled, 40 active)
- Retrieved 67 AD computers (67 Windows, 6 servers, 53 active)
- Checked Dataforth sync status (2,249 files pushed, 738 errors logged)
- All operations completed in single remote session (efficient!)

**Sync System:**
- OpenSSH tools confirmed available on AD2
- Backup created: Sync-FromNAS.ps1.backup-20260119-140918
- Script updated with error logging and verbose output
- Next sync run will reveal actual error causes

## Technical Decisions

1. **WinRM over SSH:** More efficient for PowerShell operations, better error
   handling, native Windows integration
2. **Service Account:** Follows least-privilege principle, safer for automated
   queries, easier audit trail
3. **OpenSSH over PuTTY:** Modern, maintained, native Windows tool, better error
   reporting, supports key authentication without external tools
4. **Verbose Logging:** Critical for debugging 738 sync errors - now we'll see
   actual SCP failure reasons (permissions, paths, network issues)

## Next Steps

1. Monitor next sync run (every 15 minutes) for detailed error messages
2. Analyze SCP error output to identify root cause of 738 failures
3. Implement SSH key authentication for NAS (passwordless)
4. Consider SFTP batch mode for more reliable transfers

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-19 14:28:24 -07:00

81 lines
3.1 KiB
PowerShell

# Verify the sync script update and run a test sync
$password = ConvertTo-SecureString "Paper123!@#" -AsPlainText -Force
$cred = New-Object System.Management.Automation.PSCredential("INTRANET\sysadmin", $password)
Write-Host "=== Verifying Sync Script Update ===" -ForegroundColor Cyan
Write-Host ""
Invoke-Command -ComputerName 192.168.0.6 -Credential $cred -ScriptBlock {
$scriptPath = "C:\Shares\test\scripts\Sync-FromNAS.ps1"
Write-Host "[1] Verifying OpenSSH tool paths" -ForegroundColor Yellow
Write-Host "=" * 80 -ForegroundColor Gray
$content = Get-Content $scriptPath -Raw
if ($content -match '\$SCP\s*=\s*"[^"]*OpenSSH[^"]*scp\.exe"') {
Write-Host "[OK] SCP path updated to OpenSSH" -ForegroundColor Green
} else {
Write-Host "[ERROR] SCP path not found or incorrect" -ForegroundColor Red
}
if ($content -match '\$SSH\s*=\s*"[^"]*OpenSSH[^"]*ssh\.exe"') {
Write-Host "[OK] SSH path updated to OpenSSH" -ForegroundColor Green
} else {
Write-Host "[ERROR] SSH path not found or incorrect" -ForegroundColor Red
}
Write-Host ""
Write-Host "[2] Verifying Copy-ToNAS function" -ForegroundColor Yellow
Write-Host "=" * 80 -ForegroundColor Gray
if ($content -match "SCP PUSH ERROR") {
Write-Host "[OK] Copy-ToNAS has error logging" -ForegroundColor Green
} else {
Write-Host "[WARNING] Error logging may not be present" -ForegroundColor Yellow
}
if ($content -match "StrictHostKeyChecking=accept-new") {
Write-Host "[OK] Auto host key acceptance configured" -ForegroundColor Green
} else {
Write-Host "[WARNING] Host key acceptance may not be configured" -ForegroundColor Yellow
}
Write-Host ""
Write-Host "[3] Running manual sync test" -ForegroundColor Yellow
Write-Host "=" * 80 -ForegroundColor Gray
Write-Host "Triggering a manual sync run to test OpenSSH and capture errors..." -ForegroundColor White
Write-Host ""
# Run the sync script
try {
& powershell.exe -ExecutionPolicy Bypass -File $scriptPath *>&1 | Tee-Object -Variable syncOutput
Write-Host ""
Write-Host "[4] Checking sync log for detailed errors" -ForegroundColor Yellow
Write-Host "=" * 80 -ForegroundColor Gray
$logFile = "C:\Shares\test\scripts\sync-from-nas.log"
$recentErrors = Get-Content $logFile -Tail 30 | Select-String -Pattern "SCP.*ERROR|ERROR.*push|ERROR.*pull"
if ($recentErrors) {
Write-Host "Found detailed error messages:" -ForegroundColor Cyan
$recentErrors | ForEach-Object {
Write-Host " $_" -ForegroundColor Red
}
} else {
Write-Host "No detailed SCP errors found in recent log" -ForegroundColor Yellow
Write-Host "Showing last 15 lines of log:" -ForegroundColor Gray
Get-Content $logFile -Tail 15 | ForEach-Object {
Write-Host " $_" -ForegroundColor Gray
}
}
} catch {
Write-Host "[ERROR] Sync script failed to run: $($_.Exception.Message)" -ForegroundColor Red
}
}
Write-Host ""
Write-Host "=== Test Complete ===" -ForegroundColor Cyan