<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>ing. M.A.C.M. (Martijn) van den Boom on Martijn's Notes</title><link>https://vandenboom.online/fr/authors/martijnvandenboom/</link><description>Recent content in ing. M.A.C.M. (Martijn) van den Boom on Martijn's Notes</description><generator>Hugo</generator><language>fr</language><copyright>Copyright © 2016-2026 van den &lt;span class='bold-rotate'&gt;B&lt;/span&gt;oom. All Rights Reserved.</copyright><lastBuildDate>Thu, 02 Apr 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://vandenboom.online/fr/authors/martijnvandenboom/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows Server 2022 Home Lab — AD DS, DNS, CA and Secured RDP</title><link>https://vandenboom.online/fr/posts/ws2022-home-lab-ad-dns-ca-rdp/</link><pubDate>Thu, 02 Apr 2026 10:00:00 +0200</pubDate><guid>https://vandenboom.online/fr/posts/ws2022-home-lab-ad-dns-ca-rdp/</guid><description><![CDATA[<p><a href="WS2022-Lab-Manual-EN.docx" download class="btn btn-outline-primary btn-sm mb-3"><i class="fas fa-download me-1"></i> Download as Word document</a></p>
<p>This article describes the full build of a two-server Windows Server 2022 home lab in Proxmox VE. Together, the two virtual machines provide Active Directory Domain Services, DNS, Group Policy and a Certificate Authority (ADCS). RDP connections are secured with PKI certificates so the Mac Mini M1 management workstation connects without certificate warnings.</p>
<p>This is part 3 of the series on building a Windows DevOps lab in Proxmox. In <a href="/posts/ws2022-proxmox-vm-creation/">part 1</a> I described how to create a VM, and in <a href="/posts/ws2022-proxmox-template-preparation/">part 2</a> how to prepare the template.</p>]]></description></item><item><title>Windows Server 2022 in Proxmox — Template Preparation</title><link>https://vandenboom.online/fr/posts/ws2022-proxmox-template-preparation/</link><pubDate>Tue, 31 Mar 2026 10:00:00 +0200</pubDate><guid>https://vandenboom.online/fr/posts/ws2022-proxmox-template-preparation/</guid><description><![CDATA[<p><a href="WS2022-in-Proxmox-Template-Preparation-Guide-EN.docx" download class="btn btn-outline-primary btn-sm mb-3"><i class="fas fa-download me-1"></i> Download as Word document</a></p>
<p>This is part 2 of the series on building a Windows DevOps lab in Proxmox. In <a href="/posts/ws2022-proxmox-vm-creation/">part 1</a> I described how to create the VM. In this article I prepare the VM as a reusable Proxmox template. All future VMs — the CA server, member servers and other roles — will be cloned from this template.</p>
<blockquote>
<p><strong>Important:</strong> After Sysprep, <strong>never</strong> start the VM again. If you do, the generalization is consumed and the template must be rebuilt from scratch.</p>]]></description></item><item><title>Windows Server 2022 in Proxmox — Creating a VM</title><link>https://vandenboom.online/fr/posts/ws2022-proxmox-vm-creation/</link><pubDate>Mon, 30 Mar 2026 10:00:00 +0200</pubDate><guid>https://vandenboom.online/fr/posts/ws2022-proxmox-vm-creation/</guid><description><![CDATA[<p><a href="WS2022-in-Proxmox-VM-Creation-Guide-EN.docx" download class="btn btn-outline-primary btn-sm mb-3"><i class="fas fa-download me-1"></i> Download as Word document</a></p>
<p>In this article I describe step by step how I create a Windows Server 2022 VM in Proxmox VE 9.1.6. The guide is based on real-world experience and includes all corrections and lessons learned along the way. This is part 1 of a series on building a fully functional Windows DevOps lab in Proxmox.</p>

<h2 id="lab-environment" data-numberify>Lab Environment<a class="anchor ms-1" href="#lab-environment"></a></h2>
<table>
	<thead>
			<tr>
					<th>Component</th>
					<th>Value</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Proxmox host</td>
					<td>macpro2013.local — Mac Pro 2013 Trashcan</td>
			</tr>
			<tr>
					<td>Proxmox version</td>
					<td>9.1.6</td>
			</tr>
			<tr>
					<td>RAM</td>
					<td>128 GB</td>
			</tr>
			<tr>
					<td>Storage</td>
					<td>3.6 TB NVMe (local-lvm pool)</td>
			</tr>
			<tr>
					<td>Network bridge</td>
					<td>vmbr0 — internal lab network (192.168.178.x)</td>
			</tr>
			<tr>
					<td>Proxmox WebUI</td>
					<td>https://192.168.178.205:8006</td>
			</tr>
	</tbody>
</table>
<hr>

<h2 id="why-a-ca-is-needed--the-ssl-warning" data-numberify>Why a CA Is Needed — the SSL Warning<a class="anchor ms-1" href="#why-a-ca-is-needed--the-ssl-warning"></a></h2>
<p>Anyone who opens the Proxmox WebUI via <code>macpro2013.local</code> in Safari will immediately see a certificate warning. Proxmox uses a self-signed certificate by default.</p>]]></description></item><item><title>Windows Server 2022 — Active Directory and DNS Installation</title><link>https://vandenboom.online/fr/posts/windows_server_2022_ad_dns/</link><pubDate>Fri, 27 Mar 2026 00:00:00 +0100</pubDate><guid>https://vandenboom.online/fr/posts/windows_server_2022_ad_dns/</guid><description><![CDATA[<p>This article describes step by step how I installed Active Directory Domain Services (AD DS) and DNS on a Windows Server 2022 Datacenter VM in a VMware Fusion lab environment. The result is a fully functional domain controller for the domain <strong>lab.local</strong>, serving as the foundation for a Windows DevOps lab.</p>

<h2 id="environment" data-numberify>Environment<a class="anchor ms-1" href="#environment"></a></h2>
<table>
	<thead>
			<tr>
					<th>Component</th>
					<th>Value</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Virtualization</td>
					<td>VMware Fusion (macOS)</td>
			</tr>
			<tr>
					<td>Guest OS</td>
					<td>Windows Server 2022 Datacenter (Desktop Experience)</td>
			</tr>
			<tr>
					<td>Hostname</td>
					<td>DC01</td>
			</tr>
			<tr>
					<td>Domain name</td>
					<td>lab.local</td>
			</tr>
			<tr>
					<td>NetBIOS name</td>
					<td>LAB</td>
			</tr>
			<tr>
					<td>Lab network adapter</td>
					<td>Ethernet1 — 172.16.37.10 (static IP)</td>
			</tr>
			<tr>
					<td>Internet adapter</td>
					<td>Ethernet0 — DHCP via VMware NAT</td>
			</tr>
	</tbody>
</table>
<hr>

<h2 id="step-1--configure-networking" data-numberify>Step 1 — Configure Networking<a class="anchor ms-1" href="#step-1--configure-networking"></a></h2>
<p>Before installing Active Directory, the domain controller needs a static IP address. AD DS and DNS depend on a stable address.</p>]]></description></item><item><title>Windows Packet Capturing for LDAPS Analysis</title><link>https://vandenboom.online/fr/posts/windows_packet_capturing/</link><pubDate>Sun, 18 Jan 2026 20:19:01 +0100</pubDate><guid>https://vandenboom.online/fr/posts/windows_packet_capturing/</guid><description><![CDATA[<p>Troubleshooting LDAPS Connectivity: Using Built-in Windows Tools to Audit Firewall Compliance
As organizations move toward more secure infrastructure, migrating from standard LDAP (Port 389) to LDAPS (Port 636) is a critical step. However, this transition often reveals &ldquo;silent&rdquo; failures where a network firewall might allow the initial connection but block the subsequent SSL/TLS handshake.</p>
<p>At Van den Boom Online, we understand that a smooth user experience starts with a robust backend. In this guide, we’ll show you how to perform packet capturing using only built-in Windows tools to verify if your traffic is reaching its destination or being dropped by security appliances.</p>]]></description></item><item><title>Install Ansible AWX 24.6.1 in Minikube on Ubuntu 24.04.2 LTS in a single VM</title><link>https://vandenboom.online/fr/posts/ansible_awx/</link><pubDate>Wed, 02 Jul 2025 13:35:25 +0200</pubDate><guid>https://vandenboom.online/fr/posts/ansible_awx/</guid><description><![CDATA[<p>Create a Ubuntu Virtual Machine with:</br>
32 GB RAM</br>
8 cores</br>
120 GB HD</br></p>
<p>Step-by-step: Install AWX 24.6.1 on Minikube (Ubuntu)</p>
<p>🔧 1. System Preparation</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="ln">1</span><span class="cl">$ sudo apt update &amp;&amp; sudo apt upgrade -y
</span></span><span class="line"><span class="ln">2</span><span class="cl">$ sudo apt install -y curl wget apt-transport-https ca-certificates gnupg lsb-release software-properties-common
</span></span><span class="line"><span class="ln">3</span><span class="cl">$ sudo timedatectl set-timezone Europe/Amsterdam
</span></span></code></pre></div><p>📦 2. Install Docker (Minikube backend)</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="ln"> 1</span><span class="cl">$ curl -fsSL https://get.docker.com | sudo bash
</span></span><span class="line"><span class="ln"> 2</span><span class="cl">$ sudo usermod -aG docker $USER
</span></span><span class="line"><span class="ln"> 3</span><span class="cl">$ newgrp docker  # Activate group without reboot
</span></span><span class="line"><span class="ln"> 4</span><span class="cl">
</span></span><span class="line"><span class="ln"> 5</span><span class="cl">Enable and start Docker:
</span></span><span class="line"><span class="ln"> 6</span><span class="cl">$ sudo systemctl enable docker
</span></span><span class="line"><span class="ln"> 7</span><span class="cl">$ sudo systemctl start docker
</span></span><span class="line"><span class="ln"> 8</span><span class="cl">
</span></span><span class="line"><span class="ln"> 9</span><span class="cl">Test:
</span></span><span class="line"><span class="ln">10</span><span class="cl">$ docker run hello-world
</span></span></code></pre></div><p>🧱 3. Install Minikube</p>]]></description></item><item><title>Install Red Hat Ansible Automation Platform 2.5 in a single VM</title><link>https://vandenboom.online/fr/posts/ansible_automation_platform/</link><pubDate>Sun, 29 Jun 2025 23:10:08 +0200</pubDate><guid>https://vandenboom.online/fr/posts/ansible_automation_platform/</guid><description><![CDATA[<p>Attention: I have not been able to make it restart automatically after a reboot! </br>
Perhaps it is better to look into making it run in Minikube?</br>
</br>
Create a Red Hat 9 Virtual Machine with:</br>
32 GB RAM</br>
8 cores</br>
120 GB HD</br></p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="ln">1</span><span class="cl">$ sudo hostnamectl hostname aap.vandenboom.local
</span></span></code></pre></div><p>Download the Ansible Automation Platform 2.5 Containerized Setup Bundle from:
<a href="https://access.redhat.com/downloads/content/480/ver=2.5/rhel---9/2.5/x86_64/product-software" target="_blank" rel="noopener noreferrer">https://access.redhat.com/downloads/content/480/ver=2.5/rhel---9/2.5/x86_64/product-software<i class="fas fa-external-link-square-alt ms-1"></i></a></p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-fallback" data-lang="fallback"><span class="line"><span class="ln"> 1</span><span class="cl">$ tar zxvf ansible*.tar.gz
</span></span><span class="line"><span class="ln"> 2</span><span class="cl">
</span></span><span class="line"><span class="ln"> 3</span><span class="cl">$ sudo vim /etc/hosts
</span></span><span class="line"><span class="ln"> 4</span><span class="cl">localhost aap.vandenboom.local
</span></span><span class="line"><span class="ln"> 5</span><span class="cl">
</span></span><span class="line"><span class="ln"> 6</span><span class="cl">$ ping aap.vandenboom.local
</span></span><span class="line"><span class="ln"> 7</span><span class="cl">
</span></span><span class="line"><span class="ln"> 8</span><span class="cl">$ sudo dnf install -y podman git python3-pip rsync tar jq unzip
</span></span><span class="line"><span class="ln"> 9</span><span class="cl">
</span></span><span class="line"><span class="ln">10</span><span class="cl">$ podman login registry.redhat.io
</span></span><span class="line"><span class="ln">11</span><span class="cl">
</span></span><span class="line"><span class="ln">12</span><span class="cl">$ sudo dnf install ansible-core wget
</span></span><span class="line"><span class="ln">13</span><span class="cl">
</span></span><span class="line"><span class="ln">14</span><span class="cl">$ python3 -m pip install virtualenv
</span></span><span class="line"><span class="ln">15</span><span class="cl">$ pip3 install ansible
</span></span><span class="line"><span class="ln">16</span><span class="cl">
</span></span><span class="line"><span class="ln">17</span><span class="cl">$ vim inventory
</span></span><span class="line"><span class="ln">18</span><span class="cl">Edit the settings as seen below
</span></span><span class="line"><span class="ln">19</span><span class="cl">
</span></span><span class="line"><span class="ln">20</span><span class="cl">$ time ansible-playbook -i inventory ansible.containerized_installer.install -K
</span></span></code></pre></div><p>This is the contents of the file: ./inventory</p>]]></description></item><item><title>A comparison of the resource usage of Kubernetes and OpenShift</title><link>https://vandenboom.online/fr/posts/pas_op_met_openshift/</link><pubDate>Sat, 29 Mar 2025 15:15:43 +0100</pubDate><guid>https://vandenboom.online/fr/posts/pas_op_met_openshift/</guid><description><![CDATA[<p>When comparing Kubernetes with OpenShift (Red Hat&rsquo;s Kubernetes-based platform), there are several key differences that affect how they handle resource consumption and system resources. While OpenShift is built on top of Kubernetes, there are additional functionalities and differences that impact the resource requirements:</p>
<ol>
<li>Additional Functionalities in OpenShift
OpenShift offers more out-of-the-box functionality than Kubernetes. This can lead to higher overhead, but also to more ease of use and integration:</li>
</ol>
<ul>
<li>
<p>Security: OpenShift adds extra security layers, such as Security Context Constraints (SCC) and SELinux restrictions, which may require additional resources for securing containers and applications.</p>]]></description></item><item><title>The statement 'beware of Kubernetes, it burns through your resources'</title><link>https://vandenboom.online/fr/posts/pas_op_met_kubernetes/</link><pubDate>Sat, 29 Mar 2025 15:00:43 +0100</pubDate><guid>https://vandenboom.online/fr/posts/pas_op_met_kubernetes/</guid><description><![CDATA[<p>The statement &ldquo;beware of Kubernetes, it burns through your resources&rdquo; refers to the fact that Kubernetes, although a powerful and flexible solution for orchestrating containerized applications, can consume a relatively large amount of system resources (such as CPU, memory, and storage).</p>
<p>This is due to several factors:</p>
<ol>
<li>
<p>Kubernetes has overhead: Kubernetes itself runs as a cluster of various components, such as the API server, scheduler, controller manager, and more. These components run on the control plane and need to be managed. This adds extra overhead to your system, meaning that the resources Kubernetes itself uses are added on top of the applications you are actually running.</p>]]></description></item><item><title>Golang / Go: The Smart Programming Language for Efficient Software and Concurrency</title><link>https://vandenboom.online/fr/posts/golang_go_concurrency/</link><pubDate>Sat, 22 Mar 2025 21:00:43 +0100</pubDate><guid>https://vandenboom.online/fr/posts/golang_go_concurrency/</guid><description>&lt;p>Concurrency might sound like a technical term, but it boils down to a program performing multiple tasks at once, as if it’s multitasking. Imagine you’re cooking: while the pasta is on the stove, you start the washing machine and charge your phone. Although you’re not doing everything at the exact same moment, it all happens smoothly side by side. Software that supports concurrency works the same way: a program can, for instance, download files, perform calculations, and send data to a server all at once. This multitasking makes the use of computing power more efficient and ensures faster, smoother performance.&lt;/p></description></item></channel></rss>