Even though this KB article is already on the 8th revision level and tells you it applies to OM12 as well, much has changed. Not only in OM12 but also in the Exchange 2010 MP as well. So be careful when you read that KB article and don’t follow it blindly since some parts of it simply don’t apply anymore.
For instance, the ‘queue’ sizes which allow for better resource utilization (like Persistence Cache Maximum, Persistence Version Store Maximum and Persistence Checkpoint Depth Maximum) are changed in OM12 compared to SCOM R2. When simply adjusting those sizes according to the KB article, you would REDUCE the resource utilization on those OpsMgr 2012 Management Servers instead of improving it…
Another important one: this KB talks about the RMS but that role is no more in OM12. However, the Correlation Engine (introduced with the Exchange 2010 MP, hurray…) requires the OM12 Management Server which is also the RMS Emulator. So it’s unclear whether only that OM12 Management Server requires those adjustments, or all OM12 Management Servers.
IMO, this makes a MP which is difficult to master even a bit tougher as it already is.
Soon I hope to share some personal experiences in tuning the latest version of this MP in conjunction with OM12 and how it relates to the earlier mentioned KB article.
For now, just be careful and check and double check before you change ANYTHING.