Windows 10 Education Version 1067 - no updates?

[kennysarmy]

I've been doing testing with the LTSB version for a while but thought I'd start giving EDU a go!

 

I've imported the OS in to MDT and rolled this out to a test VM and joined it to the domain.

 

It's picked up the group policies, installed Sophos and is visible on WSUS.

 

But is it right that there are no updates?

 

WSUS reports it at 100% (see screenshot)

 

I presume I've done something in WSUS to prevent the updates from being seen by the client?

[kennysarmy]

Ah - I'd only ticked Windows 10 LTSB and not Windows 10 in the Products section of WSUS..

 

Doh!

[kennysarmy]

OK, so now the updates have been downloaded to my WSUS server and they've been approved for installation.

 

But the PC sticks at 0% downloading whether I try using the "check for updates" or if I run the task sequence on my MDT server (cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf")

 

 

Any ideas?

[Simcfc73]

I'm having this with Cumulative updates and have moaned about it on here a few times.. never sorted it. Some will eventually work, others will just hang.

 

I ended up restarting the update service and deploying them through pdq deploy. Be interested if you find the reason because M$ havent given me any as of yet.

 

I actually thought it was to do with me changing the UAC.

 

other updates work for me, just the CU stuff.

[kennysarmy]

I'm having this with Cumulative updates and have moaned about it on here a few times.. never sorted it. Some will eventually work, others will just hang.

 

I ended up restarting the update service and deploying them through pdq deploy. Be interested if you find the reason because M$ havent given me any as of yet.

 

I actually thought it was to do with me changing the UAC.

 

other updates work for me, just the CU stuff.

 

Is your test PC "online" with full internet access?

[Simcfc73]

Yep.. although they are deployed not testing. I just pick a random one that failed to work on and fix.

[kennysarmy]

Yep.. although they are deployed not testing. I just pick a random one that failed to work on and fix.

 

I'm going to test further tomorrow....

 

But I had some success putting our Proxy in to the browser immediately after deploying the base image and before checking for updates from WSUS.

[mavhc]

I had to set them to only download in ye olde fashioned way.

 

https://blogs.technet.microsoft.com/mniehaus/2016/08/16/windows-10-delivery-optimization-and-wsus-take-2/

 

https://support.microsoft.com/en-gb/kb/3088114

[SHimmer45]

updates i found when downloading them directly from windows update required the proxy to be set and the winhttp proxy to be set otherwise it says you have updates but then fails to download them. change the winhttp proxy value and it springs into life.

but for WSUS enabled clients i dont see this being as issue unless the client still insists on checking something with MS 1st

[kennysarmy]

So as a further test.

 

I've re-imaged the test PC with the base EDU iso and have joined it to the domain.

 

The PC has appeared on WSUS with the status - "Not Yet Reported"

 

I've ensured that the PC has a proxy set and has internet access, but for this test I will not set the winhttp proxy.

 

I just need to wait now for the PC to report in to WSUS, so it could be Monday before I'm able to "check for udpates" on the PC.

[mullet_man]

You've hit a known bug with Windows 10 WU and WSUS.

 

You need to follow step 4 from this link, and import the latest Cumulative update into your MDT.

 

http://deploymentresearch.com/Research/Post/540/Building-a-Windows-10-v1607-reference-image-using-MDT-2013-Update-2

 

That should fix the issue.