tag:blogger.com,1999:blog-4414432572587218573.post1425781042232162038..comments2023-05-06T15:20:16.638+02:00Comments on Thoughts on Azure, OMS & SCOM: HELLO Exchange 2013 MP, GOODBYE Correlation Engine And Much More…Marnix Wolfhttp://www.blogger.com/profile/09487479325587450184noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4414432572587218573.post-52061030643588922732013-05-15T19:42:25.680+02:002013-05-15T19:42:25.680+02:00How many of the MVP's got to see this MP befor...How many of the MVP's got to see this MP before it went public, and what feedback was given to them, if any, about this new MP? The reports in the Exchange 2010 MP are horrible, and the Exchange 2010 SLA one is flat out broken, never worked, isn't fixed. Reporting in SCOM (from the console) doesn't seem to add much value honestly, since many of them break over time, not sure that has changed with 2012 (doubt it). The fact no performance is captured is good and bad. Good because they often collect too much and it fills up your dw, BAD because if operators actually use the SCOM console to look at performance, then they are in a black hole now. What the Exchange TEAM needs to do now, is release addendum MP's that monitor specific components of Exchange and maybe even an addendum MP that does synthetic transactions. Build off the base mp. Knowing their history, and the fast dev cycles of MSFT technologies, I doubt this will ever happen. Seems to me they want to offer less, to make their cloud hosting solution seem like a better solution.Blakehttps://www.blogger.com/profile/14962350282494382085noreply@blogger.com