I wont speak to the Exchange objects - other than to my knowledge SCOM doesn't use or place anything there, and this is a default hidden container present under the root of the domain when exchange is present. It would appear someone made a mistake and dragged and dropped this container. I'd coordinate any changes with your exchange and AD specialists.
As to the momlatencymonitors - this was created my the ADMP in MOM2005, or a VERY early version of the ADMP for SCOM 2007. We don't use it anymore and it is totally safe to delete the entire container. OpsMgrLatencyMonitors is the current container for AD replication. In the latest ADMP rewrite which just shipped a few days ago - I am not sure we even use this anymore.... I need to review how we are handling it. From: [email protected] [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Friday, December 23, 2016 12:46 PM To: '[email protected]' <[email protected]> Subject: [msmom] Safe to Delete 'MOMLatencyMonitors'? We are currently on SCOM 2012 R2. We do not have any remaining SCOM 2007 or MOM 2005 servers on the domain. Under the MOMLatencyMonitors container there is a sub-OU titled with an old DC hostname that has since been demoted and deleted from AD. There is also an OU titled Microsoft Exchange System Objects, which I think someone incorrectly moved under the MOMLatencyMonitors container, though we do have the Exchange MP installed. But reading through the notes there is nothing about such an OU being created. I was hoping for a sanity check via the OpsMgr experts. I want to move the Microsoft Exchange System Objects outside the MOMLatencyMonitors container, then delete the MomLatencyMonitors container. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
