Cross Forest Migration Guide – Exchange 2010 to Exchange 2010

This Migration Guide will help you to migrate mailboxes across forest

Its always people go confused when source and target forests are Exchange 2010, I have tried to explain as detailed a possible and covered one method

where “Running .\PrepareMoveRequest.ps1 first and then using ADMT to migrate the Sid History” of the users

Please share your feedback in comments , So that I can update the guide frequently

so lets go ahead

Step 1:

Have Trust in place across forests , In my Situation I created Two way Transitive Trust where I won’t get into any permission constraints

Good to know : We can limit permissions by going for different type of trusts

See –

How to Create Two way Transitive Trust – Windows Server 2008 R2

Step 2:

You need Active Directory Migration Tool to Get your User accounts migrated without any hassle, You can install it in either of the forests but , Have installed in the target forest , where I will be doing most of my work

See –

How to install ADMT 3.2 in Windows Server 2008 R2

Step 3:

If you are planning to Migrate the User account with SID – Which is recommended – where users will still have access to their old forest where they will be recognized like

access to file shares and permission groups . So I would always recommend to get your SID along with the Users

If you are planning to Migrate Users with Password that doesn’t happen by default , You have to Configure “Password Export Server” in the source domain

See –

How to Migrate Users Across forest (Cross Forest) using ADMT 3.2 with sid and Passwords

Step 4:

Enable MRS Proxy on the Source Client Access Server which is going to Facilitate the Remote move from the Source Forest,

I have described Enabling MRS proxy where version is Exchange 2010 Sp1 or later cause enabling in RTM version differs

See-

How to Enable MRS Proxy and Increase timeout In Exchange 2010

Step 5:

Ignore if you are not using a Self Signed Cert.

If you are using a Self Signed Certificate –Where Exchange servers won’t authenticate between each other

Because they won’t trust each of them

You got to Export the Cert from Source Exchange Server and import it on Target Exchange Server

Vice versa

See –

How to Export a Self signed Server Certificate and Import it on a another Server in Windows server 2008 R2

Step 6:

Check List

Now Trusts are in place
ADMT is installed on the Target DC
MRS Proxy is Enabled on the Source Forest Client Access Server
Admin User of the Target forest is a member of administrators group in the Source forest – Add vice Versa
If you are using Self Signed Cert – They have been Exported from the target and imported in source (vice versa)
If you are planning to migrate passwords as well – Password Export Service is Configured and PES service is Started in the Source Domain

Before starting, There are many methods to Move mailboxes across forest .I will go for the Recommended one .

let us call this method as “Running .\PrepareMoveRequest.ps1 first and then using ADMT to migrate the Sid History”

We will move one mailbox to get a Clear idea , Then we can go for Bulk Migration of mailboxes.

I always recommend to move few mailboxes . Test it as much as you can . they go for bulk migration

Step 7 :

Created a Test Mailbox – Mailbox1

Step 8:

First Store the Access Credentials in the Shell

Please don’t confuse yourself Here.

Am Running this on the Target Forest – $localCredentials Means the TargetForestCredentials

SourceForest – careExchange.in

TargetForest – TargetExchange.in

Please don’t forget to Type the DomainName\UserName (Note:If it fails with Error – Authentication Failed – Try Entering Domain.Com\Username ,.com or .local refers to your local domain)

$localCredentials = Get-Credential

$RemoteCredentials = Get-Credential

Means my Source Forest

Note : After Storing your Credentials – Do not Close Shell – You got to run the Future Command in the Same Power Shell Session

Step 9:

Now Preparing a Move Request

Browse your Exchange Management Shell into Scripts Folder in your Target Forest , Which will be in Exchange installation Location

.\Prepare-MoveRequest.Ps1 -Identity EmailAddress -RemoteForestDomainController FQDN of Source DC -RemoteForestCredential $RemoteCredentials -LocalForestDomainController FQDNofTargetForestDC -LocalForestCredential $LocalCredentials -TargetMailUserOU Distinguished name of OU in TargetForest –UseLocalObject -Verbose

Using –Verbose in the end of the Command

You can clearly see what are the Attributes its getting touched

Mail,Display name,Proxy address etc..

Now you can See a Disabled account which has been Created on the Specified OU

Step 10:

Now use ADMT to migrate the SID and Enable the Target Account which is “Mailbox1” in my Scenario

See-

How to Migrate Users Across forest (Cross Forest) using ADMT 3.2 with sid and Passwords

Now you can find the SID history of the account , Where you can confirm that you did things correctly

Now your AD account will get Enabled

Step 11:

Now your Account with SID and password as been moved, But still your Content of the mailbox hasn’t moved yet. Which is moved my a remote as below

Now moving the mailbox using a Remote move request

New-MoveRequest –Identity 'Mailbox1@careexchange.in' –Remote –Remotehostname 'sourceExchange.CareExchange.in'  -RemoteCredential $RemoteCredentials –TargetDeliverydomain 'targetexchange.in'

Now you can See a Remote move has been Completed

Now you won’t be able logon on the new forest directly as you required to change password as first logon

To avoid that situation

See-

How to Disable “User must change password at next logon” after cross forest move using ADMT 3.2

Open Adsiedit –Set pwdlastset to –1

or just login to a client machine and change the password at first logon

Great !! you able to login in Target Forest Success fully !!

Step 12:

To Move the Users in Bulk

See-

Cross forest Move Mailbox in Bulk – Exchange2010 to Exchange 2010

Step 13:

If you doesn’t want to share free/busy information as of now. Skip it

if you want to share Free/busy information between these forests. If source domain is always going to exist after migration . I would recommend to create Federation Trust which is free of service from Microsoft to share free busy information.

if you doesn’t want to go for Federation you can share free busy using below method

See –

How to Configure Cross forest Availability Service (Free/Busy,Auto discover) – Exchange 2010 to Exchange 2010

Step 14:

Please look into the below link for configuring Cross forest coexistence mail flow

How to Configure Cross forest connectors (Mail flow) Exchange 2010 to Exchange 2010

https://www.azure365pro.com/how-to-configure-cross-forest-connectors-mail-flow-exchange-2010-to-exchange-2010/

Happy Cross forest Migration !!

Hope I made as much simpler as I can !!

Thank you !!

152 COMMENTS

Michelle September 25, 2012 At 8:14 pm

We have purchased another company. We will need to keep their old active directory up so they can log into a propitiatory application for a while until we get fully integrated.
We both have Exchange 2010, we will be changing their email address domain as well as their logon usernames. What is the best way to go about this? Do we add their computers to the domain then move the mailbox and logon as them? What about their user profiles? Any recommendations are appreciated.

