Belton WDS Files
Find a file
2026-02-17 15:52:47 +13:00
Automation massive changes - Refactored Code and Modularized 2026-02-17 15:50:33 +13:00
Documentation Update README.md 2026-02-17 15:52:47 +13:00
Testing Massive changes to everything 2026-02-04 09:03:49 +13:00
.gitignore Massive changes to everything 2026-02-04 09:03:49 +13:00
README.md Update README.md 2026-02-17 15:52:47 +13:00

Belton WDS Automation

Windows Deployment Services automation for Belton imaging and post-deployment provisioning. Batch entry points in Automation/ orchestrate PowerShell scripts for drivers, apps, registry changes, Windows Update, and cleanup.

Architecture

Deployment phases (standard order):

  1. Pre-Check
  2. Driver Install
  3. Application Install
  4. Registry Changes
  5. Windows Updates (Prep + Install)
  6. Cleanup

Each phase has a .bat wrapper that resolves paths, calls the matching .ps1 scripts, logs a summary entry to QuickLog, and exits with an aggregated result.

Entry Points

  • WDS hook: Automation/setupcomplete.cmd
  • Phase wrappers:
    • Automation/Belton/Bat Files/Pre-Check.bat
    • Automation/Belton/Bat Files/Driver Installs.bat
    • Automation/Belton/Bat Files/Application Installs.bat
    • Automation/Belton/Bat Files/Registry Changes.bat
    • Automation/Belton/Bat Files/Updates.bat
    • Automation/Belton/Bat Files/Cleanup.bat

Core Scripts (by phase)

  • Pre-Check: Automation/Belton/Scripts/Pre-Checks/Belton Pre-Check.ps1
  • Drivers: Automation/Belton/Scripts/Installers/SDIO Driver Install.ps1
  • Apps: Automation/Belton/Scripts/Installers/Belton App Installs.ps1
  • Office: Automation/Belton/Scripts/Installers/Microsoft Office Install.ps1
  • Dock: Automation/Belton/Scripts/Installers/Startech Dock Install.ps1
  • Registry (HKCU): Automation/Belton/Scripts/Registry Changes/Belton Local Regedit.ps1
  • Registry (HKLM): Automation/Belton/Scripts/Registry Changes/Systemwide Regedit.ps1
  • Windows Update Prep: Automation/Belton/Scripts/Updates/Windows Update Prep.ps1
  • Windows Update Install: Automation/Belton/Scripts/Updates/Windows Update.ps1
  • Cleanup: Automation/Belton/Scripts/Cleanup/Belton Cleanup.ps1
  • Log Collection: Automation/Belton/Scripts/Cleanup/Belton Log Collection.ps1
  • Dock Uninstall: Automation/Belton/Scripts/Cleanup/Startech Dock Uninstall.ps1

Modules

  • Logging: Automation/Belton/Scripts/Modules/BeltonLogging.psm1
  • App Detection/Install: Automation/Belton/Scripts/Modules/BeltonAppManagement.psm1
  • Network/Drive Utilities: Automation/Belton/Scripts/Modules/BeltonNetworkUtils.psm1

Logging and Exit Codes

  • QuickLog: APPBASE\Logs\Belton QuickLog.log
  • Phase logs: APPBASE\Logs\<Phase>.log (for example Installers.log, RegistryEdits.log, WindowsUpdate_Prep.log)
  • Exit codes: 0 success, 1+ failure or aggregated error count

QuickLog format:

[YYYY-MM-DD HH:MM:SS] [SCRIPT_ALIAS] : PASS/FAIL (rc=X)

Path Resolution Pattern

All PowerShell scripts resolve APPBASE by walking two levels up from the script directory:

$scriptDir = $PSScriptRoot
$appBaseLevel1 = Split-Path $scriptDir -Parent
$appBase = Split-Path $appBaseLevel1 -Parent

External Dependencies

  • PSWindowsUpdate: installed during Windows Update Prep
  • SDIO share: \\192.168.15.5\Techbay\Belton WDS\Software\SDIO\
  • Office ODT: Software/ODT/

Remediation and Testing

  • Remediation menu: Automation/Belton/Remediation/Remediation.bat
  • Standalone scripts (absolute APPBASE variants): Testing/Standalone Scripts/
  • Additional testing utilities: Testing/

Troubleshooting Quick Checks

  • QuickLog shows PASS/FAIL for each phase. Check phase logs for details.
  • If a script cannot resolve modules, verify APPBASE\Scripts\Modules exists.
  • If SDIO fails, verify the Techbay share is reachable and credentials are valid.
  • If Windows Update fails, run Windows Update Prep and confirm PSWindowsUpdate is installed.