In order to fix this behavior, all of the FSMO roles need to be seized in order for the restored domain controller to consider the roles valid.
WARNING: It is very important to make sure there are no other existing domain controllers in the environment which are still functioning before all of the roles are seized. If this is not the case, please make sure to call Microsoft first before attempting to seize the FSMO roles.
Please review Microsoft's KB article number 255504 for the exact steps to seize the FSMO roles - https://support.microsoft.com/en-us/kb/255504
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center