Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does anyone have a checklist for what needs to be done when moving a 2003 mailbox to 2010?

I'm considering enabling circular logging, checking disk space, and possibly disabling AV to speed up the transfer.

Are there special things I need to consider for resource accounts, delegates, service mailboxes, etc?

share|improve this question
up vote 2 down vote accepted

I haven't had to "consider" too much in the E2K3 to E2K7 / E2K10 migrations I've done, personally. I've basically just left things as-is and moved the mailboxes.

If you're moving a ton of data I suppose you might enable circular logging on the destination server-- gauge your free disk space and decide if that's something you need to do. I've found that my E2K10 servers are typically so much more I/O efficient than the E2K3 servers I'm migrating from that leaving antivirus enabled on the destination server makes no difference. On the source server you might see a speed improvement, but I have no specific metrics to report.

None of my Customers have had problems with resource accounts after migrations so I haven't done anything special (both in E2K3 to E2K3 migrations nad E2K3 to E2K7 / E2K10 migrations). All mailbox access is supposed to dereference the mailbox store through the homeMDB property of the Active Directory object so the physical storage location of the mailbox should be irrelevant (and it has been in my experience).

share|improve this answer

Check through this article and this one.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.