Hi all!
We have a strange Problem.
We are running a WSUS Server on Server 2012 (not R2), patched it with everything neccessary to deliver Windows 10 Upgrades and it worked until a few days ago(time 1607 was released?). We were able to update about 150 of our 200 Windows 10 Build 10240 boxes of our customers to 1511 before, but now, no 10240 machine get´s the 1511 (May Edition) offered by WSUS.
Then i started searhing and came across KB3159706.
First I thought, that it can´t be because it describes 1607 Upgrade and future ones and other packages using ESD. But I gave it a try and followed the Instructions. It worked perfectly as described, but does not resolve the Issue, that 1511 will not be offerred any more.
Now I tried to install a new 2016TP5 based WSUS, to ensure it is not a issue with 2012 WSUS 3.0 SP2 (and Patches), but 2016TP5 WSUS does the same Thing. Then i stumbled over a comment, that 2016 Server WSUS will have KB3159706 Features when it goes RTM, so there is the possibility, that it does not have KB3159706 yet in TP5.
Here our configuration:
* WSUS 3.0 SP2, all Patches on 2012 Server (in Azure)
* Configured to not deliver packages directly, Clients have to download themfrom Microsoft (this could be important, because ESD Packages will only be downloaded by CLients not by the WSUS - So what could KB3159706 do on the Server without the ESDs to look in?
What I found interesting so far:
* WSUS marks the previously already working 1511 Upgrade Updates now as "Not Applicable" to the 10240 Clients - thats strange
* When I Change Test Clients Windows Update Agent to Microsoft Windows Update directly, the 1511 is ovvered instantly, so there is no issue withe the Clients!
* The WSUS Update ID of the correct 1511 Upgrade Update is other than this offered by Windows Update
WSUS knows the March Version with ID:d08ff53d-ce46-4ad1-8abe-538fd192e38f
WSUS knows the May Version we approved, but is not offered anymore with ID: 1105b447-525e-4192-ba5e-437cbd6c01aa
Windows Update offers a new (!) Update ID: Upgrade auf Windows 10 Pro, Version 1511, 10586 | 468e4ed0-ee60-4827-9e45-370e77dec143
So, what is going on here? Is it all because of a bug or because we are only Control our Clients with the WSUS, but they have to download directly? Does it have anything to do with 1607 release or KB3159706?
Help please - I invested days already to hunt this down...
Thanks a lot
Thomas