[Last Call] Learn how to a build a cloud-first strategyRegister Now


Exchange 2003 Exchange 2010 transition servicing multiple domains

Posted on 2011-10-27
Medium Priority
Last Modified: 2012-05-12
I have an Exchange 2003 SP2 server running on Windows 2003 which is not a DC.  I have 4 sites, each has its own domain,  all four domains are in the same forest with trust relations setup.  The domains are branch1.abc.com, branch2.abc.com,branch3.abc.com, branch4.abc.com.  The Exchange 2003 server resides at site1 (branch1.abc.com) and houses mailboxes for the other 3 sites/domains as well.  I have installed Exchange 2010 on Windows 2008 Standard R2 on a new server residing at site1 (branchh1.abc.com).  I was able to move all mailboxes for the branch1.abc.com users to the Exchange 2010 server.  The users are able to access their mailboxes on the Exchange 2010 server without any issues.  When I try to do a local mailbox move on mailboxes who's users reside branch2.abc.com, I receive a message that says Exchange can't find a domain controller on branch2.abc.com.  I receive the same message when attempting to move mailboxes on the other domains as well.
Please let me know what I need to do to be able to move all the mailboxes to the Exchange 2010 server.
Question by:mseals
  • 2
LVL 14

Expert Comment

ID: 37043730
How are you moving mailboxes? I'm sure you have to use -remotelegacy

Have a look at this


Also have you started the MRS service? Do all your exchange 2003 servers and domain controllers have service pack 2?

Author Comment

ID: 37044569
I only have one AD forest.  What is MRS service?  The only Exchange 2003 Server has SP2 and all Domain Controllers are SP2.
LVL 14

Accepted Solution

Radweld earned 2000 total points
ID: 37044703
See I have done a few cross forest moves and followed the guidelines in this blog


You still need to copy AD accounts between domains (intra forests, this is actually a move), you can use ADMT for that (or FIM), you still need to prepare those MEU with the Exchange attributes that ADMT is incable of transfering using the script preparemoverequest.ps1 once these two steps are done you should be able to move your mailboxes between domains.

If you dont want to use ADMT to copy accounts, you can use the preparemoverequest script to creat a MEU for you however this is a new security principle with no sid history and you would lose all your mailbox delegation once the mailbox is moved.

Have a read of the blog and try some of the suggesitons.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question