Adding NT4 BDC back into AD

  • Thread starter Thread starter James
  • Start date Start date
J

James

We lost a server which was an NT4 BDC in our AD domain.
After fixing it and placing it back on the network (some
week later), it failed to replicate with the DCs. We tried
deleting the account from the domain controllers OU and
adding it back, but AD sees it as a workstation, not a
domain controller. Any ideas on how to add it back and
make it function again as a NT4 domain controller?
 
If you some 2000 DC's why do you need to make the NT4 server a DC? Leave it
as a member server so that when you do a full AD migration you won't have to
worry about the NT4 server needing to be removed.
 
Have you tried installing the AD client for NT4?
James said:
There is legacy software (e-mail services) on this machine
that requires access to a local SAM database.. It cannot
connect to AD.
 
Back
Top