Having a corrupted domain controller is highly troublesome and is irritating. It was my first time to experience an environment with a corrupted domain controller. Luckily, it wasn’t the master domain controller that is corrupted.
Before jumping into conclusion by blaming the domain controller is the cause. Let’s check what are the symptoms and what could be the possible cause. Anything that is related to the domain controller will get affected.
What are the symptoms that you will experience?
- Delay synchronization between other domain controllers
- Unexpected broke down of synchronization between other domain controllers
- Inconsistent reading of synchronization
- Loss of locating the master domain controller
- Time-sync delay
- Users unable to log in to Office 365 after password reset
- Newly created Exchange Hybrid users are not reflecting
- Exchange Hybrid failure to connect
- Unexpected slow performance
- Unexpected network detection failure
The factor of the causes?
When you have a corrupted domain controller, you really have drawn the layers to investigate.
- Configuration/Settings of the domain controller
- System Information and configuration on the server
- Operating system
- Host
- Virtual appliance
- Network (firewall or infrastructure)
- Storage
- Hardware
So it is best to analyze what is the possible cause of this and how to avoid it in the future. Logs are the friends you need.
Sabrina Kay's Blog 