Skip to content

Conversation

@stephannn
Copy link

@stephannn stephannn commented Feb 10, 2023

Hi,
I did some modifications:

  • If using demo mode you can also use get-credentials
  • Fallback to a different OS Name when no Windows 11 driver exists
  • Fallback to a lower OS version
  • Save downloaded and applied driver package in the registry to skip it in case the powershell runs again
  • Added error handling like recommended: v4.2 Bad error reporting #156

@sol-at-nobia
Copy link

Hi, I did some modifications:

  • If using demo mode you can also use get-credentials
  • Fallback to a different OS Name when no Windows 11 driver exists
  • Fallback to a lower OS version
  • Save downloaded and applied driver package in the registry to skip it in case the powershell runs again
  • Added error handling like recommended: v4.2 Bad error reporting #156

Hi,
How did you setup the OS Name fallback? Didn't work "out of the box" for me, so was wondering if I had to add a parameter when invoking the script or such?

Br
Samuel

@stephannn
Copy link
Author

Just added 23H2:
https://github.com/stephannn/ModernDriverManagement/blob/master/Invoke-CMApplyDriverPackage_4.2.1_woOSVersion_4.ps1

I call the fallback like that:

Invoke-CMApplyDriverPackage_4.2.1_woOSVersion_4.ps1
-DriverUpdate -Endpoint "Server.FQDN" -RegistryValueDriverInstalled $true -PerformReboot $false -TargetOSName 'Windows 11' -TargetOSVersion "23H2" -OSVersionFallback -TargetOSNameIgnore $true -TargetOSVersionLatest $true

@osxos
Copy link

osxos commented Aug 27, 2024

This is phenomenal. Nice work on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants