Domain Controller Migration 2012 R2 to 2012 R2

[edu_infra]

Hi,

 

I am trying to migrate the domain controller of Windows Server 2012 R2 (DC01) to another Server 2012 R2 (DC02).

 

I already installed Active Directory Domain Services on DC02, and when I go to Change Directory Server appears the two servers (DC01 and DC02) as available, but when I went to DC01 is not appearing the destination server (DC02) only appears DC01. What could I am doing wrong?

 

Thanks

[kmount]

You installed the ADDS role on DC02 but did you run the process to add the new domain controller to your domain?

[edu_infra]

You installed the ADDS role on DC02 but did you run the process to add the new domain controller to your domain?

Yes, I passed troungh the wizard of Deployment Configuration, Add a domain controller to an existing domain, etc..

All the objects of AD users and computers were replicated to DC02...

 

Maybe could be something in DNS of DC01..don't know

[kmount]

Sorry, I misread your first post where you said from DC2 you could see both.

 

In AD Users and Computers on DC01 can you see DC02 here?

 

Has sysvol replicated between them?

[edu_infra]

Sorry, I misread your first post where you said from DC2 you could see both.

 

In AD Users and Computers on DC01 can you see DC02 here?

 

Has sysvol replicated between them?

 

Yes, DC02 is in Domain Controller folder (OU) in AD of DC01.

About sysvol, I don't know, since I had just used the wizard to deploy.

 

Edited July 5, 2014 by edu_infra

[LukeC]

You can check your replication by going into cmd and type repadmin /showrepl this will show you last time the CDs replicated to each other and what was replicated.

[edu_infra]

You can check your replication by going into cmd and type repadmin /showrepl this will show you last time the CDs replicated to each other and what was replicated.

 

In DC2 seems to be all right:

 

Repadmin: running command /showrepl against full DC localhost

Default-First-Site-Name\DC02

DSA Options: IS_GC

Site Options: (none)

DSA object GUID: d301c076-8430-4c31-86eb-9772e2434213

DSA invocationID: 975d50ec-c9e9-4ee8-8096-fb9261f65d16

 

 

 

==== INBOUND NEIGHBORS ======================================

 

 

DC=xyz,DC=int

Default-First-Site-Name\DC01 via RPC

DSA object GUID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

Last attempt @ 2014-07-07 16:15:28 was successful.

 

 

CN=Configuration,DC=xyz,DC=int

Default-First-Site-Name\DC01 via RPC

DSA object GUID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

Last attempt @ 2014-07-07 16:15:28 was successful.

 

 

CN=Schema,CN=Configuration,DC=xyz,DC=int

Default-First-Site-Name\DC01 via RPC

DSA object GUID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

Last attempt @ 2014-07-07 16:15:28 was successful.

 

 

DC=DomainDnsZones,DC=xyz,DC=int

Default-First-Site-Name\DC01 via RPC

DSA object GUID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

Last attempt @ 2014-07-07 16:15:28 was successful.

 

 

DC=ForestDnsZones,DC=xyz,DC=int

Default-First-Site-Name\DC01 via RPC

DSA object GUID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

Last attempt @ 2014-07-07 16:15:28 was successful.

 

 

In DC1 appearing this error:

 

Repadmin: running command /showrepl against full DC localhost

Default-First-Site-Name\DC01

DSA Options: IS_GC

Site Options: (none)

DSA object GUID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

DSA invocationID: d7f140c7-1b3c-475a-ba1c-5bc9b142563d

 

 

Source: Default-First-Site-Name\DC02

******* 1 CONSECUTIVE FAILURES since 2014-07-07 16:22:02

Last error: 8524 (0x214c):

The DSA operation is unable to proceed because of a DNS lookup failure.

 

 

Naming Context: CN=Configuration,DC=xyz,DC=int

Source: Default-First-Site-Name\DC02

******* WARNING: KCC could not add this REPLICA LINK due to error.

 

 

Naming Context: DC=xyz,DC=int

Source: Default-First-Site-Name\DC02

******* WARNING: KCC could not add this REPLICA LINK due to error.

 

 

Naming Context: CN=Schema,CN=Configuration,DC=xyz,DC=int

Source: Default-First-Site-Name\DC02

******* WARNING: KCC could not add this REPLICA LINK due to error.

Edited July 7, 2014 by edu_infra

[techy32]

Can you check the DNS entries on both servers. It seem to be DNS error....

[LukeC]

check your dns details on both DCs Nics and make sure the DNS entries point to each other Preferred and alternate address, one should be its own ip and the other should be the other DNS server (assuming both DCS on DNS servers in an ad integrated zone). Check your A and CNAME records in DNS.

You can also run dcdiag in cmd to see if that gives you any more clues.

[edu_infra]

check your dns details on both DCs Nics and make sure the DNS entries point to each other Preferred and alternate address, one should be its own ip and the other should be the other DNS server (assuming both DCS on DNS servers in an ad integrated zone). Check your A and CNAME records in DNS.

You can also run dcdiag in cmd to see if that gives you any more clues.

I found the problem.

In DC01 the DNS of the NIC was pointed to the router IP. Just changed that and at the same moment the windows "Change Directory Server" appeared the DC02 correctly.

 

Thank you so much!

[johnhart96]

Did you change the Operations master and the Forrest Root controller to the other one, because I think this does not replicate in the SYSVOL ???