Microsoft Sharepoint Products and Technologies Resource Kit eBook

Chapter 3: Installing Microsoft Office SharePoint Portal Server 2003 81
path reference is “C:\.” You can force the installer to automatically choose
the correct default path by removing an entry line completely.
4. You can modify the following path in the section starting with [gfn_mid
microsoft web storage system]:
InstallDirectory=C:\Program Files\Common Files\Microsoft Shared\Web Storage Sy
stem
The following restrictions apply:
The path cannot be at the root of a hard drive (for example, do not
change the path to “F:\”).
The entire path consists of only low-ASCII characters (no High-ASCII or
DBCS characters).
The path is no longer than 65 characters.
6. You can also modify the following paths in the section starting with [gfn_mid
microsoft sharepoint portal server]:
InstallDirectory=”C:\Program Files\SharePoint Portal Server”
Web Storage System Database Directory=”C:\Program Files\SharePoint Portal Serv
er\DMData\Web Storage System”
Web Storage System Streaming Database Directory=”C:\Program Files\SharePoint P
ortal Server\DMData\Web Storage System”
Web Storage System Database Log Directory=”C:\Program Files\SharePoint Portal
Server\DMData\Web Storage System”
7. Run setup:
1. On the taskbar, from the server on which you want to run setup, click Start,
and then click Run.
2. In Open, type installation path\setup /UnattendFile path filename.ini
where filename is the name of the .ini file that you created.
For example, if the SharePoint Portal Server CD is in drive F, you would
type F:\Optional\Server\setup /q /settings c:\setup.ini
3. Click OK.
Migrating from WMSDE to SQL Server
When you install Windows SharePoint Services on a single server choosing the
default settings, your installation will use Microsoft SQL Server 2000 Desktop Engine
(Windows) (WMSDE) for your databases. This is fine in a small-scale environment,
when you are hosting just a few websites, but if your server suddenly gets popular
and you need to start hosting hundreds of sites, you might run into performance and
storage problems or require a clustered database for high availability. If you find
yourself in one of these situations, you can scale out by switching to Microsoft
SQL Server 2000 Service Pack 3 (SP3) as your database back end. For step-by-step