Share via


WSUS installed on WID, while SCCM on SQL

Question

Sunday, February 3, 2019 5:25 PM

Hi,

in my testing lab:

When I installed WSUS role, I got successful connection with my SQL Enterprise (installed on same server), and completed the installation of WSUS, but faced issue in post-deployment was similar to this:

However, SCCM got installed well with SQL and now it is running.

I reinstalled WSUS using Windows Internal Database (WID), post-deployment worked well. 

my question, should WSUS and SCCM be installed on same database ?

or I can proceed with my setup.

also what might be the issue between WSUS and SQL Enterprise, are there prerequisites I need to consider?

regards,

All replies (3)

Sunday, February 3, 2019 6:20 PM

You should avoid installing WID and SQL on the same server. 

https://www.enhansoft.com/blog/avoid-installing-wid-and-sql-on-the-same-server

On top of that the SQL lic that you get with SCCM does NOT allow you to user SQL enterprise only SQL standard. 

Garth Jones

Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed


Tuesday, February 5, 2019 7:59 AM

Hi,

If you want or will ever want multiple SUPS then the only option is SQL since each SUP will share the same DB.  Otherwise the choice is yours.

Otherwise, WSUS maintenance step are different depending on whether you installed SUSDB on SQL Server or on Windows Internal Database (WID).

The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance

https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Tuesday, February 5, 2019 3:50 PM

> If you want or will ever want multiple SUPS then the only option is SQL since each SUP will share the same DB.  Otherwise the choice is yours.

This is not a correct statement. There is no reason that each SUP must share the same DB. It has benefits depending on the scenario, but is not required and can also be problematic depending on the scenario.

Jason | https://home.configmgrftw.com | @jasonsandys