SCCM and WSUS port issue

[Gideon_Kay]

Hi All

 

A stab in the dark here. I have about 5% of machines that are trying to query WSUS on port 8350 instead of 8351 when trying to deploy updates using sccm. There is no group policy in place and I have deleted the local gp. Whenever SCCM recreates the local GP it still reverts to 8350. These are totally random machine in various org units and other machines in the same org's are fine. I removed the sccm client, reinstalled , queried GP and cannot for the life of me find the issue.

 

Any ideas?

 

Thanks

 

GK

[DavR]

Forgive me if I've missed something, but couldn't you just put a group policy in place specifying the correct server name and port?

[glen_j]

8530 is the non ssl connection port 8531 is ssl. They are both specified under software update point settings in SCCM. The SCCM agent windows update client settings as far as i am aware. Have you forced it to connect on ssl only?

[Gideon_Kay]

Hi

 

My reason for not doing this is that everyone seems to insist on avoiding using GP's for this precise settings and let SCCM manage it. I guess I want to find the root cause before overriding it. I need to use HTTPS to allow for 3rd party updates.

 

Thanks

 

Gideon

[DavR]

Fair point I suppose. No point getting GP to manage it if something in the SCCM client is then going to argue with it.