none
Advisor Connector Enable Status monitor : Failed to enable Advisor Connector RRS feed

  • Question

  • "This computer has already enabled the Advisor Connector in a different Management Group. The Advisor Connector only supports one OM Management Group"

    I have this alert on my 2 Exchange 2010 CAS after adding them to Advisor. I only have one Mgmt Group . The agent is online, healthy. Any idea on where I start to troubleshoot this?

    Wednesday, November 26, 2014 12:44 PM

Answers

  • Daniele,

    Sorry I was away for a couple of days. As I said in my initial post, there is only one Mgmt Group and the agent properties in control panel point to that one. There are no stale ones visible. 

    The only thing I can think of that they were once part of another older non-Azure SCOM Advisor version that we tried out. But I can't find anything that points to that.   

    I suspect you had installed the standalone/old Advisor setup?

    If that's the case, yuo should find and UN-install “System Center Advisor” on the agent, and nuke the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCenterAdvisor

    If that is NOT the case, and Only SCOM-integrated Advisor was in the picture (I don't know how you got in that state), then it could mean that those agents have been previously opted in from another management group, and not opted out. The error you have appears when the registry value ‘SOFTWARE\Microsoft\System Center Operations Manager\12\Advisor\RegisterToManagementGroup’ exists and has a value that is different from the management group id that he is now trying to optin from.

    If that's the case, you can opt-out the agent by deleting some regkeys and restarting the healthservice (which is what we do in code when agents are opted out).

    Delete the following and restart healthservice

    SYSTEM\CurrentControlSet\services\HealthService\Parameters\Management Groups\AdvisorMonitorV2 node and subtree

    SYSTEM\CurrentControlSet\services\HealthService\Parameters\Registered Connectors\{A052BD1A-7DDC-4BB1-B9F8-CEA9F31F61E7} node and subtree

    SOFTWARE\Microsoft\System Center Operations Manager\12\Advisor\RegisterToManagementGroup value

    HTH

    • Proposed as answer by Daniele Muscetta Tuesday, December 2, 2014 8:18 PM
    • Marked as answer by BYODre Wednesday, December 3, 2014 10:16 AM
    Tuesday, December 2, 2014 8:18 PM

All replies

  • Is it possible that the agent was previous used with another management group and is still multi-homed?

    Check in control panel -> Microsoft monitoring agent. It will show all the management groups configured on the agent. You might need to remove 'stale' ones.

    • Proposed as answer by Daniele Muscetta Tuesday, December 2, 2014 12:31 AM
    • Unproposed as answer by BYODre Tuesday, December 2, 2014 9:01 AM
    Thursday, November 27, 2014 6:53 PM
  • Daniele,

    Sorry I was away for a couple of days. As I said in my initial post, there is only one Mgmt Group and the agent properties in control panel point to that one. There are no stale ones visible. 

    The only thing I can think of that they were once part of another older non-Azure SCOM Advisor version that we tried out. But I can't find anything that points to that. 

    I do see an Active Directory Management Pack Helper Object (1.1.0) and Microsoft Monitoring Agent (7.1.10184.0) under programs and features.

    Thank you for your help.

      

    Tuesday, December 2, 2014 9:23 AM
  • Daniele,

    Sorry I was away for a couple of days. As I said in my initial post, there is only one Mgmt Group and the agent properties in control panel point to that one. There are no stale ones visible. 

    The only thing I can think of that they were once part of another older non-Azure SCOM Advisor version that we tried out. But I can't find anything that points to that.   

    I suspect you had installed the standalone/old Advisor setup?

    If that's the case, yuo should find and UN-install “System Center Advisor” on the agent, and nuke the registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCenterAdvisor

    If that is NOT the case, and Only SCOM-integrated Advisor was in the picture (I don't know how you got in that state), then it could mean that those agents have been previously opted in from another management group, and not opted out. The error you have appears when the registry value ‘SOFTWARE\Microsoft\System Center Operations Manager\12\Advisor\RegisterToManagementGroup’ exists and has a value that is different from the management group id that he is now trying to optin from.

    If that's the case, you can opt-out the agent by deleting some regkeys and restarting the healthservice (which is what we do in code when agents are opted out).

    Delete the following and restart healthservice

    SYSTEM\CurrentControlSet\services\HealthService\Parameters\Management Groups\AdvisorMonitorV2 node and subtree

    SYSTEM\CurrentControlSet\services\HealthService\Parameters\Registered Connectors\{A052BD1A-7DDC-4BB1-B9F8-CEA9F31F61E7} node and subtree

    SOFTWARE\Microsoft\System Center Operations Manager\12\Advisor\RegisterToManagementGroup value

    HTH

    • Proposed as answer by Daniele Muscetta Tuesday, December 2, 2014 8:18 PM
    • Marked as answer by BYODre Wednesday, December 3, 2014 10:16 AM
    Tuesday, December 2, 2014 8:18 PM
  • Daniele,

    Many thanks for your excellent and well documented help. Both servers were part of a SCOM poc (and only these 2 were added as a test to the integrated advisor part) and not opted out well before migrating (mea maxima culpa).

    Deleting the regkeys and restarting the service solved our problem.

    Cheers,

    André

    Wednesday, December 3, 2014 10:26 AM