WSUS with 1607 and 2008 R2

[Sheridan]

In one of our primaries we've added a load of W10 PCs, which are on a Server 2008 R2 domain. Now I know WSUS 3.0 supports W10 (despite the Vista tags!) but oddly none of the W10 machines are even appearing in the WSUS console.

 

Checking the registry of each PC shows the correct settings and browsing the url http://server/selfupdate/iuident.cab results in a sucessfull download so I'm a bit puzzled as to where this is going wrong.

 

In the past the problems I've had with WSUS and W10 are that they appear in the console but never update their status, this is the first time they haven't appeared at all!

 

Is this another update=broken aspect to W10 I've not yet seen?

[vimagoes]

Mine is working fine. Try to resynchronize and check "products and classifications"

[Sheridan]

Its synching OK and the W7 PCs are checking in - just the W10 ones don't appear at all! I've got Windows 10 selected in the Product as well.

[vimagoes]

Try running "wuauclt.exe /reportnow" on your W10, wait a few minutes and check "Unassigned Computers"

 

I am assuming you got your policy right because your W7 are taking updates from your WSUS server, so if this doesn't work try checking if the computer is in the right OU and the GPO is applying right to it. Try with a RSOP in your W10 and check if this policy is a winning one

Edited May 8, 2017 by vimagoes

[Arthur]

Is this another update=broken aspect to W10 I've not yet seen?

2008 R2 is ancient! I think you're going to need to update your server...

 

https://twitter.com/jarwidmark/status/663757874804498432

 

Edited May 8, 2017 by Arthur

[vimagoes]

2008 R2 is ancient! I think you're going to need to update your server...

 

 

 

Well it's working for me. The sole issue I have is that the OS identified is "Windows Vista Enterprise Edition" instead of "Windows 10" and for that there will be no update/hotfix for Windows Server 2008 R2 but apart from that mine is working fine

 

See MORE INFORMATION https://support.microsoft.com/en-us/help/3095113/update-to-enable-wsus-support-for-windows-10-feature-upgrades#%2Fen-us%2Fkb%2F3095113

[Sheridan]

Yup, 2008 is ancient but a primary school doesn't have the budget or demand to upgrade to 2012 or higher!

[sted]

Yup, 2008 is ancient but a primary school doesn't have the budget or demand to upgrade to 2012 or higher!

i can also see people using an old server just for wsus keeps non critical data off new hardware and in a place that really dosent need backing up etc

[Sheridan]

Checking the registry shows that they are picking up the policy and pointing towards the correct server. I'm going to rebuild wsus on the server to start from scratch and see what reports in.

[mullet_man]

Is it Windows 10 v1607? There is a known bug with WSUS and the shipped version of 1607. you'll need to make sure you install the latest patches and it then works fine.

 

WSUS 3.0 does work with Windows 10 that's what am currently on (moving to 2016 in the summer) it will patch it but give you the full service updates e.g 1607 to 1703

 

Am guessing this is your issue, if you search back through here you'll find me and a few others tearing our hair out when 1607 was first released.

Edited May 8, 2017 by mullet_man

[mullet_man]

Sorry you mentioned it is 1607, am fairly certain this is your issue. You'll know this is the problem if you check for updates on the client and see it get stuck at searching for updates or downloading updates but never installing them and then lose the updates and have to download them again.

[Sheridan]

When you mention lastest updates on 1607, we have tried installing the April 2017 update rollup, but thats had no effect. I've rebuild WSUS on the server completely and only the W7 PCs are reappearing!

 

W10 is a real pleasure to deploy isn't it.

[Arthur]

When you mention latest updates on 1607, we have tried installing the April 2017 update rollup

Any luck with 1703 (the Creators Update)?

[Sheridan]

Oh god I don't even want to think about 1703! Every update fixes 10 things and breaks 25 new things!

[Geoff]

Win10 1703 is not working on some of my 2k8 r2 WSUS servers and it is working on others. According to Microsoft this config is 'unsupported'.

 

New 2016 server in the works :E

[Sheridan]

Thats the problem, a lot of our primaries can't afford to upgrade their servers just to cope with a few new W10 machines - not in the same year anyway.

 

Downgrade to W7 looks like a viable option. The MS way seems to be update everything all together now.

[vimagoes]

