Announcement

Collapse
No announcement yet.

Error when transfering PDC role

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error when transfering PDC role

    Greetings,

    I have inherited a domain during an acquisition of another company. I have added a second DC to their single server domain. I have moved all of the FSMO roles except the PDC emulater. When I try to migrate the PDC role I get the error.
    This computer is a non-replication partner. Transferring the role to this computer may cause a full sync on all NT4 BDCs. Do you want to continue with the transfer?
    Both DCís are W2k3 Standard and the domain function level is windows 2000 mixed Forest function level is Windows 2000.
    I have setup AD integrated DNS
    I will be updating the Domain and forest function level tonight.
    Has anyone seen this error before and has a fix for it?

  • #2
    Re: Error when transfering PDC role

    I take it you have ensured AD is replicating fully between the old and new DCs?
    Check your firewall as suggested here:
    http://webcache.googleusercontent.co...&ct=clnk&gl=uk
    (scroll way down to see useful information)
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Error when transfering PDC role

      Greetings Ossian,

      Windows Firewall is turned down on both DC's. I also have checked to make sure that AD is replicating fully between the old and new DC's.

      I have ran replmon on both DC's:

      Original DC:
      Microsoft Windows [Version 5.2.3790]
      (C) Copyright 1985-2003 Microsoft Corp.
      C:\Documents and Settings\ssimc_adm>dcdiag
      'dcdiag' is not recognized as an internal or external command,
      operable program or batch file.
      C:\Documents and Settings\ssimc_adm>cd \
      C:\>cd program files
      C:\Program Files>cd support tools
      C:\Program Files\Support Tools>dir
      Volume in drive C has no label.
      Volume Serial Number is 4479-DF59
      Directory of C:\Program Files\Support Tools
      02/13/2007 04:03 PM <DIR> .
      02/13/2007 04:03 PM <DIR> ..
      08/03/2000 05:01 PM 217,872 dcdiag.exe
      07/14/2000 11:10 AM 12,843 dcdiag_license.txt
      07/14/2000 11:47 AM 6,297 SupportToolDownloadReadme.htm
      3 File(s) 237,012 bytes
      2 Dir(s) 56,992,416,768 bytes free
      C:\Program Files\Support Tools>dcdiag
      Domain Controller Diagnosis
      Performing initial setup:
      Done gathering initial info.
      Doing initial required tests
      Testing server: Default-First-Site-Name\PRIMEENERGY
      Starting test: Connectivity
      ......................... PRIMEENERGY passed test Connectivity
      Doing primary tests
      Testing server: Default-First-Site-Name\PRIMEENERGY
      Starting test: Replications
      ......................... PRIMEENERGY passed test Replications
      Starting test: NCSecDesc
      ......................... PRIMEENERGY passed test NCSecDesc
      Starting test: NetLogons
      ......................... PRIMEENERGY passed test NetLogons
      Starting test: Advertising
      ......................... PRIMEENERGY passed test Advertising
      Starting test: KnowsOfRoleHolders
      ......................... PRIMEENERGY passed test KnowsOfRoleHolders
      Starting test: RidManager
      ......................... PRIMEENERGY passed test RidManager
      Starting test: MachineAccount
      ......................... PRIMEENERGY passed test MachineAccount
      Starting test: Services
      RPCLOCATOR Service is stopped on [PRIMEENERGY]
      TrkWks Service is stopped on [PRIMEENERGY]
      TrkSvr Service is stopped on [PRIMEENERGY]
      ......................... PRIMEENERGY failed test Services

      Starting test: ObjectsReplicated
      ......................... PRIMEENERGY passed test ObjectsReplicated
      Starting test: frssysvol
      ......................... PRIMEENERGY passed test frssysvol
      Starting test: kccevent
      ......................... PRIMEENERGY passed test kccevent
      Starting test: systemlog
      ......................... PRIMEENERGY passed test systemlog
      Running enterprise tests on : usmdcus.primeenergy.com
      Starting test: Intersite
      ......................... usmdcus.primeenergy.com passed test Intersite
      Starting test: FsmoCheck
      ......................... usmdcus.primeenergy.com passed test FsmoCheck

      ---------------------------------------------------------------------------------------------------

      The new DC has no errors.

      Comment


      • #4
        Re: Error when transfering PDC role

        If you are happy all has replicated, I would consider
        a) Attempting to transfer PDC role properly (assuming you have no NT4 BDCs as the error indicates)
        b) "Carpe FSMO" if A fails
        c) Demoting original DC, remove from domain, flatten
        d) Clean metadata to remove all traces of it
        e) Rebuild under different name, rejoin domain, DCPROMO

        That will remove any lingering errors
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: Error when transfering PDC role

          How did you try transfering this Role, GUI or using NTDSUTIL? This may be worth a read. http://www.petri.com/transferring_fsmo_roles.htm
          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment

          Working...
          X