azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
50 Commits 1 Branch 0 Tags
29e2df60c50ab9117d735ce3d47599311aea2398
Commit Graph

3 Commits

Author SHA1 Message Date
Mike Swanson
29e2df60c5 feat: Complete DOS machine deployment verification and AD2-NAS sync infrastructure 
This checkpoint establishes verified deployment infrastructure for the Dataforth
DOS Update System with proper file synchronization and documentation.

## Key Changes

### TS-4R Backup and Analysis
- Backed up complete TS-4R machine to D:\ClaudeTools\backups\TS-4R\
- Analyzed MENUX.EXE startup menu system (758-line QuickBasic program)
- Documented complete startup sequence: AUTOEXEC.BAT → STARTNET.BAT → MENUX.EXE
- Found MENUX.BAS source code (Feb 2008 version) from KEPCO ABC software archive

### AD2-NAS Sync Infrastructure Fixes
- Created junction: COMMON → _COMMON (single source of truth for software updates)
- Verified bidirectional sync logic prevents data backflow:
  * Test data: DOS → NAS → AD2 → Database (one-way, deleted from NAS)
  * Program updates: AD2 → NAS → DOS (one-way, files remain on AD2)
- Manually deployed correct BAT file versions to NAS after sync connection issues
- Verified all 9 BAT files deployed correctly (5.1KB-8.8KB each)

### Deployment Scripts Created
- check-junction.ps1: Verify COMMON/\_COMMON junction status
- compare-common-folders.ps1: Compare folder contents
- deploy-correct-bat-files.ps1: Deploy BAT files from local to AD2
- fix-common-junction.ps1: Create COMMON → _COMMON junction
- verify-bat-deployment.ps1: Verify file versions on AD2
- manual-push-to-nas.sh: Manual BAT file deployment to NAS
- read-sync-script.ps1: Read Sync-FromNAS.ps1 from AD2
- search-menux-ad2.ps1: Search for MENUX source files

### Documentation Updates
- Updated all deployment guides with MENUX startup sequence
- Added startup flow to credentials.md and session logs
- Documented junction requirement for COMMON/\_COMMON
- Added data flow verification confirming unidirectional sync

## Technical Details

**Files Deployed to NAS (2026-01-20 09:01-09:02):**
- UPDATE.BAT (5,181 bytes) - Machine backup utility
- DEPLOY.BAT (5,579 bytes) - One-time deployment installer
- NWTOC.BAT (6,305 bytes) - Network to Computer updates
- CTONW.BAT (7,831 bytes) - Computer to Network uploads
- CTONWTXT.BAT (1,504 bytes) - Text file version
- CHECKUPD.BAT (6,495 bytes) - Check for updates
- STAGE.BAT (8,794 bytes) - Stage system files
- REBOOT.BAT (5,099 bytes) - Apply staged updates
- AUTOEXEC.BAT (2,211 bytes) - DOS startup configuration

