MDT Fails to resume on reboot (Failure 70)

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 kRead More…

Removing the Windows Domain login EULA for automated deployments

Pre-login EULA’s are a common sight within organisation’s forcing a user to “read” something then click OK allowing the system to continue to login. Automated build tools such as Ivanti, or MDT however are not keen on these things and often as part of a new environment it is recommended that a new Active Directory Organisational Unit is created and blocking inheritance of group policies applied so that the EULA can be filtered out. New systems built with automation tools are joined to the domain added to these OU’s to ensure that when systems reboot the automation is not interrupted by waiting for a manual EULA acceptance. But what happens in cases where you cannot create a staging OU and stop the EULA from applying either by design or by organisational requirements. Read More…