locked
Merging & Migrating Users From Site B to Site A RRS feed

  • Question

  • Hi,

    I am looking for solution or document to fulfill our exchange email IDs merging. We have to different independent sites Site A & Site B. 
    Site A scenario - In Site A we are having active directory domain abc.com & Exchange server 2013 with multiple Internal Relay domain. Internal Relay domains are abc.com, def.com,ghi.com & more. All domain systems & exchange users login to abc.com for access as no any subdomains to active directory (like user1@abc.com login using abc\user1, user2@def.com login using abc\user2, user3@ghi.com login using abc\user3 for accessing exchange emails).  
    Site B scenario - mno.com as active directory domain & multiple email domains mno.com, pqr.com, stu.com & more. At site B all emails are hosted to Exchange Online cloud (Office 365 E1 or Office 365 E3).
    There is no any communication or trust relationship between Site A & Site B.
    Now we are merging Site A & Site B. In merging we are planning to create new exchange domain xyz.com. To xyz.com we want to migrate users from abc.com of Site A & mno.com of Site B. This will create new mailbox newuser1@xyz.com, newuser2@xyz.com. Here as per our requirement we want to migrate/ create new user to Exchange server of Site A. From Site B dont want to migrate or merge other domain users except mno.com.
    We are thinking to create new mailboxes on Exchange server for Site A (abc.com) & Site B (mno.com) users as xyz.com. For Site A users dont think much challenge, but for Site B users looking for smooth migration. When we create new email IDs for Site B users as xyz.com we are not discontinuing mno.com email IDs. These users requires emails for both domains (xyz.com on Exchange 2013 & mno.com to cloud). If we create new mailbox for Site B users how they will login to Exchange email ID using xyz\newuser. This is required for both sites users (Site A & Site B) for xyz.com users. Also how user1@mno.com emails we can forward or redirect to newuser1@xyz.com of Site B user.

    Here we want to clear that we are going to use Exchange 2013 on premise setup only.

    Looking for proper document for merger.

    Thanks,
    Sachin  
    Friday, July 17, 2020 6:20 AM

All replies

  • Hi Sachin,

    1. Is there a hybrid deployment in your site B or is it synced with AD? 

    2. Have you added all the domains in Site B to O365 or just mno.com?

    3. What's your purpose of "These users requires emails for both domains (xyz.com on Exchange 2013 & mno.com to cloud)"?  I'm asking this because it seems difficult for a mailbox using different email addresses between on-premise and Online.

    And I don't think it's possible to " forward or redirect to newuser1@xyz.com of Site B user.", except you seperate it as two mailboxes and create transport rules for forwarding messages.

    This Exchange Server 2013 - Setup, Deployment, Updates, and Migration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Eric Yin


    Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Monday, July 20, 2020 8:39 AM
  • Is there a hybrid deployment in your site B or is it synced with AD?  - Exchange on cloud O365 & local AD sync with Azure AD.

    Have you added all the domains in Site B to O365 or just mno.com? - Just mno.com & new email ID will be mno.com & xyz.com at initial stage & later on only xyz.com

    We want to migrate all mno.com to on-premise with xyz.com as additional alias.

    What is best option if we want to keep Hybrid Setup.

    Thanks,

    Sachin Shinde

    Tuesday, July 21, 2020 4:41 AM
  • Hi Sachin Shinde,

    Since there's only Exchange online on SiteB, it will be tough work to migrate those mailboxes back to on-premise.

    I would suggest to go to the final stage directly, add xyz.com as accepted domain on O365 and create email address policy for it, if you also need to logon with xyz.com, some scripts can help you change the UPN for those users.

    This Exchange Server 2013 - Setup, Deployment, Updates, and Migration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Eric Yin


    Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Thursday, July 23, 2020 7:56 AM
  • Hi,

    Now here new development, we have decided to go for Hybrid Configuration for new domain xyz.com. Users from site A on-premise having abc.com email address will add xyz.com as email alias,  & users from Site B exchange online having mno.com email address will add xyz.com as email alias. We will keep MX with on-premise setup. 

    Now our worry is if we keep Hybrid setup, how GLobal Address List & Calender sharing will happen. Will both sites able to see common address book & each other members calendar information.

    To achieve this do we require Active directory trust. As site A on-premise is having Active directory domain controller abc.com & Site B has local on-premise mno.local domain controller with Azure AD at cloud mno.com and it is connected with AD connect. Do we require Azure AD connect on-premise at Site A to connect mno.com at Site B.

    Also can we achieve this without AD trust relationship or with ADFS. 

    Note- We dont want to change AD login for either sites.

    Thanks,

    Sachin

    Friday, July 24, 2020 5:29 AM
  • Hi,

    There is one thing I want to ensure first, when you "create a new domain xyz.com", do you mean "add a tree domain to existing forest" like this?

    If yes, calendar information should not be worried. One forest can have only one Exchange organization, and calendars are visible amont those domains in same organization.

    For address book, theoretically there should be trust between them and address book should be shared, need to ask some AD experts to verify it.

    Here is a similar thread:https://social.technet.microsoft.com/Forums/en-US/0809196e-677e-47ea-a008-8a461d3830e0/crossforest-address-book-sync?forum=ocsaddressbook

    If it doesn't work as expected, some other solutions you can try:https://social.technet.microsoft.com/Forums/en-US/7e89a7c9-37cf-4db6-bcba-e0fa889a7983/how-do-i-share-exchange-global-address-list-gal-across-different-forests-without-using-federated?forum=exchangesvradmin

    This Exchange Server 2013 - Setup, Deployment, Updates, and Migration Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Eric Yin


    Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.


    Wednesday, July 29, 2020 9:15 AM