Quick Tip: Error Handling Across Parent/Child Runbooks

I got a question posed to me in the form of a design change request for Orchestrator. And, true to fashion for Orchestrator, I pointed out that what was being asked for as a feature could be solved by the existing product by just architecting the runbook in a certain way. The scenario posed was… Read more

Speeding up Runbooks by Improving Activity Loading Speed

Even on the product team, there is a lot of information we don’t see that gets published about the product. Other arms of Microsoft like Customer Support are continually listening to customers and feed bugs and change requests to the product team, but they also publish KB articles and helpful tips about performance, security, and… Read more

Removing Inaccessible Computers from Deployment Manager

Ok, I spared you the “SQL Sequel” puns this time, but this article does contain some SQL…In this article, I’m again going to talk about actually removing data, so here goes the big scary warning box: Note from the legal department: The process described here is not officially supported by Microsoft and are provided only… Read more

Sequel to the SQL Sequel: Helpful Stored Procedures for Orchestrator

I just couldn’t resist having a little fun with the title of the article…but today’s topic is a little more serious. In the previous articles,IPs and Activities and How Those are Represented in the Database and SQL Sequel: More Useful Orchestrator Database Queries, I talked about some queries to get information out of the Orchestrator… Read more

Cool Tool: Orchestrator IP Cleaner (sneak peek)

When I was writing the article I posted a few days ago about importing IPs programmatically (More Fun with COM: Importing Integration Packs via PowerShell), I had to do a lot of testing to make sure the script was going to actually work and import the Integration Packs correctly. Along the way, I would up… Read more

Understanding IP Installation: What Does Register/Unregister/Deploy/Undeploy Really Mean?

One of the most foundational activities an Orchestrator admin does is installing Integration Packs. After all, Integration Packs provide the real value to Orchestrator because they allow you to extend its capabilities and let you connect to virtually anything so you can automate and orchestrator across many different platforms. However, just because it’s one of… Read more

Quick Tip: Checking PowerShell Scripting Abilities on a Computer

I do lots of PowerShell scripting, both inside runbooks and in stand-alone scripts. I have my own little virtual lab with a bunch of VMs and a domain controller that has a group policy assigned to enable the right PowerShell scripting settings on all the domain-joined computers, so I really don’t run into execution policy… Read more

Psst! Here’s a Secret Way to Customize the Runbook Tester Window!

If you’re like me, you use the Runbook Tester a lot. And, if you’re like me, you get annoyed by always having to resize the window to maximize one area or another. For me, I use the logging section more than anything, so I want to maximize the size of that part of the window…. Read more

Orchestrator Quick Tip: What’s the Maximum Size of Parameters?

I see this question on internal discussions list every now and then, so I thought I’d answer it here to be helpful. The question was: Is there a maximum length for string parameters in the Initialize Data activity? And if the answer is “yes” – what would the maximum length for string parameters be? Let… Read more

Orchestrator Quick Tip: Setting Environment Variables in CLI Activities

Using the Orchestrator Integration Toolkit’s Command-Line Activity Wizard, you can create your own custom activities really easily just by using a simple command line or one-line PowerShell script. When creating activities, you can specify parameters that appear on the activity’s properties tab. When using PowerShell as the “mode” of the activity, the wizard lets you… Read more