When the Release Candidate of SCOM 2012 was available there were some issues with it. One of those issues was related to the Resource Pools. They were rather sensitive resulting in an unstable MG. Microsoft got a lot of feedback for it and released a quick fix KB article for it, KB2714482.
In this KB article one was told – when experiencing the Resource Pools issue with the Release Candidate version of SCOM 2012 – how to add a registry key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HealthService\Parameters\PoolManager) with certain values, modifying the release request time and resource pool latency.
So far so good. But now the BAD news.
KB2714482 is a long time ago pulled by Microsoft, almost at the same time SCOM 2012 went RTM and became general available. And there is a reason for it. The quick fix isn’t required any more since the SCOM 2012x versions after the Release Candidate contain a fix for it.
So now this quick fix works in a negative manner, resulting in unexpected and unstable behavior of the availability and recovery time of the Resource Pools.
I check on every customers location the SCOM 2012x Management Servers for the presence of this key, make a export – and after having a talk with the customer – I remove the registry key. Also reboot the servers so they start clean and with the normal configuration.
So far I have seen the SCOM 2012x become much more stable and reliable.
My two cents
Check your SCOM 2012x Management Servers for the presence of this key. When found, make an export of it, remove the key and reboot your servers. Yes, the Resource Pools will turn up grey for some time (sometimes up to 20 minutes, depending on the size and monitoring load). However afterwards your SCOM 2012x Management Servers will be okay and the overall availability and stability of your MG will improve.