When you add a member to a pool - all "Top Level Managed Entities" (TLME) are re-distributed.
This means when you add a member to a Cross Plat pool, the new server will begin hosting around half of the monitoring resources. The new member added to the pool requires that it is trusted by (and trusts) the Xplat cert that did the original signing of the xplat agent. This is covered here: https://blogs.technet.microsoft.com/kevinholman/2012/03/18/deploying-unixlinux-agents-using-opsmgr-2012/ I'd guess monitoring breaks, because you have not imported the cert from the other pool member, and created a xplat cert for the new member and imported it on the existing one, which is a requirement with multiple xplat pool members. From: [email protected] [mailto:[email protected]] On Behalf Of Rogee Fe de Leon Sent: Wednesday, May 24, 2017 1:00 PM To: [email protected] Subject: [msmom] Cross Platform Resource Pool question We have 2 Redhat servers that are monitored through SCOM via the Cross Platform Resource Pool (We set this up 2 years ago). The Resource pool has one management server. We are trying to rebuild this management server so our plan is to add another management server to the pool and then remove the original one. The problem we are experiencing is that as soon as we add the second management server to the pool we start getting issues with the monitoring of the Redhat servers in that it just stops working (so at this point we have both management servers in the pool). I am just looking for guidance on whether or not we are missing some step that we forgot about that has to be done on this additional management server. I assumed that because we are using the Run As Configuration account for Linux, that there would be no specific configuration that we had to do on the additional management server. Thanks, Rog Fedeleon
