incorrect Src Root Domain Srv entry in registry

Hello,
Just noticed that one of my domain controllers (first controller) has an
incorrect entry in the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Src Root Domain Srv , listed is an old domain controller removed several
years ago. I have found several articles about this key and most say to
delete it but I was wondering if it was that easy?
The second domain has the name of the first controller in that key so it
appears to be okay.
Windows 2003, SP2

Thanks Julie

Hello,
Just noticed that one of my domain controllers (first controller) has an
incorrect entry in the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Src Root Domain Srv , listed is an old domain controller removed several
years ago. I have found several articles about this key and most say to
delete it but I was wondering if it was that easy?
The second domain has the name of the first controller in that key so it
appears to be okay.
Windows 2003, SP2

Thanks Julie

Hi
What registry entrie are you talking about?

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

Hello Julie,

If that machine no longer exist check that command to find a new DC for sync:
w32tm /config /syncfromflags:domhier /update

After that run:
net stop w32time
net start w32time

Normally it should find the PDCEmulator which is the time source in the domain
automatic.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
There is a value named Src Root Domain Srv and it contains the name of a
server that no longer exists as a domain controller.

I am having issue's whether they are related to this I don't know. My
discovery of this started when attempting to troubleshoot my account
constantly being locked out. Errors 1083 and 1955 which indicate I have a
problem with replication. Seeing an old domain controller referenced in this
key seemed to me that that could be part of the problem.

Ok,
-Acording with the KB332199 the value is to be deleted manually when using
Forceremoval switch with dcpromo and then re-adding the DC again to the
domain, was this that happen with that DC? How did you removed that DC?

use NETLOGON debugging to troubleshoot your account lockout issues. With
that you can find the source machine of the lockouts. More info is available
if you search for it

Ok, make sure that the server was correctly removed from AD and that you
don't have any DNS records to that map to that old server, also check at
ADSS. Check the following link and make sure that the server is no longer
living in your AD:
http://support.microsoft.com/kb/216498

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services