To seize the Schema Master role from a failed domain controller (DC1) using ntdsutil.exe, you must navigate specific contexts:

1. roles: Enters the "FSMO maintenance" context.
2. connect (representing connections): Enters the "server connections" context required to bind to a specific instance.
3. connect to server dc2.adatum.com: Binds the session to the surviving domain controller (DC2) where the role will be seized.
4. quit: Exits the "server connections" context and returns to the "FSMO maintenance" context.
5. seize schema master: Executes the forced transfer of the role to the connected server (DC2).

The command metadata cleanup is used for removing records of failed servers but is not part of the immediate sequence to seize an FSMO role.

Microsoft Learn. (2024). Transfer or seize FSMO roles in Active Directory Domain Services. Retrieved from https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

Relevance: This official documentation details the exact command line sequence for ntdsutil under the section "Seize FSMO roles," confirming the order: roles > connections > connect to server > quit > seize .

Microsoft Learn. (2023). Ntdsutil. Retrieved from https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc753343(v=ws.11)

Relevance: Provides the syntax and context hierarchy for Ntdsutil commands, verifying that quit is required to return from the connection context before issuing role maintenance commands.