Workstation-Setup/DEPLOYMENT.md

Deployment

Build a release package

Run from an elevated Windows PowerShell session only when the target machine will be configured. Packaging itself does not require elevation.

.\Deploy\Package-WorkstationSetup.ps1 -Version '2026.09.09' -IncludeTests

The package is written to Releases\\Automotive-Workstation-Setup-<version>.zip and includes:

• Main setup script
• JSON configuration files
• User and troubleshooting documentation
• Validation checklist
• SHA256 release manifests
• Tests when -IncludeTests is specified

Do not distribute the temporary staging directory. Verify the generated archive hash from the accompanying .release.json file before copying it to a deployment share.

Rollout sequence

1. Verify the release archive SHA256.
2. Extract it to a versioned folder on the deployment share.
3. Boot the intended isolated Windows installation.
4. Confirm only the intended C:, S:, and P: volumes are mounted.
5. Run -Mode Plan and review the Windows/application plan.
6. Run -Mode Audit and save the generated reports.
7. Create a configuration backup.
8. Run -Mode Apply from an elevated Windows PowerShell window.
9. Restart when the checkpoint reports AwaitingRestart.
10. Resume with -ResumeFromCheckpoint.
11. Run -Mode HealthCheck and review the setup report.
12. Install licensed OEM suites and communication drivers separately through vendor installers.

Production gates

• All Pester tests pass.
• The archive hash is verified.
• The selected profile matches the isolated Windows installation.
• OEM software licensing and driver compatibility are confirmed.
• Original ECU, EEPROM, and coding data have independent backups.
• Elevated Apply testing has completed on a clean test workstation before production rollout.