Modified powershell scripts due to permissions issue#9
Open
bwilcox wants to merge 1 commit intoipcrm:masterfrom
Open
Modified powershell scripts due to permissions issue#9bwilcox wants to merge 1 commit intoipcrm:masterfrom
bwilcox wants to merge 1 commit intoipcrm:masterfrom
Conversation
…esolve an issue with insufficient permissions errors in a windows 2016 environment.
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.
This is a pretty big change in the Powershell scripts. I can't take credit for the difference, the main changes in the Set-RegOwner script came from a technet post (URL in the comments). While the original implementation worked great in my lab, for reasons I can't explain it failed with insufficient permissions in my customers environment.
This request addresses that by changing where in the scripts the security tokens are obtained and by changing the process for setting the owner from using the get-acl and set-acl commandlets to using win32 class methods directly. This allows things to work as expected both in my lab on an unmolested 2016 installation and in my customers environment.
I really wish I could say why registry_acl wasn't working in my customer environment, but I've not been able to get to the root.
I have also not had the opportunity to test this change against other versions of windows.