Answered by:
Computers not locate DC at cross forest migration scenario (testing purposes)

Question
-
Hi,
I need to create a testing cross forest migration environment.
The scenario is the following:
Domain A:
- virtual network: NETA. DNS servers: 10.0.0.4, 10.0.0.6. IP range: 10.0.0.0/8
- domain name: domaina.local
- 1 DC: 10.0.0.4. Windows 2008 R2 SP1 (enterprise root CA too)
Domain B:
- virtual network: same above
- domain name: domainb.local
- 1 DC: 10.0.0.6. Windows 2012 (enterprise root CA too)
Joining a server to DomainA (to be a Ex2007): OK
Joining a server to DomainB (to be a Ex2013): Fail. Cannot locate a DC in the domain DomainB. This is because the first DNS server at virtual network is 10.0.0.4 (DomainA DC).
I have tried creating another virtual network and connecting the DomainB VMs to this new virtual network. The I tried creating a new VM with 2 NICs (the idea was: first NIC conencted to first virtual network and second NIC conencted to second virtual network and install routing services between two virtual networks) but cannot create the second NIC.
The questions are:
It is possible to route traffic between virtual networks?
If no
How to create a cross forest migration environment like above?
Thanks in advance!
- Moved by Jambor yaoMicrosoft employee Thursday, September 11, 2014 5:15 AM
Wednesday, September 10, 2014 2:35 PM
Answers
-
Hi,
Thank you for posting here.
Q1: Is it possible to route traffic between virtual networks?
Yes.
Q2: How to create a cross forest migration environment like above?
To obtain a downloadable version of this guide in .doc format, see ADMT Guide: Migrating and Restructuring Active Directory Domains (http://go.microsoft.com/fwlink/?LinkId=191734).
As part of deploying the Active Directory® directory service or Active Directory Domain Services (AD DS), you might choose to restructure your environment for the following reasons:
- To optimize the arrangement of elements within the logical Active Directory structure
- To assist in completing a business merger, acquisition, or divestiture
Restructuring involves the migration of resources between Active Directory domains in either the same forest or in different forests. After you deploy Active Directory or AD DS, you might decide to further reduce the complexity of your environment by either restructuring domains between forests or restructuring domains within a single forest.
Refer these links for migration of AD 2003 to 2008. I hope this can be used for Windows 2008 R2 SP1 to Windows 2012 migration.
- Proposed as answer by Susie Long Wednesday, September 17, 2014 2:32 AM
- Marked as answer by Susie Long Wednesday, September 17, 2014 2:33 AM
Wednesday, September 10, 2014 5:59 PM -
Hi,
I am glad that you got most of the answers by referring the details mentioned above. Here is the link for Vnet to Vnet connection on Azure.
http://msdn.microsoft.com/en-us/library/azure/dn690122.aspx
for traffic routing between Vnets refer this link
- Marked as answer by Susie Long Wednesday, September 17, 2014 2:33 AM
Thursday, September 11, 2014 11:22 AM
All replies
-
Hi,
Thank you for posting here.
Q1: Is it possible to route traffic between virtual networks?
Yes.
Q2: How to create a cross forest migration environment like above?
To obtain a downloadable version of this guide in .doc format, see ADMT Guide: Migrating and Restructuring Active Directory Domains (http://go.microsoft.com/fwlink/?LinkId=191734).
As part of deploying the Active Directory® directory service or Active Directory Domain Services (AD DS), you might choose to restructure your environment for the following reasons:
- To optimize the arrangement of elements within the logical Active Directory structure
- To assist in completing a business merger, acquisition, or divestiture
Restructuring involves the migration of resources between Active Directory domains in either the same forest or in different forests. After you deploy Active Directory or AD DS, you might decide to further reduce the complexity of your environment by either restructuring domains between forests or restructuring domains within a single forest.
Refer these links for migration of AD 2003 to 2008. I hope this can be used for Windows 2008 R2 SP1 to Windows 2012 migration.
- Proposed as answer by Susie Long Wednesday, September 17, 2014 2:32 AM
- Marked as answer by Susie Long Wednesday, September 17, 2014 2:33 AM
Wednesday, September 10, 2014 5:59 PM -
Thanks Girish for your response.
My environment is for testing purposes only. I need to duplicate a customer's environment. Test some procedures prior production environment.
Thanks for the AD guides and links, they are helpful.
The routing between virtual networks is my main problem at azure.
Please, could you help me with the procedure to enable routing between virtual networks at azure(guides/links)?
Thanks in advance!
Thursday, September 11, 2014 4:34 AM -
Hi,
I am glad that you got most of the answers by referring the details mentioned above. Here is the link for Vnet to Vnet connection on Azure.
http://msdn.microsoft.com/en-us/library/azure/dn690122.aspx
for traffic routing between Vnets refer this link
- Marked as answer by Susie Long Wednesday, September 17, 2014 2:33 AM
Thursday, September 11, 2014 11:22 AM -
Hi,
As this thread has been quiet for a while, we will mark it as ‘Answered’ as the information provided should be helpful. If you need further help, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
By the way, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.Best regards,
Susie
Wednesday, September 17, 2014 2:33 AM