<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ansible on Tod's Homelab</title><link>https://homelab.tod.net/tags/ansible/</link><description>Recent content in Ansible on Tod's Homelab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Jul 2026 12:58:47 -0400</lastBuildDate><atom:link href="https://homelab.tod.net/tags/ansible/feed.xml" rel="self" type="application/rss+xml"/><item><title>Preparing the Windows Fleet for Samba</title><link>https://homelab.tod.net/posts/off-windows/preparing-the-windows-fleet-for-samba/</link><pubDate>Sun, 05 Jul 2026 12:58:47 -0400</pubDate><guid>https://homelab.tod.net/posts/off-windows/preparing-the-windows-fleet-for-samba/</guid><description>&lt;p&gt;&lt;strong&gt;Off Windows&lt;/strong&gt; tracks removing every remaining Windows dependency from the lab, starting with the two domain controllers that gave the series its name. &lt;a href="https://homelab.tod.net/posts/off-windows/migrating-active-directory-to-samba/"&gt;The next post in the series&lt;/a&gt; covers the actual migration — an in-place replica join that swaps both Windows DCs for a Samba box named &lt;code&gt;sidious&lt;/code&gt; without a single workstation noticing. This post covers the evening before that: getting the rest of the Windows fleet — the desktops, laptops, and &lt;code&gt;piett&lt;/code&gt;, &lt;a href="https://homelab.tod.net/posts/downsizing-the-homelab/why-im-replacing-a-homelab-that-still-works/"&gt;the Windows Server box running Veeam Backup &amp;amp; Replication&lt;/a&gt; and one of the two Windows-licensing reasons this whole series exists — under Ansible management and onto a trust chain that would survive the domain changing underneath them.&lt;/p&gt;</description></item></channel></rss>