<?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>Wsus on Aperture Zone</title>
    <link>https://aperturezone.com/tags/wsus/</link>
    <description>Recent content in Wsus 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, 22 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/wsus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WSUS &#43; WinRM &#43; Ansible: regaining control of Windows reboots</title>
      <link>https://aperturezone.com/posts/wsus_winrm/</link>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/wsus_winrm/</guid>
      <description>&lt;p&gt;This is a project I’ve been thinking about for a while, but I had to finish other tasks first (especially the vault, for those who’ve read the previous articles) before tackling this one; however, the latest reboot of my hypervisor in the middle of the night was the last straw. That was the straw that broke the camel’s back.&lt;/p&gt;
&lt;p&gt;The goal: to set up a complete workflow to &lt;strong&gt;control when updates are installed and when machines reboot&lt;/strong&gt;, with email notifications. Exactly what’s already in place for Linux servers via Ansible.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
