Anonymous
My feedback
-
5 votesAnonymous
shared this idea
·
-
33 votesAnonymous
supported this idea
·
-
75 votes
Leaving status as Noted – see https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
We don’t do anything explicit to block GPO processing, in earlier Windows versions that wasn’t the case but GPO apply was problematic in some instances
Our next step for this item is clear explanation of how GPO relates to OS Deployment Task Sequences and standalone Task Sequences.
An error occurred while saving the comment -
99 votesAnonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
I would also appreciate that. I can imagine a Tab in the properties of the Resource (User or Computer) where all direct Memberships in Collections are listed. This could also allow adding or removing them. Maybe evan a "Remove" all button.
-
6 votesAnonymous
supported this idea
·
-
859 votes
-
7 votesAnonymous
shared this idea
·
-
1 voteAnonymous
shared this idea
·
-
1 voteAnonymous
shared this idea
·
-
10 votes
An error occurred while saving the comment Anonymous
commented
This would be very welcome to Speed up the Migration process in big environments
Actually I think its good, that GPO processing is blocked during OSD. We make sure to get policies applied after the TS by doing a Reboot when the TS is finished using the SMSTSPostAction Variable with a shutdown.exe command.