SOLVED SCCM WSUS changing to itself as upstream

[Insaniq]

I have a setup with SCCM server (all major roles) and a WSUS server having WSUS and SUP roles, SQL on a separate server.
In SCCM the Microsoft update is set the update source and it stays as that.

But WSUS keeps changing that each time a Software update sync is initialized.

I have tried to uninstalling the SUP role and WSUS role(delete DB, delete IIS, Delete WID folder etc) and installing it again where I followed you guide and ran "Launch Post-Installation tasks." on WSUS server before closing it. (this seems to create the DB and setup IIS

In other guides I saw that it is recommended NOT to run the "Launch Post-Installation tasks."

Two questions - what is the correct way of installing the WSUS

And what can i do to ensure that the WSUS doesn't end up switching to pointing to itself

 

[WBH]

Hello,
I'm facing the same issue, would you help us Prajwal?

 

[khaldeman]

Did anyone ever figure this one out? Everything was working fine and now I can't figure out why WSUS reports that its upstream server is itself. I've verified that the software update point component properties is set to "Synchronize from Microsoft Update".
I can manually change WSUS to point to Microsoft, sync and I get updates. The next day I come back and it is set to itself again. Update Point Component Properties still set to sync from MS in the SCCM console.

Where is it getting this setting from?

 

[khaldeman]

This seems like a bug on the primary site server. So, a week ago, I found that somehow the software update point component properties pointed to my WSUS server. I changed the config to point to Microsoft Updates.
Administration->Site Configuration->Sites->My Site->Configure Site Components->Software Update Point

However, the primary site server was still pushing the old value to my WSUS server.

WCM.log:
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 5/3/2024 5:56:44 AM 7800 (0x1E78)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to updates.ad.domain.org SMS_WSUS_CONFIGURATION_MANAGER 5/3/2024 5:56:44 AM 7800 (0x1E78)
Based on the recommendation found here:

SCCM WSUS changing to itself as upstream - Microsoft Q&A

I have a setup with SCCM server and a WSUS server having WSUS and SUP roles, SQL on a separate server. In SCCM the Microsoft update is set the update source and it stays as that. But WSUS keeps changing the source to itself. For tests I changed source…

learn.microsoft.com

I rebooted the primary site server, and while it was booting, changed the WSUS config manually to Microsoft, and now it seems to be updating WSUS as it should.

WCM.log now:
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 5/3/2024 9:28:52 AM 7912 (0x1EE8)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 5/3/2024 9:28:52 AM 7912 (0x1EE8)

I'm sure there was a service I probably could have just restarted, but the reboot worked for me.

Hope this helps someone else in the future.