14

Can a Second Domain Controller, with buggy hard drive hardware, cause a corruption to Active Directory?

view full story
linux-howto

http://serverfault.com – We have a new Domain Controller that holds all FSMO roles. We also have two old hardware servers, about 4-5 years old each, set up as secondary Domain Controllers. My question is do I run the risk of corruption in Active Directory if I have a drive failure, due to old hardware, on one of the secondary Domain Controllers. I am really trying to convince the client to buy a new hardware based server for our second Domain Controller but again budget is tight. Thanks. (HowTos)

xskl's picture
Submitted by xskl on 07/13/2012 – Made popular on 07/13/2012

Stories similar to Can a Second Domain Controller, with buggy hard drive hardware, cause a corruption to Active Directory?

I've seen other questions and documents about doing this, but there are some things that still confuse me.

Hi I have a two domain controller domain and i will refer to them as DC1 and DC2, here is some info on them.

DC1 is or has all FMSO roles DC2 serves as another Domain Controller for replication DC1 is a basic server with a 3ware RAID 1 setup There is a buggy hard drive in DC1 and the 3ware rep recommends replacing the drive in slot 0 sooner than later.

Based on the above information I would li

Problem: Server 2000 DC hard drive failed. Purchased new drive, installed server 2000 and restored everything from a backup. Everything is back up, however none of the client machines can connect to the server and view "my documents".

This is hypothetical question, but one I’m sure that someone must have encountered and/or given some thought to before.

Situation: Consider this, a small business is running an Active Directory domain and has two domain controllers which are located in their office. The domain controllers are both physical servers (no virtualisation).

Issue Demoting Domain Controller 39 weeks 19 hours ago

I am in the process of demoting a 2003r2 DC. I have set up a 2008r2 Server, set it up as a DC and moved all the roles over. Now I am ready to demote the older DC.

I have a machine that was a domain controller and everything else, includin an IIS site. I built new 2 new domain controllers and transferred the FSMO roles and waited a day and then demoted the original domain controller.

I am unable to promote my newly installed Windows Server 2012 machine to a domain controller. Joining the domain as a server that is a member of the domain worked fine.

I'm migrating servers from colo locations to Amazon's VPC EC2 instances. If anyone hasn't worked with Amazon VPC before, VPN is a pain in the arse!

Anyways, I setup a new server that acts as the domain controller for our Amazon VPC.

I've inherited "ownership" of a network which has a Windows 2003 Server running as a Domain Controller and file server (no IIS or DNS running).