I recently needed a script that would balance mailboxes between databases. Similar scripts exist, but I wanted one that specifically met all of my requirements. This script is very simple, but does exactly what I need. For now at least… My needs The ability to maintain the number of users across an Exchange 2010 DAG with up to 30,000 users. Size of the mailboxes wasn’t that important as there is only one quota across all mailboxes. The ability to exclude certain mailboxes, in my case Symantec Enterprise Vault Archiving Mailboxes. The ability for the script to be scheduled with ease. A lot of the scripts that exist, generate a “move list”, I didn’t want that. E-Mail status reports after processing. Logic The script will discover the number of users, then discover the number of databases. It will then find the optimum number of users per database and create a move request ensuring that all but one of the databases contain the same number of users. It will then send an e-mail det
I haven’t posted anything in a while, sorry about that. I’ll try to post more often. :-) We had a call recently regarding users changing their expired password whilst logging on to a computer attached to another domain. Unfortunately or fortunately, depending on which way you look at it, almost all of our clients are Windows XP, so our initial response to these sort of queries is to ask the Local IT Administrator to fully patch the client experiencing the problem. Taking an XP client to SP3 usually solves most of the problems listed on TechNet for this particular error. Unfortunately, patching didn’t work in this instance, and we weren’t sure why this was happening, so we logged a call with Premier Support. One of the articles we had missed in our initial investigations was highlighted to us by Microsoft - http://support.microsoft.com/kb/555340/en-gb The article explained that we needed to reverse a change that was made on our Domain Controllers by the application of Server 2003 Ser