trouble removing orphan domain – role owner attribute could not be read

Home Forums Microsoft Networking and Management Services Active Directory trouble removing orphan domain – role owner attribute could not be read

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    mrjaak
    Member
    #126045

    I am having a problem removing a ophan domain. When I try and remove the domain through ntdsutil I get the error “DsRemoveDsDomainW error 0x20ae (role owner attribute could not be read)”. It gives me the same error when I try to remove the ophan domain crossRef from within ADSI edit. I have followed these two articles with no solution…

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q235416
    http://support.microsoft.com/kb/826900

    Does anybody know how I can get rid of this orphan domain.

    I inherited this configuration from the previous administrator so that is why it is sorta mangled. Originally we had 3 domain controllers, the pdc which held all the roles including GC, a backup which mainly served as a backup dns server, and a final dc which was behind a firewall. This firewall domain controller had a child domain installed on it and that is what I am trying to remove. It was too big of a hassle to try and get the DC behind the firewall connected up again so that is why I am removing it the manual way. The backup DC that was just doing DNS crashed and it will never be back online as well. Could this backup DC be causing this problem in any way? I have thought about removing the metadata for it to see if that would solve the problem of not being able to remove the child domain but I’m afraid that might make the situation worse. The whole reason behind this cleanup is so we can migrate our domain to windows 2003. It was my understanding that the cleanup needed to be done before the migration. I assume it won’t even migrate with all this stale information. Am I correct? Is it possible to migrate and then cleanup all this metadata?

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.