Using the Active directory Domain Services (AD DS) server role, you can create a scalable, secure, and manageable infrastructure for user and resource management, and can provide support for directory-enabled applications such as Microsoft Exchange server.
AD DS provides a distributed database that can store and manage information about network resources and application-specific data in directory-enabled applications. The server running AD DS is called a domain controller. Administrators can use AD DS to organize network elements, such as users, computers, and other devices, into hierarchical inline structures. Inline hierarchies include Active Directory forests, domains in the forest, and organizational units (OUs) in each domain.
Now that we are installing the domain controller, let us first understand what the requirements for running the domain controller are, as follows:
Span style= "FONT-SIZE:10PT;" > requirements |
description |
tcp/ip |
Configure the appropriate TCP/IP and DNS server addresses. |
ntfs |
|
credentials |
|
domain Name System (DNS) infrastructure |
Verify that the DNS infrastructure is in place. When you install AD DS, you can include the DNS server installation, if required. When you create a new domain, a DNS delegation is automatically created during setup. Creating a DNS delegation requires credentials that update the parent DNS zone permissions. |
adprep |
|
Read-only domain controller (RODC) |
Additional requirements for installing an RODC:
The forest functional level must be at least Windows Server 2003
At least one writable domain controller running Windows Server 2008 or later must be installed in the same domain. |
Domain controller installation Many times the need for hardware configuration is not too high, in many cases very basic configuration can be easily run up (such as 1-core 1G memory 50~100g hard disk, etc.), if the production environment is recommended to choose a relatively adequate resource installation.
Windows Server 2016-install AD Domain Services considerations