Trace Event IDs 5788 and 5789 occur across Active Directory and Windows DNS

Use this document to connect an official requirement or behavior to observable evidence: Trace Event IDs 5788 and 5789 occur across Active Directory and Windows DNS. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Event IDs 5788 and 5789 occur from Microsoft supports the following bounded statements:

• At Introduction below H1, Microsoft states: “This article provides solutions to an issue where event ID 5788 and event ID 5789 are logged when the DNS domain name and the Active Directory domain name differ on a Windows-based computer.” The research record locates this support at Introduction below H1.
• At Symptoms, Microsoft states: “On Windows Vista and later versions, you receive the following error message during interactive logon:” The research record locates this support at Symptoms.

Only the traced statements above are asserted as source facts. Apply the review to Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services after confirming that the source and deployed context match.

What the source does not establish

The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Symptoms, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Introduction below H1; Symptoms through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents.

Label this evidence set DSE-20260827-359 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

Official references

• Event IDs 5788 and 5789 occur — Microsoft