none
AD Forest Merger

    Question

  • Org A and Org B Merging to become OrgAB. We were brainstorming as to whether to setup a new brand new AD domian which will reflect  the name OrgAB or let OrbB Domain merge in to OrgA and rename the domain to OrgAB or vice versa. However considering the risk associated with  renaming a domain, we are reluctant go with the second option. At the same time setting up a new Domain has its own problem in terms of timeline and  the prepration that has to go with(We have exchange,SCOM,SCCM etc running in the environment). During the brainstorimng a new idea was floated which was to allow one domain merge in to another  and instead of renaming domain, change the UPN to reflect orgAB. So the domain name will be unchanged in the back-end , but from the end user perspective it  is a new domain. 

    Any one has attempted this before as part of merger/acquisition? What are the  risks associated with this? 

    Thank you and appreciate all your  recommendations

    Friday, February 10, 2017 11:42 AM

All replies

  • Hi

    (We have exchange,SCOM,SCCM etc running in the environment).>>> Then you should not think about domain rename operation.Cause that's not an supported scenario when exchange already deployed on domain.

     So you should setup new domain first.(AB),then migrate from domain A to Domain AB,when done,again you should migrate from domain B to domain AB.

     This is a lot pf workloaded but less risky i guess..

    Check these for migration procedure;

    ADMT ; https://technet.microsoft.com/en-us/library/cc974332%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

    exc.migrate ; https://blogs.technet.microsoft.com/meamcs/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i/


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Friday, February 10, 2017 11:57 AM
  • Hi,
    I would suggest you take a look at the following articles regarding AD forests merge, you could refer to some risks and consolidation during the process:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/32f66fc1-813b-4ccc-8ccd-9f6dd469c9bb/active-directory-forest-mergers-consolidation?forum=winserverDS
    http://windowsitpro.com/windows-server/plan-and-execute-active-directory-merger-part-1
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, February 13, 2017 8:16 AM
    Moderator
  • Thank you for the resources. However I am specifically looking for the effect of doing the upn change to reflect the new org name, Thank you.
    Monday, February 13, 2017 9:09 AM
  • Thank you for the resources. However I am specifically looking for the effect of doing the upn change to reflect the new org name, Thank you.
    Monday, February 13, 2017 9:10 AM
  • So Upn will be changed.But you need old UPN also,you can add altenate UPN.(same as old upn.)

    https://technet.microsoft.com/en-us/library/cc772007(v=ws.11).aspx


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    Monday, February 13, 2017 10:51 AM