Greetings,
We are using the MDT "Execute Runbook" in a CM2012R2 OSD task sequence but have noticed that the task sequence is completely unaware of the exit state of the runbook.
If the Runbook completes with an error or a warning, then task sequence action always sees an exit code 0 and continues on without being aware there was a problem. Looking in the BDD and ZTIExecute logs it just shows "Final job status: Completed" and "Runbook executed successfully".
Is there a property or some other trick anyone has found for the task sequence to get the return state of an execute runbook action?
Scott.
- Edited by Scott Williams - IP1 Friday, February 20, 2015 5:33 AM