The Factor of Corrupted Domain Controller, Windows Server 2016

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?

  1. Delay synchronization between other domain controllers
  2. Unexpected broke down of synchronization between other domain controllers
  3. Inconsistent reading of synchronization
  4. Loss of locating the master domain controller
  5. Time-sync delay
  6. Users unable to log in to Office 365 after password reset
  7. Newly created Exchange Hybrid users are not reflecting
  8. Exchange Hybrid failure to connect
  9. Unexpected slow performance
  10. Unexpected network detection failure

 

The factor of the causes?

When you have a corrupted domain controller, you really have drawn the layers to investigate.

  1. Configuration/Settings of the domain controller
  2. System Information and configuration on the server
  3. Operating system
  4. Host
  5. Virtual appliance
  6. Network (firewall or infrastructure)
  7. Storage
  8. 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.

 

 

 

 

How to create FTP in Windows Server 2016

 

Having a difficult time to sleep, so why not do a short video on FTP right? hahaha, Hope you guys enjoy it!

Before creating an FTP, you got to install or add from Server Manager > Add roles and features > Select Web Server (IIS) > Expand it > Select FTP Server. You got to manually check it.

Next, once you added the FTP server role and features, go to windows administrator to open FTP.

Factors for FTP;

  1. You got to create an FTP site
  2. Give suitable naming
  3. Site permission
  4. You got to make sure your application/appliance require SSL or not
  5. Virtual Directory
  6. Authentication type
  7. Credential access to the virtual directory, and which this credential will also be used by your application or appliance for authentication