26. May 2024 • 7 min. read

Deploying Windows Server Environment from Scratch (Part 1)

WindowsVirtualization

Windows Server 2022 Installation and Domain Controller Deployment

Part 1 Part 2 Part 3 Part 4

Hello everyone,

it’s been a while, again. Didn’t have much to write about, and still don’t really.

But I thought, why not create a multipart post on deploying a Windows Server environment for an imaginary business. We will go through the installation of Windows Server 2022, deployment of a domain controller, setting up a file / DHCP / DNS server, certificate authority and so on.

I will be using Proxmox for the hypervisor, since it’s what I already have. It’s the one from the “HPE Alletra 5000 iSCSI with Proxmox using OCFS2” post.

In this post, we will begin with the initial installation of Windows Server 2022 and deploy the Domain Controller, since that will be our starting point for the following servers.

I will try to mention every step and every error I receive (if any) to make it as useful as possible.

System Information

HostnameIPFunction
TEST-DC01192.168.152.200/24Domain Controller / Active Directory / DNS / DHCP

Network Information

Network192.168.152.0
Subnet255.255.255.0
Gateway192.168.152.254

Download Windows Server 2022 Evaluation ISO

First, we need the actual ISO. We can grab it from the Microsoft Evaluation Center. Go to this URL “https://www.microsoft.com/de-de/evalcenter/download-windows-server-2022” and download the ISO in your preferred language.

Once we have the ISO, we can upload it to our hypervisor of choice.

Proxmox: ISO uploaded to local storage
Proxmox: ISO uploaded to local storage

Windows Server 2022 Installation

VM Deployment in Proxmox

Alright. Let’s begin with the installation of Windows Server 2022.

I will quickly show you the steps in Proxmox, I take.

Give it a nice name. “TEST-DC01” in my case.

Proxmox: Naming the VM TEST-DC01
Proxmox: Naming the VM TEST-DC01

Choose the ISO for Windows and the virtio drivers.

Proxmox: Selecting Windows ISO and VirtIO drivers
Proxmox: Selecting Windows ISO and VirtIO drivers

Set the location for the EFI qcow2.

Proxmox: EFI disk location configuration
Proxmox: EFI disk location configuration

Configure the disk for the system. 60GB should be enough.

Proxmox: Disk configuration set to 60GB
Proxmox: Disk configuration set to 60GB

I always assign at least 2 CPU cores and, in this case, set the CPU type to “host”.

Proxmox: CPU configuration with 2 cores and host type
Proxmox: CPU configuration with 2 cores and host type

8GB of RAM. 4GB would be enough if you don’t have any to spare.

Proxmox: RAM configuration set to 8GB
Proxmox: RAM configuration set to 8GB

I will leave the defaults here.

Proxmox: Network defaults
Proxmox: Network defaults
Proxmox: VM creation summary
Proxmox: VM creation summary

Windows Server 2022 Installation

Next is the Windows Server installation. There is not much to talk about here. We mainly click “Next”. The only quirk is the drivers for the virtIO storage device I need, since I am deploying on a Proxmox Server. You won’t have this issue with VMWare or Hyper-V.

Set your Time format and keyboard layout.

Windows Setup: Language and keyboard layout selection
Windows Setup: Language and keyboard layout selection

Click on “Install now”.

Windows Setup: Install now screen
Windows Setup: Install now screen

I will select the “Windows Server 2022 Standard Evaluation (Desktop Experience)

Windows Setup: Selecting Standard Evaluation Desktop Experience
Windows Setup: Selecting Standard Evaluation Desktop Experience

Accept the license terms.

Windows Setup: License terms
Windows Setup: License terms

Select “Custom…

Windows Setup: Selecting custom installation
Windows Setup: Selecting custom installation

This is the step I mentioned earlier. If you use VMWare or Hyper-V, the disk should just show up, but in this case, we have to load the virtIO drivers.

Windows Setup: No disk shown without VirtIO drivers
Windows Setup: No disk shown without VirtIO drivers
Windows Setup: Browsing for VirtIO storage drivers
Windows Setup: Browsing for VirtIO storage drivers
Windows Setup: Selecting the VirtIO driver folder
Windows Setup: Selecting the VirtIO driver folder
Windows Setup: VirtIO driver list
Windows Setup: VirtIO driver list
Windows Setup: VirtIO driver loaded successfully
Windows Setup: VirtIO driver loaded successfully

Once loaded, we can select our disk.

Windows Setup: Selecting the disk after loading drivers
Windows Setup: Selecting the disk after loading drivers

Waiting for the installation.

Windows Setup: Installation in progress
Windows Setup: Installation in progress

Initial Configuration

Installing Guest Tools

Alright. Let’s go through the initial setup.

Set a password.

Windows Server: Setting the administrator password
Windows Server: Setting the administrator password

Login.

Windows Server: Login screen
Windows Server: Login screen

The first thing I will do, is to install the guest tools. This will install all the drivers and gives us better integration and performance. Keep in mind that, the steps are slightly different in VMware ESXi.

