RemotePowerShellEnabled disabled for every user #10026
Closed
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
|
Learn Build status updates of commit 08b9f1b: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
JohanFreelancer9
approved these changes
Oct 11, 2022
|
Already fixed yesterday #10027, thus now this PR results in merge conflicts. Closing. |
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.
Description
Using
-orcomparison inside the Where-clause to exclude specified admins leads to having RemotePowerShell disabled for those users as well.Example:
admin1 -ne admin1 -or admin1 -ne admin2->
$false -or $true->
$trueUsing the
-andcomparison fixes this behavior, since neither admin1 nor (-ne+-and) admin2 should have their RemotePowerShell disabled.Real world tests
Get-User | Where-Object {$_.UserPrincipalName -ne 'administrator@lab.local' -or $_.UserPrincipalName -ne 'admin2@lab.local'} | Set-USer -RemotePowerShellEnabled $false-andcomparison: