Migración Windows Server 2012 R2 Estándar a Windows Server Estándar 2019

Question

Siguiendo los pasos de Migración Windows Server 2012 R2 Estándar a Windows Server 2019.

Se realizan todos pasos correctos pero en el momento de despromover el DC viejo (Windows Server 2012 R2 Standrad) me da el error:

<<Error en la operación debido a: No se pudo establecer contacto con el controlador de dominio en el dominio Energy.local que contenía una cuenta para este equipo. Haga al equipo miembro de un grupo de trabajo y, después, vuelva a unirse al dominio antes de reintentar la promoción. "El dominio especificado no existe o no se pudo poner en contacto con él.">>

DNS está correcto y se comunican ambos controladores de dominio replicando la información correctamente.

Answer 1

Hello Jonathan Vico,

Thank you for posting in Microsoft Community forum.

Please check all the ports that AD required on 2012 R2 DC and 2019 DC.

Active Directory and Active Directory Domain Services Port Requirements

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd772723(v=ws.10)?redirectedfrom=MSDN

Active Directory Replication over Firewalls

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727063(v=technet.10)?redirectedfrom=MSDN

Here is a similar thread for your reference.
[42d7-bed6-87c-bf01] (microsoft.com)

I hope the information above is helpful.

If you have any question or concern, please feel free to let us know.

Best Regards,
Daisy Zhou

Answer 2

Dear colleague,

Thank you for the answer.

The firewall is disabled.

Regards.

Answer 3

Hello Jonathan Vico,

Thank you for your reply.

I assume you have transferred all the FSMO roles into 2019 DC from 2012 R2 DC.

You can check the DNS setting on this 2012 R2 DC, check if the preferred DNS server of the 2012 R2 is the IP address of 2019 DC (assume the 2019 DC is also a DNS server).

Also, on 2012 R2 DC,
ping domain name and check the result.
ping 2019DCname.domain.com (FQDN of 2019) and check the result.
ping IP address of 2019 DC and check the result.

Best Regards,
Daisy Zhou

Answer 4

The result of the PING command was successful.

I check other ways:

1. remove active directory services role and depromote domain controller wizard
2. NTDSUTIL partition management: "remove nc replica <ApplicationDirectoryPartition> <DomainController>", ""Delete NC...".

all paths without success

Answer 5

Hello Jonathan Vico,

Good day!

You can perform metadata cleanup for the 2012 R2 DC on 2019 DC, run the commands below on 2019 DC.
https://filestore.community.support.microsoft.com/api/images/af6d4ba1-26da-424b-9393-2c6e3a40cfbf?upload=true&fud_access=wJJIheezUklbAN2ppeDns8cDNpYs3nCYjgitr%2BfFBh2dqlqMuW7np3F6Utp%2FKMltnRRYFtVjOMO5tpbpW9UyRAwvLeec5emAPixgq9ta07Dgnp2aq5eJbnfd%2FU3qhn54Ui9c7IY3%2BVaDGM794ieFEWFOTytTrMKy7m1XQpeIKlfhHZvv6qxFNypZh8EVO%2BjzMgLRnj7SrY%2FjVoV7qs8fDiK994oMxVrhrFAMYDcU%2FzpY9toOXSATTjZnLSpjFz9SccXnhheNsjq5%2BSBcAlboaIyotVwfBHQkvr2r9qTwWe8LyDxKl9RZNfV1ChJKMqbiUUtc6Ih4PCDUx6UE9pGjCxQdkjeKKG5GxJq3a0zJtDJxVUB%2F1KZnJLk4U2KvbWs8va%2FQSp72ps10Y%2FphEcFEUmVonS0lP28u5FIKJe4oPeI%3D

If you have any question or concern, please feel free to let us know.

Best Regards,
Daisy Zhou