Install and Manage Active Directory on Server 2008 R2 Core - IT Guide

Installing Active Directory on Server Core

The installation of Active Directory on a Server Core deployment cannot be performed through the Optional Component Setup tool. Instead, the process necessitates the utilization of DCPROMO via the command line interface.

Please note that this guidance forms part of a continuing educational series focused on fundamental IT administration practices, and may not be universally applicable.

Prerequisites

Prior to initiating the Active Directory installation, several preparatory steps are required. These include configuring static IP address information for the network adapter and modifying the server's hostname.

All necessary configurations must be executed from the command line. The following sections detail the procedures for accomplishing these tasks.

Configuring Static IP Address

A static IP address is crucial for reliable Active Directory operation. This ensures consistent network connectivity for the domain controller.

Renaming the Server

Changing the server's name is also a necessary step. A descriptive and easily identifiable hostname simplifies administration and troubleshooting.

These initial configurations are essential for a successful Active Directory deployment on Server Core. Once completed, you can proceed with the DCPROMO command to install the Active Directory Domain Services role.

Configuring a Static IP Address

For proper functionality, Active Directory necessitates a static IP address assignment on the server. Initially, a listing of the server’s network adapters must be obtained. This is accomplished through the utilization of a netsh command:

netsh interface ipv4 show interface

The output of this command displays all network interfaces present on the system.

Having identified the network card names, the configuration for a specific adapter can be modified. The IP address is altered using another netsh command:

netsh interface ipv4 set address name="Local Area Connection" source="static" address="10.10.10.1" mask="255.255.255.0" gateway="10.10.10.254"

Ensure the following values are correctly substituted within the command:

• Name – Indicates the name of the network interface to be configured.
• Address – Represents the desired static IP address for the interface.
• Mask – Specifies the subnet mask associated with the interface.
• Gateway – Defines the default gateway for network traffic.

Properly configuring these parameters ensures network connectivity.

Subsequently, DNS information must be established for the server. This is achieved by executing the following command:

netsh interface ipv4 add dnsservers name="Local Area Connection" address="127.0.0.1" index=1 validate=no

The following values require appropriate substitution:

• Name – The name of the network interface being modified.
• Address – The IP address of the DNS server; in this case, the loopback address is used.
• Index – Determines the DNS server priority; '1' designates the primary, while '2' indicates the secondary.

This configuration ensures the server can resolve domain names correctly.

Modifying the Computer Name

Prior to elevating a server to a domain controller, renaming it is a recommended practice. This is accomplished utilizing the netdom command. Ensure you replace "DC1" in the subsequent command with your desired server name.

netdom renamecomputer %computername% /newname:DC1

The command initiates the renaming process. It's crucial to specify the new name accurately.

For the alterations to be fully implemented, a system reboot is necessary. This can be initiated directly from the command line using the following instruction:

shutdown /r /t 0

This command will immediately restart the computer. Confirm all work is saved before executing this command.

Following the reboot, the server will reflect its new designated name. This ensures proper identification within the network environment.

Important Considerations

• The netdom command requires administrative privileges.
• Verify the new name adheres to naming conventions.
• A reboot is mandatory for the name change to take effect.

Active Directory Installation Procedures

Several methods exist for installing Active Directory on a Server Core installation. This guide details the process utilizing an answer file. A sample answer file is provided as a foundation; however, for customized deployments, consult the comprehensive parameter list available in the official TechNet documentation.

The answer file, which can be created using a simple text editor like Notepad, should be saved as DCPROMO.txt.

Answer File Functionality

The specified answer file performs the following actions during the installation process:

• A new domain, named howtogeek.local, is created as the root of a new forest.
• The forest functional level is configured to Server 2008 R2.
• DNS is installed, incorporating an Active Directory Integrated Zone.
• The server is designated as a Global Catalog.
• A password, Pa$$w0rd, is set for AD Restore Mode.
• The server is automatically rebooted upon completion of the installation.

To initiate the installation using the answer file, execute the following command:

dcpromo :/unattend:”path to answer file”

This command triggers the Active Directory installation sequence and automatically reboots the server once finished.

The installation of Active Directory on Server Core is now complete.

Administering Active Directory

Managing a Server Core Server is most easily accomplished through the use of RSAT (Remote Server Administrator Tools). These tools enable the loading of MMC consoles on a Windows 7 system, facilitating connections to the server's role instance.

The RSAT package can be downloaded from a dedicated source. Installation proceeds via Windows Update; upon completion, navigate to the "Turn Windows features on or off" option within the Control Panel's Programs and Features section.

Installing Required Components

It is necessary to incorporate both the AD DS Snap-ins and Command-line tools. Refer to the accompanying screenshot for detailed guidance on locating these options.