Add support for custom driver packages #232
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If a computer manufacturer does not match one of the predefined 10, the Invoke-CMApplyDriverPackage script will fail, even if a custom driver package has been created using the driver automation tool. This default clause will allow custom driver packages to be installed while still allowing for specific handling of different computer manufacturers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a computer manufacturer does not match one of the predefined 10, the Invoke-CMApplyDriverPackage script will fail, even if a custom driver package has been created using the Driver Automation Tool. This default clause will allow custom driver packages to be installed while still allowing for specific handling of different computer manufacturers.
This would fix the issue presented by this pull request #175