Great video. This video shows modification from existing SUPs in SCCM environment. what if I want to create new WSUS/SUP and shared database. What all things I need to keep in mind before proceeding.
Hey Justin, solid work as usual! Quick question for you... I'm setting up IBCM at a site (They're not ready for CMG yet :( ) and setting up the SUP role on the IBCM server, but want to configure it to share their existing WSUS SQL database on the primary site server which is running on Windows Server 2012. However, the IBCM server in the DMZ is running Windows Server 2016. Will there be an issue if I install the WSUS role on the IBCM server running Windows Server 2016? Thanks in advance for the assist!
This is really very nice video. One question, We have setup one more SUP on our standalone primary site with shared wsus database. But now everytime the update souce in wsus options getting changed to the server itself. We need to manually change the update source to Microsoft update in wsus.
Hi, Couple of Queries: 1. Is there any difference between schedule sync and manual sync and 2. Will a schedule sync triggers a Full sync or Delta sync? And once again, thanks a lot for sharing your experience with us...
1. Not usually, some scheduled syncs will trigger a full-sync but not always. I believe there's some built-in criteria where it will periodically. 2. See above, you can always perform a full sync by dropping in a full.syn in the wsyncmgr.box
This is a great video. I have a question though, only because of dealing with this recently. I was having an issue with the WSUS Cleanup Wizard not able to start when attempted to clean unneeded update files. I banged my head against the wall for a couple days before I called Microsoft. After we looked through everything, their takeaway was that since my WSUS was connecting to a network location for the WSUS content folder, that was why I was having the problem. They told me that the WSUS Cleanup Wizard is not designed to work with the content folder on a network share of any kind, it should be local. So, giving it the benefit of the doubt, I made the change to where we store that content. As soon as I put that folder local to the WSUS server, and it synchronized, the cleanup started and worked. Have you tested to see if WSUS Cleanup Wizard works to clean up unneeded update files with this configuration? I run a non-MS script for WSUS maintenance, but it still calls the Cleanup Wizard.
@@PatchMyPC I wish. I went over all of them. It's not a terribly complex environment. They out and out told me that was the case though. That it was by design, that's why I ask. By "they" I mean Microsoft, sorry to be ambiguous.
We are planning to create one more SUP role, the server is 2019 OS and primary SUP is on 2012 R2 OS. We need to use the primary SUP as upstream server to new one and share the Same database. Should both server have same OS version. If not what would be the next step
@@PatchMyPC The Primary WSUS was being configured to synchronise from itself as an upstream server. A WSUS under a Secondary does not get discovered by the Primary as a grouped WSUS install. The Secondary configures the WSUS which in-turn sets the Upstream server to the Primary but as the DB is shared it configures all WSUS to speak to 1 internal server and never MS.
@@DaveDoes-Stuff Maybe a good idea for UserVoice configurationmanager.uservoice.com/forums/300492-ideas. I don't see any technical reason this shouldn't work.
Really appreciate the effort which you have put in for the community. Really liking the entire series.
Thanks for watching!
Great video. This video shows modification from existing SUPs in SCCM environment. what if I want to create new WSUS/SUP and shared database. What all things I need to keep in mind before proceeding.
Would basically just install WSUS with shared content and Database then add the SUP role.
Hey Justin, solid work as usual! Quick question for you... I'm setting up IBCM at a site (They're not ready for CMG yet :( ) and setting up the SUP role on the IBCM server, but want to configure it to share their existing WSUS SQL database on the primary site server which is running on Windows Server 2012. However, the IBCM server in the DMZ is running Windows Server 2016. Will there be an issue if I install the WSUS role on the IBCM server running Windows Server 2016? Thanks in advance for the assist!
You will need to be running the same version of WSUS to share the WSUSDB in a supported way.
Thanks Justin!
This is really very nice video. One question, We have setup one more SUP on our standalone primary site with shared wsus database. But now everytime the update souce in wsus options getting changed to the server itself. We need to manually change the update source to Microsoft update in wsus.
The source should be set in SCCM not WSUS
Hi,
Couple of Queries:
1. Is there any difference between schedule sync and manual sync and
2. Will a schedule sync triggers a Full sync or Delta sync?
And once again, thanks a lot for sharing your experience with us...
1. Not usually, some scheduled syncs will trigger a full-sync but not always. I believe there's some built-in criteria where it will periodically.
2. See above, you can always perform a full sync by dropping in a full.syn in the wsyncmgr.box
Thank you..
This is a great video. I have a question though, only because of dealing with this recently.
I was having an issue with the WSUS Cleanup Wizard not able to start when attempted to clean unneeded update files. I banged my head against the wall for a couple days before I called Microsoft. After we looked through everything, their takeaway was that since my WSUS was connecting to a network location for the WSUS content folder, that was why I was having the problem. They told me that the WSUS Cleanup Wizard is not designed to work with the content folder on a network share of any kind, it should be local. So, giving it the benefit of the doubt, I made the change to where we store that content. As soon as I put that folder local to the WSUS server, and it synchronized, the cleanup started and worked. Have you tested to see if WSUS Cleanup Wizard works to clean up unneeded update files with this configuration? I run a non-MS script for WSUS maintenance, but it still calls the Cleanup Wizard.
Probably issues with the computer account permissions.
@@PatchMyPC I wish. I went over all of them. It's not a terribly complex environment. They out and out told me that was the case though. That it was by design, that's why I ask. By "they" I mean Microsoft, sorry to be ambiguous.
Do we need to set SUP2 as downstream server if using Shared SUSDB and Content? Thanks for sharing!
Hey Kevin,
Is your question do you need a second SUP if you are using the same UNC and DB at the Primary SUP?
@@PatchMyPC Yup! I was able to set up second SUP using same UNC and DB. There is no DownStream in shared SUSDB..duh! LOL. Thanks for the video!
If you wanted to use SSL is there anything that would need to be done differently? Do you need to set up SSL before or after, would it matter?
Check out my PKI guide tgat covers SSL for wsus
We are planning to create one more SUP role, the server is 2019 OS and primary SUP is on 2012 R2 OS. We need to use the primary SUP as upstream server to new one and share the Same database. Should both server have same OS version. If not what would be the next step
You wouldn't want to share the WSUS DB if the host services not on the same Server version.
@@PatchMyPC thank you Sir
Might be worth noting that this cannot, and should not be done, on a Secondary Site SUP/WSUS - this will cause configuration issues
What issues has it caused you?
@@PatchMyPC The Primary WSUS was being configured to synchronise from itself as an upstream server. A WSUS under a Secondary does not get discovered by the Primary as a grouped WSUS install. The Secondary configures the WSUS which in-turn sets the Upstream server to the Primary but as the DB is shared it configures all WSUS to speak to 1 internal server and never MS.
@@DaveDoes-Stuff Maybe a good idea for UserVoice configurationmanager.uservoice.com/forums/300492-ideas. I don't see any technical reason this shouldn't work.