When deploying with Microsoft Deployment Technology (MDT) and the task sequence fails to resume after a MDT initiated reboot take a look at the BDD.log.
One of the last entries within that log may show errors registering “Microsot.BDD.Utility.dll” and will log it as error code 70. As the below example shows.
RUN: regsvr32.exe /s “C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll” LiteTouch
FAILURE (Err): 70: CreateObject(Microsoft.BDD.Utility) – Permission denied LiteTouch
If so this can be caused by User Account Control (UAC) so ensure that UAC is disabled and in addition the following registry key is set within the image.
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
FilterAdministratorToken Reg_DWORD=0
This key can be fed by the group policy or local system policy and ensuring that it is set to Disabled should resolve the issue.
Computer Configuration\Security Settings\Local Policies\Security Option\User Account Control: Admin Approval Mode for the built-in Administrator account
Once configured if you have a stuck MDT task sequence a reboot the image and the process should continue.
Author: Dale Scriven