adprep ldap errors

I am trying to upgrade my active directory scheme from a windows 2003 version to support a windows 2008 R2 server.

When I run adprep /domainprep, I receive the following error:

Adprep encountered an LDAP error.
Error code: 0x20. Server extended error code: 0x208d, Server error message: 0000
208D: NameErr: DSID-031001CD, problem 2001 (NO_OBJECT), data 0, best match of:
        'CN=GCS\0ADEL:d846d18f-b424-4d10-83fc-5c41108ad8ff,CN=Servers,CN=Default
-First-Site-Name,CN=Sites,CN=Configuration,DC=ad,DC=domain,DC=com'

From what little I can tell about the error, Ldap is looking for a domain controller (or record) that does not exist.  The domain controller in question (GCS) was forcibly removed from the domain after a catastrophic failure of the host.  The "metadata cleanup" procedures were used to remove this domain controller from the domain.

My Guess is that the bad domain controller has not been completely removed from the domain.  How do I cleanup / repair the domain so that the adprep command will run successfully?

--
Matthew Davis
AD-NoviceAsked:
Who is Participating?
 
Life1430Sr EngineerCommented:
@ dariusg :- He is using Windows 2003 X64 so there is no need to use adprep32 ..

Author:- Please Use below link to completely remove the dead DC from domain Also make sure you have the user ID have Schema admin and enterprise admin rights on Domain

Check if all FSMO's are on your functional DC use netdom query fsmo to check and if you find any roles on dead DC seize them to working DC using below link

Metadata cleanup:
http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Seize FSMO role:
http://www.petri.co.il/seizing_fsmo_roles.htm
0
 
Mike KlineCommented:
Is your 2003 box 32 bit or 64 bit?

Thanks

Mike
0
 
AD-NoviceAuthor Commented:
The 2003 box is 64 bit
0
 
Darius GhassemCommented:
You need to run metadata cleanup again

Make sure you have deleted all DNS records for this failed DC including any SRV records

You need to used adprep32 as well when upgrade schema

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/A_3644-Windows-2008-Server-R2-adprep-adprep32.html

Make sure all fsmo roles are on a functioning DC as well
0
 
Darius GhassemCommented:
Totally missed the 64-bit part
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.