Windows Server 1.1 : Prerequisites for installing Active Directory

Before turning a Windows Server 2019 machine into a domain controller, there are a few prerequisites to settle. Skipping any of them will either block the installation outright or cause headaches later that are painful to undo.

Four prerequisites to verify

  • Static IP address — domain controllers must have a static IP. If the address is dynamic (DHCP), the AD installer will throw warnings. Set it before you start.
  • Final computer name — rename the machine to its definitive name before installing Active Directory. You cannot rename a domain controller easily after promotion; the procedure is long and error-prone. Decide now, rename now.
  • Preferred DNS server — make sure the DNS settings point to the right place. When you install AD DS, the installer also offers to deploy DNS for you. When AD DS comes online, it automatically creates several DNS records and registers them against the address listed as the preferred DNS server. The simplest and safest pattern is to make the DC its own DNS server: set the preferred DNS to the machine's own IP, so the records are written locally on the same box.
  • Database file location plan — Active Directory is, in essence, a database. The installer asks where to put the database files, the transaction logs and SYSVOL. In a real-world deployment, you put the OS on one physical disk and the AD database files on a separate physical disk to avoid contention. In our lab, everything will live on the C: drive — but the rule still stands: know where the files will go before you click Install.

Once these four boxes are ticked — static IP, definitive computer name, self-referencing DNS, planned database location — you are ready to start the actual Active Directory installation in the next lesson.

Summary

This lesson covers essential prerequisites for installing Active Directory on Windows Server. Key requirements include configuring a static IP address for domain controllers, renaming the computer before installation (as it cannot be changed afterward), and properly setting up DNS server addresses. The lesson also addresses Active Directory database storage planning and the automatic DNS record creation that occurs during AD installation.

Key points

  • Domain controllers require a static IP address—dynamic IPs will cause installation errors
  • Computer name must be set before Active Directory installation; changing it after AD deployment is difficult and time-consuming
  • DNS server addresses must be configured and should point to the machine itself for proper AD functionality
  • Active Directory automatically creates DNS records during installation on the configured DNS server
  • Active Directory database and transaction log files require storage planning, ideally on a separate physical disk from the OS
  • Separating AD data storage from the operating system disk prevents I/O conflicts and performance issues

FAQ

Can I rename the computer after installing Active Directory?

No, it is very difficult and time-consuming to rename the computer after Active Directory installation. The computer name must be configured before beginning the AD installation process.

Why should the DNS server address point to the machine itself?

When Active Directory is installed, it automatically creates DNS records. The DNS server address should point to the local machine's IP address so that Active Directory can write all its DNS records directly to the local DNS service on that machine.

Is it necessary to store Active Directory database on a separate disk?

Ideally yes. In production environments, the Active Directory database and transaction log files should be stored on a separate physical disk from the operating system to avoid I/O conflicts. However, this can be configured as needed depending on your infrastructure.