<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: In-Place Upgrading A Windows Server 2012 Domain Controller to Windows Server 2019 or 2022	</title>
	<atom:link href="https://www.kjctech.net/in-place-upgrading-a-windows-server-2012-domain-controller-to-windows-server-2019-or-2022/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.kjctech.net/in-place-upgrading-a-windows-server-2012-domain-controller-to-windows-server-2019-or-2022/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=in-place-upgrading-a-windows-server-2012-domain-controller-to-windows-server-2019-or-2022</link>
	<description></description>
	<lastBuildDate>Wed, 18 Feb 2026 18:08:07 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Mekkel Richards		</title>
		<link>https://www.kjctech.net/in-place-upgrading-a-windows-server-2012-domain-controller-to-windows-server-2019-or-2022/comment-page-1/#comment-383518</link>

		<dc:creator><![CDATA[Mekkel Richards]]></dc:creator>
		<pubDate>Wed, 18 Feb 2026 18:08:07 +0000</pubDate>
		<guid isPermaLink="false">https://www.kjctech.net/?p=5146#comment-383518</guid>

					<description><![CDATA[Seems to me like this was a bad patch (cumulative update) for Server 2016 that caused the DHCP issues. I believe further updates fixed this. Can you confirm the updates fixed your problem?]]></description>
			<content:encoded><![CDATA[<p>Seems to me like this was a bad patch (cumulative update) for Server 2016 that caused the DHCP issues. I believe further updates fixed this. Can you confirm the updates fixed your problem?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
