Your company has an Active Directory domain.
The company hastwo domain controllersnamed DC1and DC2.
DC1holds the Schema Master role.
DC1 fails.
You log on to Active Directory by using the administrator account.
You are not able to transfer the Schema Master operations role.
You need to ensure that DC2 holds the Schema Master role.
What should you do?
A.
Configure DC2 as a bridgehead server.
B.
On DC2, seize the Schema Master role.
C.
Log off and log on again to Active Directory by using an account that is a member of the Schema
Administrators group. Start the Active Directory Schema snap-in.
D.
Register the Schmmgmt.dll. Start the Active Directory Schema snap-in.
Explanation:
Answer.On DC2, seize the Schema Master role.
http://technet.microsoft.com/en-us/library/cc816645%28v=ws.10%29.aspx
Transfer the Schema Master
You can use this procedure to transfer the schema operations master role if the domain controller thatcurrently
hosts the role is inadequate, has failed, or is being decommissioned. The schema master is a forest-wide
operations master (also known as flexible single master operations or FSMO) role.
..
Note: You perform this procedure by using a Microsoft Management Console (MMC) snap-in, although you can
also transfer this role by using Ntdsutil.exe.
Membership in Schema Admins, or equivalent, is the minimum required to complete this procedure.
http://technet.microsoft.com/en-us/library/cc794853%28v=ws.10%29.aspx
Seize the AD LDS Schema Master Role
The schema master is responsible for performing updates to the Active Directory Lightweight Directory
Services (AD LDS) schema. Each configuration set has only one schema master. All write operations to the AD
LDS schema can be performed only when connected to the AD LDS instance that holds the schema master
role within its configuration set. Those schema updates are replicated from the schema master to all other
instances in the configuration set.
Membership in the AD LDS Administrators group, or equivalent, is the minimum required to complete this
procedure.
Caution: Do not seize the schema master role if you can transfer it instead. Seizing the schema master role is a
drastic step that should be considered only if the current operations master will never be available again.