Not only does Microsoft provide you with a spectacular tool (Tzmove.exe), not to be confused with (Tzmove.exe) that you can distribute to all of your brilliant end users and ask them to run on your behalf.

(This works so well because as we know, end users just love running tools to fix IT problems that really should be addressed at the server level, and of course they fully understand what has to happen and why things are broken. Yes, delegating IT problems down to the user level is always the best move).

The best they could do from an Exchange administrator perspective is this:

- Create a client fix tool.

- Create absolutely the most convoluted way to take that ‘client’ based tool and script it to run on one machine, mailbox after mailbox. (That is in fact what they are doing).

- Exchange security issues as side, this should be fixable at the server level, without pretending to be a MAPI client for crying out loud.

Remember when Microsoft released the Windows NT domain, and promised us Single point of administration? This is not what I had in mind, if I wanted to script client tools to do things in bulk across my organization, we’d still be running DOS.