NOTE: If you experience a situation where removing an Operations Manager server from the All Management Servers resource pool causes the server to become grayed out see http://support.microsoft.com/kb/2853431.
As outlined in the “SC12_OpsMgr_Deployment” on page 12: (http://www.microsoft.com/en-us/download/details.aspx?id=29256) there is a slight issue with this as it’s currently written.
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.
This is a issue because the All Management Servers pool cannot be changed to manual membership through the user interface to allow removal of a management server from that resource pool.
Key points on manual and automatic resource pool membership:
1) You can convert the membership for AD Assignment Resource Pool and Notifications Resource Pool to manual, and then remove the Network MS servers.
2) The All Management Servers Resource Pool cannot be set manual in the User Interface. Per the RMSe article at: http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/91085/Default.aspx this resource pool provides: Group calculation, availability, dependency monitor, health aggregation and database grooming.
3) Good technical information on how to set resource pools from this perspective is available a http://technet.microsoft.com/en-us/library/hh920228.aspx (a subset of this text is below):
“Set-SCOMResourcePool [-ResourcePool] <ManagementServicePool> [-EnableAutomaticMembership] <Boolean> [-ComputerName <String> ] [-Credential <PSCredential> ] [-PassThru] [-SCSession <Connection> ] [-Confirm] [-WhatIf] [ <CommonParameters>]
Enables automatic membership for the resource pool. When set to $True, the resource pool contains all management servers, and membership in the pool is automatically managed. When set to $False, the resource pool can contain management servers, gateway management servers, or both, and membership in the pool is manually managed.
If the value is changed from $True to $False, the membership of the pool remains the same until manually updated.
If the value is changed from $False to $True, all members of the pool are removed, and then the pool is automatically re-populated with all management servers. The resource pool will be automatically updated as management servers are added and deleted from Operations Manager. This process can take some time to complete.”
So how do we change from automatic to manual (and back) via PowerShell for each of the three built-in Management Pools?
Configure Notifications Resource Pool to be automatic:
get-scomresourcepool –DisplayName “Notifications Resource Pool” | Set-SCOMResourcePool –EnableAutomaticMembership 1
Configure Notifications Resource Pool to be manual:
get-scomresourcepool –DisplayName “Notifications Resource Pool” | Set-SCOMResourcePool –EnableAutomaticMembership 0
You can also change this powershell scirpt to change others such as “All Management Servers Resource Pool” below:
Configure All Management Servers Resource Pool to be automatic:
get-scomresourcepool –DisplayName “All Management Servers Resource Pool” | Set-SCOMResourcePool –EnableAutomaticMembership 1
Configure All Management Servers Resource Pool to be manual:
get-scomresourcepool –DisplayName “All Management Servers Resource Pool” | Set-SCOMResourcePool –EnableAutomaticMembership 0
Configure AD Assignment Resource Pool to be automatic:
get-scomresourcepool –DisplayName “AD Assignment Resource Pool” | Set-SCOMResourcePool –EnableAutomaticMembership 1
Configure AD Assignment Resource Pool to be manual:
get-scomresourcepool –DisplayName “Ad Assignment Resource Pool” | Set-SCOMResourcePool –EnableAutomaticMembership 0
What situations require these types of changes to the resource pools?
1) Network Monitoring Management Servers should be removed from the default pools per Microsoft documentation.
2) The Orchestrator server requires the Operations Manager Management Server to be installed for the OpsMgr 2012 Integration Pack.
3) This may also apply for Management Servers which are dedicated to a specific Operations Manager function such as monitoring Linux/Unix systems or Veeam collectors which are installed on Management Servers.
Thank you to Paul Johnson for bringing this issue to my attention and for his help mapping out what situations these configurations would be relevant in!