tag:blogger.com,1999:blog-6805774517283898518.post120569224033412442..comments2023-07-13T08:53:21.744+01:00Comments on The IT Crownd: Exchange 2010 Management Pack Woes...AKhttp://www.blogger.com/profile/08191100505775131803noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6805774517283898518.post-2988200955011075772014-05-15T09:52:55.983+01:002014-05-15T09:52:55.983+01:00No. Sorry. I wish I had. I have since changed j...No. Sorry. I wish I had. I have since changed jobs so do not know if this is now fixed but when I left (2013) they were still running without SCOM monitoring Exchange 2010.AKhttps://www.blogger.com/profile/08191100505775131803noreply@blogger.comtag:blogger.com,1999:blog-6805774517283898518.post-7683903162801459912014-05-06T10:48:52.653+01:002014-05-06T10:48:52.653+01:00We are getting this on 2 of our production Exchang...We are getting this on 2 of our production Exchange 2010 boxes. Both are configured identically to servers in another site (VMWare, same configs). It's definitely the SCOM agent. Did you ever get to the bottom of this?Anonymousnoreply@blogger.com