Hello, I have a client who has been running a WSUS Server on a Windows 2003 Server Box.
Recently a good chunk have clients have been reporting errors. Want to figure out the best way to resolve this type of issue but also want to understand what the problem may be.
Please note, while we do recommend the use of HTTPS on WSUS servers, HTTPS and TLS 1.2 are not enabled by default.
If you are using WSUS 3.2 on Windows Server 2008 R2, you may perform either of the following steps to restore the scan functionality if you have deployed the Windows 8.1 Update KB2919355.
If update files are missing or have been corrupted, WSUS downloads the update files again.
If you do not,all Windows 8 machines will be listed incorrectly.
In my case, my Windows 8 x64 client was listed as Windows XP x64 If you have any clients that may have already been connected to the WSUS server prior to the update, you will need to update these clients as well.
Until that time, we are delaying the distribution of the Windows 8.1 Update KB 2919355 to WSUS servers.
You may still obtain the Windows 8.1 Update (KB 2919355) from the Windows Update Catalog or MSDN.
Note: Consider this post obsolete and replaced by https://blogs.technet.microsoft.com/mniehaus/2016/08/16/windows-10-delivery-optimization-and-wsus-take-2/, which offers more detail and clarity around the behavior of Delivery Optimization in both Windows 10 15.