SOLVED
Home

Exchange maigration mail users

%3CLINGO-SUB%20id%3D%22lingo-sub-390976%22%20slang%3D%22en-US%22%3EExchange%20maigration%20mail%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390976%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Evening%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20looking%20for%20some%20advice%20with%20an%20Exchange%20migration.%20.%20I%20have%20a%20client%20that%20has%20an%20Exchange%202007%20server%20but%20is%20using%20Office%20365%20(no%20hybrid)%20and%20we%20are%20migrating%20them%20to%20Exchange%202016.%20They%20use%20Azure%20AD%20connect%20to%20sync%20AD%20to%20Office%20365%20but%20use%20Exchange%202007%20to%20manage%20the%20mail%20attributes.%26nbsp%3B%20We%20are%20moving%20them%20to%20Exchange%202016%20as%20Exchange%202007%20is%20a%20out%20of%20support.%20Typically%20I%20would%20upgrade%20to%20Exchange%202013%20then%20Exchange%202016%20Management%20tool.%20They%20have%20no%20mailboxes%2C%20all%20their%20users%20have%20been%20setup%20as%20Mail%20Users.%20Do%20I%20need%20to%20still%20do%20the%20migration%20or%20can%20I%20decommission%20Exchange%202007%20then%20install%20Exchange%202016%20management%20tool%20and%20link%20the%20AD%20accounts%20to%20Mail%20Users%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-390976%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-391740%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20maigration%20mail%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-391740%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1978%22%20target%3D%22_blank%22%3E%40Michel%20de%20Rooij%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20Michel.%20In%20regards%20to%20the%20mail%20user%20accounts%20I%20am%20struggling%20to%20find%20material%20on%20how%20they%20are%20migrated%20to%20the%20new%20exchange%20server%2C%20do%20you%20have%20any%20information%20on%20that%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-391202%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20maigration%20mail%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-391202%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%2C%20let%20me%20remind%20you%20that%20you%20cannot%20install%20Ex2016%20in%20an%20environment%20which%20still%20contains%20Ex2007%20servers%2C%20so%20that%20sets%20your%20upgrade%20path%20through%20Ex2013.%20I%20would%20not%20start%20with%20decomissioning%20Ex2007%2C%20as%20that%20in%20essence%20means%20removing%20all%20on-prem%20configuration%20items%20related%20to%20Exchange%2C%20which%20you%20then%20need%20to%20re-configure%20after%20deploying%20Ex2016%20(e.g.%20accepted%20domains).%20Just%20follow%20the%20regular%20upgrade%20procedure%20for%20Ex2007-%26gt%3BEx2013%2C%20then%20Ex2013%20to%20Ex2016.%20Since%20everybody%20lives%20in%20Office%20365%20already%20(assuming%20you%20have%20autodiscover%20pointing%20to%20Office365%20and%20you%20have%20no%20mail%20relay%20functionality%20on-prem%2C%20etc)%2C%20you%20have%20no%20worries%20regarding%20namespace%2C%20public%20endpoints%20etc.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870402%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20maigration%20mail%20users%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870402%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F4732%22%20target%3D%22_blank%22%3E%40Brian%20McFadden%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%20Brian%2C%20check%20and%20let%20me%20know%20if%20this%20link%20is%20helpful%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Frecipients%2Fmailbox-moves%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Frecipients%2Fmailbox-moves%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Brian McFadden
Contributor

Good Evening,

 

I am looking for some advice with an Exchange migration. . I have a client that has an Exchange 2007 server but is using Office 365 (no hybrid) and we are migrating them to Exchange 2016. They use Azure AD connect to sync AD to Office 365 but use Exchange 2007 to manage the mail attributes.  We are moving them to Exchange 2016 as Exchange 2007 is a out of support. Typically I would upgrade to Exchange 2013 then Exchange 2016 Management tool. They have no mailboxes, all their users have been setup as Mail Users. Do I need to still do the migration or can I decommission Exchange 2007 then install Exchange 2016 management tool and link the AD accounts to Mail Users?

3 Replies
Solution

First, let me remind you that you cannot install Ex2016 in an environment which still contains Ex2007 servers, so that sets your upgrade path through Ex2013. I would not start with decomissioning Ex2007, as that in essence means removing all on-prem configuration items related to Exchange, which you then need to re-configure after deploying Ex2016 (e.g. accepted domains). Just follow the regular upgrade procedure for Ex2007->Ex2013, then Ex2013 to Ex2016. Since everybody lives in Office 365 already (assuming you have autodiscover pointing to Office365 and you have no mail relay functionality on-prem, etc), you have no worries regarding namespace, public endpoints etc.

 

 

@Michel de Rooij 

 

Thanks Michel. In regards to the mail user accounts I am struggling to find material on how they are migrated to the new exchange server, do you have any information on that?