This repository has been archived by the owner on Jan 21, 2021. It is now read-only.
Powerview: reintroduce New-GPOImmediateTask #325
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
WilliamBruneau
force-pushed
the
gpo_immediate_task
branch
from
cec01ee
to
6c2e397
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
New-GPOImmediateTask was removed by commit 7c32bf6.
The reason of deletion was : 'inconsistent and better done manually'.
This blog post explains some GPO internals that may explain the 'inconsistent' of this cmdlet.
This new New-GPOImmediateTask is a merge between the old implementation and the SharpGPOAbuse implementation (credit to @pkb1s).
I think this implementation solves the inconsistent issues and could be reintroduce in Powerview.