Hi, I'm having problems migrating a DC with server 2012 to Server 2016.
I followed the steps mentioned in https://social.msdn.microsoft.com/Forums/en-US/91e3213e-36ec-48c1-bbc9-8a6694df6e5b/need-help-understanding-the-proper-steps-when-migrating-from-a-server-2012-dc-to-a-server-2016-dc?forum=winservergen
Deploy a 2016 Domain controller (as Global Catalog) in your environment
Do a DCDIAG health check after deploying
Check if replication is working properly using repadmin /showrepl and repadmin /replsum
Change all DHCP scopes to use the new domain controller as a secondary DNS server
Change all static IP configuration for all your servers to use the new domain controller as a secondary DNS server
Inform all teams to make sure that all services use the new DC as a secondary DNS server
Transfer all FSMO roles to the new domain controller
Check DCDIAG and replication again and make sure everything is working as expected
Decommission the 2012R2 Domain controller
Before proceeding further, make sure that there are no traces left at all from the old DC in DNS (Check carefully)
After that you can go ahead and change the IP address of the Domain Controller (You can follow this link - It is quite simple)
Upgrade the domain functional level to 2016
My problem starts with dcdiag, in the new server, advertising, sysvol and netlogon test are not passed.
First, I do this fix : https://www.youtube.com/watch?v=iimNEeSp1is&t=264s
Now, I can see sysvol folder shared on the new DC, but no netlogon and no replication.
So after searching, I found and did this fix :
https://www.checkyourlogs.net/how-to-fix-missing-sysvol-and-netlogon-share-and-replication-issues-on-new-domain-controller-at-azure/
Now, I can see netlogon share also, but when I check the sysvol folder no replication is made.
repadmin /showrepl and repadmin /replsum shows everything is ok.
Dcdiag in the old 2012 shows everything is ok.
Primary dns in dc01 is dc02 and secondary is itself , same as the dc02.
Any clue? thanks!