Thursday, July 3, 2014

Different Resolution States in Consoles

After you’ve updated from SCOM 2007 to 2012 (or later) your console users might see different resolution states than you’ve configured see under Administration/Settings/Alerts.

That might be the case if you’ve used custom resolution states with IDs that are now used by the resolution states coming with the 2012 (or younger) version. Those resolution states are used in TFS WI sync scenarios to show the state of the related WI directly at the alert.

You can move to the settings and re-enter your display string for each resolution state. I recommend to take other IDs than the ones reserved for TFS (247, 248, 249, 250, 254) if that is possible in your environment.

Happy SCOM’ing,
Patrick

Read Full Post...

PowerShell Grid Widget Troubleshooting

A quick way to troubleshoot problems in the new PowerShell Grid Widgets and show the error directly in the dashboard:

image

Just implement the following lines into your existing widget script:

...
foreach ($object in $objects) {
 
$dataObject = $ScriptContext.CreateInstance("xsd://foo!bar/baz")
  $dataObject["Id"] = [String]($object.Id)
  $dataObject["..."] = [String](...)
  if ($error) {
    $dataObject["Error"] = [String]($error)
    $error.clear()
  }

  $ScriptContext.ReturnCollection.Add($dataObject)
}

The $error.clear() cleans up the $error variable so that every line in your dashboard only shows the related errors.

The error column will disappear once no error has occurred and you switched to another view and back.

All information is provided "as is" without any warranty! Try in lab before. Handle with care in production.

Read Full Post...