Remote mailbox move 2010 with added complications....

Posted on 2011-10-18
Medium Priority
Last Modified: 2012-05-12
OK, heres a good one for the EXPERT EXPERTS....

Here in the NHS there is NO root forest, .nhs.uk does not exist in the AD sense.  Each "NHS Trust" creates a new domain that is the forest root.

So when Trust1 set up AD for the first time they set up a forest of trust1.nhs.uk. When Trust2 set up they set up a new forest of trust2.nhs.uk. All with NOBODY in either trust knowing anything about the other and there is no need for any communication between the 2.


Now I am asked to visit trust1 and try and do a cross forrest migration and move users and mailboxes from trust1 to trust2.  When I try, after creating the users manually in trust2 along with coppies of all the correct attributes, msExch..... cn, etc...  It fails with an error of

Missing switch/Parameter: RemoteOrganizationName

Or words to that effect, im OOF now but will correct if its slightly different later.  That parameter is listed as being a microsoft internal use switch.

Any idea how to proceed? Is the fact that both domains/forest end in .nhs.uk going to be a BIG problem?


Question by:Neil Russell
  • 3
  • 2
LVL 37

Author Comment

by:Neil Russell
ID: 37032452
Not even Leew? :P
LVL 29

Expert Comment

ID: 37044616
after creating the users manually in trust2 along with coppies of all the correct attributes, msExch..... cn, etc...

I really don't know what    "all the correct attributes, msExch..... cn, etc..."    means.

If the Trust2 Domain/Forest already has an Exchange Server then the user would be associated with that Exchange and it would be creating a clean new empty mailbox,....is that what you are doing?
LVL 37

Author Comment

by:Neil Russell
ID: 37047649
We first create a new user in the target forest and follow the MS Technet guide on pre move set up as detailed in.....

LVL 29

Accepted Solution

pwindell earned 2000 total points
ID: 37048007

If it we me,...granted, it's not me,...but if it were me,...I wouldn't even worry about an Exchange Migration.  I would just create new fresh empty mailboxes on the new system.  Then I would export the mail from the old boxes into PST files,...then import the PSTs into the new mailboxes afterwards independently.  The users will be completely functional with the new empty mailboxes, they just won't be able to see their "old" mail until you get that moved,...so you deal with the most critical users first.  There may be some users with no old mail or very little old mail that they probably don't really need anyway and they can just let it die.
LVL 37

Author Closing Comment

by:Neil Russell
ID: 37171637
Were talking of 1000's of users unfortunately.
Were looking at several alternatives and talking to Quest as one possible anser. Another thought is creating a third domain.local forest and doing a three way migration but I dont fancy that :P

I'll close the question as EE keeps on reminding me its an open question but i'll post back at some point with further findings.

Thanks for your musings anyway :D


Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

You finally migrated Public Folders to Office 365, decommissioned the Public Folder mailbox database and since then, when you send an email from on-premise to mail-enabled Public Folders, you get the following error: "Misconfigured public folder mai…
In this article, I will demonstrate that how to do a PST migration from Exchange Server to Office 365. This method allows importing one single PST, or multiple PST's at once.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

615 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