Hi All

I'm working on a solution with below schenario

" there is a company call X (x.com) and it's new acquisition is Y (y.com)

Now they wanted to migrate exchange environment to  x.com from y.com

Details :

X :

Exchange 2010

Co-existence with Lotus domino (As there were some applications running on domino)

Y :

Exchange 2010

Now customer wanted to build new exchange 2013 in x.com

Migrate exchange 2010 from Y.com to exchange 2013 in x.com, and will migrate exchange 2010 in x.com to exchange 2013 in x.com later phase

y.com AD will remain as it is and it may take time to migrate y.com AD to x.com

could you please some one help how my target infrastructure should be during exchange migration and after exchange migration

and how the mail flow should happen in target state.

Thank you

You've asked what I call a "consulting engagement question", a question so complicated or requiring so many follow-up data-collection questions from us that we can't possibly give you the depth of information the issue deserves.  You really ought to hire a consultant to work this project through with you, and/or pick up Tony Redmond's and Jim McBee's books and start reading.

Hi 

Thanks for response

Could you please help with high level mail flow in target state of above example? especially for y.com users?

Hi koopula,

your target mail flow depends on your target design. Usually I expect you will implement  an MX records that points to the X infrastructure while that infrastructure will be some src.domain that may forward mail to your Y company having a dst.domain.

While saying that your posting is not clear enough to get to a technical statement, so it's all just as you plan your future design.

Regards,
Martin

You're asking us to design a solution for you.  If you have specific questions for which you provide sufficient information, we can try to help you.  But this is not the place to seek a design.

Hi,

The mail flow configuration in target server depends on you. Here are the main steps for your reference.

1. Create send connector and receive connector.

2. Create transport rules.

3. Create a test user to test the mail flow.

For your reference:

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx

Hope this can be helpful to you.

Best regards,

Hi All,

Thanks for the response.

After I introduce exchange 2013 in X.com (As per the mentioned scenario), how the mail internal mail flow happens in x.com. Are the internal users (X.com users) contact CAS 2010 or CAS 2013?

• Edited by kopuula 12 hours 7 minutes ago

Mail flow is likely the least of your issues.  Exchange figures all that out internally when you install new servers (for Exchange 2007 and later--Exchange 2003 required you to create routing group connectors).  If you want to change the routing, you'll change your send connectors, DNS records, NAT mappings, mail gateway settings, and the like.