Mind you all these steps take place AFTER the new SCOM Management Server is installed. Also good to know, this To Do List is based on OM12 SP1.
- Antivirus exclusions
Please make sure the new SCOM Management Server uses the same AV policy as the other SCOM Management Server. So the correct folders and processes are excluded from AV scans. Check KB975931 for more information.
When using Gateway Servers and/or monitoring servers using certificates, make sure the new SCOM Management Server gets a valid certificate as well. And don’t forget to configure it properly.
Make sure all the firewalls, either running on your Windows Server hosting the new SCOM Management Server role and the dedicated network firewalls, accept the traffic coming from the new SCOM Management Server. Also read this posting of my fellow MVP buddy Bob Cornelissen since it might prevent a lot of hassle.
- Resource Pools
Make sure the new SCOM Management Server is added to the proper Resource Pools so it adheres to the original design.
- UNIX/Linux monitoring
When monitoring UNIX/Linux systems and the new SCOM Management Server will become a member of that Resource Pool, make sure it has the proper certificates in place. Not only its own certificate but also the certificates of all the other Resource Pool members. Also the other Resource Pool members must get the certificate of the new SCOM Management Server as well. Kevin Holman wrote an excellent posting about it, to be found here. Look for the header Configure the Xplat certificates.
- Special MPs
Sometimes special MPs are in place, requiring additional actions on the new SCOM Management Servers. Examples are the NetApp MP, SharePoint 2013 MP.
- Console extensions
Some third party tools extend the SCOM Console, like Savision Live Maps. So install those Console extensions on the new SCOM Management Servers as well.
This covers it all and enables you to enroll successfully an additional SCOM Management Server to an existing MG without bumping into issues after it.