Satheshwaran Manoharan September 25, 2012 At 8:58 pm

Hi Michelle,

Will you be getting rid of the Active directory of the company you purchased ?
How many users are there ?
—
If its less amount of users – You can move them to your own Company – Move their AD accounts – and re Configure their Outlook to Outlook anywhere profiles for the time being.
–
Once all the applications are integrated you can rejoin the domain machines to your own domain

Jim Robert October 24, 2012 At 3:12 am

HI Satheshwaran,

Thanks for sharing these useful and step by step process to migrate mailboxes. A migration process is really complicated procedure and requires lots of planning , efforts and times. In our case, we used a program ( http://www.serversdatarecovery.com/exchange.html )and successfully migrated our 1600 mailboxes with full accuracy and quickly. It saved our a lot of time and efforts by giving an opportunity to move multiple mailboxes at a time.

Thanks
Jim

Charlespanth November 15, 2012 At 11:50 am

Hi,

Thanks for this knowledgeable advice in which you have shared the things regarding cross forest migration from exchange 2010 to 2010. I had a similar kind of problem and I read your blog and used the tool named Lepide Exchange Recovery Manager and it solved my problem easily.

mr. user November 29, 2012 At 5:03 pm

hello.

we also purchased a new company. Is it possible to keep the user account in Source Forest, but move only the mailbox to the Target Forest’s exchange Servers?

If so, What extra steps are needed?

- Satheshwaran Manoharan November 29, 2012 At 5:11 pm
  
  You will run only .Preparemoverequest.ps1 with an Extra switch of -LinkedMailUser
  and move the mailbox using New-Moverequest
  
Shabeer ahamed January 9, 2013 At 12:31 pm

After doing the mailbox move and updating the OAB, I still see the moved users as mail enabled contacts or users in the OAB. Even after updating the OAB, restarting the File distribution service, the icons for these users in GAL shows as contacts.

I waitied for 24 hours and still no luck. How to resolve this.

- Satheshwaran Manoharan January 9, 2013 At 1:03 pm
  
  How about OWA ? or Outlook in online mode ? Does that looks ok ?
  
  - Shabeer Ahamed January 9, 2013 At 8:13 pm
    
    It was an issue with OAB generation which we ahve solved it and it appears okay after that.
    
    But the new issue is that outlook profile in cache mode doesn’t receive e-mail after cross forest mailbox move. It says outlook data file cannot be accessed.It works fine in online mode.
    
    Either we have to reconfigure outlook profile or delete the ost file and resynchronize it.
    How to do it for bulk users?
    
    - Satheshwaran Manoharan January 10, 2013 At 8:01 am
      
      Yes It can’t reconfigure itself to the new user , You got to do it manually.
      
      Or you got to get in touch with a Group Policy Expert to Reconfigure it on Bulk.
      
      but machines will be joining in the old domain right ? so you planning to join to the new domain later ?
      
      and to use Outlook anywhere for the mean while ?
      
Cody March 12, 2013 At 2:50 am

If I wanted to migrate a separate forest into an existing forest and used this guide, would users maintain email addresses for both domains (source and target) and still have access to their email as the system performs a remote move? I’d think they would have access to email as it does a remote move (as it does with a local). I will have a need for the users from the source domain to receive email from the old domain name after everything is done.

The source domain as a windows infrastructure will go away but we will retain the domain for email routing purposes.

- Satheshwaran Manoharan March 12, 2013 At 3:22 am
  
  In that case . you have to move your mailboxes from Forest 1 to Forest 2 . but not the active directory accounts.
  Once you feel Migration is done. you have to move your AD accounts.
  
  –
  This procedure is different. for your requirement.
  
  http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
  
  Resource Forest
  Each mailbox in the Exchange forest must have a corresponding user in the account forest, which is granted access to logon to the mailbox. This is referred to as a “Linked Mailbox”.
  
  - Cody March 12, 2013 At 5:10 pm
    
    That doesn’t make sense to me. The last time I moved from one forest to another it was 2010 to 2007 and by default all of the old domain SMTP addresses and even the X400/X500’s stayed in place. The only way to get rid of them was manually. I still have users in my current forest with old SMTP addresses from an older domain. I didn’t have to break apart the migration for that.
    
    When the trust is in place, can’t I just add the source domain as a domain in the target domains “accepted domains” list in Exchange? Then can the source’s mx records be pointed to the target domains HUB?
    
    That document references a hybrid configuration with co-existence. Is that what you are referring to? Having enabled and disabled users and maintaining information in both domains?
    
    That resource forest method doesn’t sound like what I am in need of. We don’t want to maintain the other (source) domain. We will be moving everything as quickly as possible and in the order recommended by ADMT (groups in certain order, user/email accounts, and finally computer accounts, etc).
    
Cody March 12, 2013 At 5:26 pm

It seems there is a way to get this done without having to use a different method —
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27519022.html

I should be able to use cross-forest connectors.

Have you used this method?

- Satheshwaran Manoharan March 14, 2013 At 6:09 am
  
  I am not a member of Experts Exchange. I won’t be able to view it !
  
  - Cody March 15, 2013 At 7:29 pm
    
    If you scroll all the way down you can always read the posts. I’m not a member either.
    
    - Cody March 15, 2013 At 7:30 pm
      
      It references this:
      http://technet.microsoft.com/en-us/library/bb123546(v=exchg.141).aspx
      
      Cross forest connectors/communication
      
ROBIN March 23, 2013 At 7:05 pm

thanks a lot for posting this article .. superb one

- Satheshwaran Manoharan March 26, 2013 At 9:21 am
  
  Thank you for your comments Robin
  
Ram Reddy April 2, 2013 At 5:05 pm

This is very very usefull document. Thanks for your post

- Satheshwaran Manoharan April 3, 2013 At 1:00 am
  
  Thank you for your Comments Ram
  
Cody April 13, 2013 At 3:10 pm

Just wanted to let you know the cross-forest exchange connector works great. I have two separate forests with a bi-directional transitive trust in place. I setup that connector and if we move a user from the one forest into the one we are migrating to, they keep their email address and can still receive mail at that address.

- Satheshwaran Manoharan April 16, 2013 At 1:38 am
  
  Thanks for the update Cody !
  
Loon April 15, 2013 At 10:27 pm

Great job on this process and sharing with the greater community !

Your order is this:

1 – prepare mailbox
2 – Run ADMT on account for SID migration
3 – Migrate mailbox

I found that with a target Exchange 2013 forest from a source Exchange 2010 forest migration worked out in this order:

1 – prepare mailbox
2 – Migrate mailbox
3 – Run ADMT on account for SID migration

It seems that using the built in Exchange 2013 GUI migration tools, I can’t migrate the mailboxes after they have had ADMT run on them, probably because ADMT turns them into full blown Exchange mailboxes.

Can you add to this ?

Cheers !

- Satheshwaran Manoharan April 16, 2013 At 1:48 am
  
  Hi Loon,
  
  I haven’t started testing cross forest migration with Exchange 2013 yet.
  
  Once I post an article. I would add to this soon.
  
  thank you for your comments. It will be useful for me.
  
  - Lukas October 4, 2013 At 6:32 am
    
    Thanks Loon – I had the same issue as you (cross-forest migration from Ex2010 to Ex2013), and your post is correct.
    
    - Satheshwaran Manoharan October 4, 2013 At 6:48 am
      
      Happy to load this info Soon 🙂
      
Cody April 26, 2013 At 3:17 pm

This guide for moving users does work great for me. The only thing out of the guide that didn’t work was the free/busy sharing. I can live without that though to be honest, since the users will be in the same forest in the end and cross forest sharing won’t be required at that point.

Good article Satheshwaran! Much easier on the eyes that how Microsoft has it laid out on TechNet.

- Satheshwaran Manoharan May 15, 2013 At 2:33 am
  
  Thanks for the Update Cody.
  
  Grateful for your Comments ..
  
sonik April 30, 2013 At 6:27 pm

Hi, When I run step11 powershell command, I have this error,I installed all of certificates in both of forest exchange server 🙁
The call to ‘https://exc.mydomain.local/EWS/mrsproxy.svc’ failed. Error details: Could not establish trust relation
ship for the SSL/TLS secure channel with authority ‘exc.mydomain.local’. –> The underlying connection was closed:
Could not establish trust relationship for the SSL/TLS secure channel. –> The remote certificate is invalid according
to the validation procedure..
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : 5695ADBE,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

- Satheshwaran Manoharan May 15, 2013 At 2:29 am
  
  if you have .local domain . it might give out issues like this .
  
  Make sure if your using a cert. see it does have a .local entry.
  
  or you might have to use a self signed cert for moment to verify it does work or not
  
  hopefully MRS proxy is already enabled,
  
IT_Vision May 15, 2013 At 5:17 pm

Hello Satheshwaran,

Would you please clarify something for me.

We are looking to perform a cross-forest mailbox move from Exchange 2010 to Exchange 2010. We have a forest trust in-place. My question is, we initially utilized GALSync between the two forests to bring over contacts information. So in the destination forest we have “Cross-Forest mail contacts” in Exchange from the source forest.

We are only looking to bring over the users mailbox over to our environment.

1. The user account will remain in the source forest so I wanted to make sure we will not run into any issues with having the cross-forest mail contacts already in place.

2. Is ADMT still needed if the users account is going to remain in the source forest?

3. When the mailbox is moved, and the users account remains in the source forest, how do we get the user account over to the new forest when that time comes, and how does it changed from a none-linked user mailbox?

Any help on the process we look to do is greatly appreciated.

Cheers

- Satheshwaran Manoharan June 5, 2013 At 8:22 am
  
  1. you wont run into any issues
  
  2. ADMT is not needed in the initial move.
  
  3. We are building a , Resource forest.
  
  Just scroll up , and see . mr. user (Edit)
  
  This question is already answered
  
Siim June 14, 2013 At 4:08 pm

Hi Loon!

We are also doing cross forest migration from Exchange 2010 to 2013. Tried this order – prepare, migrate, run ADMT, everything works, no errors. But in the end we have a mail user under contacts in Exchange Admin Center instead of having normal user. Did you have this problem? Any hints are highly appreciated!

- Satheshwaran Manoharan June 15, 2013 At 2:10 pm
  
  I feel once you prepare move . a disabled account is created
  
  Once you migrate using ADMT make sure . The same account gets enabled and activated.
  
  Thank you
  
Siim June 17, 2013 At 7:58 am

Hello Satheshwaran!

Yes, everything is OK with user accounts under AD Users and Computers, first the account is disabled, and later after ADMT it gets enabled. But my problem ist that in Exchange Admin Center this new user appears under contacts, not under mailboxes as normal user should. Actually this contact appears right after running PrepareMoveRequest.ps1 script which is starnge because mail-enabled user shoult be created.

- Satheshwaran Manoharan July 16, 2013 At 1:10 am
  
  Are you sure you are running on a fresh user. who doesnt exist in the destination forest at al ?
  
sony June 17, 2013 At 9:53 am

Instead of Two way Transitive Trust, can we have one way trust between forests?

- Satheshwaran Manoharan July 16, 2013 At 1:10 am
  
  yes we can have. if its going to be a one way move
  
sony June 19, 2013 At 10:24 am

Hi,

I would also like to know the procedure for cross forest migration from 2010 to 2013. Please help.

- Satheshwaran Manoharan July 16, 2013 At 1:14 am
  
  i haven’t documented it yet. Will update you soon on this
  
Fabian Hernandez August 6, 2013 At 4:47 pm

First of all, Thank you for your detailed post!

My question is, Will migrating the SID of users make it so that when the workstations are migrated to the new forest, the users keep access to the same user profile on the workstations?

- Satheshwaran Manoharan August 6, 2013 At 5:03 pm
  
  HI Fabian,
  
  SID migration is Recognize the Migrated users ..In giving access to fileshares and stuff.
  
  But recreating the profile is must. We cannot skip it.
  Unjoin and join to new domain
  
  - Fabian Hernandez August 7, 2013 At 11:32 pm
    
    Thanks for the quick reply!
    
    Just so im clear, After Disjoining old domain and rejoining new domain with the workstation, The local Workstation profiles will be rebuilt even if user SID is migrated? or will the user see their same profile on the workstation?
    
    - Satheshwaran Manoharan August 8, 2013 At 4:34 am
      
      Profiles will be rebuilt . even if SID is migrated .
      
Fabian Hernandez August 20, 2013 At 5:17 pm

Yet Another question. Should we take the same precaution in moving distribution groups and security groups? Exchange migration first by prepare move script and then admt?

My plan was just to move the distribution groups in AD and then re enable them as mail distribution lists. Is that a sound thing to do?

Nathan August 20, 2013 At 8:21 pm

Hi, I have found your site because I am having problems moving mailboxes from one forest to another, after doing prepare-moverequest and ADMT to take over SID. These stages work great and new AD account appears with SID history and all other attributes. But the New-move request wont bring across the mailbox. It is saying: The Target mail user doesn’t have an SMTP address that matches the taget delivery domain.

I have verified all your steps:
Trusts
ADMT
MRSProxy
Certs aren’t self signed
etc..

Am at a loss…

We are migrating from Exchange 2010 SP2 to Exchange 2010 SP3
Is this the problem?
Any help appreciated..

- Satheshwaran Manoharan August 21, 2013 At 4:08 am
  
  This happens because of missing proxy address . In the command change the target delivery domain to your source domain . And change the destination email address later .
  
Fabian Hernandez August 29, 2013 At 4:57 pm

How would we include or also migrate users archive mailboxes ? Would it be easier to migrate it through the exchange mmc? Our users online archives are in a separate DB then the mailboxes. Do you perhaps have a write up somewhere or a good link to a document on the procedures?

thanks

Taksaka September 2, 2013 At 11:46 am

Hi, how to migrate Distribution list with all of the mail attribute ? Without migrate mail attribute when users open old email to distribution group and reply that email, they receive undelivered message.

- Satheshwaran Manoharan September 2, 2013 At 11:50 am
  
  Use ADMT to migrate it . Then you should not have this problem
  
  See below link –
  http://social.technet.microsoft.com/Forums/exchange/en-US/0252068c-553f-4e8a-b68b-8aa083373331/crossforest-migration-of-distribution-groups
  
Marco September 12, 2013 At 4:24 pm

Hi, thanks for the beautiful article but I think that I’m missing something.
The Prepare-MoveRequest goes like descibed (output: 1 mailbox ready to move), ADMT migrate what needed but doing the move request I recive this message:
—The target recipient “recipient” must be a mail-enabled user when the primary mailbox is moving cross forest.—
Have you got any idea about this problem?
I have tryed with different user but no luck.
Thanks for your time and your help.

- Satheshwaran Manoharan September 18, 2013 At 2:37 pm
  
  I feel while using ADMT , you are not enabling the account Marco.
  
  Once using ADMT , make sure migrating account is getting enabled
  
Steve lindsey October 22, 2013 At 5:49 pm

Hello, & thank you for this nice little nugget of knowledge.

I have been given a task of migrating Exchange from 1 domain/forest to a completley new Forest/Domain

the new domain is in place, & i have the trust setup between both. I used the ADMT to copy the OU structure, groups, Users, group memberships, SID history & Passwords. all of it is working nice.

Nowi have to migrate Exchange over. The Source environment is Exchange 2010 (not sure of the SP at the moment.) & the new Target environment is Exchange 2013.

I know little to nothing about exchange, but if i use the scripts to add the attributes to the target users, & then the script to move the mailboxes. What would be the state of the mailboxes on the Source? would users still be able to use exchange over there? or would they be forced to use the new domain/exchange environment.

What i want to do is prevent ANY changes to the source environment, as it must stay prestine for quite some time. When we fully transition EVERYTHING to the new domain/forest we will then run for about 6-12 months using the new environment ONLY & the trust between each will be severed once that initial cut over takes place, but the data will remain intact over there…Just in case we ever need to go back to the old model. Once the 1-2 year span is over, i assume our offshoot will then begin removing/deleting/cleaning up the items & data we left on their environment

thank you in advance for your response.

- Satheshwaran Manoharan November 23, 2013 At 1:42 pm
  
  If you just migrate the Data . They will still stay there.
  But once you migrate . You got to change the mail flow to the new environment.
  As your data gets old . as they are going to keep on receive new mails on the new environment
  
Paul December 3, 2013 At 11:39 am

How does the situation change if the users in one Forest are in a different SMTP domain and need to stay in the different domain?

- Satheshwaran Manoharan December 8, 2013 At 2:46 pm
  
  Yeah that’s the same . Still they will need the old proxy address added . So that they can reply their old emails
  
Danish Khan January 2, 2014 At 8:21 am

Dear Satheswaran,

Thanks for your article and i need your support regarding Cross Forest Migration between 2010 to 2013 Exchange server. Shall i used the same steps of there is any change as the in my scenario the source is Windows 2008 R2 Domain Controller and Exchange 2010 mail Server and Target is Windows 2012 DC and Exchange 2013 Mail with 2 CAS and 2 Mailbox with DAG.

Martell January 3, 2014 At 1:21 pm

Hi and a happy new year!

Thanks for these good suggestions! I have a little bit different situation – we need to separate a small bunch of users into another domain in another forest. But their mailboxes have to stay into the same Exchange 2010 server (where they are already within the existing domain). So we need to move the AD accounts away to the other DC and re-map those accounts within the existing Exchange server to the new trusted AD accounts. How could that be achieved in the right way?

- Satheshwaran Manoharan January 6, 2014 At 1:32 pm
  
  Exchange mailboxes and AD accounts have to be in the same forest .
  
  You can take the accounts migrated like a copy of it . and have a GAL sync .
  So that AD accounts used is destination forest for – system login
  AD accounts for email password will be different.
  
Danish Khan January 5, 2014 At 3:18 pm

Dear Satheswaran,

Hello and Happy New Year, this is my second email regarding the same subject I follo your article each and every step is successfully done but after running the move command I face the below error and there is no such article or help available on the below error please let me know if you have any idea on the below error

The call to ‘https://SERVERNAME.com/EWS/mrsproxy.svc’ failed. Error details: Could not establish trust
relationship for the SSL/TLS secure channel with authority ‘aucmail01.alhamranigroup.com’. –> The underlying
connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. –> The remote
certificate is invalid according to the validation procedure..

- Satheshwaran Manoharan January 6, 2014 At 1:34 pm
  
  make sure the server entry is available on the cert . otherwise its not going to trust each other .
  
Daniel Rosa February 12, 2014 At 7:29 pm

Hi,
I’m moving Exchange 2007 to Exchange 2013 intra forest, but on user I received the error:
SkipFolderPromotedProperties, WordBreak
FailureCode : -2146233088
FailureType: NonUniqueRecipientException
FailureSide: Target
Message : Error: Multiple objects with Sid S-1-5-21-2308973541-373552077-3909921197-2649 were found.

Can you help me Satheshwaran Manoharan?

Tks Daniel

- Satheshwaran Manoharan February 17, 2014 At 5:37 pm
  
  Can you check for duplicate entries
  
Dave Kings February 25, 2014 At 7:47 pm

First, thank you for this post. I’m have some some issues, I am getting the following error, ”

“This task does not support recipients of this type. The specified recipient destination.local/Imported Users/Dave Test is of type UserMailBox. Please make sure that this recipient matches the required recipient type for this task.

Well in the source domain it was mailbox enabled. I’m not quite sure what I’m missing.

Environment is Server 2008 R2 Exchange 2010 SP3 to new forest with same configuration. Account are migrated with ADMT, passwords and sync’d and “merge” is selected within ADMT. What do I need to look for.

Many Thanks, Dave

- Satheshwaran Manoharan February 26, 2014 At 9:48 am
  
  Can you check — Get-mailbox “Problematic mailboxname” | Fl
  
  Check for receipient type details. “Make sure its user mailbox”
  
Ashish April 3, 2014 At 10:50 am

Hi Satheshwaram,

This is one of finest articles I have seen on Exchange cross forest migration. Great work.

Will this approach work for exchange 2007 to 2007 as well. In the target forest the we have upgraded the Cas server to 2010 as we are using quest for legacy lotus notes connectivity.

Also what happens to free/ busy and resource booking. Is there additional steps required for that.

This is merger situation where we only want to migrate the mailboxes to new forest the users will remain in the same forest.

Thanks.

DPenneman April 29, 2014 At 2:29 pm

This will also work mostly for a Exchange 2003 cross migration also. Just a few little tweaks. Use the -remotelegacy switch during the move. Also during the new-moverequest use -baditemlimit 150 -acceptlargedataloss or a lot of mailboxes will fail after hours of waiting for them to move.
On the target server make sure the mailbox quota is larger than what you are moving.

- Satheshwaran Manoharan May 13, 2014 At 12:01 pm
  
  Thanks for Extra Inputs 🙂 Highly appreciated
  
MUSHTAQ Mondal April 30, 2014 At 12:46 am

Excellent. .extensive helpful n handy. .Appreciate your efforts.

- Satheshwaran Manoharan May 13, 2014 At 12:01 pm
  
  You are welcome 🙂
  
Rait May 19, 2014 At 1:39 pm

I have problem with New-MoveRequest.
It gets error “THe target mail user “xx” doesnt hav an SMTP address that matches the target delivery domain”.

I did :
1. Made all your steps
2. Add Target Exchange sourche exchange domain to be trusted.

What I should to step by ste to get mailboxes moved ?

- Satheshwaran Manoharan June 3, 2014 At 6:51 am
  
  I guess mail enabled contact is not created yet
  
Riaz Javed Butt May 22, 2014 At 9:45 pm

Hi,

I am following the steps that you recommend for the cross forest migration. I am able to successfully run prepare-moverequest script along with the required parameters. Successfully migrated the user account using ADMT along with SID and password history from source to target forest. but when i run the new-moverequest cmdlet i am getting the following error message.

“The Target mail user “domian.com/users/username” doesn’t have and SMTP address that matches the target delivery domain “Targetdomain.com”

Kindly if it’s possible for your then reply on my email ID. thanks…

- Satheshwaran Manoharan June 3, 2014 At 6:55 am
  
  I guess mail enabled contact is not created properly .
  
Mohan July 6, 2014 At 2:45 pm

Hi Sathesh, I followed all your steps for cross forest migration (Exchange 2010 SP3 to Exchange 2010 Sp3). when I do new-move request, am getting “doesn’t have an SMTP address that matches the target delivery domain” error but mail enabled contact is created already. please advise.

Mohan July 6, 2014 At 3:03 pm

I was able to move mailboxes before suddenly got the above said error

Mohan July 6, 2014 At 8:30 pm

Hi Sathesh, found the problem.. it was with primary SMTP address in email contact.
Thanks.

Kenneth July 17, 2014 At 11:30 pm

Hi,

I get this 🙁 please help…..

The call to ‘https://exchangeserver.domain.local/EWS/mrsproxy.svc’ failed. Error details: The remote server returned an unexpected response: (405) Method Not Allowed. –> The remote server returned an error: (405) Method not allowed…

THANKS!

- Kenneth July 17, 2014 At 11:34 pm
  
  When executing:
  
  New-MoveRequest -Identity ‘user@mail.com’ -Remote -Remotehostname ‘exchangeserver.domain.local’ -RemoteCredential $RemoteCredentials -TargetDeliverydoman domain.local
  
- Satheshwaran Manoharan July 22, 2014 At 4:16 am
  
  You enabled MRS proxy ?
  
  - Mugundhan January 13, 2015 At 5:46 am
    
    Hi Satheshwaran,
    
    I am also getting the following error while creating new move request.https://exchangeserver.domain.local/EWS/mrsproxy.svc’ failed. Error details: The remote server returned an unexpected response: (405) Method Not Allowed. –> The remote server returned an error: (405) .
    
    When i tried to open the above url in the source url, i am getting 404 error. But am able to successfully open the same url in the target exchange server.
    
    Kindly assist me in troubleshooting the issue
    
    - Satheshwaran Manoharan January 17, 2015 At 4:08 am
      
      Make sure you are entering the right credentials.
      
      Try restarting replication service. or restarting the source Exchange server may help.
      
MAJID July 24, 2014 At 1:31 pm

Hi my friend,
Thank you for this training.
I have a problem with download Password Export Server 3.1 x64. Would you please send me this software by email or upload to another place for download.
Thank you

- Satheshwaran Manoharan July 30, 2014 At 9:33 am
  
  https://connect.microsoft.com/site1164/Downloads/DownloadDetails.aspx?DownloadID=53422
  
Sandeep Singh July 30, 2014 At 7:28 am

Thanks for this great article. Getting some issues, Please help out.

While executing
New-MoveRequest –Identity ‘Mailbox1@careexchange.in’ –Remote –Remotehostname ‘sourceExchange.CareExchange.in’ -RemoteCredential $RemoteCredentials –TargetDeliverydomain ‘targetexchange.in
it end up with below error. I have already enabled MRS Proxy on source CAS and increased the data import time out to 20.

The call to ‘https://path/EWS/mrsproxy.svc’ timed out. Error details: The request channel timed out attempting to send after 00:00:00:0000005. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.

one more error: could not establish trust relationship for the SSL/TLS secure channel with aurthority ‘FQDN of source domain’

- Satheshwaran Manoharan July 30, 2014 At 9:36 am
  
  You are missing something with the SSL cert. its not trusting each other.
  
Hadi Byron August 27, 2014 At 11:48 am

Hi Satheshwaran,
thank you for the valuable info presented.
my question is , when I moved users to the target forest ( exchange 2007 to exchange 2013) using (prepare move, ADMT, move mailboxes) i have noticed that the users in the target forest don’t have GAL or address book. how to create a GAL for them inorder to be able to use it to exchange emails with other users not migrated yet in case of co-existance.
Thank you in advance

- Satheshwaran Manoharan August 28, 2014 At 4:06 am
  
  same domain ? Same domain name space sharing ? —
  
  - Hadi Byron August 28, 2014 At 4:41 am
    
    different domain, same domain name space sharing
    
    - Satheshwaran Manoharan August 28, 2014 At 4:46 am
      
      You should introduce one more SMTP domain
      Source Domain where MX is hitting.
      Mailbox in Target — Create Contact – Target Address to Target domain
      Target Domain
      Mailbox in Source – Create Contact – Target Address to Source domain
      
      Manual GAL SYnc
      Or check for any 3rd party tools like GAlsync
      
Talha Malik September 2, 2014 At 8:20 am

Satheshwaran Manoharan

Hi, I have go through your document its very help full for me to perform cross forest migration but i need to do the cross forest migration from Exchange 2010 to Exchange 2013 so steps & sequence are little bit change
Step 1
./prepare-moverequest
Step 2
./new-moverequest
Step 3
finally run ADMT tool to migrate sID History

Additionally, if new-moverequest failed with error failedother after completion 95%
then we need to run
set-moverequest -identity maibox -baditemlimit=1
resume-moverequest -identity mailbox
now mailbox move to exchange 2013 successfully.

I have done this in production environment and its worked fine.

- Satheshwaran Manoharan September 2, 2014 At 12:56 pm
  
  Thank you for Sharing . Currently am working on this . Hopefully I should post it soon, Wish you a good day.
  
Saeed Khalifi October 5, 2014 At 2:45 pm

hi & thanks for this great article, really enjoyed readin’ it.
got a couple of questions here.
our target domain is 123xyz.org (netbios name: 123xyz), our target domain is 123xyz.com (netbios name: 123zyx.
1. can we issue forest trust? (hence the netbios names of domains)
2. can we migrate from ex2010 to ex2013SP1 in this scenarion? or does this work on just EX2010 cross forest migration?
thanks in advance

- Satheshwaran Manoharan October 12, 2014 At 10:54 am
  
  Do you really have similar domains ? are you planning to build one ?
  
Anthony Obando November 23, 2014 At 5:27 pm

Hi Satheshwaran,

I’ve follow the whole steps – my scenario is cross-forest exchange 2010 mailboxes to exchange 2013.

Have one mailbox in Queued status but i dont see anything running either management console on 2010 or 2013.

Am I missing something?

Thank you

- Satheshwaran Manoharan January 7, 2015 At 4:43 am
  
  You can try restarting the Mailbox Replication Service.
  
Jason Lawrence January 15, 2015 At 3:26 pm

Hi Satheshwara,

Great article!

I’m having a bit of an issue with cross forest 2010 – 2010. After I move accounts via ADMT the account in the new forest isn’t enabling and i’m receiving an error about password requirements when i try and enable it. Step 9 seems to go fine so not sure what i’m doing wrong?

Any help would be great! Thanks

- Satheshwaran Manoharan January 17, 2015 At 4:09 am
  
  In the Group Policy make sure the password complexity is matching between the domains.
  For Example – Source domain may allow 3 letter passwords
  but target forest may not allow it.
  make sure it matches.
  
  - Jason Lawrence January 20, 2015 At 11:57 am
    
    I did check and the password was well within requirements.
    
    Oddly enough it worked if i changed the order to:
    
    Prepare mailbox
    move mailbox
    ADMT
    
    - Satheshwaran Manoharan March 8, 2015 At 12:45 pm
      
      Above method should work as well . You can skip the ADMT ,if you dont require the SID.
      
Felix January 18, 2015 At 3:56 pm

Hi Manohran,

i am having an issue accessing a mailbox after cross forest move. trust is in place and networking is fine between the two forests. the user account of the mailbox moved is to be retained in the source forest, so the -linkedmailuser switch was used to prepare the move. the disabled account created in the target AD forest is still disabled. please assist.
thanks

- Satheshwaran Manoharan January 20, 2015 At 4:26 am
  
  Try reseting the password and access it.
  If its not listed as a mailbox both the ends. please check your event viewer. let me know what it says.
  
  - Felix March 25, 2015 At 12:23 pm
    
    Hi Manoharan,
    
    issue resolved. reset the password and was able to access it.
    
    i have another concern, what happens to mail enabled groups on the source exchange by the time the mailboxes in the group are moved to another exchange organization. will the users still receive group emails or is there anything to be done to address this. Note that in this scenario, the source AD is still in use.
    
    - Satheshwaran Manoharan May 12, 2015 At 6:08 am
      
      When the mailbox is migrated – It does leave a contact pointing to the other org. SO the group members (moved/not moved) should get emails.
      
Shashank Kudi January 21, 2015 At 12:33 pm

Hi Satheshwaran,

Thanks for sharing such great information. Requesting you to please help me out for below scenario.

Source Exchange 2010 SP2:- abc.com
2AD, 2CAS & 2 MBX servers
Database:- 4
Total Users :- 3500
Accepted Domains :- 8
Total Data:- 5TB +

Target Exchange 2010 SP2:- xyz.com
Resource allocated same as above.
Now we have to migrate users along with data to target forest xyz.com keeping both setup live, as moving 5TB + data will be a ongoing process and the same will take some time.

With your guidelines we are able to migrate test users along with data, but after migration the migrated user is not able to connect through MS Outlook even not able to login into OWA. It gives error “The Outlook Web App address https://mail.abc.com/owa is out of date.”

Kindly suggest,

Kindly let me know if you want any more information from our end.

Thanks in advance.

- Satheshwaran Manoharan March 8, 2015 At 12:47 pm
  
  Once you migrate the users they should use https://mail.xyz.com/owa
  if you setup the target domain properly. outlook should work after restart most of the instances.
  
Mugundhan January 22, 2015 At 7:25 am

Am getting this error “the target recipient must be a mail enabled user when the primary mailbox is moving cross forest” after running new-move request. Can you please advise on the same.

- Satheshwaran Manoharan March 8, 2015 At 12:50 pm
  
  Your prepare move is not happening properly.
  
shafeek January 27, 2015 At 10:28 am

awesome article!!!!!

Can I use digital certificate on both forest to authenticate between each other (it doesn’t contains server name space on digital certificate but domain name persist on both certificate). If no, is it required to export certificate from all CAS server (forest A) and import into all CAS servers in forest B (vice versa);
Thank you in advance!!!!!

Regards
Shafeek

sandip February 18, 2015 At 1:40 pm

Great article !!!

It really clear my concept about cross forest migration

Hope to see more posts like this 🙂

- Satheshwaran Manoharan March 8, 2015 At 1:15 pm
  
  Thank you for your comments !
  
Jhon April 3, 2015 At 10:04 am

Nice article, it provide the migration Guide will help you to migrate mailboxes across forest and use New-MoveRequest cmdlet to perform a cross-forest move and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013. I tested this automate application ( http://www.lepide.com/exchangemigrator/ ) to accomplish this task and easily performs cross forest migration from exchange 2010.

Vishnu Pareek April 10, 2015 At 7:11 am

Hi Manoharan

Thank you very much for this document. I would like to ask you one question.

If I migrate to another forest then , can I reuse my old outlook OST files for the migrated mailbox. Or I need to create a another OST and download all mails.

- Satheshwaran Manoharan May 12, 2015 At 6:09 am
  
  While re configuring the Outlook – new ost will be generated. That cannot be reused. Until you use migration tools like binary tree.
  
Siva May 15, 2015 At 10:56 am

Hi Satheesh,

Well described document. It is really useful.
Question:- Ignore if you are not using a Self Signed Cert.

Could you suggest if client using 3rd party certificate (Both forest different vendor) what needs to be done in this syneario?

- Satheshwaran Manoharan May 24, 2015 At 9:22 am
  
  if both are 3rd party. and machine names are in the cert. nothing needs to be done.
  
Aaron June 12, 2015 At 3:42 pm

I am in a position of doing cross forest migration. Source Exchange is 2007 and target 2013.In the source mail box has got recipient limit set(ex 50). currently we are in a co-existence scenario. when a migrate user send a mail to many distribution list the user receives too many recipients error. which is generating by the remote exchange server(source). Is there away to overcome the issue without increasing the recipient limit on the source enabled user?

Siva June 23, 2015 At 4:40 pm

Hi Satheesh,
We are doing migration from exchange 2010 to different forest exchange 2010. We have user AD account and mailbox in source and the same time contact exists on target also AD object exist in target. Target AD account to access application which is located in Target forest. My concern I can migrate/merge source mailbox to target by running prepare move request then new move request by deleting existing contact adding proxy SMTP address. In this scenario if any user from target replied that contacts from their cache, obvious they may end up with NDR since legacy exchange DN is not available. How do I avoid this situation? Is there any method is available to merge target AD and contact? Then we can migrate from source to target. Please suggest. Hope you can understand the situation. Your reply is much appreciated.

Mohammad Zafar August 24, 2015 At 10:08 am

Great Article, You made my day…

Jacinto October 10, 2015 At 11:46 am

My brother suggested I would possibly like this website.
He was entirely right. This put up actually made my day.
You cann’t imagine just how a lot time I had spent for this information! Thank you!

Annie October 14, 2015 At 3:03 pm

Hi Satheshwaran,

Our one of the client have two forests, Suppose A and B . Forest A has exchange 2010 installed and Forest B doesn’t. There are two way trusts between forests. Forest B has a user’s mailboxes in forest A’s exchange server.
Now if i migrate users of Forest B users to Forest A what steps i have to be taken.
would appreciate your response.
Thanks!!

- Satheshwaran Manoharan October 27, 2015 At 7:32 am
  
  check this — https://technet.microsoft.com/en-us/library/bb201694.aspx
  
Mottj001 November 5, 2015 At 8:39 pm

Satheshwaran,

Great write up. I’ve only read through most of it, so i’m sorry if i missed this if it was previously discussed. Basically my question is… I have 2 forests, both have exchange 2013. ForestA bought out ForestB, and they created mailboxes in Forest A for all forest B users, created contacts in both Forests, and then setup forwards from the mailboxes in Forest A to Forest B. At this point they would like to migrate the users to Forest A and decommission exchange in ForestB. Since there mailboxes already exist in Forest A, but all the mail data resides on their mailboxes in Forest B, is there a way to do the cross forest migration and just merge the mail data into the empty mailbox on Forest A from Forest B?

- Satheshwaran Manoharan November 8, 2015 At 5:18 am
  
  If the same Data doesn’t exist on both the forests. if they are different set of data. go for tools like migrationwiz and sync the data and reconfigure Outlook profile and move On.
  
  - ryanp April 4, 2016 At 1:18 pm
    
    How long did this take most of you to complete, I am needing to do a 200 user site which is on a 2008r2 domain with exchange 2007, I am looking to move to a 2012 r2 domain with exchange 2010 then later move to exchange 2013.
    
ryanp April 4, 2016 At 1:09 pm

How long did this take most of you to complete, I am needing to do a 200 user site which is on a 2008r2 domain with exchange 2007, I am looking to move to a 2012 r2 domain with exchange 2010 then later move to exchange 2013.

ryanp April 5, 2016 At 8:21 am

Hi I have a 2008r2 domain with 3 DC’s, I also run exchange 2007 at the moment, if I create a new 2012r2 domain will the above steps work ok?

I have around 200 users as well and the main reason for this is they want to change the domain from what it is currently as its the old company name, with a 200 user/mailbox setup roughly how long would you expect this to take and is there much downtime incurred with doing it this way?

Pravin April 18, 2016 At 6:00 am

Hi Satheshwara,

We have migrated users from exchange 2010 to 2010 but only onsite outlook anywhere users outlook profile is not configuring automatically. if the user is in LAN then it is auto configures and works fine.

If we reconfigure the outlook profile then it will work fine.

Any suggestion.

Regards,
Pravin

- Satheshwaran Manoharan April 27, 2016 At 11:59 am
  
  This is something you cannot avoid . If its configuring automatically you are lucky i would say. Reconfigure and move on. if the users are less than 1000.
  
plastic extruder June 6, 2016 At 12:18 am

When the electricity is passed a friction is created and thereby heat.
The length-to-diameter ratio, pitch, length of each zone and helix angles of a screw must all be matched to the plastic type being used.
The plastic extruder consists from the extrusion device, the extrusion and pressing system,
the transmission system and the heating and cooling system.

Bernard June 15, 2016 At 10:45 am

Hi,

I have the same problem of some users above regarding : The target recipient must be a mail-enabled user when the primary mailbox is moving cross forest.

You’re Saying the preparation move isn’t done properly. For my part, it seems to be ok as I have the result : Preparation for ….. done.
1 mailbox(s) ready to move.

But Still it says I can’t make my new move request because of the target recipient…

Can you help ?

thanks

Pape June 29, 2016 At 12:45 pm

Hello Dear,

thanks for this nice document. I have an issue when i try to migrate bulk users i get this error: “Target user ‘Sofia Ricci’ already has a primary mailbox.
+ CategoryInfo : InvalidArgument: (alioune.local/BOS/Sofia Ricci:MailboxOrMailUserIdParameter) [New-MoveR
equest], RecipientTaskException
+ FullyQualifiedErrorId : 877911DF,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest”

can you help please?

Anonymous December 6, 2016 At 5:19 pm

thanks for this step by step really helped in deployment and running labs

Sahin February 9, 2017 At 4:35 am

Hi, great write up. Question I have is what if we created new AD accounts for the users in the Target domain, and migrated the accounts using ADMT from source to target, then merged the SID history to the new AD account in the Target domain. How do we use the scripts then.

For example:

Let’s say MBXSource1 is the AD account in the source domain.
We create a new AD ID in the target domain called MBXTarget for this user, they use that to use applications on the target domain.
Now we want to migrate Source Domain Exchange to Target Domain Exchange, but want the users to continue to use the MBXTarget account in the Target domain.
We use ADMT and migrate MBXSource1 into the Target Domain, then copy the SID History from MBXSource1 into MBXTarget account.

How do we use the PrePareMove and Move scripts?

I know this is not the conventional way, but this is the way we need to do it.

Samim Shaikh June 30, 2017 At 4:21 pm

Everything covered here… thanks for all your information.

BIG Thanks. !!!

Variable July 3, 2017 At 1:33 pm

Hi,
Great post, just what i was looking for. Perhaps someone can help me complete the script i require for my situation since im stuck. Currently i have a set up where AD with existing accounts is in Forest1 and exchange is in Forest2. I want to migrate exchange accounts from Forst2 to new server in Forest1. I can migrate the mailboxes with the above tutorial but i cant find a way to disconnect the migrated mailbox and reconnect to existing AD account. Perhaps someone has done it before and can help me figure this out?

ravi kumar July 6, 2017 At 2:07 pm

hi, we are planning for migration of two forest, and exchange 2013 to office 365 both.

need your help for this migration.

- Satheshwaran Manoharan July 30, 2017 At 6:27 am
  
  you can email us on Support @ CareExchange.in
  
Dee February 16, 2018 At 2:55 pm

Will it work if I do Cross Forest migration from Exchange 2013 to Exchange 2010 SP3? Thanks

Kevin February 22, 2018 At 3:28 pm

Hi
Brilliant article which I have used for a couple of Cross Forest migrations, Can you see any issues with a cross forest migration from Exchange 2010 in the Source Forest to Exchange 2016 in the Destination. Any help appreciated

ravi July 11, 2018 At 11:12 pm

i am trying to do cross forest migration from exchange 2010 to 2016. i have exported auto discover setting of 2016. but it looks like it is not working. any suggestion

Lokky January 17, 2020 At 3:10 am

This post so good.
I have a question? When i competed step 11 so my mailbox01 have email address mailbox01@exchange.in or mailbox’s mailbox01@targetexchange.in ?

Thanks.

- Satheshwaran Manoharan January 18, 2020 At 3:16 pm
  
  Whatever you specify as target delivery domain. ( Then if your email address of target domain will apply.Which may change the same)
  
  - Anonymous February 18, 2020 At 10:22 am
    
    Thank you so much
    
Anonymous February 19, 2020 At 9:12 am

Hi.
I competed to step 10. If i want use new-moveRequest to source domain to child domain in target domain so which command use ? I tried your command but it’s not appropriate with my project .
( Command: New-MoveRequest –Identity saigon01@hvlinh.xyz‘ –Remote –Remotehostname ‘sourceSG.hvlinh.xyz’ -RemoteCredential $RemoteCredentials –TargetDeliverydomain ‘cmcts.xyz’)
Error: the operation couldn’t be performed because object saigon01@hvlinh.xyz couldn’t be found on with

Can you help me?

Thank you.

Lokky February 19, 2020 At 9:12 am

Hi.
I competed to step 10. If i want use new-moveRequest to source domain to child domain in target domain so which command use ? I tried your command but it’s not appropriate with my project .
( Command: New-MoveRequest –Identity saigon01@hvlinh.xyz‘ –Remote –Remotehostname ‘sourceSG.hvlinh.xyz’ -RemoteCredential $RemoteCredentials –TargetDeliverydomain ‘cmcts.xyz’)
Error: the operation couldn’t be performed because object saigon01@hvlinh.xyz couldn’t be found on with

Can you help me?

Thank you.

- Satheshwaran Manoharan February 21, 2020 At 7:30 pm
  
  prepare move request worked ?
  
Strela May 11, 2022 At 11:17 am

Very good matter earned my respect i was looking for exactly this enriched my knowledge.

Your website is very interesting, congratulations, check mine too:
https://b9g.net

Strela July 9, 2022 At 7:54 pm

Perfect i was looking for exactly this how much new thing i learn here expanded my culture.

Your website is very interesting, congratulations, check mine too:
https://b9g.net

Novih Sandra October 4, 2022 At 12:00 pm

Hi Sathesh,

your article help me a lot in my project.
but i have question/issue, majority mailbox migration successfully.
but some mailbox after new-moverequest and completed migration, somehow not exist in target exchange, also if i run get-mailbox i got error user could found on domain controller “servername” but in source exchange already change as mail user. what do i check ?

thanks

Mike November 2, 2022 At 9:28 pm

Hi Sathesh,

I’ve following your migration guide on Step 11, now I am having an error: The target recipient ‘Mike Young’ must be a mail-enabled user when the primary mailbox is moving cross forest

[PS] E:\Program Files\Microsoft\Exchange Server\V15\Scripts>New-MoveRequest -Identity ‘mike_young@abc.net’ -Remote -Remotehostname ‘exchang1.abc.net’ -RemoteCredential $RemoteCredentials -TargetDeliverydomain ‘abbb.net’
The target recipient ‘Mike Young’ must be a mail-enabled user when the primary mailbox is moving cross forest.
+ CategoryInfo : InvalidArgument: (clark_kent@abc.net:MailboxOrMailUserIdParameter) [New-MoveRequest], RecipientTaskException
+ FullyQualifiedErrorId : [Server=EX2019A,RequestId=6c45f065-cd58-4db0-8e27-00f5e91528e7,TimeStamp=11/2/2022 6:54:03 PM] [FailureCategory=Cmdlet
-RecipientTaskException] 202CD93F,Microsoft.Exchange.Management.Migration.MailboxReplication.MoveRequest.NewMoveRequest
+ PSComputerName : ex2019a.abbb.net

How do I to fix with that error?

Thanks