SCCM and WSUS not talking to each other.

[McChikenhanger]

Oh masters of WSUS. I beseech you all for thy help in the arcane arts of WSUS. We have a server that uses SCCM and WSUS for updates. Now SCCM can’t get to the updates components because WSUS is not running properly. If I use the WSUS console to log onto it I get the following error.

 

 

I’ve double checked the ports and it is indeed supposed to be running from port 8530 and 8531. I checked on line and people have said not to install KB31448812, which it doesn’t have. It’s got the fix update instead which is KB3159706. Also I've checked under roles and the WSUS database is not ticket within the role. So I'm wondering if its using the SCCM database instead of a WSUS database?

 

Any help on this will be greatly appreciated.

[Oaktech]

Is there anything more informative in the role log on server manager, or in the component status of SCCM?

[Steve21]

What happens if you try it on 8350 without SSL? By default it's not enabled as required, unless you changed it.

 

What happens if you open CMD (on the server) browser to C:\Program Files\Update Services\Tools

 

And run wsusutil.exe checkhealth and look under event logs in application

 

Steve

[McChikenhanger]

Hi Steve31. I get the same result if I try to connect to port 8530, but I have fixed the issue since then.

 

It was mainly one WSUS Update that was causing issues. It provides support for Windows 10 within WSUS, but there were a few commands that had to be run from CMD to make it see the Update Repository on the server once again, and a few changes within IIS so that it operates properly on SSL.

 

And then the last one which is making sure that the WSUS Pool is running within IIS.

 

Thank you for your help though