Open the file explorer, select the virtio-win ISO and double-click the “virtio-win-guest-tools” exe.

Windows Server: VirtIO guest tools installer in file explorer
Windows Server: VirtIO guest tools installer in file explorer

Agree to the terms and click on “Install”.

Windows Server: Guest tools license agreement
Windows Server: Guest tools license agreement

For the next steps, just click on “Next” and “Install” every time. Once done, click on “Close”.

Windows Server: Guest tools installation complete
Windows Server: Guest tools installation complete

Setting the Hostname, enabling RDP

Next, open the “Server Manager”. In here, click on “Configure this local server”.

Server Manager: Configure this local server
Server Manager: Configure this local server

Click on the “computer name”, this will open a new window, where we can change the hostname to something more readable. I will set it to “TEST-DC01”.

Server Manager: Changing the hostname to TEST-DC01
Server Manager: Changing the hostname to TEST-DC01

Select “OK”, this will ask you to reboot the system. Confirm and close the windows. Again, it will ask you to reboot, but we will select “Restart Later” for now.

Server Manager: Reboot prompt after hostname change
Server Manager: Reboot prompt after hostname change
Windows Server: Selecting Restart Later
Windows Server: Selecting Restart Later

Next, we want to enable RDP. Click on “Remote Desktop - Disabled”, select “Allow remote connections to this computer” in the new window and confirm.

Server Manager: Enabling Remote Desktop
Server Manager: Enabling Remote Desktop

Now, click on “Ethernet”. We want to set a static IP. I will use “192.168.152.200” for the Domain Controller.

Server Manager: Ethernet network settings
Server Manager: Ethernet network settings
Windows Server: Setting static IP address
Windows Server: Setting static IP address
Windows Server: Confirming static IP configuration
Windows Server: Confirming static IP configuration

Once that’s done, confirm everything and reboot the system.

Windows Server: Reboot after network configuration
Windows Server: Reboot after network configuration

Activate Evaluation

If you have a license and want to switch from the evaluation to a full license, use this command.

## Standard Edition
dism /Online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

## Datacenter Edition
dism /Online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

Windows Domain Controller Deployment

Install Domain Services Role

Now that the base setup is done, we can continue with the installation of our first role.

Once logged in again, open the “Server Manager”, click on “Manage” -> “Add Roles and Features”.

Server Manager: Add Roles and Features wizard
Server Manager: Add Roles and Features wizard

Click on “Next” and make sure “Role-based and Feature-based installation” is selected. Click on “Next”.

Add Roles: Role-based installation selected
Add Roles: Role-based installation selected

Select “Next”.

Add Roles: Server selection
Add Roles: Server selection

Now, here we select the “Active Directory Domain Services”, the “DNS Server” and confirm the required features.

Add Roles: Selecting Active Directory Domain Services and DNS Server
Add Roles: Selecting Active Directory Domain Services and DNS Server
Add Roles: Confirming required features
Add Roles: Confirming required features

Click on “Next” and “Next” again on the “Select Features” tab. Continue until you get to the “Install” page.

Add Roles: Installation page
Add Roles: Installation page

Set up the Domain Service

Once the installation is done, click on the “Promote this server to a domain controller” link or select the banner on the top right.

Server Manager: Promote this server to domain controller banner
Server Manager: Promote this server to domain controller banner

This is the Active Directory Deployment. Here we can set up our Domain.

Select “Add a new forest” and give it a nice and telling name.

Domain Recommendation

In production, it is recommended to use a subdomain of your business domain. For example. My domain is “random-it-blog.de”, for my internal systems I would use something like “intra.random-it-blog.de

I will be using “test.intra

AD Deployment: Adding a new forest with domain name
AD Deployment: Adding a new forest with domain name

In the next step, we have to set a recovery password. This is only required in a disaster situation.

AD Deployment: Setting the recovery password
AD Deployment: Setting the recovery password

You can ignore the DNS warning for now. Click on “Next”.

AD Deployment: DNS delegation warning
AD Deployment: DNS delegation warning

Make sure the NetBIOS domain name is correct and click on “Next”.

AD Deployment: NetBIOS domain name
AD Deployment: NetBIOS domain name

I would recommend leaving the defaults for the system folders.

AD Deployment: Default system folder paths
AD Deployment: Default system folder paths

Here you can review the settings. If you are happy with it, click on “Next”.

AD Deployment: Review settings
AD Deployment: Review settings

Next, the system will run a prerequisite check. Again, you can ignore the DNS warning.

Select “Install”.

AD Deployment: Prerequisite check and install
AD Deployment: Prerequisite check and install

The system will automatically reboot.

AD Deployment: Server rebooting after promotion
AD Deployment: Server rebooting after promotion

Once the system boots back up, you should see your administrator account with the domain.

Windows Server: Login screen showing domain account
Windows Server: Login screen showing domain account

Alright. That’s it for the installation of a Windows Domain Controller. In Part 2 we will create a few users and groups, add a server to the domain and configure a file server.

Till next time.

Part 1 Part 2 Part 3 Part 4

Comments

Search