I haven't upgrade to W10 yet and I have no plan to do it soon, I have just one W10 as a testing machine, no rush to move to Server 2016 and W10, as you said in Primary schools money is an issue so we have to extend everything's life cycle.

 

BTW my W10 1607 works flawlessly in my environment.

[Geoff]

We'll you've got until 2020 to upgrade so it's not too bad.

[mullet_man]

Have you got the latest WSUS patches installed? Am remembering having to install a patch at some point.

 

Just checked now My WSUS version is 3.2.7600.226.

 

And my pc which is 1703 is showing in the console and reported back a few hours ago.

[Sheridan]

Have you got the latest WSUS patches installed? Am remembering having to install a patch at some point.

 

Just checked now My WSUS version is 3.2.7600.226.

 

And my pc which is 1703 is showing in the console and reported back a few hours ago.

 

Thats exactly the same version their WSUS is showing, all the W10 that aren't appearing are 1607.

 

Oddly, we have another primary running 1511 and WSUS 3.0 on Server 2008 R2 and thats working fine!

[mullet_man]

Have you double checked their is no wmi filters on the GPOs?

 

Have you ran a gpresult on one of the clients and see if it's deffo picking up the WSUS settings?

 

Can you ping the WSUS?

[Sheridan]

Have you double checked their is no wmi filters on the GPOs?

 

Have you ran a gpresult on one of the clients and see if it's deffo picking up the WSUS settings?

 

Can you ping the WSUS?

 

Yes to all, and I've even rebuilt the WSUS to move it from its original port (8530) to the default Port 80 and the W10 can see the iuident.cab file on the server!

[Geoff]

It's because of this:

 

https://blogs.technet.microsoft.com/wsus/2016/01/22/for-those-on-wsus-3-0-sp2-or-sbs-2011/

 

You can't do anything but upgrade.

[vimagoes]

just for ticking off; Have you check UAC and or Firewall on your W10 client?

 

- - - Updated - - -

 

just for ticking off; Have you check Firewall on your W10 client?

[Sheridan]

This is odd, looking at the log in Windows\SoftwareDistribution on one of the W10 PCs that isn't showing in WSUS and the end shows:

 

{01309C18-EA37-4F0E-AEB5-54004F5FD2B5} 2017-05-10 14:06:39:952+0100 1 181 [AGENT_INSTALLING_STARTED] 101 {C51E9B44-D599-4007-BAA5-0D5011C1E6DF} 1 0 Update;taskhostw Success Content Install Installation Started: Windows has started installing the following update: Microsoft .Net Native Framework Package 1.6

{48E0F841-ADC2-4DFA-9B0D-6FF83D29F02D} 2017-05-10 14:06:40:374+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {C51E9B44-D599-4007-BAA5-0D5011C1E6DF} 1 0 Update;taskhostw Success Content Install Installation Successful: Windows successfully installed the following update: Microsoft .Net Native Framework Package 1.6

{2578A138-D3C6-4E73-B7F1-3BF8B891FA84} 2017-05-10 14:06:40:415+0100 1 181 [AGENT_INSTALLING_STARTED] 101 {742DB728-811B-4F07-BCF2-0AD2B5CD9312} 1 0 Update;taskhostw Success Content Install Installation Started: Windows has started installing the following update: Microsoft .Net Native Runtime Package 1.6

{2F0D574D-4EAE-4CAD-8E57-848B0781C4EF} 2017-05-10 14:06:40:785+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {742DB728-811B-4F07-BCF2-0AD2B5CD9312} 1 0 Update;taskhostw Success Content Install Installation Successful: Windows successfully installed the following update: Microsoft .Net Native Runtime Package 1.6

{9F794BF7-08F1-4D05-86E1-235DA977D1C9} 2017-05-10 14:06:40:815+0100 1 181 [AGENT_INSTALLING_STARTED] 101 {CF0E1B33-B56C-44DF-BC4F-046683959381} 1 0 Update;taskhostw Success Content Install Installation Started: Windows has started installing the following update: Windows Camera

{1FCD6E3C-3720-4F5F-9E33-3F8733802919} 2017-05-10 14:06:41:494+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {CF0E1B33-B56C-44DF-BC4F-046683959381} 1 0 Update;taskhostw Success Content Install Installation Successful: Windows successfully installed the following update: Windows Camera

 

So its getting updates from somewhere!