For those of you that still live in the wonderful world of BizTalk 2004 and use the EnlistOrch.vbs script, I noticed today that it will always use the default Host when starting, which is a bit annoying when you have set another host during binding and are scripting your deployment…..
I’ve updated the script to accept the Host you want the orchestration to use as a command-line parameter, this ensures that the orchestration will be started with the correct Host. Invoking the script now looks something like the following (note the new HostName parameter):
C:>EnlistOrch.vbs <OrchestrationName> <Assembly> <HostName> [Action]
An updated version of the script can be downloaded here.