<?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-Server on Aperture Zone</title>
    <link>https://aperturezone.com/tags/windows-server/</link>
    <description>Recent content in Windows-Server on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/windows-server/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Active Directory: krbtgt, from theory to practice</title>
      <link>https://aperturezone.com/posts/krbtgt2/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/krbtgt2/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;https://aperturezone.fr/posts/krbtgt/&#34;&gt;first part of this article&lt;/a&gt;, we laid the groundwork: what the krbtgt account is, why the Golden Ticket is a serious threat, and a theoretical Ansible architecture for automating rotations. If you haven’t read that part, I encourage you to start there.&lt;/p&gt;
&lt;p&gt;Now we’re getting down to business. The playbook in Part 1 was intentionally simplified to illustrate the concept. In a real production environment, things get complicated—the interactive script that refuses to be controlled, the XML file that can’t be found, the Kerberos double-hop that blocks everything, the root forest that isn’t what we think it is. These are all obstacles I’ve encountered and resolved, which I’m documenting here.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Server 2022 migration: multi-domain forest</title>
      <link>https://aperturezone.com/posts/migration2022/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/migration2022/</guid>
      <description>&lt;p&gt;In a &lt;a href=&#34;https://aperturezone.com/posts/approvals&#34;&gt;previous post&lt;/a&gt;, I described the 2016 functional upgrade and the approvals audit between my two domains. I ended on this note: &lt;em&gt;&amp;quot;I’ll also need to think about upgrading the OS on my other controllers.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Well, that’s done.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;
&lt;p&gt;The infrastructure is based on a two-domain Active Directory forest:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;forest root domain&lt;/strong&gt;, dedicated to servers and hypervisors—two domain controllers ensure its availability. The first holds the domain roles (PDC Emulator, RID Master, Infrastructure Master), while the second holds the forest roles (Schema Master, Domain Naming Master).&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;child domain&lt;/strong&gt;, dedicated to workstations and users—also with two domain controllers. The first holds the domain’s FSMO roles as well as the DNS service and the primary DHCP. The second ensures continuity: Global Catalog, secondary DNS, failover DHCP, and Certificate Authority. Without these roles, a second DC would be nothing more than a passive replica—so we might as well give it a real reason to exist.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All were running on &lt;strong&gt;Windows Server 2016&lt;/strong&gt;, for which mainstream support ended in 2022 and extended support ends in January 2027. The time had come to migrate to &lt;strong&gt;Windows Server 2022&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Active Directory: krbtgt the scary account</title>
      <link>https://aperturezone.com/posts/krbtgt/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/krbtgt/</guid>
      <description>&lt;p&gt;There are elements in Active Directory that we completely forget about because they never come up in day-to-day operations. The &lt;strong&gt;krbtgt&lt;/strong&gt; account is one of them. Though invisible in everyday use, it is at the heart of all Kerberos authentication in your domain—and its compromise is one of the most catastrophic scenarios an attacker could trigger.&lt;/p&gt;
&lt;p&gt;In this article, we’ll explore what this account really is, why you need to change its password regularly, and how to automate this process cleanly with &lt;strong&gt;Ansible&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Active Directory: 2016 functional upgrade and approval audit</title>
      <link>https://aperturezone.com/posts/approbations/</link>
      <pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/approbations/</guid>
      <description>&lt;p&gt;There are some projects that we put off for years. Not because they&#39;re impossible, but because there&#39;s always something getting in the way. In my case, it was Exchange 2013—that good old mail server that stood in the way of any attempt to modernize the AD. Since migrating to a lighter solution, the coast was clear. So here&#39;s the story of a busy night&#39;s work.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;the-context&#34;&gt;The context&lt;/h2&gt;
&lt;p&gt;The infrastructure runs on two separate Active Directory domains linked by a two-way trust relationship:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
