Feature Request: DISM Fallback and OS Name Fallback #318
Description
We're deploying Windows 11 24H2 across our organization, but we're running into a real world problem: we have quite a few older HP laptops (like the EliteBook 830 G7) that are compatible with Windows 11, but HP still only provides Windows 10 driver packages for them. The script already has version fallback (which is great for 24H2→23H2 scenarios), but we needed OS name fallback so it would automatically check for Windows 10 driver packages when Windows 11 ones aren't available. Otherwise, we'd have to manually run the script twice or create wrapper scripts for every deployment scenario. The OS name fallback solves this by seamlessly falling back from Windows 11 to Windows 10 when needed, and it works together with the existing version fallback so it'll find the right package version too.
I also hit an issue where the script was failing in some of our WinPE environments because the DISM PowerShell module wasn't loaded (even though dism.exe was right there). The DISM fallback change just uses the command-line tool if the PowerShell module isn't available, which makes the script work in more WinPE setups without having to update boot images or add extra steps to our task sequences.
Amended Script attached with these settings does this believe this could be useful to others
This now allows for the parameter -OSNameFallback
Example - -BareMetal -Endpoint "ENDPOINT_NAME" -TargetOSName "Windows 11" -TargetOSVersion "24H2" -OSVersionFallback -OSNameFallback