https://aperturezone.com/tags/dfsr/ Recent content in Dfsr on Aperture Zone https://aperturezone.com/logo.webp https://aperturezone.com/logo.webp Hugo -- gohugo.io fr-fr Fri, 27 Mar 2026 00:00:00 +0000 https://aperturezone.com/posts/migration2022/ Fri, 27 Mar 2026 00:00:00 +0000 https://aperturezone.com/posts/migration2022/ <p>In a <a href="https://aperturezone.com/posts/approvals">previous post</a>, I described the 2016 functional upgrade and the approvals audit between my two domains. I ended on this note: <em>&quot;I’ll also need to think about upgrading the OS on my other controllers.&quot;</em></p> <p>Well, that’s done.</p> <hr> <h2 id="background">Background</h2> <p>The infrastructure is based on a two-domain Active Directory forest:</p> <ul> <li>A <strong>forest root domain</strong>, 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).</li> <li>A <strong>child domain</strong>, 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.</li> </ul> <p>All were running on <strong>Windows Server 2016</strong>, for which mainstream support ended in 2022 and extended support ends in January 2027. The time had come to migrate to <strong>Windows Server 2022</strong>.</p>