Thanks so much for these videos. I’ve just implemented our passive site server from your other videos. Will there be any issues moving the wsus db to a SQL cluster or AG, and then sharing it out to all sups? Thanks in advance. Cheers

First of all, thanks a lot for sharing knowledge by creating such wonderful content.

We are setting up new MECM Infra (CAS and two Primary Sites) to support around 175K endpoints across the US geo locations.
Based on the best practices recommended by MS we are thinking of setting up Shared WSUS DB for about 7-8 SUPs in our new architecture.

I have the following questions:

1) We are setting up a remote site system server for CAS SQL Site DB with 16 CPU cores and 96GB or Physical Memory. Do you recommend to use the same server for the Shared WSUS DB? If yes, do you think we might have to bump up either the CPU cores or RAM?

2) Do all SUPs need the internet connectivity for the catalog synchronization?

3) Will all WSUS servers share the Content location as well?

Thanks in Advance!
Regards

I would also be very interested in the shared SUSDB configuration in an untrusted forest.
I don’t see a way to add a SQL conneciton account during the installation of the WSUS feature. (prerequisite)
The same with the share, which must be accessible during the WSUS setup. There is also no option for a connection account.
Or did I miss something? Is there another installation method?
Thanks for the help!

Sorry for the delay, did you figure this one out?

I think just testing it would be that way to go. Ideally you would want a very good connection between the WSUS frontend and the SQL server. I know I’m a bit late, but what did you end up finding out here?

We’re looking at potentially switching to using one shared SQL database for our WSUS setup. Currently we have 1 SQL DB and 1 Upsteam WSUS server in Europe and 1 SQL DB and 1 Downstream WSUS server in Americas. This is integrated with SCCM of course.

Using iperf3 to test the connection speed between the downstream WSUS server and the European SQL server, it shows ~11.2 Mbits/sec. We have roughly 3500 clients (about 2200 in Europe/Asia which use the European servers and 1100 in Americas). Is this adequate or should I stick to separate DBs?

We just started to use PatchMyPC last year :-).

ConfigMgr will set this automatically for you. Ultimately it’s a shared DB that will look to MS updates.

In the SUP, I believe you can provide a SQL connection account.

just wondering how that works, as this is still about WSUS so far, not yet the SUP.
How can the 2nd WSUS connect to SQL in another domain without providing credentials?
Similar with the share, isn’t it?

Thanks,
John

For the database, I don’t think it will matter if one SUP is HTTPS and one is HTTP.

Yeah it is, you will need to use a connection account in the SUP site system.

again a great video!

Is it possible to share the WSUS database in an untrusted domain scenario?
Example: SUP 1 = Domain 1; SUP 2 = Domain 2 (DMZ)

Thanks!

I think it may be supported, but we have seen some issues with third-party updates (CAB) files sometimes deleting on DFS when multiple WSUS servers point to the same DFS share.

I’m really grateful for your video’s I have learned so much, however I have a question about the shared content folder.

Is locating the Shared content folder supported on a DFS share supported?

In a failure scenario it would be good not to need to recover the content folder as well as the SUSDB.

Thanks