How does Advisor work when integrated into Operations Manager?

The following is a look into the Advisor integration in Operations Manager 2012 R2 in terms of what it adds to Operations Manager for the following:

  • Management Packs
  • Classes
  • Monitors
  • Rules
  • Views
  • Alerts
  • Where is Advisor information stored in the registry?

Management Packs:

The Advisor management packs are easy to identify using the keyword “Microsoft System Center Advisor” as shown below and used throughout this blog post. The management pack list below includes both the normal Advisor functionality built into Operations Manager 2012 R2 plus the new Advisor functionality currently in preview release (check it out at http://preview.systemcenteradvisor.com )

Classes:

The relevant classes can be seen in the monitoring pane, discovered inventory, and looking for Microsoft System Center Advisor.

Monitors:

The relevant monitors can also be identified by using the same keyword (Microsoft System Center Advisor) in the authoring pane, management objects, monitors.

Rules:

The relevant rules can also be identified by using the same keyword (Microsoft System Center Advisor) in the authoring pane, management objects, rules.

Views:

There is a single folder (System Center Advisor) within the monitoring pane which provides both the Active Alerts and the Advisor Health State views shown below.

Alerts are available in the Active Alerts view as shown below. In a later blog post I will review these alerts and if there were beneficial in my environment.

It’s interesting to note that all alerts in advisor come from the same rule which is shown below.

 

Where is Advisor information stored in the registry?

Here’s where the registry key is:

Advisor information is storted on the management server in: HKLM\SOFTWARE\Microsoft\System Center Operations Manager\12\Advisor.

 

Summary: Hopefully this blog post has provided some insights into how Advisor actually integrates into Operations Manager to make it easier to work with Advisor once you have it integrated into your Operations Manager environment.

3 thoughts on “How does Advisor work when integrated into Operations Manager?

  1. Mike

    Word of warning with Advisor. Once you register Advisor in SCOM 2012R2 you have NO nice option to disable the service if it causes issues.

    I made the mistake of testing this with my production SCOM on a select group of servers and had some issues not only with those servers but other servers outside the selected group.

    The agents in the group went Grey and needed the monitoring service re-started. One of the management servers is complaining that it needs to load a Management Pack for VMM. We don’t use VMM so the MP is not part of out SCOM environment.

    Error 1:
    Found error in 2|Microsoft.IntelligencePacks.StorageDataCollection|7.0.9275.0|Microsoft.IntelligencePacks.StorageDataCollection|| with message:
    Could not load management pack [ID=Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library, KeyToken=31bf3856ad364e35, Version=3.1.6011.0]. The management pack was not found in the store.
    : An error occurred while loading management pack ed969e31-a8dc-b6d9-bc99-94dd55ab154d from the database

    Then some of the servers outside of the test group started getting these errors:

    Initialization of a module of type “System.PublishDataToEndPoint” (CLSID “{D407D659-65E4-4476-BF40-924E56841465}”) failed with error code The system cannot find the file specified. causing the rule “Microsoft.SystemCenter.CollectFlowDataToCloud” running for instance “Server” with id:”{8CA21FF1-B7AA-4778-23C9-2CD47682CF9D}” in management group “MG”

    Causing the monitoring service to crash unexpectedly.

    Sorry for the negative rant.

    Thanks again for this detailed information. I just wish they had an option to back out if you make a mistake like i did and didn’t use a test environment first.

    http://thoughtsonopsmgr.blogspot.com/2014/07/scom-2012-r2-sca-integration-when-not.html

    Any advise on this situation would be greatly appreciated. To date i can’t see any way to just disable the service and all that it brings. When i have enough time i will revisit this feature as i think it has awesome potential.

    Thanks,

    Mike

  2. Mike

    Hi Cameron,

    While reading your post in some more detail i noticed you mentioned that built in and new advisor MP’s

    “The management pack list below includes both the normal Advisor functionality built into Operations Manager 2012 R2 plus the new Advisor functionality currently in preview release”

    Just wondering if removing the new MP’s added when Advisor is registered would be the best way to remove the implementation?

    I didn’t realize so many addition MP’s were added when you register Advisor.

    I’m still a bit green around some of the implication of removing and adding MP’s to SCOM. If I delete an MP is it likely to cause issues with the monitors loaded to that agent or cause the health service to crash?

    Thanks in advance and appreciate all the information you provide to the community

    Thanks,

    Mike

  3. Cameron Fuller Post author

    Hey Mike, removal of the management packs will likely not work as Advisor appears to automatically re-add them. How about removing the advisor agent from the clients? The option to delete a client from advisor appears to exist in the management pane within the advisor section of the interface.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.