<?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: [:de]Windows Server 2016 Updates: Probleme mit WSUS, AD, DC, Diensten, Netzwerktopologie[:en]Windows Server 2016 Updates: Issues with WSUS, AD, DC, Services, Network Topology[:]	</title>
	<atom:link href="https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/</link>
	<description>Software &#124; Network &#124; Administration</description>
	<lastBuildDate>Fri, 31 Mar 2017 21:39:16 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>
	<item>
		<title>
		By: Jeremy Mayfield		</title>
		<link>https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/#comment-172</link>

		<dc:creator><![CDATA[Jeremy Mayfield]]></dc:creator>
		<pubDate>Fri, 31 Mar 2017 21:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.dxsdata.com/?p=1319#comment-172</guid>

					<description><![CDATA[I can not get my 2016 WSUS server to work at all.   I keep getting errors and cant connect at the server.   I can get to it from the Servername:8530 but when i load the MMC it will not connect.   No updates are coming through.]]></description>
			<content:encoded><![CDATA[<p>I can not get my 2016 WSUS server to work at all.   I keep getting errors and cant connect at the server.   I can get to it from the Servername:8530 but when i load the MMC it will not connect.   No updates are coming through.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: administrator		</title>
		<link>https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/#comment-171</link>

		<dc:creator><![CDATA[administrator]]></dc:creator>
		<pubDate>Mon, 19 Dec 2016 13:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.dxsdata.com/?p=1319#comment-171</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/#comment-170&quot;&gt;HOSSEIN&lt;/a&gt;.

You could start with some basics, e.g. look for a certain Win2016 update on your WSUS server, then try to find it in your WSUS content directory, then check if is accessible via IIS / HTTP.
As far as I remember, I had to manually install KB3197954 to get any Win2016 updates, so double check if it is installed.
Also have a look at your WindowsUpdate.log on your clients (servers); Powershell -&gt; Get-WindowsUpdateLog]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/#comment-170">HOSSEIN</a>.</p>
<p>You could start with some basics, e.g. look for a certain Win2016 update on your WSUS server, then try to find it in your WSUS content directory, then check if is accessible via IIS / HTTP.<br />
As far as I remember, I had to manually install KB3197954 to get any Win2016 updates, so double check if it is installed.<br />
Also have a look at your WindowsUpdate.log on your clients (servers); Powershell -> Get-WindowsUpdateLog</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: HOSSEIN		</title>
		<link>https://www.dxsdata.com/2016/11/windows-server-2016-updates-issues-with-wsus-ad-dc-services-network-topology/#comment-170</link>

		<dc:creator><![CDATA[HOSSEIN]]></dc:creator>
		<pubDate>Mon, 19 Dec 2016 12:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.dxsdata.com/?p=1319#comment-170</guid>

					<description><![CDATA[Hi, 

I have a brand new installation of Windows Server 2016 WSUS server (Fully patched until 18-Dec-2016). My network consists of about 1000 client-side operating systems and 300 server-side. The clients range from Windows 7 to Windows 10 version 1607. The servers are from Windows Server 2008 to Windows Server 2016. Every computer can connect to WSUS and pull the updates except for Windows Server 2016.

Each time I check for updates on a Windows Server 2016, I get this error: &quot;We couldn&#039;t connect to the update service. We&#039;ll try again later, or you can check now. If it still doesn&#039;t work, make sure you&#039;re connected to the Internet.&quot; 

Event Viewer: Windows Update failed to check for updates with error 0x80072EFD. 

The strange thing is, WSUS server puts a green check mark for Windows Server 2016s, but I am sure there are some updates available for them.

I have installed all the Cumulative Updates (CUs) so far available for Windows Server 2016 on one of my 2016 installations manually, to see if that would solve the problem, but it didn’t. 

Are you aware of any issue in Windows Server 2016 Update Agent in regard to WSUS or I need some configuration changes on WSUS server to make the connection happen?

Yours.]]></description>
			<content:encoded><![CDATA[<p>Hi, </p>
<p>I have a brand new installation of Windows Server 2016 WSUS server (Fully patched until 18-Dec-2016). My network consists of about 1000 client-side operating systems and 300 server-side. The clients range from Windows 7 to Windows 10 version 1607. The servers are from Windows Server 2008 to Windows Server 2016. Every computer can connect to WSUS and pull the updates except for Windows Server 2016.</p>
<p>Each time I check for updates on a Windows Server 2016, I get this error: &#8220;We couldn&#8217;t connect to the update service. We&#8217;ll try again later, or you can check now. If it still doesn&#8217;t work, make sure you&#8217;re connected to the Internet.&#8221; </p>
<p>Event Viewer: Windows Update failed to check for updates with error 0x80072EFD. </p>
<p>The strange thing is, WSUS server puts a green check mark for Windows Server 2016s, but I am sure there are some updates available for them.</p>
<p>I have installed all the Cumulative Updates (CUs) so far available for Windows Server 2016 on one of my 2016 installations manually, to see if that would solve the problem, but it didn’t. </p>
<p>Are you aware of any issue in Windows Server 2016 Update Agent in regard to WSUS or I need some configuration changes on WSUS server to make the connection happen?</p>
<p>Yours.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
