FRS / AD Issues

[Stevehewitt]

Guys,

A few months back we couldn't demote a crippled server, so we had no choice but to just format it. Thus - no 'graceful' removal from AD.

I've used the metadata cleanup in NTDSUTIL to remove references to the server (called BACKOFFICE) - however AD seems to want to replicate to this server still.

FRSDIAG lists the BACKOFFICE server as still being a DC in the list, (whilst there's no reference in any other GUI tools I use daily such as users and comps or sites and services - and the metadata shown using NTDSUTL doesn't list it either).
How can I stop AD/FRS from trying to replicate to this non-existant server. (It's filling the event logs and also failing tests when I use DCDIAG)

Cheers,




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[tfg13]

Steve,
I wonder if this tool will give you any hints on what is where?

http://www.microsoft.com/downloads/...8E-8553-4DE7-811A-562563EB5EBF&displaylang=en

Supposedly, there is also a frsflags.vbs in the 2003 resource kit. I haven't used it, so I have no idea if it would be any good, or what it would tell you, just thought it might help...

 

[Stevehewitt]

Thanks for the link. I've been using that tool to diagnose the problems with FRS - and it's simply tells me that it still thinks that BACKOFFICE is still a DC that should be getting SYSVOL replicated to.

I'll take a look at the FRSFlags.vbs script and see if that has anything useful.

Cheers,




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[tfg13]

Duh...You did tell me about using FRSDiag. Sorry....