Skip to main content

not a journey but an ADventure

 

Recently, I took a significant step in upgrading my home lab by installing a second mini PC: the BOSGAME P3 Lite Mini PC, powered by a Ryzen 7 6800H processor complimenting the mini PC I already have a GMKtec M7 AMD Ryzen 7 Gaming Mini PC 6850H. Alongside this, I added a TP-Link TL-SG608E Managed 8-Port Gigabit Network Switch, promising both increased computing power and enhanced networking capabilities.

After physically connecting and configuring the new equipment, I was inspired to create a more enterprise-like environment. My specific goal was to deploy Active Directory on a virtual machine hosted by the new mini PC, allowing me to explore Windows Server administration hands-on and experiment with real-world domain scenarios such as group policy management, user authentication, and network segmentation.

The managed switch opened opportunities to simulate advanced network topologies, including VLANs and bandwidth management. Meanwhile, the mini-PC’s robust Ryzen processor and ample RAM provided the resources necessary to run multiple virtual machines without performance issues. This setup was the ideal foundation for deepening my understanding of enterprise networking and server management all within the safe confines of my home lab.

To make the most of my new hardware, I decided to virtualize Windows Server so I could run Active Directory a core Microsoft service designed for managing users, computers, permissions, and network resources in business environments. Active Directory acts as a centralised directory service, enabling administrators to control access, implement security policies, and streamline user authentication across the network. Experimenting with it at home gave me hands-on experience with enterprise-grade network management in a controlled setting. I had already installed VirtualBox, a widely used open-source virtualization platform. Considering my installation media options, I downloaded the Windows Server ISO directly from Microsoft (https://www.microsoft.com/en-gb/evalcenter/evaluate-windows-server-2025), since they offer a free 180-day evaluation license. I chose the ISO format because VirtualBox does not natively support VHD files, and I’ve previously encountered reliability issues when attempting to convert them.

With the ISO in hand, I set up a new virtual machine in VirtualBox, allocating 100GB of storage, approximately 10GB of RAM, and 4 processor cores enough to ensure smooth operation under moderate workloads. I specifically chose VirtualBox for its open-source nature and widespread community support. Its intuitive interface and ease of use make configuring virtual machines straightforward, even for complex projects. Additionally, being free and cross-platform meant I could experiment flexibly without worrying about licensing costs or vendor lock-in, allowing my home lab to remain both cost-effective and adaptable as my needs grow. Careful preparation of these specifications and the right installation method allowed me to build a solid foundation for my future Windows Server environment.

My CPU, memory and hard drive setup for my virtual machine shown above.

 

Once the VM was configured, I installed Windows Server using the ISO. The process was straightforward: language and region selection, license agreement, and then setting an administrator password to ensure security from the start. The system booted seamlessly into the familiar Server Manager dashboard.

A screenshot of a computer program AI-generated content may be incorrect.A screenshot of a computer AI-generated content may be incorrect.

The pictures above are from the installation process and the final one is where I have logged in and can set up the sever for its role in my case a domain controller.

At this point, I intended to configure the VM as a domain controller by installing Active Directory Domain Services. However, I ran out of time before I could complete networking prerequisites like assigning a static IP address and configuring DNS. So, for now, the VM is set up with the operating system installed and ready for further configuration during my next session.

The key takeaway from this experience is that progress in learning isn’t always linear sometimes it’s just a small step forward, and other times it’s a great leap. Even when time is short, making incremental progress is valuable. Every session, no matter how brief, brings me closer to my goals.

The next step I have is to set up my windows server as a domain controller and to attach my linux endpoint to it, with the scope to add windows enterprise evaluation versions sometime after that.

Labels:

Comments

Post a Comment

Popular posts from this blog

Root of the Problem: Linux Flaws That Give Attackers Admin Rights

 I realised that I haven’t posted to my blog in a long time and this week an article about CVE’s in linux caught my eye and that was the perfect excuse to write another blog post. Cybersecurity researchers at Qualys have uncovered two critical local privilege escalation (LPE) flaws that are shaking the foundations of Linux security. These aren't your run-of-the-mill vulnerabilities; we're talking about direct, express lanes to full root access on major Linux distributions. If you use Ubuntu, Debian, Fedora, openSUSE Leap 15, or SUSE Linux Enterprise 15, you need to pay close attention. The Double Threat: CVE-2025-6018 & CVE-2025-6019 An article detailing the CVE’s can be found at the link below ( CVE-2025-6018 and CVE-2025-6019 Vulnerability Exploitation: Chaining Local Privilege Escalation Flaws Lets Attackers Gain Root Access on Most Linux Distributions | SOC Prime )     Qualys has pulled back the curtain on two distinct, yet chainable, vulnerabilit...
Post a Comment
Read more

From OVA to Rocky: My Wazuh Upgrade Story

  In this blog post I will be covering something I’ve covered in a previous blog post, but I’ve decided to change my home lab and put my Wazuh SIEM on a standalone rocky linux, there are several reasons I chose to do this, Performance & Scalability: The OVA VM is a pre-built virtual machine that may not be optimized for high availability or scalability. A dedicated instance on Rocky Linux allows for better resource allocation and tuning. Customization & Flexibility: The OVA VM comes with predefined configurations. Running Wazuh on Rocky Linux gives you full control over system settings, security policies, and software updates. Compatibility & Stability: Rocky Linux is a stable, enterprise-grade OS, and Wazuh has been tested for compatibility with newer versions like Rocky Linux 9.3. This ensures long-term support and reliability. Security & Isolation: A dedicated instance provides better security isolation compared to a shared virtualized environment. You can impl...
Post a Comment
Read more

Up the Wazuh: A SIEM-ple Adventure in Troubleshooting

Initial setup To start  I downloaded the .osa file from the  wazuh website ( https://wazuh.com ) and then installed it in my virtualbox hypervisor. Then I booted up my fedora linux VM and the wazuh VM with the dashboard and manager on.  After I had logged in to the wazuh VM with the default credentials I used the ip a command to find out the ip address of the wazuh VM. As from reading the documentation I’d need this later. In my fedora VM I opened a terminal and used the commands on the wazuh website to install the agent on the VM. After some time the installation was completed and I had to update the. conf file with the IP address of the wazuh manager. This is important because  the file is a generic file that needs to be modified to make it specific to each individual setup.  All was going well up to this point. I tried to get the fedora VM to talk to the wazuh VM. The problems I encountered It was here the problems started when I tried to pi...
Post a Comment
Read more