**Sync Logic Verified:**
- PULL: /data/test/TS-*/LOGS/*.DAT copied to AD2, then deleted from NAS
- PUSH: C:\Shares\test\_COMMON\ProdSW\* copied to /data/test/COMMON/ProdSW/
- No reverse flow in either direction (test data never returns to DOS)

**Junction Created:**
- Target: C:\Shares\test\COMMON → C:\Shares\test\_COMMON
- Eliminates duplicate file maintenance
- Backup saved to C:\Shares\test\COMMON.backup

## Files Modified
- DOS_DEPLOYMENT_GUIDE.md: Added automatic startup sequence
- docs/DEPLOYMENT_GUIDE.md: Updated post-reboot expectations
- docs/ENGINEER_HOWTO_GUIDE.md: Added MENUX menu loading step
- credentials.md: Documented startup sequence and MENUX interface
- session-logs/2026-01-19-session.md: Added startup documentation

## Files Added
- 8 PowerShell deployment/verification scripts
- 3 HTML documentation exports
- TS-4R complete backup (not committed to git)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
 2026-01-20 16:03:00 -07:00
Mike Swanson
6b232c6102 docs: Session log update - VPN setup and DOS deployment completion 
Updated comprehensive session log documenting:

## DOS System Completion (Part 1)

**Major Milestones:**
- Located and documented AD2 sync mechanism (Sync-FromNAS.ps1)
- Deployed 6 DOS batch files to production (AD2)
- Created DEPLOY.BAT for one-time DOS machine setup
- Fixed CRITICAL test data routing in CTONW v1.2
- Added root-level file sync (UPDATE.BAT, DEPLOY.BAT to T:\)

**CTONW v1.2 Critical Fix:**
- Separated software distribution (ProdSW) from test data (LOGS)
- Problem: Test data uploaded to ProdSW, but sync expects LOGS folder
- Solution: Separate workflows - programs to ProdSW, DAT files to LOGS
- Subdirectory mapping: 8BDATA→8BLOG, DSCDATA→DSCLOG, etc.
- Result: Database import now functional

## VPN System Completion (Part 2)

**Peaceful Spirit VPN Setup:**
- Created Setup-PeacefulSpiritVPN.ps1 (ready-to-run with credentials)
- Created Create-PeacefulSpiritVPN.ps1 (interactive with parameters)
- Created VPN_QUICK_SETUP.md (comprehensive 350+ line guide)

**Configuration:**
- Server: 98.190.129.150 (L2TP/IPSec)
- Authentication: MS-CHAPv2 (fixed from PAP)
- Split Tunneling: Enabled (only 192.168.0.0/24 uses VPN)
- Network: UniFi router at CC location
- DNS: 192.168.0.2, Gateway: 192.168.0.10

**Authentication Fix:**
- Error: PAP doesn't support Required encryption with L2TP/IPSec
- Solution: Changed to MS-CHAPv2 authentication
- Updated all scripts and documentation

## Credentials Documented (UNREDACTED)

**Complete credentials for:**
- Peaceful Spirit VPN (PSK, username, password, network config)
- AD2 (192.168.0.6) - C$ admin share connection method
- D2TESTNAS (192.168.0.9) - SMB1 proxy
- Jupiter (172.16.3.20) - Gitea server
- GuruRMM (172.16.3.30) - Database and API
- Gitea SSH key (needs to be added to server)

## Documentation Updates

**Files Modified:**
- session-logs/2026-01-19-session.md: Complete rewrite with both DOS and VPN work
- credentials.md: Added VPN section with network topology
- VPN_QUICK_SETUP.md: Added split tunneling section, updated examples

**Session Statistics:**
- Duration: ~5 hours (DOS + VPN work)
- Files Created: 8 files
- Files Modified: 5 files
- Lines of Code: ~1,200 lines
- Credentials Documented: 10 systems/services
- Issues Resolved: 6 issues (4 DOS, 2 VPN)

## Technical Details Documented

**DOS 6.22 Limitations:**
- Never use: %COMPUTERNAME%, IF /I, %ERRORLEVEL%, FOR /F, &&, ||
- Always use: IF ERRORLEVEL n, GOTO labels, simple FOR loops

**VPN Authentication:**
- L2TP/IPSec with PSK requires MS-CHAPv2, not PAP
- Required encryption only works with MS-CHAPv2 or EAP

**Split Tunneling:**
- Only traffic to 192.168.0.0/24 routes through VPN
- All other traffic uses local internet connection
- Configured via Add-VpnConnectionRoute

**CTONW Data Routing:**
- ProdSW: Software distribution (bidirectional)
- LOGS: Test data for database import (unidirectional upload)
- Separation critical for database import workflow

## Sync Workflow Documented

**AD2 → NAS (Software): PUSH**
- Admin deposits in C:\Shares\test\COMMON\ProdSW\
- Sync-FromNAS.ps1 runs every 15 minutes
- PSCP copies to /data/test/COMMON/ProdSW/
- DOS machines download via NWTOC from T:\COMMON\ProdSW\

**NAS → AD2 (Test Data): PULL**
- DOS machines write to T:\TS-XX\LOGS\
- Sync pulls to C:\Shares\test\TS-XX\LOGS\
- Files deleted from NAS after copy
- DAT files auto-imported to database

**Root Files: PUSH**
- UPDATE.BAT and DEPLOY.BAT sync to /data/test/ root
- Available at T:\UPDATE.BAT and T:\DEPLOY.BAT

## Pending Tasks

**Immediate:**
- DOS and VPN work complete ✅

**Short-term:**
- Add SSH key to Gitea for /sync command
- Deploy VPN to client machines
- DOS pilot deployment to 2-3 machines

## Context Recovery

Session log now contains complete context for:
- AD2 connection methods (C$ admin share works)
- CTONW test data routing (v1.2 separates ProdSW/LOGS)
- VPN authentication (MS-CHAPv2, not PAP)
- Split tunneling configuration
- All credentials unredacted

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
 2026-01-19 14:39:56 -07:00
Mike Swanson
3faf09c111 feat: Complete DOS update system with test data routing fix 
Implemented comprehensive DOS 6.22 update system for ~30 test stations with
critical fix for test data database import routing.

## Major Changes

### DOS Batch Files (7 files)
- NWTOC.BAT: Download updates from network to DOS machines
- CTONW.BAT v1.2: Upload with separate ProdSW/LOGS routing (CRITICAL FIX)
- UPDATE.BAT: Full system backup to network
- STAGE.BAT: System file staging for safe updates
- REBOOT.BAT: Apply staged updates on reboot
- CHECKUPD.BAT: Check for available updates
- DEPLOY.BAT: One-time deployment installer for DOS machines

### CTONW v1.2 Critical Fix
Fixed test data routing to match AD2 sync script expectations:
- Software distribution: C:\ATE\*.EXE -> T:\TS-4R\ProdSW\ (bidirectional)
- Test data logging: C:\ATE\8BDATA\*.DAT -> T:\TS-4R\LOGS\8BLOG\ (upload only)
- Subdirectory mapping: 8BDATA->8BLOG, DSCDATA->DSCLOG, HVDATA->HVLOG, etc.
- Test data now correctly imported to AD2 database via Sync-FromNAS.ps1

### Deployment Infrastructure
- copy-to-ad2.ps1: Automated deployment to AD2 server
- DOS_DEPLOYMENT_GUIDE.md: Complete deployment documentation
- DEPLOYMENT_GUIDE.md: Technical workflow documentation
- credentials.md: Centralized credentials (AD2, NAS, Gitea)

### Analysis & Documentation (15 files)
- CTONW_ANALYSIS.md: Comprehensive compliance analysis
- CTONW_V1.2_CHANGELOG.md: Detailed v1.2 changes
- NWTOC_ANALYSIS.md: Download workflow analysis
- DOS_BATCH_ANALYSIS.md: DOS 6.22 compatibility guide
- UPDATE_WORKFLOW.md: Backup system workflow
- BEHAVIORAL_RULES_INTEGRATION_SUMMARY.md: C: drive integration

### Session Logs
- session-logs/2026-01-19-session.md: Complete session documentation

### Conversation Reorganization
- Cleaned up 156 imported conversation files
- Organized into sessions-by-date structure
- Created metadata index and large files guide

## Technical Details

### AD2 → NAS → DOS Sync Flow
1. Admin copies files to AD2: \192.168.0.6\C$\Shares\test\
2. Sync-FromNAS.ps1 runs every 15 minutes (AD2 → NAS)
3. DOS machines access via T: drive (\D2TESTNAS\test)
4. NWTOC downloads updates, CTONW uploads test data
5. Sync imports test data to AD2 database

### DOS 6.22 Compatibility
- No %COMPUTERNAME%, uses %MACHINE% variable
- No IF /I, uses multiple case-specific checks
- Proper ERRORLEVEL checking (highest values first)
- XCOPY /S for subdirectory support
- ASCII markers ([OK], [ERROR], [WARNING]) instead of emojis

### File Locations
- AD2: C:\Shares\test\COMMON\ProdSW\ (deployed)
- NAS: T:\COMMON\ProdSW\ (synced)
- DOS: C:\BAT\ (installed)
- Logs: T:\TS-4R\LOGS\8BLOG\ (test data for database import)

## Deployment Status

✅ All 7 batch files deployed to AD2 (both COMMON and _COMMON)
⏳ Pending sync to NAS (within 15 minutes)
⏳ Pending pilot deployment on TS-4R
📋 Ready for rollout to ~30 DOS machines

## Breaking Changes

CTONW v1.1 → v1.2: Test data now uploads to LOGS folder instead of ProdSW.
Existing machines must download v1.2 via NWTOC for proper database import.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
 2026-01-19 12:49:54 -07:00