Fix – Cannot start Orchestrator Runbook via ConfigMgr Task Sequence

During TechEd I was discussing a ConfigMgr issue with Eric Leonard, a fellow ConfigMgr admin in Canada. The issue we were discussing were the following: When having multiple network access accounts configured in ConfigMgr, Orchestrator runbooks could not be started. It turned out there was a bug in ZTIExecuteRunbook.wsf script, a missing single quite. Big thanks to Eric for providing the solution.

Update 2014-05-27: Turned out to be a bug filed (Dec. 2013), please vote it up! http://connect.microsoft.com/ConfigurationManagervnext/feedback/details/812500/mdt-2013-error-in-ztiexecuterunbook-wsf-with-multiple-sccm-naa Thanks Gaëtan Hermann for letting me know.

The Fix

There bug in the ZTIExecuteRunbook.wsf script is on line 309, highlighted here:

If bNAACred Then
    ' We will try another account
    Continue
Else

Obviously, "Continue" is not a valid command in VB script so this causes an error, the fix is to simple add a single quote to comment out the line.

If bNAACred Then
    ' We will try another account
    ' Continue
Else

Happy Deployment, Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
1 Comment
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
GSimos
GSimos
8 years ago

Voted but I see that the status is:

Status: Resolved as Postponed

And who knows when it will be fixed….. 🙁


>