I received from feedback from a colleague of mine at Catapult (Paul Johnson) about an issue he has identified when UR2 is installed. The summary is that in UR2 all management servers must be members of the All Management Servers Resource pool even though it is documented to remove management servers which are dedicated to Unix and Network monitoring functionality.
The details of the situation are below:
Why to remove the Unix & Network management servers from this resource pool?
As outlined in the “SC12_OpsMgr_Deployment” on page 12:
Network monitoring in System Center 2012 – Operations Manager requires its own separate resource pool.
Create a resource pool dedicated to network management; add dedicated management servers into the newly created resource pool, then remove the dedicated management server from any other resource pool.
After installing RTM & UR1:
The All Management Server Resource Pool was set to manual from automatic using the PowerShell scripts at the end of this blog post.
The Unix & Network Device Resource Pools were populated with the specific management servers required.
These Unix & Network Device management servers were then removed from the All Management Servers Resource Pool.
This process worked as expected, until UR2 was installed.
After installing UR2:
Numerous alerts about this All Management Server Resource Pool membership were generated in Operations Manager.
The only way to stop the alerts was to the Unix & Network management servers back into the All Management Server Resource Pool
This resolved the alert issues, but does not resolve the underlying issue of having Unix & Network device focused management servers still members of the All Management Servers Resource pool.
Thank you to Paul Johnson for identifying this issue and letting me know the details which were occurring!
Additional reading on this topic:
Manual and automatic resource pools: https://www.catapultsystems.com/cfuller/archive/2012/07/24/automatic-and-manual-resource-pools-in-operations-manager-2012-scom-sysctr.aspx