<?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>Gpo on Aperture Zone</title>
    <link>https://aperturezone.com/tags/gpo/</link>
    <description>Recent content in Gpo 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>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/gpo/index.xml" rel="self" type="application/rss+xml" />
    <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>
    
  </channel>
</rss>
