Update 20150108 #1
Merged
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
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.
Update 20150108
KB3000850 introduced an issue where previous versions of the module no longer worked on Windows 8.1 and 2012 R2 computers. The problem was caused by the Access and Audit script properties on security descriptor objects being evaluated differently than before the update. I'm working on version 4.0, which is a complete re-write in compiled code, so I just made minor modification to version 3.0 that effectively removes the Access, AccessToString, Audit, and AuditToString properties. If you try to use those properties, you simply get a string asking you to use the Get-AccessControlEntry function instead.