<?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>Active Directory on Aperture Zone</title>
    <link>https://aperturezone.com/tags/active-directory/</link>
    <description>Recent content in Active Directory 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>Fri, 03 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/active-directory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DRP on Hyper-V with Veeam: from chaos to clean failover</title>
      <link>https://aperturezone.com/posts/drpveeam/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/drpveeam/</guid>
      <description>&lt;p&gt;I have a virtualized infrastructure running on &lt;strong&gt;Hyper-V&lt;/strong&gt; with a separate backup/DRP server. The entire stack runs on &lt;strong&gt;19 VMs&lt;/strong&gt;: two Active Directory domains with domain joining, Linux DNS forwarders (BIND9), RADIUS, monitoring, application services&amp;hellip; in short, not something we can afford to just reboot haphazardly.&lt;/p&gt;
&lt;p&gt;The project’s objective was simple to state, but complex to achieve:&lt;/p&gt;
&lt;p&gt;&amp;gt; &lt;strong&gt;Switchover the entire infrastructure to the DRP server with minimal effort, ensuring service continuity (at the very least, not cutting off internet access), then return to production cleanly.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Backing up GPOs with Ansible and WinRM</title>
      <link>https://aperturezone.com/posts/backup_gpo/</link>
      <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/backup_gpo/</guid>
      <description>&lt;p&gt;Group Policy Objects are at the heart of any robust Active Directory infrastructure. They define security settings, permissions, device configurations, and software restrictions. In the event of a disaster, human error, or simply a need to roll back after a change, not having a backup of your GPOs means facing hours of tedious reconstruction.&lt;/p&gt;
&lt;p&gt;The graphical interface of the Group Policy Management Console does offer a backup feature, but it is manual, easy to overlook, and, most importantly, not versioned. The goal of this article is to automate this process cleanly using Ansible via WinRM, on an infrastructure comprising &lt;strong&gt;two separate Active Directory domains&lt;/strong&gt;, with long-term archiving on a NAS and reporting via email.&lt;/p&gt;</description>
    </item>
    
    <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>
    
    <item>
      <title>Hardening AD with PingCastle</title>
      <link>https://aperturezone.com/posts/pingcastle/</link>
      <pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/pingcastle/</guid>
      <description>&lt;h1 id=&#34;pingcastle-amp-hardening-active-directory&#34;&gt;PingCastle &amp;amp; Hardening Active Directory&lt;/h1&gt;
&lt;p&gt;Active Directory is the cornerstone of identity and access management in most Windows environments. Its critical nature also makes it a prime target for attackers. A poorly configured AD can allow privilege escalation, lateral movement, or even total domain compromise.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;PingCastle&lt;/strong&gt; is now one of the benchmark tools for assessing the security posture of an Active Directory. It was developed by &lt;strong&gt;Vincent Le Toux&lt;/strong&gt;, a renowned French expert in offensive security circles whose mastery of Windows and Active Directory internals is widely recognized. He is said to have close ties to &lt;strong&gt;ANSSI&lt;/strong&gt;—a persistent urban legend in the community, fueled by the depth and quality of the tool&#39;s detection rules, which reflect a knowledge of attack vectors rarely achieved outside of government circles. Vincent Le Toux is also co-author of &lt;strong&gt;mimikatz&lt;/strong&gt;, the global benchmark tool for extracting Windows credentials.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
