Avatar of budchawla
Flag for United Kingdom of Great Britain and Northern Ireland asked on

Installing WSUS on SBS 2003 Premium

Hi all,

Looking for a definitive answer & explanation on the best route to install WSUS on SBS 2003 Premium. Actually, this is a question copied almost verbatim from one of the newsgroups that didn't get a definitive answer IMHO.

1) Should I use the SQL2000 database as the WSUS database or should
I stick with WMSDE?  (Note that when I installed the Premium technologies I
upgraded all the databases - except SBSMONITORING - to use SQL2000)

2) If I do use SQL2000 then do I just install onto the default instance or
should I create another?  I'm not clear here on when or if you should create
another SQL instance and exactly how to do it so any advice appreciated.  I
do have another 3rd party application that will need to use SQL2000 later on
if that matters.

3) If I do use SQL2000 what do I need to before the WSUS install to "prepare
it" for the install?

4) My server is not OEM, so I don't expect to run into any strange install
problems like I've seen documented in the NG's & BLOG's with OEM SBS
servers.  Are there any other issues that I am not aware of?

And as for the choice of database, can someone please explain the reasoning behind their choice...

The Microsoft step-by-step talks about extracting the wsus files, running a command line command to create the wmsde database and then running WSUS setup. There is a reference in the newsgroup thread to an article to smallbizserver.net, but that content is no longer publicly available.

Feel free to answer just a part of this question!



Avatar of undefined
Last Comment

8/22/2022 - Mon
Murat Raymond

There is no issue Just you have to make sure that you have enough space on the partition you will store the updates.
The installation is smooth and I haven't seen much problem with this version. This version is much better than SUS (previous).

Take a look at this link it will help even that I believe that you have read some documentations before. Better safe than sorry.

Good luck!
Jeffrey Kane - TechSoEasy

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Hi Guys, thanks.

Jeff- I thought pretty much the same myself, can't see why I need to use anything other than WMSDE... but what's with the deployment guide talking about extracting, running wmsde setup separately etc? I have set up dozens of WSUS servers (albeit Server 2k3, not SBS), and since WMSDE installs happily & automatically, is this step necessary?

On SBS R2, I'll upgrade alright, but I'd rather get WSUS going than wait a few months and leave the workstations to do it individually and hogging bandwidth!


Jeffrey Kane - TechSoEasy

It's necessary because the installer does not issue the right configuration commands for the WMSDE setup, which for SBS is:

Sqlrun03.msi InstanceName=WSUS BlankSAPwd=1 Reboot=ReallySuppress DisableNetworkProtocols=1 DisableAgentStartup=1 DisableThrottle=1

You can only accomplish this if you install WMSDE first.

Regarding the hogging of bandwidth... I've seen WSUS installs on SBS's that will do that all by themselves... so there's no guarantee there.

Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes

Haha OK then... thanks for the tips!