<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Patch Manager on Ryan Devs Dallas</title>
    <link>https://ryandevsdallas.com/tags/patch-manager/</link>
    <description>Recent content in Patch Manager on Ryan Devs Dallas</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Jan 2025 11:11:53 +0000</lastBuildDate>
    <atom:link href="https://ryandevsdallas.com/tags/patch-manager/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using SSM Patch Manager To Automate Windows Server Patching</title>
      <link>https://ryandevsdallas.com/posts/using-ssm-patch-manager-to-automate-windows-server-patching/</link>
      <pubDate>Wed, 29 Jan 2025 11:11:53 +0000</pubDate>
      <guid>https://ryandevsdallas.com/posts/using-ssm-patch-manager-to-automate-windows-server-patching/</guid>
      <description>&lt;p&gt;Recently at work, I was tasked with automating patching for approximately 10 Windows Servers. We already have a process around patching automation for the (approximately) 900 existing servers we manage. Most of the heavy lifting on these is done using &lt;a href=&#34;https://learn.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/deploy-windows-server-update-services&#34;&gt;WSUS&lt;/a&gt; with the help of the &lt;a href=&#34;https://www.ajtek.ca/&#34;&gt;AJ Tek WAM tool&lt;/a&gt;. Unfortunately, in this edge case, we won’t be able to use our existing methods. These new server are separated from the bulk of our network for compliance reasons and are also not joined to a domain.  So there is no pre-existing centralized group policy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
