henryv/www.henryvchild.eu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed date of upload and images (One day I will get this right first try)
All checks were successful
Generate and upload hugo website / generate_and_upload_site (push) Successful in 23s
Details

Browse Source
This commit is contained in:
Henry V Child 2025-06-22 11:26:26 +02:00
parent 7bd5b519e6
commit fdafb060b4
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/posts/2025/Setting up a Windows Homelab/index.md
View File

@ -1,5 +1,5 @@
--- ---
date: 2025-02-22T11:00:00+01:00 date: 2025-06-22T11:00:00+02:00
draft: false draft: false
title: Setting up a Windows Homelab title: Setting up a Windows Homelab
tags: tags:
@ -16,7 +16,7 @@ The plan for this project is to setup a Active Directory Domain Controller in th
Firstly I created a new Linux bridge for the home lab. I gave it the unambiguous name of WindowsLab to make it stand out. Firstly I created a new Linux bridge for the home lab. I gave it the unambiguous name of WindowsLab to make it stand out.
![[proxmox_linux_bridge.png]] ![An images of the proxmox linus bridge](./images/proxmox_linux_bridge.png "he System -> Networking tab of my Proxmox host with my new Linux bridge")
*The System -> Networking tab of my Proxmox host with my new Linux bridge* *The System -> Networking tab of my Proxmox host with my new Linux bridge*
Then I created two virtual machines. One for the firewall and one for the domain controller. Then I created two virtual machines. One for the firewall and one for the domain controller.
@ -34,28 +34,28 @@ To begin with I will only be configuring IPv4 addresses, just because they are e
Since the firewall bridges my home network and the windows lab network the firewall needs to be connected both networks. It's connected to my home LAN through the standard Proxmox bridge, and to the windows lab through the WindowsLab bridge. Since the firewall bridges my home network and the windows lab network the firewall needs to be connected both networks. It's connected to my home LAN through the standard Proxmox bridge, and to the windows lab through the WindowsLab bridge.
![[opensense_networking.png]] ![The OPNsense interfaces in Proxmox](./images/opensense_networking.png)
*The OPNsense interfaces in Proxmox* *The OPNsense interfaces in Proxmox*
![[wan_interface_settings.png]] ![Configuring the WAN interface in OPNsense](./images/wan_interface_settings.png)
*Configuring the WAN interface in OPNsense* *Configuring the WAN interface in OPNsense*
![[lan_interface_settings.png]] ![Configuring the LAN interface pt1](./images/lan_interface_settings.png)
*Configuring the LAN interface pt1* *Configuring the LAN interface pt1*
![[lan_interface_settings_ipv4.png]] ![Configuring the LAN interface pt2](./images/lan_interface_settings_ipv4.png)
*Configuring the LAN interface pt2* *Configuring the LAN interface pt2*
## The domain controller ## The domain controller
The Domain controlling virtual machine is only attached to the WindowsLab bridge. It has no connection to my home LAN other that through the firewall. I chose to install Windows server 2022 Standard evaluation with the desktop environment. After install I configured a static IP for the server. The Domain controlling virtual machine is only attached to the WindowsLab bridge. It has no connection to my home LAN other that through the firewall. I chose to install Windows server 2022 Standard evaluation with the desktop environment. After install I configured a static IP for the server.
![[dc_networking.png]] ![The Domain Controller interfaces in Proxmox](./images/dc_networking.png)
*The Domain Controller interfaces in Proxmox* *The Domain Controller interfaces in Proxmox*
Active Directory Domain Services and DNS where installed through the roles and features wizard. After the install and a reboot I promoted the server to domain controller, created a new Forrest and otherwise keeping the AD DS configuration options default. Active Directory Domain Services and DNS where installed through the roles and features wizard. After the install and a reboot I promoted the server to domain controller, created a new Forrest and otherwise keeping the AD DS configuration options default.
![[AD_DS.png]] ![Active Directory Users and Computers is available](./images/AD_DS.png)
*Active Directory Users and Computers is available* *Active Directory Users and Computers is available*
## Conclusion ## Conclusion