39 lines
2.6 KiB
Markdown
39 lines
2.6 KiB
Markdown
# Validation Checklist
|
|
|
|
## Before Setup
|
|
|
|
- [ ] Boot the intended isolated Windows installation.
|
|
- [ ] Confirm only `C:`, `S:`, and `P:` are mounted.
|
|
- [ ] Confirm `S:` label is `AUTO_DATA` and `P:` label is `PORTABLE_APPS`.
|
|
- [ ] Run `-HealthCheck` and review the generated HealthReport files.
|
|
- [ ] Confirm the selected `-WorkstationProfile` matches the installation purpose.
|
|
- [ ] Validate JSON definitions with `Get-Content -Raw .\Config\*.json | ConvertFrom-Json` or the repository validation command.
|
|
|
|
## After Setup
|
|
|
|
- [ ] Review `SetupReport_<timestamp>.html` and `.json`.
|
|
- [ ] Review failed and skipped entries in the result CSV.
|
|
- [ ] Confirm hash records were created in `Manifests\Hashes` for portable downloads.
|
|
- [ ] Confirm `Installed_Software`, `Portable_Apps`, `VSCode_Extensions`, `Drivers`, `USB_Devices`, `Disk_Inventory`, `Environment_Variables`, and `Services` inventories exist.
|
|
- [ ] Confirm each profile-specific workspace, configuration, installer, and backup location exists.
|
|
- [ ] Confirm Google Chrome Portable launches from all three Windows installations with the shared `P:\PortableApps\Config\Chrome\User Data` profile.
|
|
- [ ] Confirm Xhorse `RESOURCE_CATALOG.md`, `LINK_INDEX.md`, `CHANGELOG.md`, and `README.md` exist under `P:\PortableApps\Automotive\XHorse`.
|
|
- [ ] Create and test a configuration backup before vendor diagnostic tools or drivers are installed.
|
|
|
|
## Communication Software On All Three Windows Installations
|
|
|
|
Run the following command once while booted into each isolated Windows installation:
|
|
|
|
```powershell
|
|
.\Automotive-Workstation-Setup.ps1 -WorkstationProfile 'DailyTech & Tuning' -InstallCommunicationSoftware
|
|
.\Automotive-Workstation-Setup.ps1 -WorkstationProfile 'ODIS & XENTRY' -InstallCommunicationSoftware
|
|
.\Automotive-Workstation-Setup.ps1 -WorkstationProfile 'PIWIS & ISTA' -InstallCommunicationSoftware
|
|
```
|
|
|
|
- [ ] MVCI PRO J2534 installer launched and completed on the current Windows installation.
|
|
- [ ] Autel Maxi PC Suite package downloaded automatically from the official Autel page, extracted, and completed on the current Windows installation.
|
|
- [ ] J2534/Autel USB drivers installed on the current Windows installation.
|
|
- [ ] Interface firmware, licensing, and device registration completed with the interface connected only when the vendor wizard requests it.
|
|
- [ ] Communication test completed on a supported, authorized vehicle or bench setup.
|
|
|
|
The script downloads the current Windows Maxi PC Suite package from Autel's official software downloads page and creates a shared installation handoff file under `P:\Install\Autel\Maxi-PC-Suite`. It does not silently install the vendor package. |