New WSUS Server. Not quite working :(

[kennysarmy]

New WSUS server created last week.

 

I've now got all our Servers checked in and at 100% - great.

 

However my Windows 10 clients are struggling for some reason - I've only had about 40 check in with the new server :/

 

 

Clients appear to pick up the edited WSUS policy and the server name is in the registry OK.

 

 

But when they attempt to check for updates they give this error:

 

 

 

Wondered the best way to troubleshoot this?

[Steve21]

I don’t know if it’s still broke in the latest wsus servers (haven’t used it in a long time with sccm) but that used to be when you had to increase the iis pool memory on the server

 

Steve

[kennysarmy]

Tried this: - shot in the dark...

 

If this client comes from an OS image and Sysprep wasn’t run then the issue may be that multiple clients are using the same SUSClientID key.

Check HKLM\Software\Microsoft\Windows\CurrentVersion\WIndowsUpdate and delete the current SUSClientID.

Run wuauclt /resetauthorization /detectnow from an elevated command prompt.

 

No change

[mavhc]

WSUS is very dead, https://docs.microsoft.com/en-gb/archive/blogs/wsus/

[3s-gtech]

Is your new server in your proxy exceptions? I've had fun with that in the past.

[kennysarmy]

On the client I can use a browser to navigate to : http://fp8:8530/

 

There is no error so I presume it connects OK.

 

If I try and false server eg: http://xxx:8530/ then it does fail.

[Jcx500]

We had issues with clients not being picked up, Sadly the the only fix for us was to setup a fresh wsus server. We've kept ours on 2016 for now as its been stable atm

[Steve21]

WSUS is very dead, https://docs.microsoft.com/en-gb/archive/blogs/wsus/

 

You know if you spent more time actually reading the stuff you post and trying to help others rather than trying to be smart you'd realise that is the archive link for blogs that hasn't been updated in years, not active posts...

 

Steve

[3s-gtech]

As Steve21 mentioned - the IIS pool stopping can cause some very irritating issues. You tend to see that in the MMC also, but sometimes it just stops serving updates out.

[kennysarmy]

Is your new server in your proxy exceptions? I've had fun with that in the past.

 

Hi,

 

not explicitly...

 

But : 10.*;*.local

 

is in there.

 

 

However your message prompted me to check the winhttp settings!

 

[kennysarmy]

Test PC has now checked in

 

Hopefully there is a way to set winhttp proxy via group policy!

[FragglePete]

I had this. Even rebuilt the server (it was due), but still the problem persisted even on a new build. Increasing the IIS Pool Memory resolved it and now appears to be behaving itself.

 

This link with Stone Computers proved helpful:

 

https://kb.stonegroup.co.uk/index.php?View=entry&EntryID=620

 

Pete

[mavhc]

You know if you spent more time actually reading the stuff you post and trying to help others rather than trying to be smart you'd realise that is the archive link for blogs that hasn't been updated in years, not active posts...

 

Steve

 

Interesting, where are the active posts?

[3s-gtech]

Test PC has now checked in

 

Hopefully there is a way to set winhttp proxy via group policy!

Startup script?

[Jcx500]

Startup script?

We was doing that, winhttp proxy is now embedded in our image via hostname incase we every change proxy or ip ranges

[kennysarmy]

https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/use-group-policy-apply-winhttp-proxy-settings

 

Followed the instructions here.

 

Already up to almost 400 clients talking back