"" <> wrote in
message news:156848D3-8FA4-4576-8AD3-...
>I have been recieveing this error under DFS Management in the event veiwer
> for about two monthes. This is about the same time as one of the DC
> crasher
> and had to be removed from AD using ntdsutil.
>
> I have also noticed that under replacation on DFS management in
> administrative tools, I have invalid members that with the same member
> name.
>
> The member cn=.... does not refer to a valid computer object. The cn=...
> is
> the same as the one's that show up in the event ID Error 6002.
>
> Should I delete (or just disadle them) them from from under DFS management
> both under namespace and replication? Please advice.
>
> Regards,
> DJ
Hello,
I think you should delete not-existing objects in DFS management AND in
Adsiedit.msc
Quote:
"This can be fixed by using ADSIEDIT. Under the Server Container for your
server you will find the records for the old FRS replication that is
conflicting. Delete the references for all members. This solution has been
tested and resolves this issue"
Best regards,
Luca Chiaverini
|