Re: metadata cleanup
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Fri, 31 Aug 2007 11:52:58 +0100
The dead DC is lost forever right?
- Perform Metada Cleanup for the Dead DC.
- Delete any DNS records that map to that server from DNS.
-Make sure that you have at least 1 GC.
-Seize the role(s) to an existing server.
-Bring the new server online and configure it as you want.
-Add it as addtional DC.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"Manu" <Manu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A76737CA-074A-4D0E-82F0-AFC5068994E5@xxxxxxxxxxxxxxxx
so correct me i am wrong you had a domain controller lets say DC1 and DC2,
We
promoted another domain controller with the same name and Ip.
Question
1> Was the meta cleanup done using ntdsutil before the server could have
been brought again with the same name?
Also check in ADSI Edit, Configuration partition->Sites and see if you see
any connection object marked as DEL, if yes go ahead and delete it.
If the answer to the question 1 is NO the would strongly suggest demoting
and repromoting the server back again.
Regards
"MaryElizabeth" wrote:
We have 1 domain w/2 dc, (servers=2003) In the event log I have error
2091,
NTDS Replication, and it shows a deleted record.
This record is referencing and old dc that died and held the role of the
infrastrucutre master.
The server that replaced the old domain controller was brought back with
the
same name. We have tried to transfer the role to an exsiting dc, but
this
does not work.
I want to run the metadata cleanup to remove this orphaned record, but am
worried that since the old dc and the new dc have the same name this will
cause a problem with my new dc?? Or does metadata only remove the old
records?
.
- Prev by Date: Re: Password Policy
- Next by Date: Re: Password Policy
- Previous by thread: LDAP user authentication error with VBScript from ASP
- Next by thread: What are my programmers asking me to do with my AD?
- Index(es):
Relevant Pages
|
