Thursday, 6 September 2007

SBS - Installing Windows SharePoint Services 3 on SBS

Some How To articles:
To quote from the Official SBS Blog on the proper order of things:
How to install SharePoint 3.0 and then WSUS 3.0.
  1. Install SBS R2 including WSUS 2.0.
  2. Install WSS 3.0 using the side by side installation steps in the white paper. Complete all steps.
  3. Upgrade to WSUS 3.0.
If you install WSS 3.0 after WSUS 3.0, the SharePoint setup will complete, but the SharePoint Products and Technologies Configuration Wizard that runs after setup will fail to create a configuration database and WSS 3.0 will not be functional.
To obtain the above mentioned KB 934790 hotfix if WSS 3.0 was installed after WSUS 3.0, one is required to call Product Support Services.

This post is further to step 13 (reordered), install WSS 3.0 in side-by-side mode, in the previous blog post: SBS 2K3 R2 - Setup steps and resources.

UPDATE: Missed an important link!

Installing Windows SharePoint Services 3.0 on a Server Running Windows Small Business Server 2003 (Link to download SBSWSSv3.doc).

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

2 comments:

Tim Barrett said...

I started doing WSS v3 on SBS installs w/ the intructions Chad Gross came up with:
http://msmvps.com/blogs/cgross/archive/2007/01/25/companyweb-sharepoint-v3-part-1.aspx

I've not been brave enough to try swapping out the COMPANYWEB site, but maybe I'll give it a spin in a VPC. In the mean time, installing WSS v3 & providing training / customization continues to be an excellent source of additional revenue for us, and has opened a few verticals - especially in the project management realm. What an excellent product!!

-Tim

Philip E. said...

Tim,

Yeah, I read through his 5 or 6 part series avidly as it crossed the RSS reader.

Given the amount of work, and the risk involved, we decided that if we attempted it, the only place that would happen would be internally or in a VM.

We decided it was too risky for a client production environment.

Philip