Windows 10: Windows Server / Reset of krbtgt account / replication on other DC

Good morning, I am having a question.I was resetting a krbtgt password of an AD an old one - migrated, which appereantly could cause a problem in case that domain is indeed old and password was never reseted. After the first reset which was successfull .. AD is alive I noticed that krbtgt account does exist only on one DC, but not on the other one and I am not sure wheter was there even before .. :/ .Is this expected behaviour? .. Should krbtgt account exist only on the "first/original" DC and not on the other? Can someone pls check if you can see krbtgt on all of you DCs?Best Regards v

:)

 

Windows Server 2008R2 Main DC replicated into Windows Server 2012 Backuo DC - What to consider

Hello,

A server 2012 backup DC was created, altought, DHCP for exemple is not replicated from Server 2008.

Anyone know how to do it so if the server 2008 Main DC is down, users can access the ressources by the DHCP of the 2012 bachup DC

thanks in advance!

D OLI

 

NTDS replication failed on restored DC - Windows server 2008 R2 Enterprise

We have 2 DCs (Windows server 2008 R2 Enterprise) in our exchange domain, as one of them (not the GC) failed to startup properly after applying patch, we have restored it with the backup a day
before.


The DC was restored with non-authoritative mode with the procedure in the link below, and boot into DSRM on the first boot,
AD Protection Best Practices: Restoring Domain Controller (Part 2)


After restoring, the NTDS replication between servers failed with the error “The target principal name is incorrect”.

we found a solution in the link below

Troubleshoot AD replication error -2146893022 - Windows Server

In the first normal boot of the restored DC,- DNS on the restored DC can be launched

- Repadmin /replicate successful from GC to DC

- REPADMIN /SHOWREPS all passed

- REPADMIN /SHOWREPL all passed

- REPADMIN /replsummary with “The target principal name is incorrect” error- REPADMIN /SYNCALL with “The target principal name is incorrect”
and exited with fatal Win32 error: 8440 (0x20f8)

After the above test and rebooting the restored DC, DNS failed to launch with access denied error.
Some connectivity test failed as well.

As the top resolution in the above link doesn’t resolve the issue, it is suggested changing the password on the PDC Emulator operations master role holder with netdom resetpwd.

Target Principal Name is incorrect when manually replicating data between domain controllers - Windows Server

which means we have to make amendment on GC ( currently the only workable DC) in production site. We hope to know is there any
alternative in stead of making amendment on the GC.

Any one has idea on how to solve the replication error with “The target principal name is incorrect”? Thank you.

 

Server 2012

Also don't forget to reset the account in AD Users and Computers to avoid any SID issues.