This weekend I struggled a little but with an installation of Windows SharePoint Services. I had a test server installed with ASP.NET and a SQL Server running on it; the goal was to install SharePoint that should be using the SQL Server instance instead of installing Microsoft SQL Server 2000 Desktop Engine (MSDE). By default, the Setup installs an new instance of MSDE to use as database, even if there's a SQL Server available on the same machine. The trick is to use the remotesql command-line option with the setupsts.exe application. The only nasty thing is that first you have to run the STSV2.exe package, so the installation files are decompressed, and then abort the STSV2.exe package:
- Download STSV2.exe to your computer.
- Run STSV2.exe to extract the installation files.
- When the Windows SharePoint Services installation starts, click Cancel.
- Click Start, and then click Run.
- In the Open box, type c:\folder\setupsts.exe remotesql=yes (where c:\folder is the path to the Setupsts.exe file on your local computer).For example, if you installed the US English version of STSV2.exe, then the folder is c:\program files\STS2Setup_1033.
- Click OK.
- The Windows SharePoint Services Setup program opens.
- On the End-User License Agreement page, review the terms, and then select the I accept the terms in the License Agreement check box, and then click Next.
- On the Type of Installation page, click Server Farm, and then click Next.
- On the Summary page, verify that only Windows SharePoint Services will be installed, and then click Install.
- Setup runs and installs Windows SharePoint Services.
Update: Patrick has added a nice tip (see comments): “Maybe a good remark is also to first create an additional virtual server in IIS so that you can host your WSS sites on that one. Otherwise the default Web site will be used and you will not be able anymore to host 'normal' Web sites (due to the ISAPI filter installed by WSS).”