Announcement

Collapse
No announcement yet.

Problem Demoting a DC

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

  • Problem Demoting a DC

    Hi all,
    Im working in a child domain, the domain has 2 DCs, gvanet1 and gvanet3.

    Im trying to demote gvanet3, we are in the process of migrating to a single domain model instead of parent/child/external.

    When I run dcpromo, I hit next on the screen asking to indicate whether this is the last DC in the domain (without checking the box because its not!) I get this message:

    You did not indicate that this AD DC is the last DC for the domain
    However, no other AD DCs for that domain can be contacted.

    Do you want to proceed anyway?

    bleh bleh

    My problem is this is not the last DC in the domain.

    I run netdom query fsmo and it returns:

    Schema master NYCDC02.z.com
    Domain naming master NYCDC02.z.com
    PDC gvanet1.GVA.Z.com
    RID pool manager gvanet1.GVA.Z.com
    Infrastructure master gvanet1.GVA.Z.com
    (replaced my domain with a z)

    I then did:
    nslookup
    Default Server: gvanet1.gva.z.com
    Address: 192.168.96.156
    > set type=srv
    > _ldap._tcp.pdc._msdcs.gva.z.com
    Server: gvanet1.gva.z.com
    Address: 192.168.96.156
    _ldap._tcp.pdc._msdcs.gva.z.com SRV service location:
    priority = 0
    weight = 100
    port = 389
    svr hostname = gvanet1.gva.z.com
    gvanet1.gva.z.com internet address = 192.168.96.156


    I also get an error when I try to open the AD Domains and Trusts mmc, it also says it cannot locate a PDC.

    Im running a dcdiag /e /c /v /f:dcdiag.txt now and can post the results tomorrow when its done.

    I did run a straight up dcdiag and saw this:

    Running enterprise tests on : Z.com
    Starting test: LocatorCheck
    Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
    A Primary Domain Controller could not be located.
    The server holding the PDC role is down.
    ......................... Z.com failed test LocatorCheck

    These servers are Windows server 2008. I ran all of those commands above from GVANET3, thats the guy thats giving me problems. oh, and I dont want to force the demotion because we dont know if there is an sidhistory or anything being used over there.

    Does anyone know what I can do to fix this so I can demote the DC? Thanks!
    Last edited by braul; 30th September 2010, 22:40.

  • #2
    Re: Problem Demoting a DC

    run the DCdiag commands, and even the demote command, from an elevated command prompt.

    I've found with 2008, that even being a full DA or EA sometimes isn't enough.
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Problem Demoting a DC

      Hi Tehcamel,

      Ive tried using an elevated command prompt, I know what you mean about 2008 requiring it sometimes. Unfortunetly I think the problem is a little deeper especially considering I cant open the domains and trusts mmc without it barking about not finding the PDC.

      Thanks for the input!

      Comment

      Working...
      X