This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 1%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Hi,
I know this question has been asked before, but none of the answers has resolved my issue. We have a Server 2016 with the WSUS role installed. It has been working fine as our WSUS server for years. I was recently tasked with configuring our SCCM (Ver: 2111, Site Version: 5.0.9068.1052.1000) for third party updates. We did not use SCCM for updates, so I installed the SUP role on the WSUS server. I finally got it to connect and get update list from WSUS. Now, the WSUS server keeps changing it's source from "Microsoft Update" to itself. No group policy has been added/changed. I've looked at both the SCCM server and WSUS server and there is no Local Policy being applied to either. SCCM SUP settings say to use Microsoft Update. Any help would be appreciated.
Thanks,
Ron Soulliard
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 24%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
Now, the WSUS server keeps changing it's source from "Microsoft Update" to itself.
In order to help me research further, please provide a screenshot for reference.
In addition, please try to run the WSUS Server Configuration Wizard on the WSUS console and check whether it is helpful.
Best regards,
Rita
Hi,
What do you need a screenshot of? I reran the Configuration Wizard on the WSUS server and it didn't solve the problem.
Thanks
Ron
Hello Ron,
What is the meaning of
Now, the WSUS server keeps changing it's source from "Microsoft Update" to itself.
Just one more question. Where did you want your devices get updates from? WSUS Server or MECM site server.
Please refer to the below screenshot to change the sync settings as your like on the MECM console:
Regards,
Rita
HI,
The setting is correct in SCCM.
This is the same setting on the WSUS server:
I correct it on the WSUS server and everything works. Less than 60 minutes later, it is changed back to point to itself.
Hello Ronald Soulliard,
Thanks for your response.
According to the screenshot above, you want the SUP sync the updates from Microsoft Update. So The MECM Server has nothing to do with the standalone WSUS Server. Change the Update Source from itself to Microsoft.
Then we should sync updates manually on the WSUS console.
Best regards,
Rita
HI,
I'm not sure why, but it seems since our last maintenance on 4/15/2022, when we installed the latest updates and rebooted the server, it stopped changing the sync source. I think it is resolved and this thread can be closed.
Thanks
Ron
That is what I am doing now. Before I configured it as the SUP, the WSUS server settings didn't change for years. It would automatically sync with microsoft everyday and get the updates. Now, it fails unless I manually go in and change the setting and kick off the sync. This isn't acceptable. I need it to work the way it has in the past. We are looking at possible moving the patch management to SCCM since we need to do more third-party application, but we can't if the sync continues to fail. Changing the setting every time and manually syncing is not the solution.
Hello Ron Soulliard,
Thanks for your response.
Please help to confirm whether the MECM Server and the WSUS server have the same database. We could check the WSUS Server is database as the following screenshot:
Please help to confirm whether the Remote SUP have the same SUSDB with the MECM.
In addition, I found a Official Document for your reference:
https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/configuring-multiple-software-update-points-in-a-configmgr-2012/ba-p/322922
In a shared scenario the SUSDB will be updated by the master SUP – in this case SUP a (or the first one you install). Since SUP b shares SUSDB there is no need for the update to again be synchronized into SUSDB because it is already there. In the scenario where each SUP maintains it’s own SUSDB there would be a requirement to synchronize the update to each.
Also we could review the WSUSCtrl.log to get more error information.
Best regards,
Rita
@Ronald Soulliard
It seems that there are no updates for a long time. May I know the status of the case? Please help to confirm whether the remote SUP and the MECM server have the same SUSDB database or not if the issue haven't been resolved right now. I tested in my lab and it seems that the issue occurred on the Servers who have the same SUSDB.
Thanks for your understanding and cooperation. Don't forget to share the solutions if the issue has been resolved.
Have a great day.
Best regards,
Rita
Hello Ron,
Thanks very much for your feedback. We're glad that the question is solved now. Here's a short summary for the problem , this will help other users to search for useful information more quickly.
Problem/Symptom:
WSUS server changing sync source to itself automatically
Possible Solution/Workaround:
Install the latest updates and rebooted the server
Best regards,
Rita
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.