Have you ever wondered why, in Exchange 2010, you can create a new mailbox and you don't have to tell Exchange in what mailbox database it should be created? Or had an administrator in one departm...
Updated Jul 01, 2019
Version 2.0
Blog Post
This is very nice. Like others have said it would be good if it could take database size into account. I know there are existing scripts but still.
As for scoping it, I agree that you don't always want to put everyone who works together on the same database or servers (although if you do your DAGs right and have some mature operations procedures this shouldn't matter much.) But the scoping here is based on the abilities of the IT admin. In large orgs with decentralized IT, you as the master messaging admin may want to give certain departments their own databases or servers so that manage it without affecting the rest, and of course so they can be responsible for their own storage and server costs. Depends on the org.
As for scoping it, I agree that you don't always want to put everyone who works together on the same database or servers (although if you do your DAGs right and have some mature operations procedures this shouldn't matter much.) But the scoping here is based on the abilities of the IT admin. In large orgs with decentralized IT, you as the master messaging admin may want to give certain departments their own databases or servers so that manage it without affecting the rest, and of course so they can be responsible for their own storage and server costs. Depends on the org.