This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 84%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Hi All ,
I have a task sequence to deploy windows 10 1909 and the machine deploy the OS , join the domain and install config Mgr client and so on .... the Task sequence has many restart steps while installing applications.
my question is , will computer Group policies being applied even while the OSD Task sequence is still running ?
No device-targeted group policies aren't contingent on a user logging on.. There's nothing built-in for this although I'd probably question what and why you are doing this in the first place.
If you feel you must do this and it is causing an issue, you'll have to manipulate the OU that the system is in so that these GPOs aren't applied until later.
It's possible yes. There is nothing in the task sequence engine to preclude this so it's ultimately up to the Win 10 version's behavior.
Is there something that you are specifically concerned about?
my concern is what if I want disable some services although I need these restrictions to be applied only after the OSD is completed because those restrictions might interrupt the applications deployment steps in the Task sequence.
Do I have away to make computer GPOs apply only with the first user login? or after the task sequence is completed
It's not that the task sequence blocks GPO - it doesn't - its that GPO doesn't run until the Windows Setup completes. Since the task sequence runs entirely within Windows Setup, then GPO doesn't run until the task sequence completes. This is documented here:
Theoretically GPOs can run during the task sequence if its triggered appropriately, but it's not recommended since certain GPOs can conflict with the task sequence. Also, this only really applies to task sequences installing a new OS. For other types of task sequences - stand-alone, in-place upgrade - GPO can theoretically run while the task sequence is running.
