Changed WMI Keys #11
Open
Changed WMI Keys #11
Conversation
This file contains hidden or 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
$null on left side of comparision No usage of alias functions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In my opinion 'MappedDriveReport' does not work as advertised. The mapped drives are written to WMI correctly but the WMI class definition is incorrect. If the created WMI class gets imported to SCCM only one drive is collected per device.
Only if "ComputerName", "DriveLetter" and "UserName" are defined as key a correct inventory will be created.
Every user can have multiple drive maps and every drive letter can be used by multiple users. Therefore only a combination of three keys defines a unique data set.