Issue seizing fsmo role

Jason 1 Reputation point
2020-08-14T02:14:38.81+00:00

Hello All

I'm trying to transfer fsmo role from a 2008 sbs to 2012 r2 server but having some issue transferring the PDC and RID master roles. The others (schema master, naming master and infrstructure master) were trasnfered successfully.

i ran ntdsuil.exe and seize the PDC and RID and it says 'transferred successful - seizure not required'

However 'netdom query fsmo' shows it's still on the sbs 2008.

Now this is where its get even more complicated. When you open AD user and computer and check operations master on the 2012 server it shows the PDC and RID master as the 2012 server but on the 2008 sbs it still shows the server 2008 as the operation master for PDC and RID and does not allow it to be change there either as it list its own self as the server to change to.

Any solution will be appreciated

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,616 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
417 questions
0 comments

14 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Thameur-BOURBITA 32,626 Reputation points
    2020-08-14T12:02:53.673+00:00

    Hi

    When you seize FSMO role to another domain controller , you have to demote old DC using metadata cleanup procedure on new DC.

    In your case , since you have performed a seizing operation , you have to remove old DC using metadata cleanup procedure.

    https://video2.skills-academy.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

    Please don't forget to mark this reply as answer if it help you to fix your issue

    0 comments
  2. Anonymous
    2020-08-14T12:15:20.307+00:00

    I'd decommission / demote the new one, then work through these ones to clear up the journal wrap errors
    https://video2.skills-academy.com/en-us/services-hub/health/remediation-steps-ad/investigate-file-replication-service-frs-journal-wrap-conditions-on-domain-controllers
    https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi

    perform cleanup (if necessary) to remove failed / non-existent domain controllers.
    https://video2.skills-academy.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

    once domain health is confirmed 100% try again.

    if problems persist then put up a new set of files to look at.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  3. Jon Alfred Smith 541 Reputation points
    2020-08-14T12:19:40.27+00:00

    Be aware that the source is Small Business Server (SBS), which behaves differently from normal Windows servers. It was never designed to co-exist with another DC. There used to be tools to migrate and update from SBS. Now you have to do it manually. Be sure that the transfer of FISMO roles is the last thing you do. There is a grace period of I think 21 days. After that SBS will shut down without FISMO roles. With SBS 2003 R2 I've seen strange behaviors, the same FISMO roles pretending to be two places at once. (I once worked with SBS for some two or three years.)

    0 comments
  4. Vicky Wang 2,646 Reputation points
    2020-08-17T07:02:54.847+00:00

    Hi,
     
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
     
    Best Regards,
    Vicky

    0 comments
  5. Jason 1 Reputation point
    2020-08-17T13:42:40.327+00:00

    Thanks for the information. I'm still working on it.