Configure gMSA Kerberos delegation without relying on the missing tab

Use this document to connect an official requirement or behavior to observable evidence: Configure gMSA Kerberos delegation without relying on the missing tab. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Configuring Kerberos Delegation for Group Managed Service Accounts from Microsoft supports the following bounded statements:

• The ADUC Delegation tab does not appear for standalone or group managed service accounts. The research record locates this support at Opening overview.
• Microsoft documents PowerShell and direct userAccountControl approaches for configuring the required delegation state. The research record locates this support at Sections: Use PowerShell commands; Manually update the userAccountControl value.

Only the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match.

What the source does not establish

Use constrained delegation designs and verify SPNs before changing delegation attributes. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Sections: Use PowerShell commands; Manually update the userAccountControl value, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?
• Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

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 forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.

Verification and evidence

Keep the source locations Opening overview; Sections: Use PowerShell commands; Manually update the userAccountControl value adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, with enough identity and timing data for an independent recheck.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• Configuring Kerberos Delegation for Group Managed Service Accounts — Microsoft