Orchestrator Health Checker


If you haven’t heard of this tool I highly recommend you download it now.  It’s called Orchestrator Health Checker and it is an invaluable tool to keep an eye on the health of your Orchestrator servers.  You can find this tool hear.  I wont go into too many details since there is quite a bit of information already listed but one issue I’ve always had was getting the Start and Stop Monitor buttons to work properly.

First the easy one, to fix the stop all monitors button all of your monitoring runbooks must START with the word Monitor in the runbook name.  That one made me feel a little dumb!

Now for the Start All Monitors button…This one was a little tricky.  This actually requires a runbook to start all of the monitors.  If you have already implemented my Orchestrator Maintenance Automated project then you are already 90% there, and dont worry, you can call the 1.3 Start Monitors runbook individually without it calling back the main runbook.  If you haven’t or don’t need that then you can just start and stop at section 1.3 Start Monitors.  Notice I named that runbook Start RBs?  That is important because that is what you will need to put in the Orchestrator Health Checker.exe.config file.  Below is my configuration file so you can see how it is supposed to be setup.

<?xml version=”1.0″ encoding=”utf-8″ ?>
<configuration>
<startup>
<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0,Profile=Client” />
</startup>
<connectionStrings>
<add name=”PlayLab_SCORCH_DB” connectionString=”Server=SCDB.play.lab;Database=Orchestrator;Trusted_Connection=True;”/>
</connectionStrings>
<appSettings>
<add key=”LogFileFormat” value=”CMTrace”/>
<add key=”LogPurgeTrendDays” value=”7″/>
<add key=”TimeZoneToUse” value=”Central Standard Time”/>
<add key=”PlayLab_SCORCH Web Service” value=”http://SCORCH:81/Orchestrator2012/Orchestrator.svc”/>
<add key=”PlayLab_RB Start Monitors” value=”Start RBs“/>
</appSettings>
</configuration>

The red sections can be called anything and this is what will show up in the dropdown.  You probably want to put “Production” here if this will be connecting to your production environment.

The green sections will be unique to your environment.  The name of the server the database is installed on and the name of the webserver that the Orchestrator Console is installed on.

The blue section is the name of the runbook that will be starting all of the monitors.

And thats it.  Maybe next time I will read the instructions a little closer 🙂

Advertisements

One thought on “Orchestrator Health Checker

  1. Pingback: Orchestrator 2016 Upgrade – System Center

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s