Ok so it's my understanding that during OSD GPUpdate is blocked and will not run... I have seen several 'solution' although none of them actually end up running GPUpdate during the TS. I really need to be able to do this as if the policy doesn't come down I don't get connected to our Wi-Fi.

My question is... What is Blocking GPUpdates? is it something like 'provisioning mode' that I can disabled via script (a service?) or regkey temporarily and then re-enable it at the end of a GPUpdate TS step?

There is always a working solution... whatever must be done.

http://henkhoogendoorn.blogspot.com/2013/05/doing-group-policy-update-during-os.html

http://social.technet.microsoft.com/Forums/systemcenter/en-US/2b6274b7-2ce3-44b0-9e36-8ea6bca77fbd/group-policy-application-in-osd-task-sequence?forum=configmgrosd

I have read those articles and neither provides any insight into the possibility of making gpupdate function inside of an OSD TS.

what is blocking gpupdate? reg key / service / process?

GPOs are blocking during the execution of a task sequence. You can easily workaround it by importing regkeys are WiFi profiles etc (depending on your exact requirements).

Yes I can inject the Wi-Fi profile but to authenticate to our Wi-Fi the device is required to have a cert that they receive via group policy. no group policy, no cert, no wifi...

to clearify why this is a pain and why it should matter that it connects to wifi during the TS...

I am imaging tablets... Dell Venues 11 Pros in this case... on a dock. I have a process in the task sequence that prompts to remove the device from the dock it the connects to the wifi, wipes the dock mac and triggers a hardware inventory so that dock is no longer associated with the device.

http://blogs.technet.com/b/askpfeplat/archive/2014/07/28/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd.aspx

blocked during the execution of a task sequence is quite vague...

doesn't anyone have any idea of a component that is accomplishing this so that someone, myself or otherwise can be one step closer to scripting a solution.

Ok well supported or no it seems my hunch payed off.

As my third last step of my task sequence I disable provisioning mode:

reg add "HKEY_LOCAL_MACHINE\Software\Microsoft\CCM\CcmExec " /v ProvisioningMode /t REG_SZ /d false /f

Then as my second last step I am able to run gpupdate to get my wifi cert:

cmd.exe /c gpupdate /target:computer /force

Then as my last step I am able to run a script to connect to the wifi and wipe the imaging dock mac address and trigger a hardware inventory action:

http://blogs.technet.com/b/askpfeplat/archive/2014/07/28/how-to-use-the-same-external-ethernet-adapter-for-multiple-sccm-osd.aspx

So far I have only been pleased with the success... no issue with this to report so far but for anyone else traveling down this path, be wary as Group policy can interfere with your imaging process so disabling provisioning mode to soon in the task sequence could be a real issue.

• Marked as answer by KPRDave Tuesday, August 12, 2014 3:17 PM

Nice work figuring this out! I too don't like the idea of having to reboot and run GPUpdate via RunOnce and wasn't too thrilled it was blocked/disabled during the Task Sequence. So far this is working perfectly near the very end of my tasks. just in front of my cleanup and reboot, good job!

Jack