WSUS and Windows 10 1607 EDU

[Drayton95]

Hi all,

 

I've been searching hi and low for a olution to this issue but havent found anything solid as of yet.

 

Basically my issue is that my Windows 10 clients will not download any updates from our new WSUS server.

They can find the updates on the server but when actually starting the download they sit at 0% and will not proceeed from there.

This is causing the machines to lock up on the "Getting Windows Ready" screen ob boot, and takes about 10 minutes for it to time out and actually load into Windows.

 

So far I have tried adding the MIMe type for .esd "application/octet-stream", but that has not worked.

I have tried changing the delivery optimization to Bypass, but that has made no difference.

I have even tried the built in trouble shooter for Windows Update, but that reports that there are no issues.

 

Has anyone had this before and if so, how on earth did you fix it?

I'd rather not have to download all the updates manually and walk around to 100+ computers to install them.

 

Open to any suggestions

 

Thanks,

Drayton95

[3s-gtech]

Do you have things like proxy exceptions in place for your WSUS server address?

[Drayton95]

I have the clients set up to connect via host-name, and the proxy settings have been configured to bypass the proxy on local addresses, is this the correct way of doing it?

They seem to be contacting the server, as they can see which updates they need, but then fail on downloading by sitting at 0%

And the they report to the server, and come up in the computers section of WSUS

 

[LytchettNM]

Have you setup and configured BITS as I believe this is the transport that used for update across the LAN and without any config it restricts bandwidth massively by default.

[Drayton95]

I have looked at the BITS group policy settings, and it seems to be restricting it too 500KB/s so the network traffic doesn't grind to a halt, I have tried only approving a single security update for the clients, but that won't even start to download, and that's only a couple meg

[mullet_man]

Drayton95 there is a known issue with 1607 and WSUS. What version are you of 1607?

 

What are you using for deployment? You need to inject the latest cumulative patch into your deployment image.

[free780]

Its best to use the Windows 10 1607 updates Nov 2016 iso when capturing your image. This is the CBB one.

[abaxter2]

This is a known issue with version 1607, myself and others like mullet_man had fun and games when version 1607 first came out. You can read my post here: http://www.edugeek.net/forums/windows-10/173835-windows-10-1607-wsus.html

 

The answer is to use the Nov 2016 version of 1607 for your base image as this includes the updates to get Windows 10 1607 working with WSUS.

[abaxter2]

This is a known issue with version 1607, myself and others like mullet_man had fun and games when version 1607 first came out. You can read my post here: http://www.edugeek.net/forums/windows-10/173835-windows-10-1607-wsus.html

 

The answer is to use the Nov 2016 version of 1607 for your base image as this includes the updates to get Windows 10 1607 working with WSUS.

[mullet_man]

Although to be honest it might be worth waiting for the creators update now if it means building a new image.

 

I was thinking about rebuilding a new image due to my modern apps/start menu issue but with 1703 I think it's going to be named coming out early next month I was going to rebuild then.

[mullet_man]

Although to be honest it might be worth waiting for the creators update now if it means building a new image.

 

I was thinking about rebuilding a new image due to my modern apps/start menu issue but with 1703 I think it's going to be named coming out early next month I was going to rebuild then.

[free780]

You have to bear in mind at some point MS will stop updating 1511. Probably in the autumn, Whenever 1703 goes CBB.

[free780]

You have to bear in mind at some point MS will stop updating 1511. Probably in the autumn, Whenever 1703 goes CBB.

[Drayton95]

You have to bear in mind at some point MS will stop updating 1511. Probably in the autumn, Whenever 1703 goes CBB.

I think I will end up just waiting for the new one then and create a new image from that.

Now that this has happened once hopefully they don't screw it up again.

 

 

 

What are you using for deployment? You need to inject the latest cumulative patch into your deployment image.

 

I am currently just using generalised sysprep'd images via WDS, not sure on how to get other solutions like system centre working because I simply don't have the time at the moment.

 

Does anyone know if there is an easy way to deploy the latest cumulative update via a GPO or script? Although I am going to create a new image, I would still like to get the current one working, if possible.

[ITGURU]

Make sure you download and use the latest November ISO release from volume licensing site

Whist I had no issues with the original release, reports say this was an issue and a new update was released.