+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 18 of 18
Windows Thread, Corrupt AD HELP!! in Technical; So the server is DNS / DHCP / Print Server / Etc. Generally these aren't a big deal to bring ...
  1. #16

    Geoff's Avatar
    Join Date
    Jun 2005
    Fylde, Lancs, UK.
    Thank Post
    Thanked 582 Times in 503 Posts
    Blog Entries
    Rep Power

    Re: Corrupt AD HELP!!

    So the server is DNS / DHCP / Print Server / Etc.
    Generally these aren't a big deal to bring up on another DC. Especially if your DNS is AD integrated.

    Plus is houses all user folders / profiles / network shares.
    presumably you have all this data safely backed up.

    At the moment windows has stoped the server from replicating with DC02. The main issues now are the Event ID: 474 NTDS ISAM / Event ID: 1084 NTDS ISAM.
    This is windows attempting to stop data corruption propagating to your other DC.

    AD on DC01 can be accessed now and all data seems to be there except I get errors when trying to access an OU which houses all the IT suite computers.
    Because AD is corrupt on the server.

    I am hoping now that this issue is being caused by the faulty hard drive and that "IF" i can image the old / new disks then AD will replicate again. Clutching at straws I know.
    Yes, but you'll need to do an authoritative restore from your second dc.

  2. #17
    Busybub's Avatar
    Join Date
    Feb 2007
    Thank Post
    Thanked 39 Times in 37 Posts
    Rep Power

    Re: Corrupt AD HELP!!

    Might be a bit late but you may get additional AD problems if you install a DC using an existing name without cleanly demoting the existing one.

    From experience I would demote the troublesome server (after transferring roles) before doing anything else!

    If you don't cleanly demote the DC, any new DC using the same name will have a new GUID allocated. You will get replication errors everywhere as your online DCs attempt replication with a server that doesn't actually exist. If you are lucky you will be able to get rid of the rogue entry by doing a metadata cleanup in ntdsutil. If you are unlucky you will be stuck with it forever.

    Using a known good backup may not help if it is more than a few days old. The last time I tried it with a 3 day old backup, the server had changed its GUID... *argh* ... and the restored DC appeared as a different computer.

  3. #18

    Re: Corrupt AD HELP!!

    Cheers for all the info guys. I will back on site tomorrow, hopefully with a shiny new HDD waiting. So be ready for lots more questions :P

+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Corrupt Word/Excel files
    By ind13 in forum Office Software
    Replies: 5
    Last Post: 6th June 2008, 02:03 PM
  2. Replies: 2
    Last Post: 26th April 2007, 04:07 PM
  3. Profile Corrupt: User Cannot Logon
    By DaveP in forum Wireless Networks
    Replies: 4
    Last Post: 12th December 2006, 09:59 PM
  4. Restoring data from a corrupt sd card
    By timbo343 in forum Windows
    Replies: 4
    Last Post: 15th June 2006, 09:37 AM
  5. Recovering Files From a Corrupt Floppy
    By Preston in forum Windows
    Replies: 15
    Last Post: 27th April 2006, 03:39 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts