Automotive Workstation Setup User Guide

Modes

Run the script from an elevated Windows PowerShell session for installation modes. Read-only modes do not require elevation.

# Preview changes
.\Automotive-Workstation-Setup.ps1 -Mode Plan -WorkstationProfile 'DailyTech & Tuning'

# Inspect the current workstation
.\Automotive-Workstation-Setup.ps1 -Mode Audit -WorkstationProfile 'ODIS & XENTRY'

# Apply the selected profile
.\Automotive-Workstation-Setup.ps1 -Mode Apply -WorkstationProfile 'PIWIS & ISTA'

# Create a project workspace
.\Automotive-Workstation-Setup.ps1 -Mode CreateWorkspace `
  -WorkstationProfile 'DailyTech & Tuning' `
  -JobId 'VW001' -Manufacturer 'Volkswagen' -Model 'Golf' `
  -ModelYear 2015 -Module ECU -Technician 'Technician Name'

-HealthCheck, -BackupConfiguration, and -RestoreConfiguration remain supported for compatibility with older commands.

Profiles

DailyTech & Tuning: tuning, binary analysis, reverse engineering, and CAN work.
ODIS & XENTRY: VAG and Mercedes diagnostic sessions.
PIWIS & ISTA: Porsche and BMW diagnostic sessions.

The profile determines application selection, Windows power policy, and workspace structure.

Reports and State

Reports are written under the configured local root:

Logs: setup logs, CSV summaries, plans, and workspace results.
Config: local profile metadata, Windows state, and checkpoint state.
Manifests: portable application hashes and inventories when the shared portable root is available.

The checkpoint file is Config\\.workstation-setup-state.json. Resume a prior apply run with:

.\Automotive-Workstation-Setup.ps1 -Mode Apply `
  -WorkstationProfile 'DailyTech & Tuning' -ResumeFromCheckpoint

For portable ZIP entries, RequireAuthenticode: true validates the extracted expected .exe or .dll before replacing an installed version. Entries whose expected file cannot carry an Authenticode signature fail validation when this option is enabled. This option is not currently enabled for any bundled portable entry; it must be explicitly set in the configuration.

Workspace Data Handling

Always preserve original ECU, EEPROM, and coding reads in the Originals or profile-equivalent folder. Calculate hashes before editing. Keep modified files in WorkingCopies, CodingBackups, or the matching profile folder. Do not flash or code a vehicle without authorization, verified backups, stable power, and a vendor-supported procedure.

Testing

Run the Pester suite from the repository root:

.\Tests\\Run-AllTests.ps1

The suite is designed to use temporary roots and does not install applications or modify Windows settings.

2.7 KiB Raw Permalink Blame History