<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AD CS – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/ad-cs/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-US</language><lastBuildDate>Tue, 29 Sep 2026 19:05:28 +0200</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/ad-cs/index.xml" rel="self" type="application/rss+xml"/><item><title>My Own Little Certificate Authority: AD CS, Auto-Enrollment and Goodbye to “Your Connection Is Not Private”</title><link>https://www.apt-upgrade.me/2026/09/29/my-own-little-certificate-authority-ad-cs-auto-enrollment-and-goodbye-to-your-connection-is-not-private/</link><pubDate>Tue, 29 Sep 2026 19:05:28 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/29/my-own-little-certificate-authority-ad-cs-auto-enrollment-and-goodbye-to-your-connection-is-not-private/</guid><description>&lt;p&gt;My homelab has three domain controllers, two clients, three iLO management boards and, until last week, exactly zero certificates anyone had a reason to trust. Every RDP session started with a warning, every iLO greeted me with &lt;em&gt;&amp;ldquo;Your connection is not private&amp;rdquo;&lt;/em&gt; (issuer: &lt;em&gt;Default Issuer (Do not trust)&lt;/em&gt;, which is at least honest), and the domain controllers didn&amp;rsquo;t speak LDAPS at all.&lt;/p&gt;&#10;&lt;p&gt;I don&amp;rsquo;t run many internal web services, so for a while I assumed a private PKI was a solution looking for a problem. Wrong. A Windows domain has plenty of places where certificates quietly make things better. The trick is to let Active Directory hand them out on its own, so that I never have to think about renewing them again.&lt;/p&gt;</description></item><item><title>Enough YAML for Now: Three Servers, Windows Server 2025, and a Crash Course on the Dark Side</title><link>https://www.apt-upgrade.me/2026/09/23/enough-yaml-for-now-three-servers-windows-server-2025-and-a-crash-course-on-the-dark-side/</link><pubDate>Wed, 23 Sep 2026 21:06:04 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/23/enough-yaml-for-now-three-servers-windows-server-2025-and-a-crash-course-on-the-dark-side/</guid><description>&lt;p&gt;Confession time. After the &lt;a href="https://www.apt-upgrade.me/2026/09/21/bare-metal-to-k3s-a-nextcloud-migration-battle-log/"&gt;Nextcloud migration battle log&lt;/a&gt;, a double-digit number of playbook runs, one nftables ruleset that cheerfully flushed K3s&amp;rsquo; own tables, and more YAML than any human should read in a single week, I had officially had it up to &lt;em&gt;here&lt;/em&gt; with &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt;, Ansible and anything containing the word &amp;ldquo;migration&amp;rdquo;.&lt;/p&gt;&#10;&lt;p&gt;So I did what any reasonable Linux nerd does when burned out on Linux: I went over to the other side. Three servers, three fresh installs of &lt;strong&gt;Windows Server 2025&lt;/strong&gt;, and a few evenings of Active Directory, DNS, DHCP, Group Policy, Storage Spaces and BitLocker. No YAML. Just a lot of &lt;code&gt;Get-&lt;/code&gt; and &lt;code&gt;Set-&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>