AD issue with DC after Server was stolen
From: Rob W (rob.wilcox_at_mkl.co.uk)
Date: 09/01/04
- Next message: SA: "Re: How is network neighborhood populated?"
- Previous message: Laura E. Hunter \(MVP\): "Re: How do I log Failed Logon attempts"
- Next in thread: Herb Martin: "Re: AD issue with DC after Server was stolen"
- Reply: Herb Martin: "Re: AD issue with DC after Server was stolen"
- Reply: Nick: "AD issue with DC after Server was stolen"
- Messages sorted by: [ date ] [ thread ]
Date: 1 Sep 2004 07:02:29 -0700
Hi Guys, I had a DC at one of our remote depots, but it was stolen.
Before i properly thought about the issue, i got another replacement
bought and configured it exactly the same as the stolen one, and
dcpromo'd it onto the domain. It went on ok as i thought, but i
started to notice replication hadn't taken place with all my policies
within sysvol, DNS wouldn't play ball and now, every 3 mins i get a
SAM eror : Event ID 16650 in the system log. I have assumed myself,
that because the old stolen server wasn't removed from AD correctly
with DCPROMO and me adding an identical replacement server has screwed
everything up!!!! I have thought of an easy possible way round this,
and i am hoping somebody can confirm this would be ok. I am thinking
of DCPROMOing the new server off the domain again, then renaming it to
something completely different, then DCPROMOing it back onto the
domain again?? Would this simple idea be effective??
Any thoughts, or other ideas would be greatly appreciated!!
Kind regards
Rob W
- Next message: SA: "Re: How is network neighborhood populated?"
- Previous message: Laura E. Hunter \(MVP\): "Re: How do I log Failed Logon attempts"
- Next in thread: Herb Martin: "Re: AD issue with DC after Server was stolen"
- Reply: Herb Martin: "Re: AD issue with DC after Server was stolen"
- Reply: Nick: "AD issue with DC after Server was stolen"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
