Microsoft Sharepoint Products and Technologies Resource Kit eBook

Chapter 2: Installing Windows SharePoint Services 27
Installing Windows SharePoint Services on a Single
Machine with WMSDE
When you install Windows SharePoint Services using the default commands, the
WMDSE database installs. WMDSE can be installed only on the same server as Windows
SharePoint Services and is most appropriate for smaller environments that will
host fewer than 1000 websites. You should also not consider using WMSDE if you
are using very large amounts of data.
The version of WMSDE installed with Windows SharePoint Services is different
from the standard MSDE database, which limited the number of possible concurrent
connections to five and the size of the database to 2 GB. The WMDSE has neither of
those limitations built in. Be aware, however, that remote users still cannot connect
to the WMSDE database, which prevents its use on a remote server, in a server farm
scenario, or in a clustered environment.
Avoiding Installation Issues
Avoid the following two common mistakes when installing Windows SharePoint
Services with WMSDE:
■ Unintentionally damaging the default website
■ Introducing an error that relates to a virtual server running FrontPage 2002
Server Extensions
Before installing Windows SharePoint Services, ensure that all your existing
websites have been backed up because an install of Windows SharePoint Services
extends the default website in IIS. If you already have a website running in the
default website, Windows SharePoint Services will extend that site, which could
have unpredictable results depending on how that site is configured.
If you want to specify the location other than the default website to install the
WMSDE database, use the /datadir= option with the Setupsts.exe command-line
tool. The syntax is as follows:
setupsts.exe /datadir="path\\”
For example, to install the WMSDE database to the d:\program files\wmsdedata\
directory, type the following command:
setupsts.exe /datadir="d:\program files\wmsdedata\\”
You can avoid another issue by verifying that FrontPage 2002 Server Extensions
from Microsoft are not running on the virtual server on port 80. (If you
upgraded from Windows 2000 to Windows Server 2003, FrontPage 2002 Server
Extensions were installed by default to port 80.) If FrontPage 2002 Server Extensions