AD User Migration Exchange Mailbox last

%3CLINGO-SUB%20id%3D%22lingo-sub-1093938%22%20slang%3D%22de-DE%22%3EAD%20User%20Migration%20Exchange%20Mailbox%20last%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1093938%22%20slang%3D%22de-DE%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eone%20Question%2C%20we%20have%20a%20multidomain%20environment%2C%20with%20an%20Exchange%202016%20DAG.%3C%2FP%3E%3CP%3EOur%20company%20consists%20of%20several%20companies%2C%20and%20I%20have%20to%20separate%20them%20into%20several%20separated%20AD%20Domains.%3C%2FP%3E%3CP%3EWe%20want%20to%20migrate%20users%20with%20ADMT%20to%20the%20new%20domain%20via%20SID-History%2C%20and%20they%20should%20use%20their%20old%20mailbox%20(per%20linked%20mailbox)%20until%20we%20are%20able%20to%20migrate%20Exchange%20completely.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20read%20just%20About%20Migrate%20Exchange%20first%2C%20so%20my%20Question%20is%2C%20is%20our%20solution%20a%20valid%20way%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1093938%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmt%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELast%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELinked%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELinked%20mailbox%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMailbox%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1157737%22%20slang%3D%22en-US%22%3ERe%3A%20AD%20User%20Migration%20Exchange%20Mailbox%20last%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157737%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F508786%22%20target%3D%22_blank%22%3E%40Hermulus%3C%2FA%3E%26nbsp%3B%3CFONT%3E%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3EWe%20did%20with%20ADMT%20last%20year%20with%20new%20Exchange%202019%20and%20Windows%202019%20DC%20servers%20at%20the%20end.%20You%20can%20use%20ADMT%20it's%20not%20a%20problem.%3CBR%20%2F%3EWith%20ADMT%20is%20a%20lot%20of%20scripts%20to%20manage%20particulary%20in%20Exchange.%20Last%20time%20I%20did%20a%20migration%20with%20ADMT%20I%20used%20Efflux%20migrator%20tool%20for%20help%20us.%20This%20tool%20need%20a%20license%20it's%203%20%24%20per%20user.%20This%20tool%20help%20you%20a%20lot%20when%20you%20do%20the%20final%20step%20of%20sync%20user%20and%20for%20monitor%20the%20entire%20migration%20steps.%3CBR%20%2F%3EUsing%20ADMT%20or%20a%20other%20tool%20to%20help%20you%20for%20your%20migration%20remember%20that%20all%20domains%20and%20forests%20are%20different%20so%20you%20have%20to%20test%20all%20the%20scenarios.%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3ERegards%2C%3CBR%20%2F%3EThierry%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Visitor

Hi, 

 

one Question, we have a multidomain environment, with an Exchange 2016 DAG.

Our company consists of several companies, and I have to separate them into several separated AD Domains.

We want to migrate Users with ADMT to the new domain per SID-History, and they should use their old Mailbox (per linked Mailbox) until we are able to migrate Exchange completely.

 

I read just About Migrate Exchange first, so my Question is, is our solution a valid way?

 

1 Reply
Highlighted

Hi @Hermulus 
 
We did with ADMT last year with new Exchange 2019 and Windows 2019 DC servers at the end. You can use ADMT it's not a problem.
With ADMT is a lot of scripts to manage particulary in Exchange. Last time I did a migration with ADMT I used Efflux migrator tool for help us. This tool need a license it's 3 $ per user. This tool help you a lot when you do the final step of sync user and for monitor the entire migration steps.
Using ADMT or a other tool to help you for your migration remember that all domains and forests are different so you have to test all the scenarios.
 
Regards,
Thierry