Detailed SQL Server instructions for WSUS

Question

Hi, I'm having a devil of a time getting my WSUS server up and running.

I've rebuilt it several times from clean server install and I keep getting different problems. The latest problem is it was working for a few weeks, but suddenly the WID database has started throwing errors, stopping the WSUS server.

Can anyone provide me very kindly with step-by-step instructions on how to configure WSUS on SQL Server?

This would be much appreciated as I'm approaching the end of my tether.

Regards

Paul

PS. I'm running the WSUS and SQL services under hyper-V. The base operating system is Windows 2022 service. I've applied all updates and patches.

Answer 1

Hi @Paul Louis

In a WSUS implementation, at least one WSUS server in the network must connect to Microsoft Update to get available update information. You can determine, based on network security and configuration, how many other servers connect directly to Microsoft Update.

This guide provides conceptual information for planning and deploying Windows Server Update Service.

• Plan your WSUS deployment
• Step 1: Install the WSUS Server Role
• Step 2: Configure WSUS
• Step 3: Approve and Deploy Updates in WSUS
• Step 4: Configure Group Policy Settings for Automatic Updates

Best regards,

Cosmog Hong

---

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.

Answer 2

Follow my guides - part 1 will start you off - make it through the entire 8 part series to learn how to get WSUS working properly, managing it so that it only takes 5-15 minutes a month to approve and then re-approve updates to both your testing groups and then to the production groups.

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-1-choosing-your-server-os/

This is on WID - SQL is not needed. WID can handle 20,000 clients (if hardware/vm spec'd is appropriately.)

I recommend WID.