Orchestrator 2012 SP1: SCOM 2012 SP1 Integration Pack – Start Maintenance Mode Activity changed

After upgrading System Center Orchestrator from 2012 RTM to 2012 SP1 and also the System Center integration packs including System Center Operations Manager 2012 SP1 Integration Pack I realized that the monitor setting entry has changed.

I have a small runbook that shows this. The first activity only translates a netbios servername to a FQDN and the second activity sets the maintenance in SCOM.

mm

The Start Maintenance Mode activity looked like this before the upgrade to SP1:

setmaintold

The Monitor entry had a format like this: Microsoft.Windows.Computer:ServernameFQDN to set the whole server into maintenance.

After upgrade to SP1 you get the following error.

error

So it does not find the monitor anymore.

Change the activity to this:

setmaintnew

The monitor entry needs to have this format now:
ServernameFQDN : Microsoft.Windows.Computer:ServernameFQDN

Now it should run successful.

Advertisements
Post a comment or leave a trackback: Trackback URL.

Comments

  • Adam Ladd  On February 28, 2013 at 12:55 am

    Good find. We will have to update our runbooks after we upgrade the IP to sp1.

    Could you post the logic behind your Get FQDN activity?

  • AndrewR  On March 24, 2013 at 10:31 pm

    Hi there,
    I too recently experienced this issue, so tried your fix, however still get the issue. I have SCOM 2012 SP1, SCORCH 2012 SP1 and have only recently installed and configured it.
    In an attempt to resolve, I have since removed any reference to ServernameFQDN and hard coded in the monitor field an actual computer Health Monitor, as selected by the interface into SCOM, ie “servername.domain.com : Micorosoft.Windows.Computer:servername.domain.com” which returns “Failed to convert property value to required type”
    Any ideas, I can confirm that SCORCH is initiating connections with SCOM as I can see within the event logs an entry for the specific user account.

    PS I really like your idea of the SCCM Maintenance Window tied in with the SCOM Maintenance Mode, which I will explore for our next patch cycle.
    Cheers
    Andrew

    • opsmgrtipps  On April 11, 2013 at 2:07 pm

      Hi Andrew, I can only assume that the path is not correct. So have you tried to set the windows computer into maintenance mode or your special health monitor? If you have only tried the health monitor, then please try the windows computer class. Otherwise, can you send me the name (not the display name) of the monitor you want to set into maintenance?

      Regards
      Natascia

      • AndrewR  On April 11, 2013 at 10:56 pm

        Hi Natasha,
        Thanks for your reply, I was on leave for about ten days and when I returned with a fresh set of eyes, I realised that I hadn’t used the published values but had manually entered them in. After amending to published values it worked. Apologies for not removing the post, however the comment was still in “to be reviewed”
        Thanks again, and I will be looking to try your SCCM Maint Window later this week.
        Cheers
        Andrew

  • klaus  On April 26, 2014 at 8:41 am

    Hi,
    I don’t understand why MS does not include a field for entering the ID of an object to start/stop the Maintenance mode. However, I just required the “Start Maintenance Mode” Activity to set a distributed app and a websphere application server instance (which is not linked with the server itself). And I did not find any documentation how to fill the field – only this one with Windows Computer.

    So I’ll post my result on how to get the value which needs to be entered within the “Monitor” field:
    (PowerShell – Use “Activities > System > Run .Net Script > Type: Powershell)
    import-module operationsmanager
    $object= Get-SCOMMonitoringObject -displayname “<desired object displayname";
    # or use the ID instead:
    # $object = Get-SCOMMonitoringObject -ID "”;
    $name = $object.displayname;
    $fullname = $object.fullname;
    $monitor = $name + ” : ” + $fullname

    Then put $monitor within “published data” and you can use it directly in the “Start Maintenance Mode” Activity.

    Best Regards
    Klaus S
    Austria

    • opsmgrtipps  On April 28, 2014 at 8:36 am

      Hi Klaus,

      Thank you for your great feedback!

      Greetings from Germany

      Natascia

Trackbacks

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

%d bloggers like this: