Not to add to some of the other criticisms which seem to have nothing to do with this specific post, but I am a bit confused as to why a nice guy reporting toolset that has all of these power shell capabilities built into it has not been introduced for Exchange 2013. We're forced to find these scripts on blogs such as this and then we have to hack them together to make a solution. I'm sure anyone competent on the Exchange product group could easily port this into a standard EAC toolset with very minimal effort. I also need to point out to the Exchange team that we've been begging for this kind of functionality ever since Exchange 2013 came out and while it's great to see this toolset finally available, it's not full baked yet and it should have been placed into the Exchange 2013 RTM bits from the get-go.