# Domain Controller Promotion

### Overview

After the Windows Server 2019 VM was built, the next step was installing the Active Directory Domain Services (AD DS) role and promoting the server to a Domain Controller. This created a brand new Active Directory forest for the lab environment.

***

### Installing the AD DS Role

1. Opened Server Manager
2. Clicked Add Roles and Features
3. Proceeded through wizard:
   * Installation Type: Role-based or feature-based
   * Server Selection: DC01 (local server)
   * Server Roles: Checked Active Directory Domain Services
   * Clicked Add Features when prompted
   * Left all other screens at defaults
4. Clicked Install and waited for completion

***

### Promoting to Domain Controller

After AD DS installed, a yellow notification flag appeared in Server Manager:

1. Clicked the flag → Promote this server to a domain controller
2. Selected Add a new forest
3. Set Root Domain Name: lab.local

#### Domain Controller Options

| Setting                 | Value                           |
| ----------------------- | ------------------------------- |
| Forest Functional Level | Windows Server 2016             |
| Domain Functional Level | Windows Server 2016             |
| DNS Server              | Enabled                         |
| Global Catalog          | Enabled                         |
| DSRM Password           | Set and stored securely offline |

> **Why Windows Server 2016 functional level?** Setting functional level to 2016 enables all modern AD features while maintaining compatibility for future migration scenarios — a common MSP consideration when managing mixed server version environments.

***

### Completing the Wizard

* DNS Options: Ignored delegation warning — expected in a new forest with no parent DNS zone
* Additional Options: NetBIOS name auto populated as LAB
* Paths: Left all defaults
* Prerequisites Check: Passed after network configuration fix (see Static IP & DNS page)
* Clicked Install — server automatically rebooted

***

### Post Promotion Login

After reboot, login format changed to domain credentials:

* Username: LAB\Administrator
* Password: \[stored securely offline]

> The LAB\ prefix specifies authentication against the domain rather than the local machine — important distinction when managing domain vs local accounts

***

### Verification

After logging in, confirmed AD DS installed correctly by checking Windows Administrative Tools:

* ✅ Active Directory Users and Computers
* ✅ Active Directory Domains and Trusts
* ✅ DNS Manager
* ✅ Group Policy Management

***

### Troubleshooting Notes

**Issue:** Prerequisites check failed — TCP/IP networking protocol must be properly configured **Cause:** VM had no static IP assigned and network adapter was disconnected **Fix:** Configured static IP and connected VM to LabSwitch virtual switch **Full details:** See Static IP & DNS Configuration page

***

### Skills Practiced

* Installing Windows Server roles via Server Manager
* Active Directory Domain Services installation
* Domain Controller promotion
* New forest creation
* Functional level selection and implications
* DSRM password configuration
* Post-promotion domain authentication


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://stefs-documentation.gitbook.io/stefs-documentation-docs/project-overview-bare-metal-homelab/active-directory/domain-controller-promotion.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.