I have currently set up and upgrade MDT Task Sequence in SCCM to be deployed as an available deployment it carries 2 run-books. The first one moves the asset in Active Directory to a staging OU so the asset can run through the task sequence correctly. I have the second runbook staged just after the first reboot after applying the OS under Setup Operating System. I have the toolkit and gather steps before the runbook step. However it never reaches the SCORCH Service and fails with;
The task sequence execution engine failed executing the action (1.2.5.3 CLIENT OU MOVE TO ECC10 FROM STAGING) in the group (Setup Operating System) with the error code 10801Action output: ... ed.
Microsoft Deployment Toolkit version: 6.3.8330.1000
The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.
Orchestrator server URL = https://server/Orchestrator2012/Orchestrator.svc/Jobs
Runbook name = 1.2.5.3 CLIENT OU MOVE TO ECC10 FROM STAGING
Runnbook ID = aa181885-e356-4734-a8f1-f0cc73021e10
Runbook parameter mode = AUTO
Added parameter _SMSTSMachineName (2c037158-b8fa-434f-90c9-c2f0600d8fc3)
PropertyUserDomain is now = Domain
Property UserID is now = Network Account
<Message containing password has been suppressed>
Process completed with exit code 10801
Error executing web service https://Server/Orchestrator2012/Orchestrator.svc/Jobs: The server returned an invalid or unrecognized response
(-2147012744)
FAILURE ( 10801 ): Unable to create Orchestrator job for the specified runbook.
Command line cscript.exe "C:\_SMSTaskSequence\WDPackage\Scripts\ZTIExecuteRunbook.wsf" returned 10801.
I have moved the step around later in the task sequence and also have had a play with the .VBS script for moving assets in AD. Is it a limitation in the process for a dedicated Upgrade Task Sequence?
Any assistance will be greatly appreciated.