One trick that I always recommended for everyone who is designing Orchestrator runbooks, is to name their Connections properly.
If you have 2 environments, one test and one production, the easiest way to transfer runbooks is the name the connection configurations in the 2 environments exactly the same name.
but in some cases this is not possible to have them named the same.
One scenario could be when transferring from one customer to another.
Luckily it is easy to fix!
Since all exports are XML files, you can change the name of the connections in a couple of easy steps.
- Using the Runbook designer, export the runbook or folder to an ois_export file.
- Open the file in text editor or in XML notepad (get xml notepad http://www.microsoft.com/en-us/download/details.aspx?id=7973)
- Search for <Connection datatype="string">SCSM</Connection> (replace SCSM with your connection name)
- Replace any instances of the connection name by the new connection name.
That’s it! 
thanks for your interesting Post.
I use the Microsoft AD IP and i would like to switch the create User connection from my Test Domain to the production environment.
If I export the runbook and modify Configuration datatype in the XML File i can’t import the modified ois_export file.
Do you have any ideas?
It is hard for me to guess what could be wrong since you do not provide an error message.
do you get an error message?
Maybe you have replaced the name in too many places, I mean if some other object has the same name, and you accidently replaced that name too.
[…] « SCO 2012 Tricks: Change Integration Pack Connection name when transferring runbooks between environm… SCO 2012 – SCOM 2012: Best Practice – Monitor alert and restart a service […]