Hi Pisek,
Thank you for running the additional read-only search and confirming that no production changes have been made.
Is the evidence sufficient to plan the recovery?
Yes. Because the Infrastructure Master can read the domain root and the subtree search returned no matching object, this is strong evidence that the Password Settings Container is absent from that DC’s domain naming context. Combined with your earlier LDAP, ADSI Edit, and Recycle Bin checks, it is sufficient to plan the recovery documented in Microsoft KB3144809.
Before carrying out the repair, make sure the earlier searches covered each writable DC using the domain naming context as the search base. Microsoft’s documented read-only search is:
repadmin /showattr <DC-FQDN> ncobj:domain: /filter:"(objectClass=msDS-PasswordSettingsContainer)" /subtree
If any DC returns the object at a different location, follow the KB’s guidance for moving it; do not use the missing-container repair path.
How should you identify the operation marker?
The KB’s missing-container procedure shows this operation marker as its example:
CN=71482d49-8870-4cb3-a438-b6fc9ec35d70
You can check whether that exact object exists under CN=Operations on the Infrastructure Master with this read-only query:
$dc = (Get-ADDomain).InfrastructureMaster
$domainDN = (Get-ADRootDSE -Server $dc).defaultNamingContext
$markerDN = "CN=71482d49-8870-4cb3-a438-b6fc9ec35d70,CN=Operations,CN=DomainUpdates,CN=System,$domainDN"
Get-ADObject -Server $dc -Identity $markerDN -Properties objectGUID,whenCreated,whenChanged
The KB names this GUID as an example in this recovery procedure. Confirm that the exact object exists at that location before considering any deletion. Do not delete all entries under CN=Operations, substitute a different marker, or select one based on revision 16; the revision value does not identify the marker. If the specified object is absent or you cannot confirm that it is the applicable operation, pause and have an AD DS specialist or Microsoft Support review the marker before making changes.
Precautions before and after the repair
Before proceeding, verify replication health with repadmin /replsummary and dcdiag /e /c /v, confirm that you have recent, valid AD-aware system-state backups and a recovery plan, and record the current revision and operation-marker details. Schedule a change window and follow the KB’s sequence on the Infrastructure Master as a Domain Admin. Microsoft’s Adprep documentation confirms the role and permission requirements for /domainprep.
The KB does not include a step to restart or demote the Infrastructure Master. However, the procedure changes replicated AD update state, so uninterrupted authentication cannot be guaranteed. Afterward, review ADPrep.log, confirm the container is under CN=System, and verify that it has replicated to all writable DCs. Recheck replication health and monitor authentication-related events.
Thank you again for documenting the checks and taking a cautious approach. If you share whether the marker query finds the GUID and provide a redacted replication summary, we can review those results before you proceed.