Skip to content

SCOM 2012 Multihomed agents, how does it work?

March 14, 2012

If you need your server(s) to be managed by more than one management group you can multihome your agents. In SCOM 2012 there is an enhancement in how you can accomplish this. In older versions you needed to go to add/remove programs and adjust the installation for the SCOM agent or use the MOMAgent.msi. In SCOM 2012 you simply go to control panel and select Operations Manager Agent and add or remove a management group.

The main reason for using more management groups is to distribute monitoring requirements across different groups. Now this i want to testdrive!

I prepared a side-by-side installation SCOM 2012 and SCOM 2007R2 and multihomed an agent to connect to both management groups. The MG for SCOM 2012 is called RHEENEN and the SCOM 2007R2 is called Company. If i load the same management packs in both management groups and add different overrides in the management packs, will the agent still be able to send the right notifications to both management groups?

The answer is yes and here is why:

The first interesting thing to know would be how the overrides are applied.
As you might know, all management packs are distrubuted to the agents and are stored by default in “C:\Program Files\System Center Operations Manager\Agent\Health Service State\Management Packs” So if you apply an override you make an adjustment to, or create a new management pack. When you push the apply button, the change the management pack will be transported to the clients in a matter of minutes. The way the agent knows that the override is for a specific management group is configured in the OpsMgrConnector.Config.xml which is located by default in C:\program Files\System Center Operations Manager\Agent\Health Service State\Connector Configuration Cache\<management group name>. When you have two management groups configured there will be a folder for both.

If you open the xml file for the management pack you just modified you will find a RevisionID in the top line which will look something like this: 89f3c073-fc2a-2f96-b3d7-f0fe4b9eb5e2. Now this RevisionID will only be found in one OpsMgrConnector.Config.xml file which means the manaqement pack is applied only for this management group.

One more example. If you load the OS monitoring management pack for Windows 2008 in one environment it will get to the agent managed client. You will find the management pack name and a number. Now when i load the same management pack in the other environment (management packs for 2007 can also be used in 2012) it will also get to the agent managed client only with another number:

Al these tests are done in the same domain and kerberos authentication can be used. It will also be possible to use certificates and monitor your customers environment.

I hope this will make things a bit more clear. If you like this post please leave a comment!


From → System Center

One Comment
  1. eray permalink

    if the agent gets the same mp from both management groups, does it run the same mp for two times (one for the firt mg and one for the second mg also) at each period or it only run once and forward the same result to both of the management groups.?

Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: