<?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>Windows on Martijn's Notes</title><link>https://vandenboom.online/de/tags/windows/</link><description>Recent content in Windows on Martijn's Notes</description><generator>Hugo</generator><language>de</language><copyright>Copyright © 2016-2026 van den &lt;span class='bold-rotate'&gt;B&lt;/span&gt;oom. All Rights Reserved.</copyright><lastBuildDate>Tue, 14 Apr 2026 19:01:00 +0200</lastBuildDate><atom:link href="https://vandenboom.online/de/tags/windows/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure DevOps – Teil 2: Ihre erste YAML-Pipeline</title><link>https://vandenboom.online/de/posts/2026-azure-devops-pipelines-eerste-pipeline/</link><pubDate>Tue, 14 Apr 2026 19:01:00 +0200</pubDate><guid>https://vandenboom.online/de/posts/2026-azure-devops-pipelines-eerste-pipeline/</guid><description><![CDATA[<p>In <a href="../2026-azure-devops-repos-branches-policies-pull-requests/">Teil 1</a> wurde der <code>azure-pipelines.yml</code> über einen Pull Request in den Zweig <code>main</code> eingebunden. In diesem zweiten Teil hängen wir diese YAML an eine Pipeline an und führen sie auf einem von Microsoft gehosteten Windows-Agenten in der Cloud aus.</p>

<h2 id="der-abschnitt-pipelines" data-numberify>Der Abschnitt „Pipelines“.<a class="anchor ms-1" href="#der-abschnitt-pipelines"></a></h2>
<p>Der Abschnitt „Pipelines“ in der Seitenleiste enthält mehr Elemente als Repos:</p>
<ul>
<li><strong>Pipelines</strong> – die CI-Pipelines (Build)</li>
<li><strong>Umgebungen</strong> – Bereitstellungsziele wie Akzeptanz und Produktion</li>
<li><strong>Releases</strong> – die klassischen visuellen Release-Pipelines (älteres System, wird durch mehrstufiges YAML ersetzt)</li>
<li><strong>Bibliothek</strong> – Variablengruppen und sichere Dateien</li>
<li><strong>Aufgabengruppen</strong> – wiederverwendbare Aufgabenblöcke, die über mehrere Pipelines hinweg gemeinsam genutzt werden können</li>
<li><strong>Bereitstellungsgruppen</strong> – selbstgehostete Agenten, gruppiert nach Umgebung</li>
</ul>
<p>Bei einem neuen Projekt ist die Pipelines-Liste leer.</p>]]></description><enclosure url="https://vandenboom.online/posts/2026-azure-devops-pipelines-eerste-pipeline/cover.png" length="110910" type="image/png"/></item><item><title>Azure DevOps — Part 1: Repos, Branches, Policies and Pull Requests</title><link>https://vandenboom.online/de/posts/2026-azure-devops-repos-branches-policies-pull-requests/</link><pubDate>Tue, 14 Apr 2026 19:00:00 +0200</pubDate><guid>https://vandenboom.online/de/posts/2026-azure-devops-repos-branches-policies-pull-requests/</guid><description><![CDATA[<p>Azure DevOps is Microsoft&rsquo;s platform for managing the complete software delivery chain: version control, CI/CD pipelines, project planning, package feeds and documentation. In this first part of the series we build the foundation: a Git repository, branch protection and the Pull Request workflow.</p>

<h2 id="setup-organisation-and-project" data-numberify>Setup: organisation and project<a class="anchor ms-1" href="#setup-organisation-and-project"></a></h2>
<p>After logging in to <a href="https://dev.azure.com" target="_blank" rel="noopener noreferrer">dev.azure.com<i class="fas fa-external-link-square-alt ms-1"></i></a> the <code>mvdboom</code> organisation is visible with one existing project.</p>
<p><picture><img class="img-fluid " alt="mvdboom organisation with test_hello_world project" src="/posts/2026-azure-devops-repos-branches-policies-pull-requests/screenshot-01-mvdboom-organisatie.png" loading="lazy" width="2559" height="1410" />
</picture>

</p>]]></description><enclosure url="https://vandenboom.online/posts/2026-azure-devops-repos-branches-policies-pull-requests/screenshot-11-feature-branch.png" length="168514" type="image/png"/></item><item><title>Windows Server 2022 — Active Directory and DNS Installation</title><link>https://vandenboom.online/de/posts/windows_server_2022_ad_dns/</link><pubDate>Fri, 27 Mar 2026 00:00:00 +0100</pubDate><guid>https://vandenboom.online/de/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/de/posts/windows_packet_capturing/</link><pubDate>Sun, 18 Jan 2026 20:19:01 +0100</pubDate><guid>https://vandenboom.online/de/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></channel></rss>