Introduction
Often times in Exchange Support we get cases reporting that the size of one or more Exchange databases is growing abnormally. The questions or comments that we get will range from “The...
Updated Apr 28, 2020
Version 4.0
Blog Post
This would all be so much easier with a simple, intuitive Windows-based admin console.
For example, I can run the script in mode 1 to export into an XML, but if I want to run mode 2 I have to type in the whole wonky path with spaces and everything to find the XML file it just saved? Then to run mode 3 we also have to type in the entire damn path all over again.
Can someone, ANYONE on the Exchange team please explain to me why this has not been integrated into the EAC yet as a standard gui tool? Why can we not just simply browse to the file or have that file cached?
It seems like everything in Exchange 2010 was perfect and now everything that was an automated process has been stripped out of Exchange 2013 and we now are forced to use command line manual methods to perform tasks? This script only captures the top 25 mailboxes making it COMPLETELY USELESS IN LARGE ORGANIZATIONS! It doesn't even offer an HTML view. We have to run yet ANOTHER command to convert to CSV? Who thought of this garbage?
It's all command line junk that has been very poorly thought out. I am so disappointed in Exchange 2013 even after update 4 that I could scream. EAC and OWA both look terrible compared to Exchange 2010 and now even the tools require multiple manual steps with complex typing involved and are beyond limiting in scope. It wasn't enough that you removed most of the toolbox, you had to make the new methods suck too.