Problems migrating from server 2003 R2 to server 2012 R2 essentials
I am trying to migrate a Windows Server 2003 R2 SP2 to Windows Server 2012 R2 Essentials (this is an installed server not a role). I get to Step 2 of "Install Windows Server 2012 R2 Essentials as a new replica domain controller:
http://technet.microsoft.com/en-us/library/dn408637.aspx
On this page I get to item 2 "2.To install Windows Server Essentials as a replica Windows Server 2012 R2 domain controller in an existing domain as global catalog, follow instructions in Install a Replica Windows Server 2012 Domain Controller in an Existing Domain (Level 200)."
This takes me to this page: http://technet.microsoft.com/en-us/library/jj574134.aspx
In the Active Directory Domain Services Configuration Wizard (ADDSCW) I select Add a domain controller to an existing domain. Click Next enter in the administrator credentials and domain. Clicking Next I get the following error "An Active Directory domain controller for the domain "mycompany.local" could not be contacted"
More info supplies the following info: Ensure that you supplied the correct DNS domain name. The 2003 server can be pinged by name and resolves to the correct IP address.
http://technet.microsoft.com/en-us/library/dn408637.aspx
On this page I get to item 2 "2.To install Windows Server Essentials as a replica Windows Server 2012 R2 domain controller in an existing domain as global catalog, follow instructions in Install a Replica Windows Server 2012 Domain Controller in an Existing Domain (Level 200)."
This takes me to this page: http://technet.microsoft.com/en-us/library/jj574134.aspx
In the Active Directory Domain Services Configuration Wizard (ADDSCW) I select Add a domain controller to an existing domain. Click Next enter in the administrator credentials and domain. Clicking Next I get the following error "An Active Directory domain controller for the domain "mycompany.local" could not be contacted"
More info supplies the following info: Ensure that you supplied the correct DNS domain name. The 2003 server can be pinged by name and resolves to the correct IP address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Don S.
There are two likely problems (I ran into the second one my self just last week) The first is as the error indicates - an improperly configured DNS somewhere. OR since this is a SBS2003 server youa re trying to contact, it likely has ISA server running on it. This will inherently block the DC join requests. You can mess around with the ISA rules and probably get it to work, or you can simply uninstall ISA on the SBS2003 server since one of the first steps was to replace it with an external Firewall device and point all the clients to the new firewall - so you should be needing the ISA any more. Once uninstalled, the SBS2003 server rebooted and the ICEW wizard rerun, you will find the new 2012 DC will join up just fine. Just went through this four days ago.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The DNS was working properly, server 2012 however uses IPV6 as the primary and as a result could not locate the domain sitting on a 2003 server.