Professional Documents
Culture Documents
Despliegue Con Microsoft Spserv
Despliegue Con Microsoft Spserv
Abstract
This book provides information and guidelines to lead a team through the steps of deploying a
solution based on Windows SharePoint Services 3.0. The audiences for this book are business
application specialists, line-of-business specialists, information architects, IT generalists, program
managers, and infrastructure specialists who are deploying a solution based on Windows
SharePoint Services 3.0. You can find information about upgrading to Windows SharePoint
Services 3.0 in the book Upgrading to Windows SharePoint Services 3.0 technology
(http://go.microsoft.com/fwlink/?LinkId=85554&clcid=0x409).
The content in this book is a copy of selected content in the Windows SharePoint Services
technical library (http://go.microsoft.com/fwlink/?LinkId=81199) as of the date above. For the most
current content, see the technical library on the Web.
The information contained in this document represents the current view of Microsoft Corporation
on the issues discussed as of the date of publication. Because Microsoft must respond to
changing market conditions, it should not be interpreted to be a commitment on the part of
Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the
date of publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this document may be reproduced, stored in or introduced into a
retrieval system, or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the express written
permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail
addresses, logos, people, places and events depicted herein are fictitious, and no association
with any real company, organization, product, domain name, e-mail address, logo, person, place
or event is intended or should be inferred.
2009 Microsoft Corporation. All rights reserved.
Microsoft, Access, Active Directory, Excel, Groove, InfoPath, Internet Explorer, OneNote, Outlook,
PerformancePoint, PowerPoint, SharePoint, SQL Server, Visio, Windows, Windows Server, and
Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their
respective owners.
ii
Contents
Getting Help............................................................................................................................. xi
Roadmap to Windows SharePoint Services 3.0 content..........................................................1
Windows SharePoint Services 3.0 content by audience..........................................................1
Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle...........2
Evaluate............................................................................................................................. 2
Plan.................................................................................................................................... 3
Deploy................................................................................................................................ 4
Operate.............................................................................................................................. 6
Security and Protection...................................................................................................... 6
Technical Reference.......................................................................................................... 7
Solutions............................................................................................................................ 7
I. End-to-end deployment scenarios........................................................................................ 8
Chapter overview: End-to-end deployment scenarios..............................................................9
Install Windows SharePoint Services 3.0 on a stand-alone computer....................................10
Hardware and software requirements.....................................................................................11
Configure the server as a Web server....................................................................................11
Install and configure IIS.................................................................................................... 11
Install the Microsoft .NET Framework version 3.0............................................................12
Enable ASP.NET 2.0........................................................................................................ 12
Install and configure Windows SharePoint Services 3.0 with Windows Internal Database.....12
Post-installation steps............................................................................................................ 14
Deploy in a simple server farm...............................................................................................16
Deployment overview............................................................................................................. 16
Deploying Windows SharePoint Services 3.0 in a DBA environment.................................17
Suggested topologies...................................................................................................... 17
Before you begin deployment..........................................................................................17
Overview of the deployment process...............................................................................18
Phase 1: Deploy and configure the server infrastructure....................................................18
Phase 2: Deploy and configure SharePoint site collections and sites.................................18
Deploy and configure the server infrastructure.......................................................................18
Prepare the database server............................................................................................ 18
SQL Server and database collation....................................................................................19
Required accounts.............................................................................................................. 19
Verify that servers meet hardware and software requirements........................................20
Install and configure IIS...................................................................................................... 21
Install the Microsoft .NET Framework version 3.0..............................................................21
Enable ASP.NET 2.0........................................................................................................... 22
iv
Install Windows SharePoint Services 3.0 and run the SharePoint Products and Technologies
configuration wizard.......................................................................................................... 100
Run Setup on the first server................................................................................................100
Run the SharePoint Products and Technologies Configuration Wizard..........................101
Add servers to the farm.................................................................................................. 103
Run the SharePoint Products and Technologies Configuration Wizard on additional
servers........................................................................................................................ 104
Start the Windows SharePoint Services Search service......................................................105
Deploy language packs (Windows SharePoint Services 3.0)...............................................106
About language IDs and language packs.............................................................................106
Preparing your front-end Web servers for language packs..................................................108
Installing language packs on your front-end Web servers....................................................109
Uninstalling language packs............................................................................................. 110
B. Perform additional configuration tasks............................................................................112
Chapter overview: Perform additional configuration tasks....................................................113
Configure additional administrative settings.........................................................................113
Configure incoming e-mail settings.......................................................................................115
Install and configure the SMTP service................................................................................115
Start the Windows SharePoint Services Web Application service..................................116
Install the SMTP service................................................................................................. 116
Configure the SMTP service.......................................................................................... 117
Add an SMTP connector in Exchange Server................................................................118
Configure Active Directory.................................................................................................... 118
Configure Active Directory under atypical circumstances..............................................120
To delegate full control of the organizational unit to the Central Administration application
pool account............................................................................................................... 120
To add the Delete Subtree permission for the Central Administration application pool
account....................................................................................................................... 121
Configure permissions to the e-mail drop folder...................................................................122
Configure e-mail drop folder permissions for the logon account for the Windows
SharePoint Services Timer service.............................................................................122
Configure e-mail drop folder permissions for the application pool account for a Web
application.................................................................................................................. 122
Configure DNS Manager...................................................................................................... 123
Configure attachments from Outlook 2003...........................................................................124
Configure incoming e-mail settings......................................................................................124
Configuring incoming e-mail on SharePoint sites.................................................................126
Configure outgoing e-mail settings.......................................................................................127
Install and configure the SMTP service................................................................................127
Install the SMTP service................................................................................................ 127
Configure the SMTP service..........................................................................................128
vi
vii
viii
ix
Getting Help
Every effort has been made to ensure the accuracy of this book. This content is also available
online in the Office System TechNet Library, so if you run into problems you can check for
updates at:
http://technet.microsoft.com/office
If you do not find your answer in our online content, you can send an e-mail message to the
Microsoft Office System and Servers content team at:
o12ITdx@microsoft.com
If your question is about Microsoft Office products, and not about the content of this book, please
search the Microsoft Help and Support Center or the Microsoft Knowledge Base at:
http://support.microsoft.com
xi
Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle
IT Professionals
Developers
Content available on
Office Online
TechNet
MSDN
Developer Center a
central portal for
Developer resources
(http://go.microsoft.com/
fwlink/?
LinkId=88910&clcid=0x4
09)
MSDN Library an
index for Developer
content
(http://go.microsoft.com/
fwlink/?
LinkID=86923&clcid=0x
409)
Downloadable books an
article that lists the books
available for download
(http://go.microsoft.com/fwlink/
?LinkId=88907&clcid=0x409)
Additionally, there is information for all users of SharePoint Products and Technologies at the
community and blog sites listed in the following table.
Evaluate
During the evaluation stage, IT professionals (including decision makers, solution architects, and
system architects) focus on understanding a new technology and evaluate how it can help them
address their business needs. The following table lists resources that are available to help you
evaluate Windows SharePoint Services 3.0.
Content
Description
Links
Online
content
Content
Description
Links
continually
refreshed with
new and updated
content.
Evaluation
Guide
Provides an
overview,
information about
what's new, and
conceptual
information for
understanding
Windows
SharePoint
Services 3.0.
Plan
During the planning stage, IT professionals have different needs depending on their role within an
organization. If you are focused on designing a solution, including determining the structure,
capabilities, and information architecture for a site, you might want information that helps you to
determine which capabilities of Windows SharePoint Services 3.0 you want to take advantage of,
and that helps you to plan for those capabilities and to tailor the solution to your organization's
needs. On the other hand, if you are focused on the hardware and network environment for your
solution, you might want information that helps you to structure the server topology, plan
authentication methods, and understand system requirements for Windows SharePoint Services
3.0. We have planning content, including worksheets, to address both of these needs.
The following table lists resources that are available to help you plan for using Windows
SharePoint Services 3.0.
Content
Description
Links
Online
content
Planning
Guide, Part 1
Provides in-depth
planning
Content
Planning
Guide, Part 2
Description
Links
information for
application
administrators who
are designing a
solution based on
Windows
SharePoint
Services 3.0.
LinkId=79600)
Provides in-depth
Planning and architecture for Windows SharePoint
planning
Services, part 2 (http://go.microsoft.com/fwlink/?
information for IT
LinkId=85553)
professionals who
are designing the
environment to
host a solution
based on Windows
SharePoint
Services 3.0.
Deploy
During the deployment stage, you configure your environment, install Windows SharePoint
Services 3.0, and then start creating SharePoint sites. Depending on your environment and your
solution, you may have several configuration steps to perform for your servers, for your Shared
Services Providers, and for your sites. Additionally, you may have templates, features, or other
custom elements to deploy into your environment.
The process of upgrading from a previous-version product, such as Microsoft Office SharePoint
Portal Server 2003, Microsoft Content Management Server 2002, or Windows SharePoint
Services, is also part of the deployment stage of the IT life cycle. We have content that addresses
planning for upgrade, performing the upgrade, and performing post-upgrade steps.
The following table lists resources that are available to help you deploy or upgrade to Windows
SharePoint Services 3.0.
Content
Description
Links
Online content
Includes the
most up-to-date
content. The
Technical
Library on
TechNet is
continually
Content
Description
Links
refreshed with
new and
updated
content.
Deployment
Guide
Provides indepth
deployment
information for
Windows
SharePoint
Services 3.0.
Upgrade Guide
Provides
Upgrading to Windows SharePoint Services 3.0
overview and in- (http://go.microsoft.com/fwlink/?LinkId=85554)
depth
information for
upgrading from
a previous
version product
to Windows
SharePoint
Services 3.0.
Migration and
Upgrade for
SharePoint
Developers
Operate
After deployment, in which you install and configure your environment, you move to the
operations stage. During this stage, you are focused on the day-to-day monitoring, maintenance,
and tuning of your environment.
The following table lists resources that are available to help with day-to-day operations for
Windows SharePoint Services 3.0.
Content
Description
Links
Description
Links
Technical Reference
Technical reference information supports the content for each of the IT life cycle stages by
providing the technical information you need to work with Windows SharePoint Services 3.0. For
example, the Technical Reference content has information about how permissions work, how to
perform operations from the command line, and how to use Setup.exe from the command line.
The following table lists resources that are available to help you work with Windows SharePoint
Services 3.0.
Content
Description
Links
Online
Content
Description
Links
content
up-to-date
content. The
Technical Library
on TechNet is
continually
refreshed with
new and updated
content.
(http://go.microsoft.com/fwlink/?LinkID=88902&clcid=0x409)
Solutions
In addition to these IT life cycle-specific resources, we also offer several solution guides that help
you plan, deploy, and operate a specific type of solution based on Windows SharePoint Services
3.0. For a current list of solution guides for Windows SharePoint Services 3.0, see Downloadable
books for Windows SharePoint Services 3.0 (http://go.microsoft.com/fwlink/?
LinkId=89165&clcid=0x409).
discusses how to
install Windows SharePoint Services 3.0 on a single server computer. A stand-alone
configuration is useful if you want to evaluate Windows SharePoint Services 3.0 features and
capabilities, such as collaboration, document management, and search. A stand-alone
configuration is also useful if you are deploying a small number of Web sites and you want to
minimize administrative overhead.
discusses how to
deploy Windows SharePoint Services 3.0 with Service Pack 1 (SP1) on the new Windows
Server 2008 operating system. Only Windows SharePoint Services 3.0 with SP1 or later can
be installed on Windows Server 2008. You can deploy in a server farm environment if you are
hosting a large number of sites, if you want the best possible performance, or if you want the
scalability of a multi-tier topology. A server farm consists of one or more servers dedicated to
running the Windows SharePoint Services 3.0 applications.
Install and configure Windows SharePoint Services 3.0 with Windows Internal Database
Post-installation steps
You can quickly publish a SharePoint site by deploying Windows SharePoint Services 3.0 on a
single server computer. A stand-alone configuration is useful if you want to evaluate Windows
SharePoint Services 3.0 features and capabilities, such as collaboration, document management,
and search. A stand-alone configuration is also useful if you are deploying a small number of Web
sites and you want to minimize administrative overhead. When you deploy Windows SharePoint
Services 3.0 on a single server using the default settings, the Setup program automatically
installs the Windows internal Database uses it to create the configuration database and content
database for your SharePoint sites. Windows Internal Database uses SQL Server technology as
a relational data store for Windows roles and features only, such as Windows SharePoint
Services, Active Directory Rights Management Services, UDDI Services, Windows Server Update
Services, and Windows System Resources Manager.. In addition, Setup installs the SharePoint
Central Administration Web site and creates your first SharePoint site collection and site.
Note:
There is no direct upgrade from a stand-alone installation to a farm installation.
10
11
page, follow the instructions for downloading and installing the .NET Framework version 3.0.
There are separate downloads for x86-based computers and x64-based computers. Be sure to
download and install the appropriate version for your computer. The .NET Framework version 3.0
download contains the Windows Workflow Foundation technology, which is required by workflow
features.
Note:
You can also use the Microsoft .NET Framework version 3.5. You can download the .NET
Framework version 3.5 from the Microsoft Web site (http://go.microsoft.com/fwlink/?
LinkId=110508).
If you uninstall Windows SharePoint Services 3.0, and then later install Windows
SharePoint Services 3.0 on the same computer, the Setup program could fail when
creating the configuration database causing the entire installation process to fail. You can
prevent this failure by either deleting all the existing Windows SharePoint Services 3.0
databases on the computer or by creating a new configuration database. You can create
a new configuration database by running the following command:
Run Setup
1. On the Read the Microsoft Software License Terms page, review the terms, select the
12
I accept the terms of this agreement check box, and then click Continue.
2. On the Choose the installation you want page, click Basic to install to the default
location. To install to a different location, click Advanced, and then on the Data Location
tab, specify the location you want to install to and finish the installation.
3. When Setup finishes, a dialog box prompts you to complete the configuration of your
server. Be sure that the Run the SharePoint Products and Technologies
Configuration Wizard now check box is selected.
4. Click Close to start the configuration wizard.
Run the SharePoint Products and Technologies Configuration Wizard
1. On the Welcome to SharePoint Products and Technologies page, click Next.
2. In the dialog box that notifies you that some services might need to be restarted or reset
during configuration, click Yes.
3. On the Configuration Successful page, click Finish. Your new SharePoint site opens.
Note:
If you are prompted for your user name and password, you might need to add the
SharePoint site to the list of trusted sites and configure user authentication
settings in Internet Explorer. Instructions for configuring these settings are
provided in the following procedure.
Note:
If you see a proxy server error message, you might need to configure your proxy
server settings so that local addresses bypass the proxy server. Instructions for
configuring proxy server settings are provided later in this section.
Add the SharePoint site to the list of trusted sites
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Security tab, in the Select a Web content zone to specify its security settings
box, click Trusted Sites, and then click Sites.
3. Clear the Require server verification (https:) for all sites in this zone check box.
4. In the Add this Web site to the zone box, type the URL to your site, and then click Add.
5. Click Close to close the Trusted Sites dialog box.
6. Click OK to close the Internet Options dialog box.
If you are using a proxy server in your organization, use the following steps to configure Internet
Explorer to bypass the proxy server for local addresses.
Configure proxy server settings to bypass the proxy server for local addresses
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Connections tab, in the Local Area Network (LAN) settings area, click LAN
Settings.
13
3. In the Automatic configuration section, clear the Automatically detect settings check
box.
4. In the Proxy Server section, select the Use a proxy server for your LAN check box.
5. Type the address of the proxy server in the Address box.
6. Type the port number of the proxy server in the Port box.
7. Select the Bypass proxy server for local addresses check box.
8. Click OK to close the Local Area Network (LAN) Settings dialog box.
9. Click OK to close the Internet Options dialog box.
Post-installation steps
After Setup finishes, your browser window opens to the home page of your new SharePoint site.
Although you can start adding content to the site or you can start customizing the site, we
recommend that you perform the following administrative tasks by using the SharePoint Central
Administration Web site.
Configure incoming e-mail settings You can configure incoming e-mail settings so that
SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail
settings so that SharePoint sites can archive e-mail discussions as they happen, save emailed documents, and show e-mailed meetings on site calendars. In addition, you can
configure the SharePoint Directory Management Service to provide support for e-mail
distribution list creation and management. For more information, see Configure incoming email settings
Configure outgoing e-mail settings You can configure outgoing e-mail settings so that
your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and
notifications to site administrators. You can configure both the "From" e-mail address and the
"Reply" e-mail address that appear in outgoing alerts. For more information, see Configure
outgoing e-mail settings.
Configure diagnostic logging settings You can configure several diagnostic logging
settings to help with troubleshooting. This includes enabling and configuring trace logs, event
messages, user-mode error messages, and Customer Experience Improvement Program
events. For more information, see Configure diagnostic logging settings.
Configure antivirus protection settings You can configure several antivirus settings if you
have an antivirus program that is designed for Windows SharePoint Services 3.0. Antivirus
settings enable you to control whether documents are scanned on upload or download and
whether users can download infected documents. You can also specify how long you want
the antivirus program to run before it times out, and you can specify how many execution
threads the antivirus program can use on the server. For more information, see Configure
anti-virus settings.
Create SharePoint sites When Setup finishes, you have a single Web application that
contains a single SharePoint site collection that hosts a SharePoint site. You can create more
SharePoint sites collections, sites, and Web applications if your site design requires multiple
14
sites or multiple Web applications. For more information, see Deploy and configure
SharePoint sites.
Perform administrator tasks by using the Central Administration site
1. Click Start, point to All Programs, point to Administrator Tools, and then click
SharePoint 3.0 Central Administration.
2. On the Central Administration home page, under Administrator Tasks, click the task
you want to perform.
3. On the Administrator Tasks page, next to Action, click the task.
15
Deployment overview
Deployment overview
Important:
This article discusses how to do a clean installation of Windows SharePoint Services 3.0
in a server farm environment. It does not cover upgrading from previous releases of
Windows SharePoint Services 3.0 or from previous releases of Windows SharePoint
Services. For more information about upgrading from a previous release of Windows
SharePoint Services, see Upgrading to Windows SharePoint Services 3.0.
Note:
This article does not cover installing Windows SharePoint Services 3.0 on a single
computer as a stand-alone installation. For more information, see Install Windows
SharePoint Services 3.0 on a stand-alone computer.
You can deploy Windows SharePoint Services 3.0 in a server farm environment if you are hosting
a large number of sites, if you want the best possible performance, or if you want the scalability of
a multi-tier topology. A server farm consists of one or more servers dedicated to running the
Windows SharePoint Services 3.0 application.
Note:
There is no direct upgrade from a stand-alone installation to a farm installation.
Because a server farm deployment of Windows SharePoint Services 3.0 is more complex than a
stand-alone deployment, we recommend that you plan your deployment. Planning your
deployment can help you to gather the information you need and to make important decisions
before beginning to deploy. For information about planning, see Planning and architecture for
Windows SharePoint Services 3.0 technology.
16
Suggested topologies
Server farm environments can encompass a wide range of topologies and can include many
servers or as few as two servers.
A server farm typically consists of a database server running either Microsoft SQL Server 2005 or
Microsoft SQL Server 2000 with the most recent service pack, and one or more servers running
Internet Information Services (IIS) and Windows SharePoint Services 3.0. In this configuration,
the front-end servers are configured as Web servers. The Web server role provides Web content
and services such as search.
A large server farm typically consists of two or more clustered database servers, several loadbalanced front-end Web servers running IIS and Windows SharePoint Services 3.0, and two or
more servers providing search services.
To deploy Windows SharePoint Services 3.0 in a server farm environment, you must provide
credentials for several different accounts. For information about these accounts, see Plan for
administrative and service accounts (http://technet.microsoft.com/enus/library/cc288210.aspx).
You must install Windows SharePoint Services 3.0 on the same drive on all load-balanced
front-end Web servers.
All the instances of Windows SharePoint Services 3.0 in the farm must be in the same
language. For example, you cannot have both an English version of Windows SharePoint
Services 3.0 and a Japanese version of Windows SharePoint Services 3.0 in the same farm.
You must install Windows SharePoint Services 3.0 on a clean installation of the Microsoft
Windows Server 2003 operating system with the most recent service pack. If you uninstall a
previous version of Windows SharePoint Services 3.0, and then install Windows SharePoint
Services 3.0, Setup might fail to create the configuration database and the installation will fail.
Note:
We recommend that you read the Known Issues/Readme documentation before you
install Windows SharePoint Services 3.0 on a domain controller. Installing Windows
SharePoint Services 3.0 on a domain controller requires additional configuration
steps that are not discussed in this article.
17
Running Setup on all servers you want to be in the farm, including running the SharePoint
Products and Technologies Configuration Wizard.
18
Required accounts
The following table describes the accounts that are used to configure SQL Server and to install
Windows SharePoint Services 3.0. For more information about the required accounts, including
specific privileges required for these accounts, see Plan for administrative and service accounts
[Windows SharePoint Services].
Account
Purpose
Requirements
SQL Server
Service Account
MSSQLSERVER
SQLSERVERAGENT
MSSQL$InstanceName
SQLAgent$InstanceNam
e
19
Account
Purpose
Requirements
Setup user
account
The SharePoint
Products and
Technologies
Configuration Wizard
The PSConfig
command-line tool
Server farm
The Server farm account is
account/Database used to:
access account
Act as the application
pool identity for the
SharePoint Central
Administration
application pool.
20
acting as a database server. For more information about these requirements, see Determine
hardware and software requirements (http://technet.microsoft.com/en-us/library/cc288751.aspx).
Important:
Windows SharePoint Services 3.0 requires Active Directory directory services for farm
deployments. Therefore Windows SharePoint Services 3.0 cannot be installed in a farm
on a Microsoft Windows NT Server 4.0 domain.
21
version 3.0 download contains the Windows Workflow Foundation technology, which is required
by workflow features.
Note:
You can also use the Microsoft .NET Framework version 3.5. You can download the .NET
Framework version 3.5 from the Microsoft Web site (http://go.microsoft.com/fwlink/?
LinkId=110508).
22
Note:
Setup installs the Central Administration Web site on the first server on which you run
Setup. Therefore, we recommend that the first server on which you install Windows
SharePoint Services 3.0 is a server from which you want to run the Central Administration
Web site.
Run Setup on the first server
1. From the product disc, run Setup.exe, or from the product download, run WSSv3.exe, on
one of your Web server computers.
2. On the Read the Microsoft Software License Terms page, review the terms, select the I
accept the terms of this agreement check box, and then click Continue.
3. On the Choose the installation you want page, click Advanced. The Basic option is for
stand-alone installations.
4. On the Server Type tab, click Web Front End. The Stand-alone option is for standalone installations.
5. Optionally, to install Windows SharePoint Services 3.0 at a custom location, select the
Data Location tab, and then type the location name or Browse to the location.
6. Optionally, to participate in the Customer Experience Improvement Program, select the
Feedback tab and select the option you want. To learn more about the program, click the
link. You must have an Internet connection to view the program information.
7. When you have chosen the correct options, click Install Now.
8. When Setup finishes, a dialog box appears that prompts you to complete the
configuration of your server. Be sure that the Run the SharePoint Products and
Technologies Configuration Wizard now check box is selected.
9. Click Close to start the configuration wizard. Instructions for completing the wizard are
provided in the next set of steps.
23
4. In the Specify Configuration Database Settings dialog box, in the Database server
box, type the name of the computer that is running SQL Server.
5. Type a name for your configuration database in the Database name box, or use the
default database name. The default name is "SharePoint_Config".
6. In the User name box, type the user name of the server farm account. (Be sure to type
the user name in the format DOMAIN\username.)
Important:
This account is the server farm account and is used to access your SharePoint
configuration database. It also acts as the application pool identity for the
SharePoint Central Administration application pool and it is the account under
which the Windows SharePoint Services Timer service runs. The SharePoint
Products and Technologies Configuration Wizard adds this account to the SQL
Server Logins, the SQL Server Database Creator server role, and the SQL
Server Security Administrators server role. The user account that you specify as
the service account must be a domain user account, but it does not need to be a
member of any specific security group on your Web servers or your back-end
database servers. We recommend that you follow the principle of least privilege
and specify a user account that is not a member of the Administrators group on
your Web servers or your back-end servers.
7. In the Password box, type the user's password, and then click Next.
8. On the Configure SharePoint Central Administration Web Application page, select the
Specify port number check box and type a port number if you want the SharePoint
Central Administration Web application to use a specific port, or leave the Specify port
number check box cleared if you do not care which port number the SharePoint Central
Administration Web application uses.
9. On the Configure SharePoint Central Administration Web Application dialog box, do
one of the following:
If you want to use Kerberos authentication, click Negotiate (Kerberos), and then
click Next.
Note:
In most cases, you should use the default setting (NTLM). Use Negotiate
(Kerberos) only if Kerberos authentication is supported in your environment.
Using the Negotiate (Kerberos) option requires you to configure a Service
Principal Name (SPN) for the domain user account. To do this, you must be a
member of the Domain Admins group. For more information, see How to
configure a Windows SharePoint Services virtual server to use Kerberos
authentication and how to switch from Kerberos authentication back to NTLM
authentication (http://go.microsoft.com/fwlink/?LinkID=76570&clcid=0x409).
10. On the Completing the SharePoint Products and Technologies Configuration Wizard
page, click Next.
24
25
You must have SQL Server running on at least one back-end database server before you install
Windows SharePoint Services 3.0 on your farm servers.
Important:
If you uninstall Windows SharePoint Services 3.0 from the first server on which you
installed it, your farm might experience problems.
Run Setup on additional servers
1. From the product disc, run Setup.exe, or from the product download, run WSSv3.exe, on
one of your Web server computers.
2. On the Read the Microsoft Software License Terms page, review the terms, select the I
accept the terms of this agreement check box, and then click Continue.
3. On the Choose the installation you want page, click Advanced. The Basic option is for
stand-alone installations.
4. On the Server Type tab, click Web Front End. The Stand-alone option is for standalone installations.
5. Optionally, to install Windows SharePoint Services 3.0 at a custom location, select the
Data Location tab, and then type the location name or Browse to the location.
6. Optionally, to participate in the Customer Experience Improvement Program, select the
Feedback tab and select the option you want. To learn more about the program, click the
link. You must have an Internet connection to view the program information.
7. When you have chosen the correct options, click Install Now.
8. When Setup finishes, a dialog box appears that prompts you to complete the
configuration of your server. Be sure that the Run the SharePoint Products and
Technologies Configuration Wizard now check box is selected.
9. Click Close to start the configuration wizard. Instructions for completing the wizard are
provided in the next set of steps.
26
4. In the Specify Configuration Database Settings dialog box, in the Database server
box, type the name of the computer that is running SQL Server.
5. Click Retrieve Database Names, and then from the Database name list, select the
database name that you created when you configured the first server in your server farm.
6. In the User name box, type the user name of the account used to connect to the
computer running SQL Server. (Be sure to type the user name in the format
DOMAIN\username.) This must be the same user account you used when configuring the
first server.
7. In the Password box, type the user's password, and then click Next.
8. On the Completing the SharePoint Products and Technologies Configuration Wizard
page, click Next.
9. On the Configuration Successful page, click Finish.
27
first perform the following administrative tasks by using the SharePoint Central Administration
Web site.
Configure incoming e-mail settings You can configure incoming e-mail settings so that
SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail
settings so that SharePoint sites archive e-mail discussions as they happen, save e-mailed
documents, and show e-mailed meetings on site calendars. In addition, you can configure the
SharePoint Directory Management Service to provide support for e-mail distribution list
creation and management. For more information, see Configure incoming e-mail settings.
Configure outgoing e-mail settings You can configure outgoing e-mail settings so that
your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and
notifications to site administrators. You can configure both the "From" e-mail address and the
"Reply" e-mail address that appear in outgoing alerts. For more information, see Configure
outgoing e-mail settings.
Configure diagnostic logging settings You can configure several diagnostic logging
settings to help with troubleshooting. This includes enabling and configuring trace logs, event
messages, user-mode error messages, and Customer Experience Improvement Program
events. For more information, see Configure diagnostic logging settings.
Configure antivirus protection settings You can configure several antivirus settings if you
have an antivirus program that is designed for Windows SharePoint Services 3.0. Antivirus
settings enable you to control whether documents are scanned on upload or download, and
whether users can download infected documents. You can also specify how long you want
the antivirus program to run before it times out, and you can specify how many execution
threads the antivirus program can use on the server. For more information, see Configure
anti-virus settings
Perform administrator tasks by using the Central Administration site
1. Click Start, point to All Programs, point to Administrative Tools, and then click
SharePoint 3.0 Central Administration.
2. On the Central Administration home page, in the Administrator Tasks section, click
the task you want to perform.
3. On the Administrator Tasks page, next to Action, click the task.
28
You can also migrate content from a pre-existing Microsoft Content Management Server 2002
source. For information, see Upgrading to Windows SharePoint Services 3.0.
Before you can create a site or a site collection, you must first create a Web application. A Web
application is comprised of an Internet Information Services (IIS) site with a unique application
pool. When you create a new Web application, you also create a new database and define the
authentication method used to connect to the database.
If you are in an extranet environment where you want different users to access content by using
different domains, you might also need to extend a Web application to another IIS Web site. This
action exposes the same content to different sets of users by using an additional IIS Web site to
host the same content.
Create a new Web application
1. In the SharePoint Central Administration Web site, on the Application Management page,
in the SharePoint Web Application Management section, click Create or extend Web
application.
2. On the Create or Extend Web Application page, in the Adding a SharePoint Web
Application section, click Create a new Web application.
3. On the Create New Web Application page, in the IIS Web Site section, you can configure
the settings for your new Web application.
a. To choose to use an existing Web site, select Use an existing Web site, and specify
the Web site on which to install your new Web application by selecting it from the
drop-down menu.
b. To choose to create a new Web site, select Create a new IIS Web site, and type the
name of the Web site in the Description box.
c.
In the Port box, type the port number you want to use to access the Web application.
If you are creating a new Web site, this field is populated with a suggested port
number. If you are using an existing Web site, this field is populated with the current
port number.
d. In the Host Header box, type the URL you want to use to access the Web
application. This is an optional field.
e. In the Path box, type the path to the site directory on the server. If you are creating a
new Web site, this field is populated with a suggested path. If you are using an
existing Web site, this field is populated with the current path.
4. In the Security Configuration section, configure authentication and encryption for your
Web application.
a. In the Authentication Provider section, choose either Negotiate (Kerberos) or
NTLM.
Note:
To enable Kerberos authentication, you must perform additional
configuration. For more information about authentication methods, see Plan
authentication methods (http://technet.microsoft.com/en-
29
us/library/cc288475.aspx).
b. In the Allow Anonymous section, choose Yes or No. If you choose to allow
anonymous access, this enables anonymous access to the Web site by using the
computer-specific anonymous access account (that is, IUSR_<computername>).
Note:
If you want users to be able to access any site content anonymously, you
must enable anonymous access for the entire Web application. Later, site
owners can configure how anonymous access is used within their sites. For
more information about anonymous access, see Choose which security
groups to use (http://technet.microsoft.com/en-us/library/cc288957.aspx).
c.
In the Use Secure Sockets Layer (SSL) section, select Yes or No. If you choose to
enable SSL for the Web site, you must configure SSL by requesting and installing an
SSL certificate.
Important:
If you use SSL, you must add the appropriate certificate on each server by
using IIS administration tools. For more information about using SSL, see
Plan for secure communication within a server farm
(http://technet.microsoft.com/en-us/library/cc288488.aspx).
5. In the Load Balanced URL section, type the URL for the domain name for all sites that
users will access in this Web application. This URL domain will be used in all links shown
on pages within the Web application. By default, the box is populated with the current
server name and port.
The Zone box is automatically set to Default for a new Web application, and cannot be
changed from this page. To change the zone for a Web application, see Create or extend
Web applications.
6. In the Application Pool section, choose whether to use an existing application pool or
create a new application pool for this Web application. To use an existing application
pool, select Use existing application pool. Then select the application pool you want to
use from the drop-down menu.
a. To create a new application pool, select Create a new application pool.
b. In the Application pool name box, type the name of the new application pool, or
keep the default name.
c.
In the Select a security account for this application pool section, select
Predefined to use an existing application pool security account, and then select the
security account from the drop-down menu.
d. Select Configurable to use an account that is not currently being used as a security
account for an existing application pool. In the User name box, type the user name of
the account you want to use, and type the password for the account in the Password
box.
7. In the Reset Internet Information Services section, choose whether to allow Windows
SharePoint Services to restart IIS on other farm servers. The local server must be
30
restarted manually for the process to finish. If this option is not selected and you have
more than one server in the farm, you must wait until the IIS Web site is created on all
servers and then run iisreset/noforce on each Web server. The new IIS site is not
usable until that action is completed. The choices are unavailable if your farm only
contains a single server.
8. In the Database Name and Authentication section, choose the database server,
database name, and authentication method for your new Web application.
Item
Action
Database Server
Database Name
Database Authentication
9. Click OK to create the new Web application, or click Cancel to cancel the process and
return to the Application Management page.
For information about how to perform this procedure using the Stsadm command-line tool, see
Createsiteinnewdb: Stsadm operation (http://technet.microsoft.com/en-us/library/cc288051.aspx).
Create a site collection
1. On the SharePoint Central Administration home page, click the Application
Management tab on the top link bar.
2. On the Application Management page, in the SharePoint Site Management section,
click Create site collection.
31
3. On the Create Site Collection page, in the Web Application section, select a Web
application to host the site collection from the Web Application drop-down list.
4. In the Title and Description section, type a title and description for the site collection.
5. In the Web Site Address section, select a URL type (personal or sites), and then type a
URL for the site collection.
6. In the Template Selection section, select a template from the tabbed template control.
7. In the Primary Site Collection Administrator section, specify the user account for the
user you want to be the primary administrator for the site collection. You can also browse
for the user account by clicking the Book icon to the right of the text box. You can check
the user account by clicking the Check Names icon to the right of the text box.
8. Optionally, in the Secondary Site Collection Administrator section, specify the user
account for the user you want to be the secondary administrator for the site collection.
You can also browse for the user account by clicking the Book icon to the right of the text
box. You can check the user account by clicking the Check Names icon to the right of the
text box.
9. Click Create to create the site collection.
For information about how to perform this procedure using the Stsadm command-line tool, see
Createsite: Stsadm operation (http://technet.microsoft.com/en-us/library/cc287992.aspx).
Create a SharePoint site
1. On the SharePoint Central Administration home page, click the Application
Management tab on the top link bar.
2. On the Application Management page, in the SharePoint Site Management section,
click Site collection list.
3. On the Site Collection List page, in the URL column, click the URL for the site collection
to which you want to add a site. The full URL path for the site collection appears in the
URL box.
4. Copy and paste the full URL path into your browser, and then, on the home page of the
top-level site for the site collection, on the Site Actions menu, click Create.
5. On the Create page, in the Web Pages section, click Sites and Workplaces.
6. On the New SharePoint Site page, in the Title and Description section, type a title and
description for the site.
7. In the Web Site Address section, type a URL for the site.
8. In the Template Selection section, select a template from the tabbed template control.
9. Either change other settings, or click Create to create the site.
10. The new site opens.
After creating sites, you might want to configure alternate access mappings. Alternate access
mappings direct users to the correct URLs during their interaction with Windows SharePoint
Services 3.0 (while browsing to the home page of a Windows SharePoint Services 3.0 Web site,
for example). Alternate access mappings enable Windows SharePoint Services 3.0 to map Web
32
requests to the correct Web applications and sites, and they enable Windows SharePoint
Services 3.0 to serve the correct content back to the user. For more information, see Plan
alternate access mappings (http://technet.microsoft.com/en-us/library/cc288609.aspx).
3. Ensure that the path specified in the Path box has enough room to store the extra log
files, or change the path to another location.
Tip:
We recommend that you store log files on a hard drive partition that is used to
store log files only.
4. Click OK.
Trace log files can help you to troubleshoot issues related to configuration changes of the
Windows SharePoint Services Search service. Because problems related to configuration
changes are not always immediately discovered, we recommend that you save all trace log files
that the system creates on any day that you make any configuration changes related to either
search service. Store these log files for an extended period of time in a safe location that will not
be overwritten. See step 3 in the previous procedure to determine the location that the system
stores trace log files for your system.
33
For information about how to perform this procedure using the Stsadm command-line tool, see
Logging and Events: Stsadm operations (http://technet.microsoft.com/enus/library/cc288075.aspx).
34
Required accounts
35
Required accounts
The DBA needs to create SQL Server logins for the accounts that are used to access the
databases for Windows SharePoint Services 3.0 and add them to roles. For more information
about required accounts, including specific permissions and user rights required for these
accounts, see Plan for administrative and service accounts (http://technet.microsoft.com/enus/library/cc288210.aspx).
36
The following table describes the accounts that are used to access the databases for Windows
SharePoint Services 3.0.
Account
Purpose
Requirements
SQL Server
Service Account
MSSQLSERVER
SQLSERVERAGENT
MSSQL$InstanceName
SQLAgent$InstanceNam
e
Setup user
account
The SharePoint
Products and
Technologies
Configuration Wizard
The PSConfig
command-line tool
37
Account
Purpose
Server farm
The Server farm account is
account/Database used to:
access account
Act as the application
pool identity for the
SharePoint Central
Administration
application pool.
Requirements
Note:
If you are using the least-privilege principle for added security, use a different account for
each service, process, and application pool identity for each Web application.
38
39
40
Deployment overview
As of Windows SharePoint Services 3.0 with Service Pack 1 (SP1), you can now install Windows
SharePoint Services 3.0 on Windows Server 2008. As with the Windows Server 2003 operating
system, you must download and run Setup and the SharePoint Products and Technologies
Configuration Wizard. You cannot install Windows SharePoint Services 3.0 without service packs
on Windows Server 2008.
Important:
The following components are required for Windows SharePoint Services 3.0 to run
correctly: the Web Server role, the Microsoft .NET Framework version 3.0, and Active
Directory Domain Services. Do not uninstall them, or Windows SharePoint Services 3.0
will cease to run.
Deployment overview
Important:
This article discusses how to do a clean installation of Windows SharePoint Services 3.0
with SP1 in a server farm environment on Windows Server 2008. It does not cover
upgrading the operating system from Windows Server 2003 to Windows Server 2008. For
more information about upgrading the operating system, see Upgrading to Windows
Server 2008 for Windows SharePoint Services 3.0 with SP1.
Note:
This article does not cover installing Windows SharePoint Services 3.0 on a single
computer as a stand-alone installation on Windows Server 2008. For more information,
see Install a stand-alone server on Windows Server 2008.
You can deploy Windows SharePoint Services 3.0 in a server farm environment if you are hosting
a large number of sites, if you want the best possible performance, or if you want the scalability of
a multi-tier topology. A server farm consists of one or more servers dedicated to running Windows
SharePoint Services 3.0.
41
Note:
There is no direct upgrade from a stand-alone installation to a farm installation.
Because a server farm deployment of Windows SharePoint Services 3.0 is more complex than a
stand-alone deployment, we recommend that you plan your deployment. Planning your
deployment can help you to gather the information you need and to make important decisions
before beginning to deploy. For information about planning, see Planning and architecture for
Windows SharePoint Services 3.0 technology.
Suggested topologies
Server farm environments can encompass a wide range of topologies and can include many
servers or as few as two servers.
A server farm typically consists of a database server running either Microsoft SQL Server 2005 or
Microsoft SQL Server 2000 with the most recent service pack, and one or more servers running
Internet Information Services (IIS) and Windows SharePoint Services 3.0. In this configuration,
the front-end servers are configured as Web servers. The Web server role provides Web content
and services such as search.
A large server farm typically consists of two or more clustered database servers, several loadbalanced front-end Web servers running IIS and Windows SharePoint Services 3.0, and two or
more servers providing search services.
To deploy Windows SharePoint Services 3.0 in a server farm environment, you must provide
credentials for several different accounts. For information about these accounts, see Plan for
administrative and service accounts (http://technet.microsoft.com/enus/library/cc288210.aspx).
You must install Windows SharePoint Services 3.0 on the same drive on all load-balanced
front-end Web servers.
All the instances of Windows SharePoint Services 3.0 in the farm must be in the same
language. For example, you cannot have both an English version of Windows SharePoint
Services 3.0 and a Japanese version of Windows SharePoint Services 3.0 in the same farm.
42
Note:
We recommend that you read the Known Issues/Readme documentation before you
install Windows SharePoint Services 3.0 on a domain controller. Installing Windows
SharePoint Services 3.0 on a domain controller requires additional configuration
steps that are not discussed in this article.
Running Setup on all servers you want to be in the farm, including running the SharePoint
Products and Technologies Configuration Wizard.
43
2. In the SQL Server 2005 Surface Area Configuration dialog box, click Surface Area
Configuration for Services and Connections.
3. In the tree view, expand the node for your instance of SQL Server, expand the Database
Engine node, and then click Remote Connections.
4. Select Local and Remote Connections, select Using both TCP/IP and named pipes,
and then click OK.
44
Required accounts
The following table describes the accounts that are used to configure SQL Server and to install
Windows SharePoint Services 3.0. For more information about the required accounts, including
specific role memberships and permissions required for these accounts, see Plan for
administrative and service accounts [Windows SharePoint Services].
Account
Purpose
Requirements
SQL Server
Service Account
MSSQLSERVER
SQLSERVERAGENT
MSSQL$InstanceName
SQLAgent$InstanceNam
e
Setup user
account
The SharePoint
Products and
Technologies
Configuration Wizard
The PSConfig
command-line tool
45
Account
Purpose
Server farm
The Server farm account is
account/Database used to:
access account
Act as the application
pool identity for the
SharePoint Central
Administration
application pool.
Requirements
46
47
3. On the Choose the installation you want page, click Advanced. The Basic option is for
stand-alone installations.
4. On the Server Type tab, click Web Front End. The Stand-alone option is for standalone installations.
5. Optionally, to install Windows SharePoint Services 3.0 at a custom location, select the
Data Location tab, and then type the location name or Browse to the location.
6. Optionally, to participate in the Customer Experience Improvement Program, select the
Feedback tab and select the option you want. To learn more about the program, click the
link. You must have an Internet connection to view the program information.
7. When you have chosen the correct options, click Install Now.
8. When Setup finishes, a dialog box appears that prompts you to complete the
configuration of your server. Be sure that the Run the SharePoint Products and
Technologies Configuration Wizard now check box is selected.
9. Click Close to start the configuration wizard. Instructions for completing the wizard are
provided in the next set of steps.
Note:
Do not add any server roles in Windows Server 2008 Server Manager before setup for
Windows SharePoint Services 3.0 is complete. If you add a server role, the setup
process will fail and you will need to uninstall and reinstall Windows SharePoint Services
3.0.
48
If you want to use Kerberos authentication, click Negotiate (Kerberos), and then
click Next.
Note:
In most cases, you should use the default setting (NTLM). Use Negotiate
(Kerberos) only if Kerberos authentication is supported in your environment.
Using the Negotiate (Kerberos) option requires you to configure a service
principal name (SPN) for the domain user account. To do this, you must be a
member of the Domain Admins group. For more information, see How to
configure a Windows SharePoint Services virtual server to use Kerberos
authentication and how to switch from Kerberos authentication back to NTLM
authentication (http://go.microsoft.com/fwlink/?LinkID=76570&clcid=0x409).
10. On the Completing the SharePoint Products and Technologies Configuration Wizard
page, click Next.
11. On the Configuration Successful page, click Finish.
The SharePoint Central Administration Web site home page opens.
Note:
If you are prompted for your user name and password, you might need to add the
SharePoint Central Administration site to the list of trusted sites and configure
49
50
If you uninstall Windows SharePoint Services 3.0, and then later install Windows
SharePoint Services 3.0 on the same computer, the Setup program could fail when
creating the configuration database causing the entire installation process to fail. You can
prevent this failure by either deleting all the existing Windows SharePoint Services 3.0
databases on the computer or by creating a new configuration database. You can create
a new configuration database by running the following command from the path
%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\bin:
51
52
53
If it is Inbound connections that do not match a rule are allowed, then you do not
need to complete this procedure.
If it is Inbound connections that do not match a rule are blocked, then you must
proceed to the next step in this procedure to configure the firewall to allow Windows
SharePoint Services 3.0 traffic.
4. On the console tree, select Inbound Rules, and then in the action pane click New Rule.
5. Complete the New Inbound Rule Wizard using the settings from the following table.
Wizard page
Settings
Rule Type
Select Port.
Select TCP.
Select Specific local ports. In the
Specific local ports text box,
identify all the ports that you need.
Action
Profile
Name
For more information about Windows Firewall with Advanced Security, see Windows Firewall
(http://go.microsoft.com/fwlink/?LinkID=84639).
54
Configure incoming e-mail settings You can configure incoming e-mail settings so that
SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail
settings so that SharePoint sites can archive e-mail discussions as they happen, save emailed documents, and show e-mailed meetings on site calendars. In addition, you can
configure the SharePoint Directory Management Service to provide support for e-mail
distribution list creation and management. For more information, see Configure incoming email settings.
Configure outgoing e-mail settings You can configure outgoing e-mail settings so that
your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and
notifications to site administrators. You can configure both the "From" e-mail address and the
"Reply" e-mail address that appear in outgoing alerts. For more information, see Configure
outgoing e-mail settings.
Configure diagnostic logging settings You can configure several diagnostic logging
settings to help with troubleshooting. This includes enabling and configuring trace logs, event
messages, user-mode error messages, and Customer Experience Improvement Program
events. For more information, see Configure diagnostic logging settings.
Configure antivirus protection settings You can configure several antivirus settings if you
have an antivirus program that is designed for Windows SharePoint Services 3.0. Antivirus
settings enable you to control whether documents are scanned on upload or download and
whether users can download infected documents. You can also specify how long you want
the antivirus program to run before it times out, and you can specify how many execution
threads the antivirus program can use on the server. For more information, see Configure
anti-virus settings.
Perform administrator tasks by using the Central Administration site
1. Click Start, point to All Programs, point to Administrative Tools, and then click
SharePoint 3.0 Central Administration.
2. On the Central Administration home page, in the Administrator Tasks section, click
the task you want to perform.
3. On the Administrator Tasks page, next to Action, click the task.
55
If you are in an extranet environment where you want different users to access content by using
different domains, you might also need to extend a Web application to another IIS Web site. This
action exposes the same content to different sets of users by using an additional IIS Web site to
host the same content.
56
In the Port box, type the port number you want to use to access the Web application.
If you are creating a new Web site, this field is populated with a suggested port
number. If you are using an existing Web site, this field is populated with the current
port number.
d. In the Host Header box, type the URL you want to use to access the Web
application. This is an optional field.
e. In the Path box, type the path to the site directory on the server. If you are creating a
new Web site, this field is populated with a suggested path. If you are using an
existing Web site, this field is populated with the current path.
4. In the Security Configuration section, configure authentication and encryption for your
Web application.
a. In the Authentication Provider section, choose either Negotiate (Kerberos) or
NTLM.
Note:
To enable Kerberos authentication, you must perform additional
configuration. For more information about authentication methods, see Plan
authentication methods (http://technet.microsoft.com/enus/library/cc288475.aspx).
b. In the Allow Anonymous section, choose Yes or No. If you choose to allow
anonymous access, this enables anonymous access to the Web site by using the
computer-specific anonymous access account (that is, IUSR_<computername>).
Note:
If you want users to be able to access any site content anonymously, you
must enable anonymous access for the entire Web application. Later, site
owners can configure how anonymous access is used within their sites. For
more information about anonymous access, see Choose which security
groups to use (http://technet.microsoft.com/en-us/library/cc288957.aspx).
c.
In the Use Secure Sockets Layer (SSL) section, select Yes or No. If you choose to
57
enable SSL for the Web site, you must configure SSL by requesting and installing an
SSL certificate.
Important:
If you use SSL, you must add the appropriate certificate on each server by
using IIS administration tools. For more information about using SSL, see
Plan for secure communication within a server farm
(http://technet.microsoft.com/en-us/library/cc288488.aspx).
5. In the Load Balanced URL section, type the URL for the domain name for all sites that
users will access in this Web application. This URL domain will be used in all links shown
on pages within the Web application. By default, the box is populated with the current
server name and port.
The Zone box is automatically set to Default for a new Web application, and cannot be
changed from this page. To change the zone for a Web application, see Create or extend
Web applications.
6. In the Application Pool section, choose whether to use an existing application pool or
create a new application pool for this Web application. To use an existing application
pool, select Use existing application pool. Then select the application pool you want to
use from the drop-down menu.
a. To create a new application pool, select Create a new application pool.
b. In the Application pool name box, type the name of the new application pool, or
keep the default name.
c.
In the Select a security account for this application pool section, select
Predefined to use an existing application pool security account, and then select the
security account from the drop-down menu.
d. Select Configurable to use an account that is not currently being used as a security
account for an existing application pool. In the User name box, type the user name of
the account you want to use, and type the password for the account in the Password
box.
7. In the Reset Internet Information Services section, choose whether to allow Windows
SharePoint Services to restart IIS on other farm servers. The local server must be
restarted manually for the process to finish. If this option is not selected and you have
more than one server in the farm, you must wait until the IIS Web site is created on all
servers and then run iisreset/noforce on each Web server. The new IIS site is not
usable until that action is completed. The choices are unavailable if your farm only
contains a single server.
8. In the Database Name and Authentication section, choose the database server,
database name, and authentication method for your new Web application.
58
Item
Action
Database Server
Database Name
Database Authentication
9. Click OK to create the new Web application, or click Cancel to cancel the process and
return to the Application Management page.
Create a site collection
1. On the SharePoint Central Administration home page, click the Application
Management tab on the top link bar.
2. On the Application Management page, in the SharePoint Site Management section,
click Create site collection.
3. On the Create Site Collection page, in the Web Application section, select a Web
application to host the site collection from the Web Application drop-down list.
4. In the Title and Description section, type a title and description for the site collection.
5. In the Web Site Address section, select a URL type (personal or sites), and then type a
URL for the site collection.
6. In the Template Selection section, select a template from the tabbed template control.
7. In the Primary Site Collection Administrator section, specify the user account for the
user you want to be the primary administrator for the site collection. You can also browse
for the user account by clicking the Book icon to the right of the text box. You can check
59
the user account by clicking the Check Names icon to the right of the text box.
8. Optionally, in the Secondary Site Collection Administrator section, specify the user
account for the user you want to be the secondary administrator for the site collection.
You can also browse for the user account by clicking the Book icon to the right of the text
box. You can check the user account by clicking the Check Names icon to the right of the
text box.
9. Click Create to create the site collection.
Create a SharePoint site
1. On the SharePoint Central Administration home page, click the Application
Management tab on the top link bar.
2. On the Application Management page, in the SharePoint Site Management section,
click Site collection list.
3. On the Site Collection List page, in the URL column, click the URL for the site collection
to which you want to add a site. The full URL path for the site collection appears in the
URL box.
4. Copy and paste the full URL path into your browser, and then, on the home page of the
top-level site for the site collection, on the Site Actions menu, click Create.
5. On the Create page, in the Web Pages section, click Sites and Workplaces.
6. On the New SharePoint Site page, in the Title and Description section, type a title and
description for the site.
7. In the Web Site Address section, type a URL for the site.
8. In the Template Selection section, select a template from the tabbed template control.
9. Either change other settings, or click Create to create the site.
10. The new site opens.
After creating sites, you might want to configure alternate access mappings. Alternate access
mappings direct users to the correct URLs during their interaction with Windows SharePoint
Services 3.0 (while browsing to the home page of a Windows SharePoint Services 3.0 Web site,
for example). Alternate access mappings enable Windows SharePoint Services 3.0 to map Web
requests to the correct Web applications and sites, and they enable Windows SharePoint
Services 3.0 to serve the correct content back to the user. For more information, see Plan
alternate access mappings (http://technet.microsoft.com/en-us/library/cc288609.aspx).
60
are using the Windows SharePoint Services Search service, we recommend that you configure
the trace log to save seven days of events.
You can use the Diagnostic Logging page in Central Administration to configure the maximum
number of trace log files to maintain and how long (in minutes) to capture events to each log file.
By default, 96 log files are kept, each one containing 30 minutes of events.
96 log files * 30 minutes of events per file = 2880 minutes or two days of events.
You can also specify the location where the log files are written or accept the default path.
Configure the trace log to save seven days of events
1. In Central Administration, on the Operations tab, in the Logging and Reporting section,
click Diagnostic logging.
2. On the Diagnostic Logging page, in the Trace Log section, do the following:
3. Ensure that the path specified in the Path box has enough room to store the extra log
files, or change the path to another location.
Tip:
We recommend that you store log files on a hard drive partition that is used to
store log files only.
4. Click OK.
Trace log files can help you to troubleshoot issues related to configuration changes of the
Windows SharePoint Services Search service. Because problems related to configuration
changes are not always immediately discovered, we recommend that you save all trace log files
that the system creates on any day that you make any configuration changes related to either
search service. Store these log files for an extended period of time in a safe location that will not
be overwritten. See step 3 in the previous procedure to determine the location that the system
stores trace log files for your system.
61
62
Install and configure Windows SharePoint Services 3.0 with Service Pack 1
Post-installation steps
As of Windows SharePoint Services 3.0 Service Pack 1 (SP1), you can now install Windows
SharePoint Services 3.0 on Windows Server 2008. As with the Windows Server 2003 operating
system, you must download and run Setup and the SharePoint Products and Technologies
Configuration Wizard. You cannot install Windows SharePoint Services 3.0 without service packs
on Windows Server 2008.
Important:
This article discusses how to do a clean installation of Windows SharePoint Services 3.0
with SP1 in a stand-alone environment on Windows Server 2008. It does not cover
upgrading the operating system from Windows Server 2003 to Windows Server 2008. For
more information about upgrading the operating system, see Upgrading to Windows
Server 2008 for Windows SharePoint Services 3.0 with SP1.
Note:
This article does not cover installing Windows SharePoint Services 3.0 in a server farm
installation on Windows Server 2008. For more information, see Deploy a simple farm on
the Windows Server 2008 operating system.
You can quickly publish a SharePoint site by deploying Windows SharePoint Services 3.0 on a
single server computer. A stand-alone configuration is useful if you want to evaluate Windows
SharePoint Services 3.0 features and capabilities, such as collaboration, document management,
and search. A stand-alone configuration is also useful if you are deploying a small number of Web
sites and you want to minimize administrative overhead. When you deploy Windows SharePoint
Services 3.0 on a single server using the default settings, the Setup program automatically
installs the Windows Internal Database and uses it to create the configuration database and an
initial content database for your SharePoint sites. Windows Internal Database uses SQL Server
technology as a relational data store for Windows roles and features only, such as Windows
SharePoint Services, Active Directory Rights Management Services, UDDI Services, Windows
Server Update Services, and Windows System Resources Manager.. In addition, Setup installs
the SharePoint Central Administration Web site and creates your first SharePoint site collection
and site.
63
Important:
The following components are required for Windows SharePoint Services 3.0 to run
correctly: the Web Server role, the Microsoft .NET Framework version 3.0, and Windows
Internal Database. Do not uninstall them, or Windows SharePoint Services 3.0 will cease
to run.
Note:
There is no direct upgrade from a stand-alone installation to a farm installation.
64
If you uninstall Windows SharePoint Services 3.0, and then later install Windows
SharePoint Services 3.0 on the same computer, the Setup program could fail when
creating the configuration database causing the entire installation process to fail. You can
prevent this failure by either deleting all the existing Windows SharePoint Services 3.0
databases on the computer or by creating a new configuration database. You can create
a new configuration database by running the following command from the path
%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\bin:
Download and run setup for Windows SharePoint Services 3.0 with SP1
1. Download Windows SharePoint Services 3.0 with SP1 from the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=105656), and then run SharePoint.exe.
2. On the Read the Microsoft Software License Terms page, review the terms, select the
I accept the terms of this agreement check box, and then click Continue.
3. On the Choose the installation you want page, click Basic to install to the default
location. To install to a different location, click Advanced, and then on the Data Location
tab, specify the location you want to install to and finish the installation.
4. When Setup finishes, a dialog box prompts you to complete the configuration of your
server. Be sure that the Run the SharePoint Products and Technologies
Configuration Wizard now check box is selected.
5. Click Close to start the wizard.
Note:
Do not add any server roles in Windows Server 2008 Server Manager before setup for
Windows SharePoint Services 3.0 is complete. If you add a server role, the setup
process will fail, and you will need to uninstall and reinstall Windows SharePoint Services
3.0.
Run the SharePoint Products and Technologies Configuration Wizard
1. On the Welcome to SharePoint Products and Technologies page, click Next.
2. In the dialog box that notifies you that some services might need to be restarted or reset
during configuration, click Yes.
3. On the Configuration Successful page, click Finish. Your new SharePoint site opens.
Note:
If you are prompted for your user name and password, you might need to add the
SharePoint site to the list of trusted sites and configure user authentication
settings in Internet Explorer. Instructions for configuring these settings are
provided in the following procedure.
Note:
If you see a proxy server error message, you might need to configure your proxy
server settings so that local addresses bypass the proxy server. Instructions for
configuring proxy server settings are provided later in this section.
Add the SharePoint site to the list of trusted sites
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Security tab, in the Select a Web content zone to specify its security settings
65
Post-installation steps
After Setup finishes, your browser window opens to the home page of your new SharePoint site.
Although you can start adding content to the site or you can start customizing the site, we
recommend that you perform the following administrative tasks by using the SharePoint Central
Administration Web site.
Configure incoming e-mail settings You can configure incoming e-mail settings so that
SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail
settings so that SharePoint sites can archive e-mail discussions as they happen, save emailed documents, and show e-mailed meetings on site calendars. In addition, you can
configure the SharePoint Directory Management Service to provide support for e-mail
distribution list creation and management. For more information, see Configure incoming email settings.
Configure outgoing e-mail settings You can configure outgoing e-mail settings so that
your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and
notifications to site administrators. You can configure both the "From" e-mail address and the
"Reply" e-mail address that appear in outgoing alerts. For more information, see Configure
outgoing e-mail settings.
Configure diagnostic logging settings You can configure several diagnostic logging
settings to help with troubleshooting. This includes enabling and configuring trace logs, event
66
Configure antivirus protection settings You can configure several antivirus settings if you
have an antivirus program that is designed for Windows SharePoint Services 3.0. Antivirus
settings enable you to control whether documents are scanned on upload or download and
whether users can download infected documents. You can also specify how long you want
the antivirus program to run before it times out, and you can specify how many execution
threads the antivirus program can use on the server. For more information, see Configure
anti-virus settings.
Create SharePoint sites When Setup finishes, you have a single Web application that
contains a single SharePoint site collection that hosts a SharePoint site. You can create more
SharePoint sites collections, sites, and Web applications if your site design requires multiple
sites or multiple Web applications. For more information, see Deploy and configure
SharePoint sites.
Note:
If you create additional Web applications to host SharePoint sites, you must also
configure Windows Firewall to allow communication on the ports for those Web
applications. For more information, see Deploy a simple farm on the Windows Server
2008 operating system.
Perform administrator tasks by using the Central Administration site
1. Click Start, point to All Programs, point to Administrative Tools, and then click
SharePoint 3.0 Central Administration.
2. On the Central Administration home page, under Administrator Tasks, click the task
you want to perform.
3. On the Administrator Tasks page, next to Action, click the task.
67
3. Ensure that the path specified in the Path box has enough room to store the extra log
files or change the path to another location.
Tip:
We recommend that you store log files on a hard drive partition that is used to
store log files only.
4. Click OK.
Trace log files can help you to troubleshoot issues related to configuration changes of the
Windows SharePoint Services Search service. Because problems related to configuration
changes are not always immediately discovered, we recommend that you save all trace log files
that the system creates on any day that you make any configuration changes related to the
search service. Store these log files for an extended period of time in a safe location that will not
be overwritten. See step 3 in the previous procedure to determine the location that the system
stores trace log files for your system.
68
69
Create a Web application and a site collection by using the Stsadm command-line tool
This article discusses how to do a clean installation of Windows SharePoint Services 3.0 in a
server-farm environment by using command-line tools.
Command-line tools enable you to customize the configuration of Windows SharePoint Services
3.0. Additionally, you can streamline deployment by using command-line tools in combination with
other administrator tools to automate unattended installations.
To install Windows SharePoint Services 3.0 on a server farm, you have to complete the following
steps:
1. Plan your deployment and ensure that you have installed all the software requirements.
2. Determine the required accounts that are used during installation.
3. Install Windows SharePoint Services 3.0 by running Setup at a command prompt and
specifying a configuration file.
4. Configure the server by using the Psconfig command-line tool with the appropriate options.
5. Create a Web application by using the Stsadm command-line tool.
6. Create a site collection by using the Stsadm command-line tool.
70
Windows SharePoint Services 3.0 on a clean installation of the Windows Server 2003
operating system with the most recent service pack. To install Windows SharePoint Services
3.0 on Windows Server 2008, see Chapter overview: End-to-end deployment scenarios.
Note:
All the instances of Windows SharePoint Services 3.0 in the farm must be in the
same language. For example, you cannot have both English and Japanese versions
of Windows SharePoint Services 3.0 in the same farm.
The Microsoft .NET Framework version 3.0. The .NET Framework version 3.0 download
contains the Windows Workflow Foundation technology, which is required by workflow
features.
Note:
You can also use the Microsoft .NET Framework version 3.5. You can download the
.NET Framework version 3.5 from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=110508).
ASP.NET 2.0 enabled in the Internet Information Services (IIS) Manager on all servers that
are running Windows SharePoint Services 3.0.
Microsoft SQL Server 2000 or Microsoft SQL Server 2005 with the most recent service pack
running on at least one database server before you install Windows SharePoint Services 3.0
on your Web servers.
To deploy a server farm, you must have at least one server computer acting as a Web server and
an application server, and one server computer acting as a database server.
Plan for administrative and service accounts (Windows SharePoint Services 3.0)
(http://technet.microsoft.com/en-us/library/cc288210.aspx)
71
The following table describes the accounts that are used during installation and configuration of
Windows SharePoint Services 3.0. You must create and configure these accounts before you run
Setup.
72
Account
Purpose
Requirements
securityadmin fixed
server role
73
The SharePoint.exe file has to be extracted, which you do at the command prompt:
drive:\path\SharePoint.exe /extract:drive:\path
The folder to which you extracted the SharePoint.exe file contains examples of configuration
(Config.xml) files. These example files are stored under the \Files folder in the root directory of
the DVD, in folders that correspond to different scenarios. These example files are described in
the following table.
Configuration file
Description
Setup\Config.xml
SetupFarmSilent\Config.xml
SetupGradualUpgradeSilent\Config.xml
SetupSilent\Config.xml
SetupUpgradeSilent\Config.xml
Note:
The example configuration files that are included with Windows SharePoint Services 3.0
omit the <Setting Id="SETUP_REBOOT"Value="Never"/> setting. You must include this
setting if you want to suppress restarts during a command-line installation.
Example
74
The following example shows the configuration for setting up a farm in silent mode
(SetupFarmSilent).
<Configuration>
<Package Id="sts">
<Setting Id="REBOOT" Value="ReallySuppress"/>
<Setting Id="SETUPTYPE" Value="CLEAN_INSTALL"/>
</Package>
<Logging Type="verbose" Path="%temp%" Template="Microsoft Windows SharePoint Services
3.0 Setup(*).log"/>
<Setting Id="SERVERROLE" Value="WFE"/>
<Setting Id="USINGUIINSTALLMODE" Value="0"/>
<Display Level="none" CompletionNotice="no" />
</Configuration>
Run Setup with a Config.xml file at a command prompt
1. On the drive on which Windows SharePoint Services 3.0 is installed, change to the root
directory to locate the setup.exe file.
2. Run Setup with the selected Config.xml file.
setup /config<path and file name>
Note:
You can select one of the example configuration files, or customize your own
configuration file.
3. Press ENTER.
Setup is now finished.
Example
To set up a farm in silent mode, type the following command at a command prompt, and then
press ENTER:
setup /config Files\SetupFarmSilent\config.xml
You can also customize your own configuration file. To control the installation, first edit the
Config.xml file in a text editor to include the elements that you want with the appropriate settings
for those elements. Then run setup /config<path and file name> to specify that Setup runs and
uses the options that you set in the Config.xml file. For example, a typical configuration option
includes adding a location for a log file, <Logging Type="off" | "standard"(default) | "verbose"
Path="path name" Template="file name.log"/>, which you can view if command-line installation
fails.
Important:
Use a text editor, such as Notepad, to edit the Config.xml file. Do not use a generalpurpose XML editor such as Microsoft Office Word 2007.
75
For more information about the options available for customizing the configuration file, see
Config.xml reference (Windows SharePoint Services 3.0).
For more information about the command-line options for Setup, see Setup.exe command-line
reference (https://technet.microsoft.com/en-us/library/cc288033.aspx).
76
77
78
stsadm -o extendvs
-url <URL name>
-ownerlogin <domain\user name>
-owneremail <e-mail address>
[-exclusivelyusentlm]
[ownername<display name>]
[databaseuser<database user name>]
[-databaseserver <database server name>]
[-databasename <new content database name>]
[databasepassword<database password>]
[lcid<language>]
[sitetemplate<site template>]
[description]
[sethostheader]
[-apidname <application pool name>]
[-apidtype {configurableID | NetworkService}]
[-apidlogin <domain\user name>]
[-apidpwd <application pool password>]
For more information, see Stsadm command-line tool (https://technet.microsoft.com/enus/library/cc288981.aspx) and Extendvs: Stsadm operation
(https://technet.microsoft.com/en-us/library/cc287873.aspx).
Example
The following command creates a Web application and a site collection with the URL
http://intranet that uses the corporate team site template.
stsadm -o extendvs -url http://intranet -ownerlogin <domain\user name> -owneremail
<user@domain.com>-sitetemplate STS#0 -exclusivelyusentlm -databaseserver <database
server name> -databasename <content database name> -apidname <application pool name>
-apidtype {configurableID | NetworkService} -apidlogin <domain\user name> -apidpwd
<password>
If you do not specify the template to use, site owners can choose the template when they first
browse to the site.
If you want to create additional Web applications or site collections by using the Stsadm
command-line tool, you can use either the extendvs or createsite operation.
The extendvs operation extends a Web application and creates a new content database. The
createsite operation creates a site collection at a specific URL with a specified user as site
owner.
Note:
The createsite operation does not create a new content database. If you want to create a
new content database together with the new site, see the createsiteinnewdb operation.
79
For more information, see Createsite: Stsadm operation (https://technet.microsoft.com/enus/library/cc287992.aspx) and Createsiteinnewdb: Stsadm operation
(https://technet.microsoft.com/en-us/library/cc288051.aspx).
The extendvs operation also enables administrators to specify the language of the site collection
by using the Locale ID (LCID) parameter. If you do not specify an LCID, the language of the
server is used for the site collection. For more information about the available LCID values, see
List of Locale ID (LCID) Values as Assigned by Microsoft(http://go.microsoft.com/fwlink/?
LinkId=63028&clcid=0x409).
After creating sites, you might want to configure alternate access mappings. Alternate access
mappings direct users to the correct URLs during their interaction with Windows SharePoint
Services 3.0 (while browsing to the home page of a Windows SharePoint Services 3.0 Web site,
for example). Alternate access mappings enable Windows SharePoint Services 3.0 to map Web
requests to the correct Web applications and sites, and they enable Windows SharePoint
Services 3.0 to serve the correct content back to the user. For more information, see Plan
alternate access mappings (http://technet.microsoft.com/en-us/library/cc288609.aspx).
80
Create a Web application and a site collection by using the Stsadm command-line tool
This article discusses how to install Windows SharePoint Services 3.0 on a stand-alone server or
on a server farm by using least-privilege administration.
The Windows SharePoint Services 3.0 standard configuration uses a set of user accounts and
installation settings for both stand-alone servers and server farms to simplify the installation
process. However, enterprises are often required to use the least-privilege security practice in
which each service or user is provided with only the minimum permissions and group
memberships that they must have to do the tasks that they are authorized to perform. Installing
Windows SharePoint Services 3.0 to meet least-privilege requirements requires additional
preparation and configuration steps. We strongly recommend that you use least-privilege
administration.
To install Windows SharePoint Services 3.0 by using least-privilege administration on either a
stand-alone server or a server farm, you must complete the following steps:
1. Plan the deployment and ensure that you have installed all the software requirements.
2. Determine the required accounts that are used during installation.
3. Use the least-privilege Setup user account to install Windows SharePoint Services 3.0 by
using Setup at a command prompt, and specifying a configuration file.
4. Configure the server by using the Psconfig command-line tool with the appropriate options.
5. Create a Web application by using the Stsadm command-line tool (only applies on serverfarm installations).
6. Create a site collection by using the Stsadm command-line tool (only applies on server-farm
installations).
81
Windows SharePoint Services 3.0 for a server farm environment. Ensure that you have the
following software requirements before you run Setup in any deployment:
Windows SharePoint Services 3.0 on a clean installation of the Windows Server 2003
operating system with the most recent service pack. To install Windows SharePoint Services
3.0 on Windows Server 2008, see Chapter overview: End-to-end deployment scenarios.
Note:
All the instances of Windows SharePoint Services 3.0 in the farm must be in the
same language. For example, you cannot have both English and Japanese versions
of Windows SharePoint Services 3.0 in the same farm.
The Microsoft .NET Framework version 3.0. The .NET Framework version 3.0 download
contains the Windows Workflow Foundation technology, which is required by workflow
features.
Note:
You can also use the Microsoft .NET Framework version 3.5. You can download
the .NET Framework version 3.5 from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=110508).
ASP.NET 2.0 enabled in Internet Information Services (IIS) Manager on all servers that are
running Windows SharePoint Services 3.0.
Microsoft SQL Server 2000 or Microsoft SQL Server 2005 with the most recent service pack
running on at least one database server before you install Windows SharePoint Services 3.0
on the Web servers.
To deploy a server farm, you must have at least one server computer acting as a Web server and
an application server, and one server computer acting as a database server.
Plan for administrative and service accounts (Windows SharePoint Services 3.0)
(http://technet.microsoft.com/en-us/library/cc288210.aspx)
Many requirements and configuration steps for installing Windows SharePoint Services 3.0 by
using least-privilege administration resemble the standard farm installation, with which you should
be familiar. For more information about the standard farm installation, see Install Windows
SharePoint Services 3.0 for a server farm environment.
82
The following table describes the accounts that are used to install Windows SharePoint Services
3.0 by using least-privilege administration, compared to the standard account requirements for
farm installation.
Account
Purpose
Least-privilege
requirements
administration using
domain user accounts
requirements
Setup user
account
following:
Setup on each
server.
The SharePoint
Products and
Technologies
Configuration
Wizard.
The Psconfig
command-line tool.
The Stsadm
command-line tool.
securityadmin fixed
server role
dbcreator fixed
server role
Use a separate
domain user
account.
83
Account
Purpose
Least-privilege
requirements
administration using
domain user accounts
requirements
Server farm
account or
database
access
account
Configure and
manage the server
farm.
Act as the
application pool
identity for the
SharePoint Central
Administration Web
site.
Run the Windows
SharePoint
Services Timer
service.
automatically added as a
SQL Server login on the
computer that is running SQL
Server and added to the
following SQL Server security
roles:
securityadmin fixed
server role
db_owner fixed
database role for all
databases in the server
farm
Use a separate
domain user
account.
The server farm
account is not a
member of the
Administrators
group on any
server in the server
farm. This includes
the computer that
is running SQL
Server.
The server farm
account does not
require
permissions to
SQL Server before
you create the
configuration
database.
By using separate service accounts for each service and limiting the permissions assigned to
each account, you reduce the opportunity for a malicious user or process to compromise the
environment.
You can implement least-privilege administration in many ways, depending upon the security
configuration of each scenario. The configurations for least-privilege administration include:
84
The SharePoint.exe file has to be extracted, which you do at the command prompt:
drive:\path\SharePoint.exe /extract:drive:\path
The folder to which you extracted the SharePoint.exe file contains examples of configuration
(Config.xml) files. These example files are stored under the \Files folder in the root directory of
the DVD, in folders that correspond to different scenarios. The example files are listed and
described in the following table.
Configuration file
Description
Setup\Config.xml
SetupFarmSilent\Config.xml
SetupGradualUpgradeSilent\Config.xml
SetupSilent\Config.xml
SetupUpgradeSilent\Config.xml
Important:
The example configuration files that are included with Windows SharePoint Services 3.0
omit the <Setting Id="SETUP_REBOOT" Value="Never"/> setting. You must include this
setting if you want to suppress restarts during a command-line installation.
85
Example
The following example shows the configuration for setting up a farm in silent mode
(SetupFarmSilent).
<Configuration>
<Package Id="sts">
<Setting Id="REBOOT" Value="ReallySuppress"/>
<Setting Id="SETUPTYPE" Value="CLEAN_INSTALL"/>
</Package>
<Logging Type="verbose" Path="%temp%" Template="Microsoft Windows SharePoint Services
3.0 Setup(*).log "/>
<Setting Id="SERVERROLE" Value="WFE"/>
<Setting Id="USINGUIINSTALLMODE" Value="0"/>
<Display Level="none" CompletionNotice="no" />
</Configuration>
Run Setup with a Config.xml file at a command prompt
1. On the drive on which Windows SharePoint Services 3.0 is installed, change to the root
directory to locate the setup.exe file.
2. Run Setup with the selected Config.xml file.
setup /config<path and file name>
Note:
You can select one of the example configuration files, or customize your own
configuration file.
3. Press ENTER.
Setup is now complete.
Example
To set up a farm in silent mode, type the following command at a command prompt, and then
press ENTER:
setup /config Files\SetupFarmSilent\config.xml
You can also customize your own configuration file. To control the installation, first edit the
Config.xml file in a text editor to include the elements that you want with the appropriate settings
for those elements. Then run setup /config<path and file name> to specify that Setup runs and
uses the options that you set in the Config.xml file. For example, a typical configuration option
includes adding a location for a log file, <Logging Type="off" | "standard"(default) | "verbose"
Path="path" Template="file name.log"/>, which you can view if command-line installation fails.
Important:
Use a text editor, such as Notepad, to edit Config.xml. Do not use a general-purpose
XML editor such as Microsoft Office Word 2007.
86
For more information about the options available for customizing the configuration file, see
Config.xml reference (https://technet.microsoft.com/en-us/library/cc287749.aspx).
For more information about the command-line options for Setup, see Setup.exe command-line
reference (https://technet.microsoft.com/en-us/library/cc288033.aspx).
87
The following procedure describes how to configure the first server in the farm.
Configure Windows SharePoint Services 3.0 on a farm by using the Psconfig commandline tool
1. Log on by using the Setup user account that you created and configured previously.
2. On the drive on which SharePoint Products and Technologies is installed, change to the
following directory: %COMMONPROGRAMFILES%\Microsoft shared\Web server
extensions\12\Bin.
3. Create the configuration database:
psconfig-cmd configdb -create -server<database server name>-database<database
name>
[ -dbuser<domain\user name>-dbpassword<password>]
-user<domain\user name> -password<password>
-addomain<domain name>-adorgunit<org unit>
-admincontentdatabase<Central Administration Web application content database
name>
Note:
The dbuser and dbpassword parameters are only used in deployments that use
SQL Server authentication. If you are using Windows authentication, these
parameters are not necessary.
4. Install the Help collection:
psconfig-cmd helpcollections -installall
5. Perform resource security enforcement:
psconfig-cmd secureresources
6. Register services in the server farm:
psconfig-cmd services -install
Note:
After installing services, you must start and configure Windows SharePoint
Services Search by using the Stsadm command-line tool:
a. stsadm-o spsearch -action start -farmserviceaccount <domain\user name>
-farmservicepassword<password> [-database name<content database name>][database server<server instance>][-search server<search server name>]
For more information, see Spsearch: Stsadm operation
(https://technet.microsoft.com/en-us/library/cc288507.aspx).
Note:
Use the domain and user account information for the server farm account
that you previously created and configured.
b. Provision the services of the farm:
psconfig -cmd services provision:
88
89
90
For more information, see Stsadm command-line tool (https://technet.microsoft.com/enus/library/cc288981.aspx) and Extendvs: Stsadm operation
(https://technet.microsoft.com/en-us/library/cc287873.aspx).
Example
The following command creates a Web application and a site collection with the URL
http://intranet that uses the corporate team site template.
stsadm -o extendvs -url http://intranet -ownerlogin <domain\user name> -owneremail
<user@domain.com>sitetemplate STS#0 -exclusivelyusentlm -databaseserver <database
server name> -databasename <content database name> -apidname <application pool name>
-apidtype {configurableID | NetworkService}-apidlogin<domain\user name> -apidpwd
<password>
If you do not specify the template to use, site owners can choose the template when they first
browse to the site.
If you want to create additional Web applications or site collections by using the Stsadm
command-line tool, you can use either the extendvs or createsite operation.
The extendvs operation extends a Web application and creates a new content database. The
createsite operation creates a site collection at a specific URL with a specified user a site
collection owner and site collection administrator.
Note:
The createsite operation does not create a new content database. If you want to create a
new content database together with the new site, use the createsiteinnewdb operation.
For more information, see Createsite: Stsadm operation (https://technet.microsoft.com/enus/library/cc287992.aspx) and Createsiteinnewdb: Stsadm operation
(https://technet.microsoft.com/en-us/library/cc288051.aspx).
The extendvs operation also enables you to specify the language of the site collection by using
the Locale ID (LCID) parameter. If you do not specify an LCID, the language of the server is used
for the top-level site collection. For more information about the available LCID values, see List of
Locale ID (LCID) Values as Assigned by Microsoft (http://go.microsoft.com/fwlink/?
LinkId=63028&clcid=0x409).
After creating sites, you might want to configure alternate access mappings. Alternate access
mappings direct users to the correct URLs during their interaction with Windows SharePoint
Services 3.0 (while browsing to the home page of a Windows SharePoint Services 3.0 Web site,
for example). Alternate access mappings enable Windows SharePoint Services 3.0 to map Web
requests to the correct Web applications and sites, and they enable Windows SharePoint
Services 3.0 to serve the correct content back to the user. For more information, see Plan
alternate access mappings (http://technet.microsoft.com/en-us/library/cc288609.aspx).
91
By default, Windows SharePoint Services 3.0 saves two days of events in the trace log files. This
means that trace log files that contain events that are older than two days are deleted. When you
are using the Windows SharePoint Services Search service, we recommend that you configure
the trace log to save seven days of events.
You can use the Diagnostic Logging page in Central Administration to configure the maximum
number of trace log files to maintain, and how long (in minutes) to capture events to each log file.
By default, 96 log files are kept, each one containing 30 minutes of events.
96 log files * 30 minutes of events per file = 2880 minutes or two days of events.
You can also specify where the log files are written or accept the default path.
Trace log files can help you troubleshoot issues related to configuration changes of the Windows
SharePoint Services Search service. Because problems related to configuration changes are not
always immediately discovered, we recommend that you save all trace log files that the system
creates on any day that you make any configuration changes. Store these log files for some time
in a safe location that will not be overwritten. We recommend that you store log files on a hard
disk drive partition that is used to store log files only.
92
93
94
Suggested topologies
Server farm environments can encompass a wide range of topologies, and can include many
servers or as few as two servers.
A server farm typically consists of a database server running either Microsoft SQL Server 2005 or
Microsoft SQL Server 2000 with the most recent service pack, and one or more servers running
Internet Information Services (IIS) and Windows SharePoint Services 3.0. In this configuration,
the front-end servers are configured as Web servers. The Web server role provides Web content
and services such as search.
A large server farm typically consists of two or more clustered database servers, several loadbalanced front-end Web servers running IIS and Windows SharePoint Services 3.0, and two or
more servers providing search services.
95
To deploy Windows SharePoint Services 3.0 in a server farm environment, you must provide
credentials for several different accounts. For information about these accounts, see Plan for
administrative and service accounts.
You must install Windows SharePoint Services 3.0 on the same drive on all load-balanced
front-end Web servers.
All the instances of Windows SharePoint Services 3.0 in the farm must be in the same
language. For example, you cannot have both an English version of Windows SharePoint
Services 3.0 and a Japanese version of Windows SharePoint Services 3.0 in the same farm.
You must install Windows SharePoint Services 3.0 on a clean installation of the Microsoft
Windows Server 2003 operating system with the most recent service pack. If you uninstall a
previous version of Windows SharePoint Services 3.0, and then install Windows SharePoint
Services 3.0, Setup might fail to create the configuration database and the installation will fail.
Note:
We recommend that you read the Known Issues/Readme documentation before you
install Windows SharePoint Services 3.0 on a domain controller. Installing Windows
SharePoint Services 3.0 on a domain controller requires additional configuration
steps that are not discussed in this article.
Installing available language template packs on front-end Web servers (optional). For more
information about installing language template packs, see Deploy language packs (Windows
SharePoint Services 3.0).
96
For more information about creating site collections and sites, see Deploy and configure
SharePoint sites.
97
Required accounts
Before installing Windows SharePoint Services 3.0, you must prepare the database server.
The database server must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000
with the most recent service pack.
The Windows SharePoint Services 3.0 Setup program automatically creates the necessary
databases when you install and configure Windows SharePoint Services 3.0. Optionally, you can
preinstall the required databases if your IT environment or policies require this.
For more information about prerequisites, see Determine hardware and software requirements.
If you are using SQL Server 2005, you must also change the surface area settings.
Configure surface area settings in SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to
Configuration Tools, and then click SQL Server Surface Area Configuration.
2. In the SQL Server 2005 Surface Area Configuration dialog box, click Surface Area
Configuration for Services and Connections.
3. In the tree view, expand the node for your instance of SQL Server, expand the Database
Engine node, and then click Remote Connections.
4. Select Local and Remote Connections, select Using both TCP/IP and named pipes,
and then click OK.
Required accounts
The following table describes the accounts that are used to configure Microsoft SQL Server and
to install Windows SharePoint Services 3.0. For more information about the required accounts,
including specific privileges required for these accounts, see Plan for administrative and service
accounts (http://technet.microsoft.com/en-us/library/cc288210.aspx).
98
Account
Purpose
99
Before you install and configure Windows SharePoint Services 3.0, be sure that your servers
have the recommended hardware and software. To deploy a server farm, you need at least one
server acting as a Web server and an application server, and one server acting as a database
server.
For more information about these requirements, see Determine hardware and software
requirements (http://technet.microsoft.com/en-us/library/cc288751.aspx).
100
101
SharePoint Services 3.0 be a server from which you want to run the Central
Administration Web site.
Run Setup on the first server
1. On the Read the Microsoft Software License Terms page, review the terms, select the I
accept the terms of this agreement check box, and then click Continue.
2. On the Choose the installation you want page, click Advanced. The Basic option is for
stand-alone installations.
3. On the Server Type tab, click Web Front End. The Stand-alone option is for standalone installations.
4. Optionally, to install Windows SharePoint Services 3.0 at a custom location, select the
Data Location tab, and then type the location name or Browse to the location.
5. Optionally, to participate in the Customer Experience Improvement Program, select the
Feedback tab and select the option you want. To learn more about the program, click the
link. You must have an Internet connection to view the program information.
6. When you have chosen the correct options, click Install Now.
7. When Setup finishes, a dialog box appears that prompts you to complete the
configuration of your server. Be sure that the Run the SharePoint Products and
Technologies Configuration Wizard now check box is selected.
8. Click Close to start the configuration wizard. Instructions for completing the wizard are
provided in the next set of steps.
102
6. In the User name box, type the user name of the server farm account. (Be sure to type
the user name in the format DOMAIN\username.)
Important
This account is the server farm account and it is used to access your configuration database.
It also acts as the application pool identity for the SharePoint Central Administration
application pool, and it is the account under which the Windows SharePoint Services Timer
service runs. The SharePoint Products and Technologies Configuration Wizard adds this
account to the SQL Server Logins, the SQL Server Database Creator server role, and the
SQL Server Security Administrators server role.
The user account that you specify for this service account must be a domain user account.
Because this account does not require a high level privilege, we recommend that you follow
the principle of least privilege, and specify a user account that is not a member of the
Administrators group on your Web servers or your back-end servers.
7. In the Password box, type the user's password, and then click Next.
8. On the Configure SharePoint Central Administration Web Application page, select the
Specify port number check box; type a port number if you want the SharePoint Central
Administration Web application to use a specific port, or leave the Specify port number
check box cleared if you do not care which port number the SharePoint Central
Administration Web application uses.
9. In the Configure SharePoint Central Administration Web Application dialog box, do
one of the following:
If you want to use Kerberos authentication, click Negotiate (Kerberos), and then
click Next.
Note:
In most cases, use the default setting (NTLM). Use Negotiate (Kerberos)
only if Kerberos authentication is supported in your environment. Using the
Negotiate (Kerberos) option requires you to configure a Service Principal
Name (SPN) for the domain user account. To do this, you must be a member
of the Domain Admins group. For more information, see How to configure a
Windows SharePoint Services virtual server to use Kerberos authentication
and how to switch from Kerberos authentication back to NTLM authentication
(http://go.microsoft.com/fwlink/?LinkID=76570&clcid=0x409).
10. On the Completing the SharePoint Products and Technologies Configuration Wizard
page, click Next.
11. On the Configuration Successful page, click Finish.
The SharePoint Central Administration Web site home page opens.
Note:
If you are prompted for your user name and password, you might need to add the
SharePoint Central Administration Web site to the list of trusted sites, and then
configure user authentication settings in Internet Explorer. Instructions for
103
104
105
106
Language packs enable site owners and site collection administrators to create SharePoint sites
and site collections in multiple languages without requiring separate installations of Windows
SharePoint Services 3.0. You install language packs, which contain language-specific site
templates, on your front-end Web servers. When an administrator creates a site or a site
collection based on a language-specific site template, the text that appears on the site or the site
collection is displayed in the site template's language. Language packs are typically used in
multinational deployments where a single server farm supports people in different locations or in
situations where sites and Web pages must be duplicated in one or more languages.
Note:
You cannot change an existing site, site collection, or Web page from one language to
another by applying different language-specific site templates; once you choose a
language-specific site template for a site or a site collection, the site or site collection will
always display content in the language of the original site template.
Word breakers and stemmers enable you to efficiently and effectively search across content on
SharePoint sites and site collections in multiple languages without requiring separate installations
of Windows SharePoint Services 3.0. Word breakers and stemmers are automatically installed on
your front-end Web servers by Setup.
You can install language lacks for Windows SharePoint Services 3.0 from the Microsoft Download
site, at "Windows SharePoint Services 3.0 Language Pack"
(http://www.microsoft.com/downloads/details.aspx?FamilyID=36ee1bf0-652c-4e38-b247f29b3eefa048&DisplayLang=en).
Important:
If you are uninstalling Windows SharePoint Services 3.0, you must uninstall all language
packs before you uninstall Windows SharePoint Services 3.0.
107
toolbars, navigation bars, lists, and column headings appear in French. Likewise, if a site
administrator chooses to create a site in Arabic, the site's toolbars, navigation bars, lists, and
column headings appear in Arabic, and the default left-to-right orientation of the site changes to a
right-to-left orientation to properly display Arabic text.
The list of available languages that a site administrator can use to create a site or site collection is
generated by the language packs that are installed on your front-end Web servers. By default,
sites and site collections are created in the language in which Windows SharePoint Services 3.0
was installed. For example, if you install the Spanish version of Windows SharePoint Services
3.0, the default language for sites, site collections, and Web pages is Spanish. If a site
administrator needs to create sites, site collections or Web pages in a language other than the
default Windows SharePoint Services 3.0 language, you must install the language pack for that
language on your front-end Web servers. For example, if you are running the French version of
Windows SharePoint Services 3.0, and a site administrator wants to create sites in French,
English, and Spanish, you must install the English and Spanish language packs on your front-end
Web servers.
Note:
By default, when a site administrator creates a new Web page within a site, the Web
page uses the site's language ID to display text.
Language packs for Windows SharePoint Services 3.0 are not bundled into multilingual
installation packages. You must install a specific language pack for each language that you want
to support. Also, language packs must be installed on each of your front-end Web servers to
ensure that each Web server can render content in the specified language.
The following table lists the language packs that are available for Windows SharePoint Services
3.0.
Language
Country/Region
Language ID
German
Germany
1031
English
United States
1033
Japanese
Japan
1041
Although a site administrator specifies a language ID for a site, some user interface elements
such as error messages, notifications, and dialog boxes do not display in the language that was
specified. This is because Windows SharePoint Services 3.0 relies on several supporting
technologies for example, the Microsoft .NET Framework, Microsoft Windows Workflow
Foundation, Microsoft ASP.NET, and Microsoft SQL Server 2005 some of which are localized
into only a limited number of languages. If a user interface element is generated by any of the
supporting technologies that is not localized into the language that the site administrator specified
for the site, the user interface element appears in English. For example, if a site administrator
creates a site in Hebrew, and the.NET Framework component displays a notification message,
the notification message will not display in Hebrew because the .NET Framework is not localized
into Hebrew. This situation can occur when sites are created in any language except the
following: Chinese, French, German, Italian, Japanese, Korean, and Spanish.
108
In some cases, some text might originate from the original installation language, which can create
a mixed-language experience. This type of mixed-language experience is typically seen only by
content creators or site administrators and is not seen by site users.
Install Windows SharePoint Services 3.0 on each of your front-end Web servers.
Run the SharePoint Products and Technologies Configuration Wizard on each of your frontend Web servers.
Language files are used by the operating system and provide support for displaying and entering
text in multiple languages. Language files include:
Keyboard files
Most language files are installed by default on the Microsoft Windows Server 2003 operating
system. However, you must install supplemental language files for East Asian languages and
languages that use complex script or require right-to-left orientations. The East Asian languages
include Chinese, Japanese, and Korean; the complex script and right-to-left oriented languages
include Arabic, Armenian, Georgian, Hebrew, the Indic languages, Thai, and Vietnamese.
Instructions for installing these supplemental language files are provided in the following
procedure.
We recommend that you install these language files only if you need them. The East Asian files
require about 230 megabytes of hard disk space. The complex script and right-to-left languages
do not use much disk space, but installing either set of files might reduce performance when
entering text.
Note:
You must be a member of the Administrators group on the computer to install these
language files. After the language files are installed, the languages are available to all
users of the computer.
Note:
You will need your Windows Server 2003 product disc to perform this procedure, or you
will need to know the location of a shared folder that contains your operating system
installation files.
109
Note:
You must restart your computer after you install supplemental language files.
Install additional language files
1. On your front-end Web server, click Start, point to Settings and then Control Panel, and
then click Regional and Language Options.
2. In the Regional and Language Options dialog box, on the Languages tab, in the
Supplemental Language Support section, select one or both of the following
checkboxes:
3. Click OK in the dialog box that alerts you that additional disk space is required for the
files.
4. Click OK to install the additional language files.
5. When prompted, insert your Windows Server 2003 product disc or provide the location of
your Windows Server 2003 installation files.
6. When prompted to restart your computer, click Yes.
After you install the necessary language files on your front-end servers, you need to install
Windows SharePoint Services 3.0 and run the SharePoint Products and Technologies
Configuration Wizard. The wizard creates and configures the configuration database and
performs other configuration tasks that must be done before you install language packs. For more
information about installing Windows SharePoint Services 3.0 and running the SharePoint
Products and Technologies Configuration Wizard, see Deploy in a simple server farm and Install
Windows SharePoint Services 3.0 on a stand-alone computer.
110
accept the terms of this agreement check box, and then click Continue.
3. The setup wizard runs and installs the language pack.
4. Rerun the SharePoint Products and Technologies Configuration Wizard, using the default
settings. If you do not run the SharePoint Products and Technologies Configuration
Wizard after you install a language pack, the language pack will not be installed properly.
Rerun the SharePoint Products and Technologies Configuration Wizard
1. Click Start, point to All Programs, point to Administrative Tools, and then click
SharePoint Products and Technologies Configuration Wizard.
2. On the Welcome to SharePoint Products and Technologies page, click Next.
3. Click Yes in the dialog box that alerts you that some services might need to be restarted
during configuration.
4. On the Modify server farm settings page, click Do not disconnect from this server
farm, and then click Next.
5. If the Modify SharePoint Central Administration Web Administration Settings page
appears, do not modify any of the default settings, and then click Next.
6. On the Completing the SharePoint Products and Technologies Configuration Wizard
page, click Next.
7. On the Configuration Successful page, click Finish.
When you install language packs, the language-specific site templates are installed in the
\Program Files\Common Files\Microsoft Shared\web server extensions\12\template\number
directory, where number is the Language ID for the language that you are installing. For example,
the US English language pack installs to the \Program Files\Common Files\Microsoft Shared\web
server extensions\12\template\1033 directory. After you install a language pack, site owners and
site collection administrators can create sites and site collections based on the language-specific
site templates by specifying a language when they are creating a new SharePoint site or site
collection.
111
112
Configure incoming e-mail settings You can configure incoming e-mail settings so that
SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail
settings so that SharePoint sites can archive e-mail discussions as they happen, save emailed documents, and show e-mailed meetings on site calendars. In addition, you can
configure the SharePoint Directory Management Service to provide support for e-mail
distribution list creation and management. For more information, see Configure incoming email settings.
Configure outgoing e-mail settings You can configure outgoing e-mail settings so that
your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and
notifications to site administrators. You can configure both the "From" e-mail address and the
"Reply" e-mail address that appear in outgoing alerts. You can also configure outgoing e-mail
settings for all Web applications or for only one Web application. For more information, see
Configure outgoing e-mail settings and Configure outgoing e-mail settings for a specific Web
application.
Create SharePoint sites When Setup finishes, you have a single Web application that
hosts a single SharePoint site. If your site design requires multiple sites or multiple Web
applications, you can create more SharePoint sites and Web applications. For more
information, see Deploy and configure SharePoint sites.
Configure workflow settings You can configure workflow settings to enable end users to
create their own workflows by using code pre-generated by administrators. You can also
configure whether internal users without site access can receive workflow alerts, and whether
external users can participate in workflows by receiving copies of documents by e-mail. For
more information, see Configure workflow settings.
Configure diagnostic logging settings You can configure several diagnostic logging
settings to help with troubleshooting. These include enabling and configuring trace logs,
event messages, user-mode error messages, and Customer Experience Improvement
Program events. For more information, see Configure diagnostic logging settings.
Configure antivirus settings You can configure several antivirus settings if you have an
antivirus program that is designed for Windows SharePoint Services 3.0. Antivirus settings
113
allow you to control whether documents are scanned on upload or on download, and whether
users can download infected documents. You can also specify how long you want the
antivirus program to run before it times out, and you can specify how many execution threads
the antivirus program can use on the server. For more information, see Configure anti-virus
settings.
You can use the following procedure to configure optional administrative settings using
SharePoint Central Administration.
Configure administrative settings using SharePoint Central Administration
1. Click Start, point to All Programs, point to Administrative Tools, and then click
SharePoint 3.0 Central Administration.
2. On the SharePoint Central Administration home page, under Administrative Tasks,
click the administrative task that you want to perform.
3. On the Administrative Tasks page, next to Action, click the task.
114
Use this procedure to configure the incoming e-mail settings for Windows SharePoint Services
3.0.
The features of Windows SharePoint Services 3.0 that use incoming e-mail are not available until
these settings are configured.
Before you configure incoming e-mail settings in Windows SharePoint Services 3.0, confirm that:
One or more servers in your server farm are running the Internet Information Services (IIS)
Simple Mail Transfer Protocol (SMTP) service, or you know the name of another server that is
running the SMTP service. This server must be configured to accept relayed e-mail from the
mail server for the domain.
One or more servers in your server farm are running the Microsoft SharePoint Directory
Management Service, or you know the name of another server that is running the SharePoint
Directory Management Web Service.
The application pool account for the SharePoint Central Administration Web site has the
Create, delete, and manage user accounts right to the container in the Active Directory
directory service.
The application pool account for Central Administration, the logon account for the Windows
SharePoint Services Timer service, and the application pool accounts for your Web
applications have the correct permissions to the e-mail drop folder.
The domain controller running Active Directory has a Mail Exchanger (MX) entry in DNS
Manager for the mail server that you plan to use for incoming e-mail.
Note:
All of these configuration steps are described in detail in the following sections.
115
recommended because administrators of the other server can affect the availability of incoming email by changing the configuration of SMTP, and because this requires the additional step of
configuring permissions to the e-mail drop folder.
If a drop folder is not used, the SMTP service must be installed on each server that is used to
receive and process incoming e-mail. Typically, this includes every front-end Web server in the
farm.
116
117
118
3. Type the name of the organizational unit, and then click OK.
After creating the organization unit, we recommend that you delegate the Create, delete, and
manage user accounts right to the container.
Important:
Membership in the Domain Administrators group or the Enterprise Administrators group in
Active Directory, or delegated authority for administration, is required to complete this
procedure.
Delegate right to the application pool account
1. In Active Directory Users and Computers, find the organizational unit that you just
created.
2. Right-click the organizational unit, and then click Delegate control.
3. On the Welcome page of the Delegation of Control Wizard, click Next.
4. On the Users and Groups page, click Add, and then type the name of the application
pool identity account that the Web application uses.
5. In the Select Users, Computers, and Groups dialog box, click OK.
6. On the Users or Groups page of the Delegation of Control Wizard, click Next.
7. On the Tasks to Delegate page of the Delegation of Control Wizard, select the Create,
delete, and manage user accounts check box, and then click Next.
8. On the last page of the Delegation of Control Wizard, click Finish to exit the wizard.
If you must add permissions for the application pool identity account directly, complete the
following procedure.
Important:
Membership in the Account Operators group, Domain Administrators group, or the
Enterprise Administrators group in Active Directory, or delegated authority for
administration, is required to complete this procedure.
Add permissions for the application pool account
1. In Active Directory Users and Computers, click the View menu, and then click Advanced
Features.
2. Right-click the organizational unit that you just created, and then click Properties.
3. In the Properties dialog box, click the Security tab, and then click Advanced.
4. Click Add, and then type the name of the application pool identity account for the Web
application.
5. Click OK.
6. In the Permission Entries section, double-click the application pool identity account.
7. In the Permissions section, under Allow, select the Modify permissions check box.
8. Click OK to close the Permissions dialog box.
119
120
8. In the Permissions section, select Create all Child Objects and Delete all Child
Objects.
9. Click Next.
10. On the last page of the Delegation of Control wizard, click Finish to exit the wizard.
Delegating full control of the organizational unit to the Central Administration application pool
account enables administrators to enable e-mail for a list. Administrators cannot disable email for the list or document library after delegating full control because the Central
Administration account tries to delete the contact from the entire organizational unit rather
than deleting the contact from the list.
121
WSS_Admin_WPG, which includes the application pool account for Central Administration
and the logon account for the Windows SharePoint Services Timer service, has Full Control
permission.
WSS_WPG, which includes the application pool accounts for Web applications, has Read &
Execute, List Folder Contents, and Read permissions.
In some cases, these groups might not be configured automatically for the e-mail drop folder. For
example, if Central Administration is running as the Network Service account, the groups or
accounts needed for incoming e-mail will not be added when the e-mail drop folder is created. It
is a good idea to check whether these groups have been added automatically to the e-mail drop
122
folder. If the groups have not been added automatically, you can add them or add the specific
accounts that are required.
Important:
Membership in the Administrators group on the local computer that contains the e-mail
drop folder is required to complete this procedure.
Configure e-mail drop folder permissions
1. In Windows Explorer, right-click the drop folder, click Properties, and then click the
Security tab.
2. On the Security tab, under the Group or user names box, click the Add button.
3. In the Select Users, Computers, or Groups dialog box, in the Enter objects to select
box, type the name of the worker process group or application pool account for the Web
application, and then click OK.
Note:
This account is listed on the Identity tab of the Properties dialog box for the
application pool in IIS.
4. In the Permissions for User or Group box, next to Modify, select the Allow check box.
5. Click OK.
123
124
To accept only messages from authenticated users, click Yes for Accept messages
6. If you want to use a remote SharePoint Directory Management Web Service, select Use
remote.
a. In the Directory Management Service URL box, type the URL of the Microsoft
SharePoint Directory Management Service that you want to use.
b. In the SMTP mail server for incoming mail box, type the name of the SMTP mail
server. The server name must match the fully qualified domain name in the MX entry
for the mail server in DNS Manager on the domain server.
c.
To accept messages from authenticated users only, click Yes for Accept messages
from authenticated users only. Otherwise, click No.
d. To allow creation of distribution groups from SharePoint sites, click Yes for Allow
creation of distribution groups from SharePoint sites. Otherwise, click No.
7. If you do not want to use the Microsoft SharePoint Directory Management Service, click
No.
8. In the Incoming E-Mail Server Display Address section, type a display name for the email server (for example, mail.fabrikam.com) in the E-mail server display address box.
Tip:
You can specify the e-mail server address that is displayed when users create an
incoming e-mail address for a list or group. Use this setting together with the
Microsoft SharePoint Directory Management Service to provide an e-mail server
address that is more user-friendly.
9. In the Safe E-Mail Servers section, select one of the following options:
Accept mail from these safe e-mail servers. If you select this option, type the IP
addresses (one per line) of the e-mail servers that you want to specify as safe in the
corresponding box.
10. In the E-mail Drop Folder section, in the E-mail drop folder box, type the name of the
folder in which Microsoft Windows SharePoint Services polls for incoming e-mail from the
SMTP service.
This option is available only if you selected advanced mode.
11. Click OK.
125
126
Use this procedure to configure the default outgoing e-mail settings for all Web applications. You
can override the default outgoing e-mail settings for specific Web applications by using the
procedure that is described in Configure outgoing e-mail settings for a specific Web application.
127
128
129
Use this procedure to configure the outgoing e-mail settings for a specific Web application. Before
using this procedure, you must first configure the default outgoing e-mail settings for all Web
applications by using the procedure described in Configure outgoing e-mail settings.
130
9. When Windows has finished installing the SMTP service, on the Completing the Windows
Components Wizard page, click Finish.
131
132
133
the document, select Yes if you want documents to be sent to external users by e-mail
when those users are part of the workflow but they do not have access permissions to
the documents. If you do not want documents to be sent to external users who do not
have access permissions, select No.
Note:
If the object in the workflow is not a document but a list item, the list item
properties are displayed in a table as part of the e-mail message.
7. Click OK.
For information about how to perform this procedure using the Stsadm command-line tool, see
Workflow management: Stsadm properties.
134
Error reports
Event throttling
Use this procedure to configure the diagnostic logging settings for Windows SharePoint Services
3.0.
You can configure how diagnostic events are logged according to their criticality. Additionally, you
can set the maximum number of log files that can be maintained, and you can set how long to
capture events to a single log file.
You can also indicate whether or not to provide Microsoft with continuous improvement and Dr.
Watson event data.
Error reports
Error reports are created when your system encounters hardware or software problems. Microsoft
and its partners actively use these reports to improve the reliability of your software. Error reports
include the following: information regarding the condition of the server when the problem occurs;
the operating system version and computer hardware in use; and the Digital Product ID, which
can be used to identify your license. The IP address of your computer is also sent because you
are connecting to an online service to send error reports; however, the IP address is used only to
generate aggregate statistics.
Microsoft does not intentionally collect any personal information. However, error reports could
contain data from log files, such as user names, IP addresses, URLs, file or path names, and email addresses. Although this information, if present, could potentially be used to determine your
identity, the information will not be used in this way. The data that Microsoft collects will be used
only to fix problems and to improve software and services. Error reports will be sent by using
encryption technology to a database with limited access, and will not be used for marketing
purposes.
135
For more information, see the Microsoft Error Reporting Service privacy statement
(http://go.microsoft.com/fwlink/?LinkId=85028&clcid=0x409).
If you want to provide error reports to Microsoft and its partners, select the option to collect error
reports. Base your decision on your organization's policies about sharing the information
collected by error reports, and the potential impact of error collection on users and administrators.
Two options are available for error reports:
You can choose to periodically download a file from Microsoft that can help identify system
problems based on the error reports that you provide to Microsoft.
You can change the error collection policy to silently send all reports. This changes the
computer's error reporting behavior to automatically send reports to Microsoft without
prompting users when they log on.
Event throttling
You can configure the diagnostic options for event logging. Events can be logged in either the
Windows event log or the trace log. You can configure event throttling settings to control how
many events are recorded in each log, according to the criticality of the events. To provide more
control in event throttling, you can decide to throttle events for all events, or for any single
category of events. Several categories of events are available, based on different services and
features of SharePoint Products and Technologies.
Categories of events can be defined by individual services or by groupings of related events.
Selected event categories include:
All
Categories defined by product, such as Office SharePoint Server 2007 and Microsoft Office
Project Server 2007
Feature areas such as Document Management, E-Mail, Forms Services, Information Policy
Management, Information Rights Management, Publishing, Records Center, Site Directory,
Site Management, User Profiles, and Workflow
SharePoint Services and other services such as the Load Balancer Service
Shared services such as all Office Server Shared Services, Business Data, and Excel
Calculation Services
For the selected category, select the least-critical event to record, for both the Windows event log
and the trace log. Events that are equally critical to or more critical than the selected event will be
recorded in each log. The list entries are sorted in order from most-critical to least-critical.
The levels of events for the Windows event log include:
None
Error
Warning
Audit Failure
136
Audit Success
Information
None
Unexpected
Monitorable
High
Medium
Verbose
For more information about the Windows event log or the trace log, see the Windows
documentation.
If you select Yes, users can decide whether they want to report Customer Experience
Improvement Program events to Microsoft.
4. In the Error Reports section, under Error reporting, select one of the following:
Change this computer's error collection policy to silently send all reports. This
changes the computer's error reporting behavior to automatically send reports to
Microsoft without prompting users when they log on.
5. In the Event Throttling section, in the Select a category menu, select a category of
137
events:
a. In the Least critical event to report to the event log menu, select the least-critical
event to report to the event log for the selected category.
b. In the Least critical event to report to the trace log menu, select the least-critical
event to report to the trace log for the selected category.
6. In the Trace Log section, in the Path text box, type the local path to use for the trace log
on all servers in the farm. The location must exist on all servers in the farm.
a. In the Number of log files text box, type the maximum number of files that you want
to maintain.
b. In the Number of minutes to use a log file text box, type the number of minutes to
use each log file.
7. Click OK.
For information about how to perform this procedure using the Stsadm command-line tool, see
Listlogginglevels and Setlogginglevels.
138
Scan documents on upload: Select this setting to scan uploaded documents. This helps
prevent users with infected documents from distributing them to other users.
Scan documents on download: Select this setting to scan downloaded documents. This
helps prevent users from downloading infected documents by warning them about infected
files. Users can still choose to download infected files, unless the option to allow users to
download infected documents is not selected.
Allow users to download infected documents: If this option is selected, users can
download infected documents. In most cases, do not select this option. Unless you have a
specific reason to download infected documents, such as troubleshooting a virus infection on
your system, do not select this option.
Attempt to clean infected documents: Select this setting to automatically clean infected
documents that were discovered during scanning.
Administrative credentials
Membership in the Administrators group of the Central Administration site is required to complete
this procedure.
Configure antivirus settings
1. On the top navigation bar, click Operations.
2. On the Operations page, in the Security Configuration section, click Antivirus.
3. On the Antivirus page, in the Antivirus Settings section, select one or all of the
following:
4. Click OK.
For information about how to perform this procedure using the Stsadm command-line
tool, see Antivirus: Stsadm properties (http://technet.microsoft.com/enus/library/cc288097.aspx)
139
140
Configure authentication
In this article:
To use a Windows authentication mechanism, you need an environment that supports user
accounts that can be authenticated by a trusted authority.
If you use a Windows authentication mechanism, the operating system performs user
credential management tasks. If you use an authentication provider other than Windows,
such as forms authentication, you must plan and implement a credential management system
and determine where to store user credentials.
Windows SharePoint Services 3.0 authentication for is built on the ASP.NET authentication model
and includes three authentication providers:
You can use the Active Directory directory service for authentication, or you can design your
environment to validate user credentials against other data stores, such as a Microsoft SQL
Server database, a lightweight directory access protocol (LDAP) directory, or any other directory
that has an ASP.NET 2.0 membership provider. The membership provider specifies the type of
data store you are going to use. The default ASP.NET 2.0 membership provider uses a SQL
Server database. ASP.NET 2.0 includes a SQL Server membership provider.
The authentication providers are used to authenticate against user and group credentials that are
stored in Active Directory, in a SQL Server database, or in a Non-Active Directory LDAP directory
service (such as NDS). For more information about ASP.NET membership providers, see
141
Anonymous authentication
Anonymous authentication enables users to find resources in the public areas of Web sites
without having to provide authentication credentials. Internet Information Services (IIS)
creates the IUSR_computername account to authenticate anonymous users in response to a
request for Web content. The IUSR_computername account, where computername is the
name of the server that is running IIS, gives the user access to resources anonymously under
the context of the IUSR account. You can reset anonymous user access to use any valid
Windows account. In a stand-alone environment, the IUSR_computername account is on the
local server. If the server is a domain controller, the IUSR_computername account is defined
for the domain. By default, anonymous access is disabled when you create a new Web
application. This provides an additional layer of security, because IIS rejects anonymous
access requests before they can ever be processed if anonymous access is disabled.
Basic authentication
Basic authentication requires previously assigned Windows account credentials for user
access. Basic authentication enables a Web browser to provide credentials when making a
request during an HTTP transaction. Because user credentials are not encrypted for network
transmission, but are sent over the network in plaintext, using basic authentication over an
unsecured HTTP connection is not recommended. To use basic authentication, you should
enable Secure Sockets Layer (SSL) encryption.
Digest authentication
Digest authentication provides the same functionality as basic authentication, but with
increased security. User credentials are encrypted instead of being sent over the network in
plaintext. User credentials are sent as an MD5 message digest in which the original user
name and password cannot be deciphered. Digest authentication uses a challenge/response
protocol that requires the authentication requestor to present valid credentials in response to
a challenge from the server. To authenticate against the server, the client has to supply an
MD5 message digest in a response that contains a shared secret password string. The MD5
Message-Digest Algorithm is described in detail in Internet Engineering Task Force (IETF)
RFC 1321 (http://www.ietf.org).
To use digest authentication, note the following requirements:
142
The user and IIS server must be members of, or trusted by, the same domain.
Users must have a valid Windows user account stored in Active Directory on the domain
controller.
The domain must use a Microsoft Windows Server 2003 domain controller.
You must install the IISSuba.dll file on the domain controller. This file is copied
automatically during Windows Server 2003 Setup.
143
The user and IIS server must be members of, or trusted by, the same domain.
Users must have a valid Windows user account stored in Active Directory on the domain
controller.
The domain must use a Microsoft Windows Server 2003 domain controller.
You must install the IISSuba.dll file on the domain controller. This file is copied automatically
during Windows Server 2003 Setup.
You must install Windows Server 2003 with SP2 or later. Windows SharePoint Services 3.0
does not support digest authentication on Windows Server 2003 with SP1 or earlier.
To enable digest authentication to work with browsers other than Microsoft Internet Explorer
6.0 or Internet Explorer 7.0, you must install the IIS hotfix described in Knowledge Base
article 932729. For information about this hotfix, see FIX: Error message when you try to
access a Web site that is hosted on IIS 6.0: Access Denied (http://go.microsoft.com/fwlink/?
LinkId=92784&clcid=0x409).
144
At this point use the IIS Management Console to configure IIS to enable digest authentication.
145
146
In addition, ASP.NET supports the use of pluggable authentication providers, which means that
you can write an authentication provider to support any credential store that you want to use.
A database
To enable forms-based authentication for a Windows SharePoint Services 3.0 Web site and add
users to the user account database, perform the following procedures.
Create a new site
1. On the home page of the SharePoint Central Administration Web site, click Application
Management.
2. On the Application Management page, in the SharePoint Web Application
Management section, click Create or extend Web application.
147
3. On the Create or Extend Web Application page, click Create a new Web application.
4. On the Create New Web Application page, in the Security Configuration section, make
sure NTLM is selected under Authentication provider. Also, select Yes under Allow
Anonymous.
5. Use the default entries to complete the new Web application creation procedure and click
OK.
At this point, you have created a new site placeholder. Use the following procedure to create a
site collection.
Create a site collection
1. On the top link bar, click Application Management.
2. On the Application Management page, in the SharePoint Site Management section,
click Create site collection.
3. On the Create Site Collection page, in the Web Application section, verify that the Web
application in which you want to create the site collection is selected.
If it is not, click Change Web Application on the Web Application menu. Then, on the
Select Web Application page, click the Web application in which you want to create the
site collection.
4. In the Title and Description section, type the title and description for the site collection.
5. In the Web Site Address section, under URL, select the path to use for your URL.
Note:
If you select a wildcard inclusion path, you must also type the site name to use in
the URL of your site. The paths available for the URL option are taken from the
list of managed paths that have been defined as wildcard inclusions.
6. In the Template Selection section, in the Select a template list, select the template that
you want to use for the top-level site in the site collection.
7. In the Primary Site Collection Administrator section, enter the user name (in the form
domain\username) for the user who will be the site collection administrator.
8. If you want to identify a user as the secondary owner of the new top-level Web site
(recommended), in the Secondary Site Collection Administrator section, enter the
user name for the secondary administrator of the site collection.
9. If you are using quotas to limit resource use for site collections, in the Quota Template
section, click a template in the Select a quota template list.
10. Click OK.
At this point, you have created a site collection. Use the following procedure to configure a formsbased authentication provider.
Configure a forms-based authentication provider
1. On the home page of the SharePoint Central Administration Web site, click Application
Management.
148
If you select Yes, features that start client applications according to document types
will be enabled. This option will not work correctly with some types of forms-based
authentication.
If you select No, features that start client applications according to document types
will be disabled. Users will have to download documents and then upload them after
they make changes.
Notes
149
because client integration does not natively support forms-based authentication. You might be
able to use many client integration features with forms-based authentication, and there are
workarounds available to implement varying levels of client integration functionality with
forms-based authentication. However, if published workarounds are inadequate, or if you find
unexpected issues using workarounds, we do not provide support and there are no product
changes to address these issues. If you plan to use client integration with forms-based
authentication, you must fully test any available solutions or workarounds to determine if the
performance and functionality are acceptable in your environment.
Product Support can provide commercially reasonable support to help you troubleshoot
published workarounds.
After a user provides credentials, the system issues a cookie that identifies the user. On
subsequent requests, the system first checks the cookie to see whether the user has already
been authenticated, so the user does not have to supply credentials again.
If the user has not selected the Remember me? box on the logon page, the credential
information is not cached on the client computer, and is valid only during the current session. This
is especially important in a scenario where users are connecting from public computers or kiosks,
where you would not want user credentials to be cached. Users are required to reauthenticate if
they close the browser, log off from a session, or navigate to another Web site. Also, you can
configure a maximum idle session time-out value to force reauthentication if a user is idle for a
prolonged period of time during a session.
Default zone
Intranet zone
Internet zone
Custom zone
Extranet zone
Note:
If you use forms-based authentication and the Windows SharePoint Services 3.0 crawler
polls a zone that is configured to support Kerberos authentication, the Windows
SharePoint Services 3.0 crawler will fail.
Windows SharePoint Services 3.0 does not allow a Web application to work with the same
provider name across multiple zones. You can configure the Web.config file to use the same
provider for each zone; however, the name of the provider has to be unique for each zone.
150
For additional information on authentication mechanisms and samples for configuring formsbased authentication with multiple providers, see Plan for authentication
(http://technet.microsoft.com/en-us/library/cc288627.aspx).
151
Microsoft SharePoint Products and Technologies Team Blog entry about configuring multiple
authentication providers (http://blogs.msdn.com/sharepoint/archive/2006/08/16/configuringmultiple-authentication-providers-for-sharepoint-2007.aspx).
152
Note:
When you use the People Picker to add users to Windows SharePoint Services 3.0,
Windows SharePoint Services 3.0 validates the users against the provider, which in this
example is ADFS. Therefore, you should configure the Federation Server before you
configure Windows SharePoint Services 3.0.
Important:
The setup process has been captured in a VBScript file that you can use to configure
Windows SharePoint Services 3.0 to use ADFS for authentication. This script file is
contained in the file (SetupSharePointADFS.zip) and is available on the Microsoft
SharePoint Products and Technologies blog, listed in the Attachments section. For more
information, see the blog page A script to configure SharePoint to use ADFS for
authentication (http://go.microsoft.com/fwlink/?LinkId=113894&clcid=0x409).
Give the site a host header name that you will configure in DNS for your extranet users to
resolve against.
d. Click Use Secure Sockets Layer (SSL), and change the port number to 443. ADFS
requires that sites be configured to use SSL.
e. In the Load Balanced URL box, delete the text string :443. Internet Information Services
(IIS) will automatically use port 443 because you specified the port number in the
previous step.
f.
Complete the rest of the steps on the page to finish extending the Web application.
153
5. On the Alternate Access Mappings (AAM) page, verify that the URLs resemble the following
table.
Internal URL
Zone
http://trey-moss
Default
http://trey-moss
https://extranet.treyresearch.net
Extranet
https://extranet.treyresearch.net
6. Add an SSL certificate to the Extranet Web Site in IIS. Make sure that this SSL certificate is
issued to extranet.treyresearch.net, because this is the name that clients will use when they
access the sites.
7. Configure the Authentication provider for the extranet zone on your Web application to use
Web SSO by doing the following:
a. On the Application Management page of your farms Central Administration site, click
Authentication Providers.
b. Click Change in the upper-right corner of the page, and then select the Web application
on which you want to enable Web SSO.
c.
In the list of two zones that are mapped for this Web application (both of which should
say Windows), click the Windows link for the Extranet zone.
154
d. To add a user claim, specify their e-mail address or User Principal Name in the
Users/Groups section. If both UPN and e-mail claims are sent from the federation
155
server, then SharePoint will use UPN to verify against the MembershipProvider.
Therefore, if you want to use e-mail, you will have to disable the UPN claim in your
federation server. See Working with UPN and e-mail Claims for more information.
e. To add a group claim, type the name of the claim you want the SharePoint site to use in
the Users/Groups section. For example, create an organizational group claim named
Adatum Contributers on the Federation Server. Add the claim name Adatum
Contributers to the Sharepoint site as you would a Windows user or group. You can
assign this claim Home Members [Contribute], and then any user who accesses the
SharePoint site by using this group claim will have Contributor access to the site.
f.
g. Click OK.
5. Use the text editor of your choice to open the web.config file for the extranet site, and add the
following entry in the <configSections> node.
<sectionGroup name="system.web">
<section name="websso"
type="System.Web.Security.SingleSignOn.WebSsoConfigurationHandler,
System.Web.Security.SingleSignOn, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35, Custom=null" />
</sectionGroup>
6. Add the following entry to the <httpModules> node
<add name="Identity Federation Services Application Authentication
Module"
type="System.Web.Security.SingleSignOn.WebSsoAuthenticationModule,
System.Web.Security.SingleSignOn, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35, Custom=null" />
Note:
The ADFS authentication module should always be specified after the Sharepoint
SPRequest module in the <httpModules> node of the web.config file. It is safest to
add it as the last entry in that section.
7. Add the following entry anywhere under the <system.web> node.
<membership defaultProvider="SingleSignOnMembershipProvider2">
<providers>
<add name="SingleSignOnMembershipProvider2"
type="System.Web.Security.SingleSignOn.SingleSignOnMembershipProvider
2, System.Web.Security.SingleSignOn.PartialTrust, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</providers>
</membership>
<roleManager enabled="true"
defaultProvider="SingleSignOnRoleProvider2">
156
<providers>
<add name="SingleSignOnRoleProvider2"
type="System.Web.Security.SingleSignOn.SingleSignOnRoleProvider2,
System.Web.Security.SingleSignOn.PartialTrust, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</providers>
</roleManager>
<websso>
<authenticationrequired />
<auditlevel>55</auditlevel>
<urls>
<returnurl>https://your_application</returnurl>
</urls>
<fs>https://fs-server/adfs/fs/federationserverservice.asmx</fs>
<isSharePoint />
</websso>
Note:
Change the value for fs-server to your Federation Server computer, and change the
value of your_application to reflect the URL of your extranet Web application.
8. Browse to the https://extranet.treyresearch.net Web site as an ADFS user who has
permissions to the extranet web site.
Granting rights by policy is a very coarse operation. It allows the user (or group) to have the
same set of rights in every Web site, in every site collection on the whole Web application. It
should be used very judiciously; in this particular scenario, we can grant access to ADFS
users without using this method.
After the sites are being used in an extranet environment, it is very likely that the internal
users will be responsible for granting access to sites and content. Because only the farm
administrators have access to the Central Administration site, it makes the most sense that
internal users can add ADFS claims from the default zone site that is using Windows
authentication.
As you extend Web applications by using different providers, you can configure one or more
of them to be able to find users and groups from various providers that you are using on that
Web application. In this scenario, we configured our site that uses Windows authentication in
a way that allows users of that site to select other Windows users, Windows groups, and
ADFS claims, all from one site.
157
Create a new file named stsadm.exe.config in the same directory where stsadm.exe is
located (%programfiles%\Common Files\Microsoft Shared Debug\Web Server
Extensions\12\BIN). Add the following entry in the stsadm.exe.config file:
<configuration>
<system.web>
<membership defaultProvider="SingleSignOnMembershipProvider2">
<providers>
<add name="SingleSignOnMembershipProvider2"
type="System.Web.Security.SingleSignOn.SingleSignOnMembershipProvider
2, System.Web.Security.SingleSignOn.PartialTrust, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" fs="https://fsserver/adfs/fs/federationserverservice.asmx" />
</providers>
</membership>
<roleManager enabled="true"
defaultProvider="SingleSignOnRoleProvider2">
<providers>
<add name="SingleSignOnRoleProvider2"
type="System.Web.Security.SingleSignOn.SingleSignOnRoleProvider2,
System.Web.Security.SingleSignOn.PartialTrust, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35" fs="https://fsserver/adfs/fs/federationserverservice.asmx" />
</providers>
</roleManager>
</system.web>
</configuration>
Note:
Change the value of fs-server to your resource Federation Server
(adfsresource.treyresearch.net).
158
159
160
Select Adatum SharePoint Contributors, and then map it to the incoming claim name
adatum-trey-contributors.
4. Right-click the Windows SharePoint Services 3.0 Web application, and then click Enable on
both the Reader and Contributor claims.
Browse to the http://trey-moss site on the Trey Research side as the site administrator, and then
do the following:
1. Click the Site Actions menu, point to Site Settings, and then click People and Groups.
2. If it is not already selected, click the Members group for your site.
3. Click New, and then click Add Users on the toolbar.
4. Click the address book icon next to the Users/Groups box.
5. In the Find box in the People Picker dialog box, type
Adatum SharePoint Readers
In the Give Permission section, select SharePoint group home Visitors [Readers].
6. In the Find box, type
Adatum SharePoint Contributors
In the Give Permission section, select SharePoint group home Members [Contribute].
161
Anonymous access enables users to find resources in the public areas of Web sites without
having to provide authentication credentials.
Internet is the zone used for customers. Typically, the Internet zone is the only zone you
would configure for anonymous access.
162
Important:
Membership in the Farm Administrators SharePoint group is the minimum required to
complete this procedure.
Enable anonymous access for a zone of a Web application
1. From Administrative Tools, open the SharePoint Central Administration Web site
application.
2. On the Central Administration home page, click Application Management.
3. On the Application Management page, in the Application Security section, click
Authentication providers.
4. On the Authentication Providers page, make sure the Web application that is listed in the
Web Application box (under Site Actions) is the one that you want to configure. If the
listed Web application is not the one that you want to configure, click the drop-down
arrow to the right of the Web Application drop-down list box and select Change Web
Application.
5. In the Select Web Application dialog box, click the Web application that you want to
configure.
6. On the Authentication Providers page, click the zone of the Web application on which you
want to enable anonymous access. The zones that are configured for the selected Web
application are listed on the Authentication Providers page.
7. On the Edit Authentication page, in the Anonymous Access section, select Enable
Anonymous Access, and then click Save.
At this point, the Web application zone has been enabled for anonymous access.
Entire Web site Select this option if you want to enable anonymous access for the
entire Web site.
Lists and libraries Select this option if you want to limit anonymous access to only
the lists and libraries on your site.
Nothing Select this option if you want to prevent anonymous access from being
163
164
165
166
After you have configured the settings that the previous articles
describe, you can create a site collection. This article helps you create a site collection from
Central Administration and assign primary and secondary owners. If you want to allow users
to create their own sites, you need to configure Self-Service Site Management for the Web
application. For more information about choosing a method to use for site creation, see Plan
process for creating sites [Windows SharePoint Services].
If you are using hostnamed sites with forms authentication, you need to configure additional settings for search.
This article helps you configure host-named sites for search crawls.
If you are using hostnamed sites with Basic authentication, you need to configure additional settings for search.
This article helps you configure host-named sites for search crawls.
After you have created your site collection, you can begin adding site
content. This article provides links to information that can help you add content to your sites.
After you have created your site, you can add users and grant
them access to the site. This article helps you add users to a site collection.
167
168
In the Port box, type the port number you want to use to access the Web application.
If you are creating a new Web site, this field is populated with a suggested port
number. If you are using an existing Web site, this field is populated with the current
port number.
d. In the Host Header box, type the URL you want to use to access the Web
application. This is an optional field.
e. In the Path box, type the path to the site directory on the server. If you are creating a
new Web site, this field is populated with a suggested path. If you are using an
existing Web site, this field is populated with the current path.
4. In the Security Configuration section, configure authentication and encryption for your
Web application.
a. In the Authentication Provider section, choose either Negotiate (Kerberos) or
NTLM.
Note:
To enable Kerberos authentication, you must perform additional
configuration. For more information about authentication methods, see Plan
authentication methods (http://technet.microsoft.com/enus/library/cc288475.aspx).
b. In the Allow Anonymous section, choose Yes or No. If you choose to allow
anonymous access, this enables anonymous access to the Web site by using the
computer-specific anonymous access account (that is, IUSR_<computername>).
Note:
If you want users to be able to access any site content anonymously, you
must enable anonymous access for the entire Web application. Then later,
site owners can configure how anonymous access is used within their sites.
For more information about anonymous access, see Choose which security
169
In the Use Secure Sockets Layer (SSL) section, select Yes or No. If you choose to
enable SSL for the Web site, you must configure SSL by requesting and installing an
SSL certificate.
Important:
If you use SSL, you must add the appropriate certificate on each server by
using IIS administration tools. For more information about using SSL, see
Plan for secure communication within a server farm
(http://technet.microsoft.com/en-us/library/cc288488.aspx).
5. In the Load Balanced URL section, type the URL for the domain name for all sites that
users will access in this Web application. This URL domain will be used in all links shown
on pages within the Web application. By default, the box is populated with the current
server name and port.
The Zone box is automatically set to Default for a new Web application, and cannot be
changed from this page. To change the zone for a Web application, see Extend an
existing Web application later in this article.
6. In the Application Pool section, choose whether to use an existing application pool or
create a new application pool for this Web application. To use an existing application
pool, select Use existing application pool. Then select the application pool you want to
use from the drop-down menu.
a. To create a new application pool, select Create a new application pool.
b. In the Application pool name box, type the name of the new application pool, or
keep the default name.
c.
In the Select a security account for this application pool section, select
Predefined to use an existing application pool security account, and then select the
security account from the drop-down menu.
d. Select Configurable to use an account that is not currently being used as a security
account for an existing application pool. In the User name box, type the user name of
the account you want to use, and type the password for the account in the Password
box.
7. In the Reset Internet Information Services section, choose whether to allow Windows
SharePoint Services to restart IIS on other farm servers. The local server must be
restarted manually for the process to finish. If this option is not selected and you have
more than one server in the farm, you must wait until the IIS Web site is created on all
servers and then run iisreset /noforce on each Web server. The new IIS site is not
usable until that action is completed. The choices are unavailable if your farm only
contains a single server.
8. In the Database Name and Authentication section, choose the database server,
database name, and authentication method for your new Web application.
170
Item
Action
Database Server
Database Name
Database Authentication
9. Click OK to create the new Web application, or click Cancel to cancel the process and
return to the Application Management page.
171
use the default entries or type the information you want in the boxes.
6. In the Security Configuration section, configure authentication and encryption for the
extended Web application.
a. In the Authentication Provider section, choose either Negotiate (Kerberos) or
NTLM.
Note:
To enable Kerberos authentication, you must perform additional
configuration. For more information about authentication methods, see Plan
authentication methods (http://technet.microsoft.com/enus/library/cc288475.aspx).
b. In the Allow Anonymous section, choose Yes or No. If you choose to allow
anonymous access, this enables anonymous access to the Web site by using the
computer-specific anonymous access account (that is, IUSR_<computername>).
Note:
If you want users to be able to access any site content anonymously, you
must enable anonymous access for the entire Web application. Then later,
site owners can configure how anonymous access is used within their sites.
For more information about anonymous access, see Choose which security
groups to use (http://technet.microsoft.com/en-us/library/cc288957.aspx).
c.
In the Use Secure Sockets Layer (SSL) section, select Yes or No. If you choose to
enable SSL for the Web site, you must configure SSL by requesting and installing an
SSL certificate.
Important:
If you use SSL, you must add the appropriate certificate on each server by
using IIS administration tools. For more information about using SSL, see
Plan for secure communication within a server farm
(http://technet.microsoft.com/en-us/library/cc288488.aspx).
7. In the Load Balanced URL section, type the URL for the domain name for all sites that
users will access in this Web application. This URL domain will be used in all links shown
on pages within the Web application. By default, the text box is populated with the current
server name and port.
8. In the Load Balanced URL section, under Zone, select the zone for the extended Web
application from the drop-down menu. You can choose Intranet, Internet, Custom, or
Extranet.
9. Click OK to extend the Web application, or click Cancel to cancel the process and return
to the Application Management page.
For information about how to perform this procedure using the Stsadm command-line tool, see
Extendvs.
172
173
1. On the Alternate Access Mappings page, click the internal URL that you want to edit or
delete.
2. In the Edit internal URL section, modify the URL in the URL protocol, host and port box.
3. In the Zone list, click the zone for the internal URL.
4. Do one of the following:
Click Cancel to discard your changes and return to the Alternate Access Mappings page.
Default
Intranet
Extranet
Internet
Custom
5. Click Save.
174
175
A quota template consists of storage limit values that specify how much data can be stored in a
site collection and the storage size that triggers an e-mail alert to the site collection administrator
when that size is reached. You can create a quota template that can be applied to any site
collection in the farm.
Note:
When you apply a quota template to a site collection, the storage limit applies to the site
collection as a whole. In other words, the storage limit applies to the sum of the content
sizes for the top-level site and all subsites within the site collection.
You can also modify existing quota templates. When a quota template is modified, the new
storage limits you defined in the template will apply to any site collection that uses that quota
template. This allows you to modify storage limits for multiple site collections without having to
change settings for each site collection individually.
If you want to base your new template on an existing quota template, click the
Template to start from down arrow and select the desired template from the dropdown menu.
6. In the Storage Limit Values section, set the values you want to apply to the template.
a. If you want to restrict the amount of data that can be stored, click the Limit site
storage to a maximum of check box and type the storage limit in megabytes into
the text box.
b. If you want an e-mail to be sent to the site collection administrator when a certain
176
storage threshold is reached, click the Send warning E-mail when site storage
reaches check box and type the threshold in megabytes into the text box.
7. Click OK to create the new quota template, or click Cancel to cancel the operation and
return to the Application Management page.
177
178
Solution prerequisites
When configuring a Web application to use host-named sites, Web hosters typically use Basic
authentication for the default zone. The index component of the search server, sometimes called
the crawler, cannot crawl host-named Web sites that are deployed in the usual way for the
following reasons:
Host-named sites do not enable the index component of the search server to authenticate by
using another zone in the polling order.
For more information about how polling order works with non-host-named sites, see the
Authentication requirements for crawling content section in Plan authentication methods
[Windows SharePoint Services].
This article describes how to create a solution in Windows SharePoint Services 3.0 so the crawler
can crawl your host-named sites. The components of the solution are to:
Direct requests from end-users to the default zone, which is configured for Basic
authentication.
Direct requests from intranet users and the crawler directly to the Intranet zone, which you
configure for NTLM authentication.
Solution prerequisites
The procedures included in this solution require the following types of administrators:
Server administrator
Farm administrator
Two DNS servers: one Internet-facing DNS server, and one intranet-facing DNS server.
Two static IP addresses: one from the Internet-facing DNS server, and a different static IP
address from the intranet-facing DNS server. These two IP addresses must be associated
with the same site name.
179
A server administrator either configures separate network interface cards (NICs) on all frontend Web servers in the server farm with both static IP addresses or adds both static IP
addresses to one NIC.
The search server that you will use for your Web application is running.
This solution requires two DNS servers. Each DNS server maps the same host name to a
different static IP address. This is typically referred to as a split DNS environment. The Internetfacing DNS server resolves the URL of the host-named site to the default zone of your Web
application. This is the zone end-users use to access the site using Basic authentication. The
intranet-facing DNS server resolves this same URL to an IP address that is mapped to the
Intranet zone of your Web application. This is the zone that intranet users and the crawler use to
access the site using NTLM authentication.
This mapping is possible because when a new zone is created by extending the Web application,
Windows SharePoint Services 3.0 creates an Internet Information Services (IIS) Web site for that
zone. A server administrator can use IIS Manager to map a static IP address directly to an IIS
Web site, which is associated with a particular zone of a particular Web application.
180
High-level steps
The following list describes the high-level steps for this solution.
1. The farm administrator uses the Central Administration Web site to create a Web application
on port 80 without a host header assigned to it.
2. The farm administrator configures the default zone of this Web application to use Basic
authentication.
3. The farm administrator extends the Web application, specifies the host header name, and
then specifies NTLM authentication on the intranet zone.
4. The DNS administrator maps the site name to the static IP addresses in DNS.
5. The server administrator uses IIS Manager to perform the following actions:
Map the static IP address from the Internet-facing DNS server to the IIS Web site that is
associated with the default zone (that is, the zone that uses Basic authentication) of your
Web application.
Map the static IP address from the intranet-facing DNS server to the IIS Web site
associated with the Intranet zone (that is, the zone that uses NTLM authentication) of
your Web application, and remove the IIS host header that was assigned to this site in
step 3.
6. The server administrator creates a host header-based site collection by using the Stsadm
command-line utility.
Note:
You must use the Stsadm command-line utility to specify the URL that you want for
your host header-based site collection.
7. The farm administrator can grant permissions to the Web application and the site collection
administrator can grant permissions to the site collection.
181
a. Accept the default setting, Create a new IIS web site, and then type a name for the
Web site in the Description box.
b. In the Port box, type 80.
c.
6. In the Application Pool section, select Use existing application pool, or accept the
default setting, Create new application pool. If you are creating a new application pool,
specify the security account to use for the new application pool.
7. In the Search Server section, select the search server that you want to use to index this
Web application from the Select Windows SharePoint Services search server list.
8. Click OK.
Perform the following procedure on all front-end Web servers in the server farm.
Restart IIS
1. Click Start and then click Run.
2. In the Run dialog box, in the Open box, type cmd, and then click OK.
3. At the command prompt, type the following command, and then press ENTER:
iisreset /noforce
4. Close the command prompt window.
Perform the following procedure to configure the Web application to use Basic authentication.
Configure the default zone to use Basic authentication
1. On the Central Administration home page, click Application Management.
2. On the Application Management page, in the Application Security section, click
Authentication providers.
3. On the Authentication Providers page, in the Zone column, click Default.
4. In the IIS Authentication Settings section, select Basic authentication (password is
sent in clear text).
5. Click Save.
182
4. On the Extend Web Application to Another IIS Web Site page, in the Web Application
section, on the Web Application menu, click Change Web Application.
5. On the Select Web Application page, select the Web application you want to extend. This
is the Web application you created earlier in this article.
6. In the IIS Web Site section, do the following:
a. In the Description box, type a description for the new site.
b. In the Port box, type 80.
c.
183
The following procedure must be performed by a server administrator on each front-end Web
server in the server farm.
Map the static IP addresses to the Web sites
1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet
Information Services (IIS) Manager.
2. In the console tree, expand the local computer node, expand Web Sites, right-click the
Web site you configured for Basic authentication, and then click Properties.
3. In the Properties dialog box, on the Web Site tab, in the Web site identification
section, in the IP address list, select the IP address that you want to map to the
customer-facing Web site.
4. Click OK to close the Properties dialog box.
5. In the console tree, right-click the Web site you configured for NTLM authentication, and
then click Properties.
6. In the Properties dialog box, on the Web Site tab, in the Web site identification
section, click Advanced.
7. In the Advanced Web Site Identification dialog box, in the Multiple identities for this
Web site section, select the row containing the host header name you configured for the
Web site that is using NTLM authentication, and then click Edit.
8. In the Add/Edit Web Site Identification dialog box, select the IP address that you want
to map to the Web site that is using NTLM authentication from the IP address list.
9. In the Host Header value box, make a note of the host header name. This is the host
header name you assigned to the site that you configured for NTLM authentication. You
will need to use this name in the next procedure.
10. In the Host Header value box, delete the host header name, and then click OK.
11. Click OK to close the Advanced Web Site Identification dialog box.
12. Click OK to close the Properties dialog box.
13. Close IIS Manager.
Use the following procedure to create a site collection for your Web application. You must be a
server administrator to perform the following steps.
Create a site collection for the Web application
1. Click Start and then click Run.
2. In the Run dialog box, in the Open box, type cmd, and then click OK.
3. Browse to the following folder:
systemdrive:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\BIN
where systemdrive is the drive on which Windows SharePoint Services 3.0 is installed.
4. In the command window, type the following command, and then press ENTER:
stsadm.exe -o createsite -url http://<HostNamedSiteAddress> -ownerlogin
184
Description
HostNamedSiteAddress
DomainName\UserName
username@example.com
WebApplicationUrl
185
Solution prerequisites
When configuring a Web application to use host-named sites, Web hosters typically use forms
authentication for the default zone. The index component of the search server, sometimes called
the crawler, cannot crawl host-named Web sites that are deployed in the usual way for the
following reasons:
Host-named sites do not enable the index component of the search server to authenticate by
using another zone in the polling order.
For more information about how polling order works with non-host-named sites, see the
Authentication requirements for crawling content section in Plan authentication methods
[Windows SharePoint Services].
This article describes how to create a solution in Windows SharePoint Services 3.0 so the crawler
can crawl your host-named sites. The components of the solution are to:
Direct requests from end-users to the default zone, which is configured for forms
authentication.
Direct requests from intranet users and the crawler directly to the Intranet zone, which you
configure for NTLM authentication.
Solution prerequisites
The procedures included in this solution require the following types of administrators:
Server administrator
Farm administrator
Two DNS servers: one Internet-facing DNS server and one intranet-facing DNS server.
Two static IP addresses: one from the Internet-facing DNS server and a different static IP
address from the intranet-facing DNS server. These two IP addresses must be associated
with the same site name.
186
A server administrator will either configure separate network interface cards (NICs) on all
front-end Web servers in the server farm with both static IP addresses or will add both static
IP addresses to one NIC.
The search server that you will use for your Web application is running.
You have already implemented forms authentication in your environment. Note that forms
authentication can be implemented using several different authentication providers. The
authentication provider you use with your implementation of forms authentication determines
where user accounts are stored.
This solution requires two DNS servers. Each DNS server maps the same host name to a
different static IP address. This is typically referred to as a split DNS environment. The Internetfacing DNS server resolves the URL of the host-named site to the default zone of your Web
application. This is the zone end-users use to access the site using forms authentication. The
intranet-facing DNS server resolves this same URL to an IP address that is mapped to the
Intranet zone of your Web application. This is the zone intranet users and the crawler use to
access the site using NTLM authentication.
This mapping is possible because when a new zone is created by extending the Web application,
Windows SharePoint Services 3.0 creates an Internet Information Services (IIS) Web site for that
187
zone. A server administrator can use IIS Manager to map a static IP address directly to an IIS
Web site, which is associated with a particular zone of a particular Web application.
High-level steps
The following list describes the high-level steps for this solution.
1. The farm administrator uses the Central Administration Web site to create a Web application
on port 80 without a host header assigned to it.
2. The farm administrator configures the default zone of this Web application to use forms
authentication.
3. The server administrator adds a custom XML element to the appropriate Web.config files to
specify the name of the authentication provider used with forms authentication.
4. The server administrator creates a file named stsadm.exe.config to enable the Stsadm
command-line utility to determine how to find the authentication provider you want to use with
forms authentication.
5. The farm administrator extends the Web application, specifies the host header name, and
then specifies NTLM authentication on the Intranet zone.
6. The DNS administrator maps the site name to the static IP addresses in DNS.
7. The server administrator uses IIS Manager to do the following:
Map the static IP address from the Internet-facing DNS server to the IIS Web site
associated with the default zone (that is, the zone using forms authentication) of your
Web application.
Map the static IP address from the intranet-facing DNS server to the IIS Web site
associated with the Intranet zone (that is, the zone using NTLM authentication) of your
Web application and removes the IIS host header that was assigned to this site in step 5.
8. The server administrator creates a host header-based site collection by using the Stsadm
command-line utility.
Note:
You must use the Stsadm command-line utility to specify the URL you want for your
host header-based site collection.
9. The farm administrator can grant permissions to the Web application and the site collection
administrator can grant permissions to the site collection.
188
Management.
3. On the Application Management page, in the SharePoint Web Application
Management section, click Create or extend Web application.
4. On the Create or Extend Web Application page, in the Adding a SharePoint Web
Application section, click Create a new Web application.
5. On the Create New Web Application page, in the IIS Web Site section, configure the
following settings for your new Web application.
a. Accept the default setting, Create a new IIS web site, and then type a name for the
Web site in the Description box.
b. In the Port box, type 80.
c.
6. In the Application Pool section, select Use existing application pool, or accept the
default setting, Create new application pool. If you are creating a new application pool,
specify the security account to use for the new application pool.
7. In the Search Server section, select the search server that you want to use to index this
Web application from the Select Windows SharePoint Services search server list.
8. Click OK.
Perform the following procedure on all front-end Web servers in the server farm.
Restart IIS
1. Click Start and then click Run.
2. In the Run dialog box, in the Open box, type cmd, and then click OK.
3. In the command window, type the following command, and then press ENTER:
iisreset /noforce
4. Close the command prompt window.
Perform the following procedure to configure the Web application to use forms authentication.
Configure the default zone to use forms authentication
1. On the Central Administration home page, click Application Management.
2. On the Application Management page, in the Application Security section, click
Authentication providers.
3. On the Authentication Providers page, in the Zone column, click Default.
4. On the Edit Authentication page, in the Authentication Type section, select Forms.
5. In the Membership Provider Name section, in the Membership provider name box, type
the name of your membership provider.
6. Optionally, in the Role Manager Name section, in the Role manager name box, type the
name of your role manager.
7. Click Save.
189
190
2. Click Start, and then click Run. In the Run dialog box, type inetmgr, and then click OK.
3. In IIS Manager, in the console tree, expand the local computer node, and then expand
Web Sites.
4. Right-click the Central administration Web site, and then click Explore. This site is
named SharePoint Central Administration v3, by default.
5. In the Name column, right-click web.config, click Open, and then open the file using an
ASCII text editor, such as Notepad.
6. Insert your custom XML element named <connectionStrings> immediately after the
</configSections> element.
7. If you are using custom <membership> or <roleManager> elements, you must insert
them inside the <system.web> element.
8. Save and close the Web.config file.
9. Repeat steps 1 through 7 on any additional server in your farm running the Central
Administration service.
Use the following procedure to create a file named stsadm.exe.config. This file must contain the
same XML element that you added to the Web.config files. This file enables the Stsadm
command-line utility to determine how to find the authentication provider you want to use.
Create the stsadm.exe.config file
1. Open an ASCII text editor, such as Notepad, and add the following text:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configuration> <system.web> </system.web> </configuration>
2. Insert the same custom XML element named <connectionStrings> that you added to your
Web.config files in the preceding step after the <configuration> tag.
3. If you are using custom <membership> or <roleManager> elements, you must insert
them inside the <system.web> element.
4. Save the file and name it stsadm.exe.config.
5. You must ensure that the text editor you are using does not add the .txt extension to the
filename. If this occurs, remove the .txt extension before proceeding to the next step.
6. Copy the stsadm.exe.config file to the following folder on each server in the farm from
which a farm administrator might use the stsadm.exe utility:
systemdrive:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\BIN
We recommend that you copy this file to each server in the server farm.
191
192
Likewise, the administrator for the intranet-facing DNS must map this same site name to a
different static IP address. In a later step, the server administrator will map this static IP address
to the IIS Web site that is configured to use the Intranet zone used by the Web application.
Additionally, this DNS administrator must also map the host header name that the farm
administrator used when extending the Web application to this static IP address. Even though this
host name is removed in a later procedure, this host name is used by the crawler to access the
Web application on the Intranet zone.
The following procedure must be done by a server administrator on each front-end Web server in
the server farm.
Map the static IP addresses to the Web sites
1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet
Information Services (IIS) Manager.
2. In the console tree, expand the local computer node, expand Web Sites, right-click the
Web site you configured for forms authentication and then click Properties.
3. In the Properties dialog box, on the Web Site tab, in the Web site identification
section, select the IP address that you want to map to the customer-facing Web site from
the IP address list.
4. Click OK to close the Properties dialog box.
5. In the console tree, right-click the Web site you configured for NTLM authentication and
then click Properties.
6. In the Properties dialog box, on the Web Site tab, in the Web site identification
section, click Advanced.
7. In the Advanced Web Site Identification dialog box, in the Multiple identities for this
Web site section, select the row containing the host header name you configured for the
Web site that is using NTLM authentication and then click Edit.
8. In the Add/Edit Web Site Identification dialog box, select the IP address you want to
map to the Web site that is using NTLM authentication from the IP address list.
9. In the Host Header value box, make a note of the host header name. This is the host
header name you assigned to the site that you configured for NTLM authentication. You
will need to use this name in the next procedure.
10. In the Host Header value box, delete the host header name and then click OK.
11. Click OK to close the Advanced Web Site Identification dialog box.
12. Click OK to close the Properties dialog box.
13. Close IIS Manager.
Use the following procedure to create a site collection for your Web application. You must be a
server administrator to perform the following steps.
Create a site collection for the Web application
1. Click Start and then click Run.
2. In the Run dialog box, in the Open box, type cmd, and then click OK.
193
Description
HostNamedSiteAddress
ProviderName:UserName
username@example.com
WebApplicationUrl
URL on the default zone of the Web application. You can find
this address on the Web Application List page in Central
Administration.
194
There are several methods that you can use to add content to sites, including:
Depending on your scenario, you may find particular methods more appropriate.
Use Web site designers to design and add content when you are working with:
Migrate content from another site when you are working with:
Allow users to add content directly when you are working with:
A collaboration site in which the site owner can create the lists and libraries that are needed,
and then grant site members access so that they can begin contributing content.
A blog site in which the blog owner can set up the structure for the blog, and then start
creating posts.
A wiki site in which the wiki site owner can grant access to users and the users can start
creating topics in the wiki.
195
The Export and Import operations for the Stsadm command-line tool to migrate site
collections or subsites.
For more information about using Stsadm operations, see the following resources:
The Content Migration object model to programmatically move content at any level in the site
(Web site, list, library, folder, file, or list item).
For more information about using the Content Migration object model, see "Content Migration
Overview" in the Windows SharePoint Services 3.0 Software Development Kit
(http://go.microsoft.com/fwlink/?LinkId=86999&clcid=0x409).
196
After you create your site collection and populate it with content, you are ready to grant access to
end users. This article helps you configure administrative and user permissions for a site
collection. Note that you can also configure permissions for the following securable objects within
a site collection: site, list, library, folder, document, or item. For more information about assigning
permissions for different securable objects within a site collection, see Plan site security
(http://technet.microsoft.com/en-us/library/cc287752.aspx).
In most cases, these actions are not performed by farm administrators, but are performed by site
collection administrators or site owners. Moreover, these steps are performed in the site collection
itself, not in Central Administration. (However, you can add site collection administrators by using
Central Administration and by using the Site Settings page in the site collection.) Nonetheless,
this information is presented in the Deployment Guide because it is truly the final stage of
deployment the stage when the site collection is made available for end users.
This article does not cover how to enable anonymous access. When you create a Web
application, you decide whether to allow anonymous access for site collections on that Web
application. For more information about anonymous access, see the following resources:
197
In the Select Site Collection dialog box, select the site for which you want to
manage administrators.
Click OK.
4. In either the Primary site collection administrator box or the Secondary site
collection administrator box, enter the user name of the user to whom you want to
assign that role.
5. Click OK.
198
199
200
Site admin templates are custom templates that are easy for any SharePoint site
administrator to install into the template gallery.
Server admin templates were created as site definitions, enabling tighter integration and
enhanced functionality with the Windows SharePoint Services 3.0 platform. They require
administrator permissions on the server to install.
201
202
203
The following procedure will not remove any sites that were already created by using the
template. It will only prevent users from creating new sites based on the template. The Application
Template Core solution must remain installed and deployed for other server admin templates to
be installed.
Remove a template
1. Log on to the server running Windows SharePoint Services 3.0 as a member of the
Administrators group on the server.
2. Do one or both of the following:
To remove a solution from the list of templates for new sites, at the command prompt,
type stsadm -o retractsolution -name <template_name>.wsp, and then press
ENTER.
Note:
Additional attributes may be required based on your Windows SharePoint
Services 3.0 configuration. For more information about available attributes,
type stsadm -help retractsolution, and then press ENTER.
To remove a solution from the server, at the command prompt, type stsadm -o
deletesolution -name <template_name>.wsp, and then press ENTER.
Note:
Additional attributes may be required based on your Windows SharePoint
Services 3.0 configuration. For more information about available attributes,
type stsadm -help deletesolution, and then press ENTER.
204
205
Verify installation
Known issues
To help you better understand the update deployment process we have posted the Presentation:
Understanding and deploying hotfixes, public updates, and service packs
(http://go.microsoft.com/fwlink/?LinkId=121946&clcid=0x409), given by Daniel Winter at the
SharePoint Products and Technologies conference in March, 2008. This presentation provides
valuable information about the different types of software updates that Microsoft releases for
Windows SharePoint Services and Microsoft Office SharePoint Server.
Using Service Pack 1 for Windows SharePoint Services 3.0 and Microsoft Office SharePoint
Server 2007 as examples, Daniel Winter provides detailed information about pre-upgrade steps,
deploying the upgrade, validating the upgrade, and troubleshooting the upgrade. Viewing the
presentation is highly recommended prior to reading further in this topic and deploying an update.
We recommend that you follow the process and procedures in this topic for most deployment
scenarios, from stand-alone server deployments to very large server farms. The typical process
for installing software updates consists of copying the files to a computer and then running either
the SharePoint Products and Technologies Configuration Wizard or the Psconfig command-line
tool to upgrade the databases.
Note:
In this article, we use the term software update as a general term for all update types,
including any service pack, update, update rollup, feature pack, critical update, security
update, or hotfix used to improve or fix this software product.
If you chose Basic installation (single server with Microsoft SQL Server Desktop Engine) when
you installed your Web server running Windows SharePoint Services 3.0, you do not need to
follow the process and procedures in this topic. In this case, if you have Automatic Updates
enabled, your computers are updated automatically. If you do not have Automatic Updates
enabled, you can use the Microsoft Update (http://go.microsoft.com/fwlink/?
LinkId=90953&clcid=0x409) Web site to install the software updates.
206
Note:
Typically, only public software updates, such as operating system fixes or security
patches can be installed from the Microsoft Update Web site.
After the software update is installed, the SharePoint Products and Technologies Configuration
Wizard runs automatically to update the databases for SharePoint Products and Technologies. In
this scenario, the SharePoint Products and Technologies Configuration Wizard will not prompt for
user input or display any notifications.
For any deployment other than single server, such as Web servers in a server farm, you must
visit the Microsoft download center to download and then install the software update. The
software update will not be installed automatically, even if Automatic Updates is enabled on your
Web servers, and you cannot use the Windows Update Web site to initiate the software update
installation.
The software update checks the registry and blocks automatic installation on any Web server that
does not contain the value singleserver in the SERVERROLE key.
If you need to determine whether to manually download and install the software update, use a
registry editor to verify the value in the following key:
HKLM\Software\Microsoft\Shared Tools\Web server extensions\12.0\WSS\SERVERROLE
In server farm deployments, you must update all the Web servers running Windows SharePoint
Services 3.0 to the same software update version. If the software update versions are not the
same on all of the Web servers running Windows SharePoint Services 3.0 in your server farm,
when users request resources from a Web server that does not have the software update
installed, they receive a Page cannot be found (404) error. If you attempt to install the software
update and the installation fails, all user requests to the Web servers with a failed software
update installation will return the error: Server error: http://go.microsoft.com/fwlink?
LinkID=96177. Once the software update installation is successful, the Web server displays
content as expected.
207
valid requests result in errors. When the software update has been installed on all of the Web
servers in the server farm, results are returned to users as expected.
When you first installed Windows SharePoint Services on the Web servers in your server farm, if
you used an upgrade methodeither in-place or gradualand upgrade jobs are still in progress,
the software update installation might fail. To ensure that none of the upgrade processes are
running, you must view the Timer Job Status page on the SharePoint Central Administration Web
site. If you see any upgrade jobs listed, you must allow the upgrade to finish before you install the
software update.
The upgrade jobs that appear on the Timer Job Status page result from the following operations:
You selected the in-place upgrade option in the SharePoint Products and Technologies
Configuration Wizard.
After you have verified that no upgrade items are listed on the Timer Job Status page, you can
continue installing the software update.
Pre-upgrade preparation
Before you install a software update, we recommend the following:
If there are orphaned objects in the content databasesorphans are items that do not have
any parent or child relationshipsthe software update installation will fail. To make sure that
the installation can succeed, you must either fix the relationship or drop the orphans before
you begin the software update installation. For more information about a resolution for when
the content database contains one or more orphaned objects, see the Microsoft Knowledge
Base article titled Error message when you try to upgrade Windows SharePoint Services 2.0
to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were
not updated by Prescan.exe and must exit" (http://go.microsoft.com/fwlink/?LinkId=105755).
If you customized a predefined site template by directly modifying the site template files
something we do not recommend doingthe software update installation may overwrite
some of the files that you modified, and your customizations in those files will be lost. You
must reapply any site-template customizations after you install the software update.
Stop the World Wide Web publishing service (W3SVC) on all front-end Web servers to
disconnect all the users from the server farm. In server farms with multiple front-end Web
servers, if you allow users to connect after the files and databases have been updated on one
Web server, and the other Web servers have not been updated, users will not be able to
browse the Web sites.
Note:
If you manually stop the World Wide Web Publishing service, you must manually start
it at the end of the installation.
208
Before you start the backup you should clean up your environment by performing the
following steps.
Defragment all of the SQL Server database indexes. For more information, see How to
defragment Windows SharePoint Services 3.0 databases and SharePoint Server 2007
databases (http://go.microsoft.com/fwlink/?LinkID=102795&clcid=0x409).
Make sure that there is adequate hard drive space in your database files volumes,
tempdb volumes, and Windows temporary folder on the servers running SQL Server,
front-end Web servers, and application servers. The upgrade operation writes the
progress of various steps into an upgrade log that can take up disk space, but if you plan
for extra storage you should not encounter issues due to space limitations.
If any of your databases contain more than the number of site collections recommended in
the Information Architecture Recommendations of the download White paper: Performance
recommendations for storage planning and monitoring, you should load-balance your site
collections across multiple databases.
Follow the best practices for content database sizing before you perform any upgrade
operations.
Make sure that you follow the recommendations concerning SQL Server page-fill factor and
other storage planning best practices before you begin the upgrade. For more information
about storage best practices, see Performance recommendations for storage planning and
monitoring (http://go.microsoft.com/fwlink/?LinkID=105890&clcid=0x409)
Back up the server farm before you start the software update installation. You should create a
backup of search and all databases. We recommend that you follow these guidelines:
Content databases: Perform a full backup operation with either Stsadm or SQL Server
to back up all content databases. If you are using SQL Server, use the simple recovery
model, so that your transaction log is truncated.
Single sign-on (SSO) database: Perform a full backup operation with SQL Server to
back up the SSO database. If you are using SQL Server, use the simple recovery model,
so that your transaction log is truncated.
Front-end Web server: If you have customized the front-end Web server, or are unsure
of the extent of the customizations to your Web applications, we recommend that you
make a backup image of your front-end Web server. Make sure you have a backup of any
solution packages that you have deployed on your front-end Web servers.
Note:
Ideally, if you are customizing front-end Web computers, the customization
should be managed using a robust build process or script that allows the
customizations to be applied to a new computer.
If you experience an unrecoverable failure during upgrade, you may have to restore your
server from the backup image you created. You would need to manually apply any
customizations to your front-end Web server.
209
Note:
We recommend that you back up the server farm after you have verified that the
software update installation succeeded.
After you have backed up all of your databases, use the SQL Server DBCC shrinkfile
command to free unused log space, making the logs as empty as possible. For more
information, see Shrinking the Transaction Log (http://go.microsoft.com/fwlink/?
LinkId=105233). It is a best practice to verify that you can restore the databases.
For more information about how to perform backups, see Prepare to back up Windows
SharePoint Services 3.0 technology.
In server farms that have a large number of sites, you will find that installing a software
update with the content databases attached is not practical in terms of downtime. In order to
minimize the downtime, we recommend that you perform the additional step of detaching the
content databases.
To deploy software updates in a server farm you must be logged in to the Web server or
application server as a domain account that also has the following permissions:
Member of the Administrators group on the server running SQL Server or be granted the
fixed database role db_owner to all SharePoint Products and Technologies databases.
If you have previously installed a hotfix, and the problem that it addresses is not fixed in this
widely available software update, you must obtain the updated version of that hotfix to
address specific issues in your environment by contacting Microsoft Customer Support
Services (http://go.microsoft.com/fwlink/?LinkId=99201).
For more information about the software updates in Windows SharePoint Services 3.0 with
Service Pack 1, see Microsoft Knowledge Base article 942388 (http://go.microsoft.com/fwlink/?
LinkId=105672&clcid=0x409).
For more information about the software updates in Windows SharePoint Services 3.0 Post
Service Pack 1 rollup, see Microsoft Knowledge Base article 941422
(http://go.microsoft.com/fwlink/?LinkId=102044&clcid=0x409).
Note:
All Web servers running Windows SharePoint Services in the server farm must be
running Windows SharePoint Services 3.0.
210
You must download the correct software update file for your hardware and language. The
pattern for the software update naming convention is productnamerrr-kby-xnn-fullfilelang.exe, where:
rrr is a description of the release. For example, Service Pack 1 would be sp1.
y is a number that corresponds to the Knowledge Base article about the software update.
lang is the language of the software update. For example, U.S. English is en-us.
For example, the file name for the Windows SharePoint Services 3.0 Service Pack 1 (SP1) file, in
U.S. English and for x86-based hardware, is wssv3sp1-kb936988-x86-fullfile-en-us.exe.
For more information, and to download the appropriate file, see Download details: Windows
SharePoint Services 3.0 Service Pack 1 (SP1) (http://go.microsoft.com/fwlink/?
LinkID=91024&clcid=0x409).
211
To ensure that you have the correct permissions to install the software update and run the
SharePoint Products and Technologies Configuration Wizard, we recommend that you add the
account for the SharePoint Central Administration v3 application pool identity to the
Administrators group on each of the local Web servers and application servers and then log on by
using that account. These changes are only required for installing the update and then running
the SharePoint Products and Technologies Configuration Wizard to complete the upgrade.
If you use a different account to install the software update, it must be a domain account with the
following memberships, roles, and authorization:
Granted the fixed database role db_owner to all SharePoint Products and Technologies
databases.
Make all software update files available on all servers in your server farm.
212
Note:
This manual step is done as a precaution to ensure that the service is fully
stopped.
2. Download and install the appropriate Windows SharePoint Services 3.0 software update
for all servers in your server farm.
3. At the end of the software update installation, the SharePoint Products and Technologies
Configuration Wizard starts.
Note:
If the wizard does not start automatically, click Start, point to All Programs, point
to Administrative Tools, and then click SharePoint Products and
Technologies Configuration Wizard.
4. On the SharePoint Products and Technologies Configuration Wizard Welcome page, click
Next.
5. In the dialog box that notifies you that some services might need to be restarted during
configuration, click Yes.
6. On the Completing the SharePoint Products and Technologies Configuration
Wizard page, click Next.
7. When the dialog box about installation in a server farm appears, do not click OK.
Instead, leave each server with the following dialog box displayed:
You must run Setup to install new binary files for every server in your server farm. If you
have multiple servers in your server farm, run Setup and the configuration wizard on the
other servers now, and then return to this server and click OK to continue.
8. When the dialog box from the previous step is displayed on all Web servers in the server
farm, use one Web server that hosts the Central Administration Web site to finalize the
installation.
9. On the server you selected in the previous step, click OK.
10. On the Configuration Successful page, click Finish.
11. After you have finished updating one Web server that hosts the Central Administration
Web site, you should follow the procedures in the "Verify installation" section on this one
Web server to ensure that the software update installation was successful.
12. Continue updating the remaining computers in the server farm, one at a time, by clicking
OK in the dialog box.
Note:
It is important that the SharePoint Products and Technologies Configuration
Wizard perform the configuration procedures on only one computer at a time.
13. When the software update installation and configuration is complete on all the Web
servers in the server farm, make the Web servers available to users by manually starting
the World Wide Web Publishing service on each server on which you manually stopped
the service.
213
If you completed the "To detach content databases" procedure, depending on if you configured
additional computers to upgrade the content databases, you must use one of the following
procedures to attach the content database after the software update installation is complete.
Note:
If you did not follow the "To detach content databases" procedure, you can skip the "To
attach the content database" procedures.
If you did not configure additional computers specifically to upgrade the content databases, you
will need to follow the "To attach the content database from the command line" procedure. This
procedure attaches and initiates an upgrade of the content database.
To attach the content database from the command line
If you did configure additional computers specifically to upgrade the content databases, you can
use the following procedure to attach the content database to the updated computers.
To attach the content database
1. Click Start, point to All Programs, point to Administrative Tools, and then click
SharePoint 3.0 Central Administration.
2. On the Central Administration site, click Application Management.
3. On the Application Management page, in the SharePoint Web Application
Management section, click Content databases.
4. On the Manage Content Databases page, click Add a content database.
5. Enter the information for the content database you detached earlier.
6. Repeat steps 4 and 5 for every content database you want to attach.
You must perform the following procedure on all indexers and query servers in your server farm if
either of the following conditions is true:
The account that you are using for the search service is either:
214
3. Log on to each computer, either locally or through a remote connection, that is returned in
the list from the previous step and run the following command:
stsadm -o spsearch -action start
Large-farm optimization
In very large server farms, installing a software update with the content databases attached is not
practical in terms of downtime. In the scenario where you have a large number of sites or many
Web servers, to minimize the downtime required to upgrade, we recommend that you perform the
additional step of detaching the content databases. For the best performance with the upgrade
operations, you should use four or five front-end Web servers per database server.
Note:
Unless you are dealing with a very large server farm, you do not need to follow this
procedure.
To detach content databases
1. To detach a content database using Stsadm, open a command prompt and change
directories to %COMMONPROGRAMFILES%\Microsoft Shared\Web server
extensions\12\Bin.
2. Run the following operation from the command line:
stsadm -o deletecontentdb -url http://computername -databasename
In this operation, -url specifies the Web application from which the content databases will
be detached and -databasename specifies the name of content database to be
detached.
Note:
If your database server is on a separate server, you need to use the
-databaseserver parameter to specify the database server name.
After you upgrade your server farm, you must attach the content databases back to the server
farm. You can only attach one content database to the server farm at a time, because when you
attach the databases to the upgraded server farm, the content database is upgraded
automatically.
If you want to streamline the upgrade process even further, you can configure additional
computers as Web servers running Windows SharePoint Services 3.0 with SP1 in a singlecomputer server farm; we recommend four to five Web servers. You must configure alternate
access mappings on these temporary front-end Web servers to match the original servers. If the
alternate access mappings are not identical, the content databases may be upgraded with the
wrong URLs within their site content. This will result in certain pages not displaying correctly, and
you must contact Microsoft Product Services to correct this problem. Then, to perform a parallel
upgrade of the content databases, use these Web servers to upgrade the content databases
while they are detached from the original server farm.
215
After you detach the upgraded content databases from the temporary Web server, and attach
them back to the original server farm, the content databases are ready for service. At this point,
you should remove any content databases from the previous version and then back up the server
farm.
Notes
If you detach and reattach a content database, be aware that the next time the content
within that content database is crawled a full crawl will occur, even if an incremental crawl
has been requested. Because a full crawl recrawls all content, regardless of whether that
content has been previously crawled, full crawls can take significantly more time to
complete than incremental crawls.
If you are running the Infrastructure Update for Windows SharePoint Services 3.0, the
identifier (ID) of each content database is retained when you restore or reattach the
database by using built-in tools. Default change log retention behavior when using built-in
tools is as follows:
When a database ID and change log are retained, Search continues crawling based on
the regular schedule defined by crawl rules. When a change log is not retained, Search
performs a full crawl during the next scheduled crawl.
For more information, see Move all databases (http://technet.microsoft.com/enus/library/cc512723.aspx) and Back up and restore the farm
(http://technet.microsoft.com/en-us/library/cc287896.aspx).
The limiting factor for this method is that you cannot simultaneously update more than one
content database for each Web applicationeven if you use multiple computers.
Verify installation
After you install a software update, you should verify that the installation was successful by
reviewing the upgrade log file (Upgrade.log), as described in the following procedure.
To view the upgrade log file
1. In Windows Explorer, change to the following directory:
%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS
2. Use a text editor to open the Upgrade.log file.
3. Scroll to the date on which you installed the software update.
4. Search, or visually scan, for the following entries:
Finished upgrading SPFarm Name=<Name of Configuration Database>
In-place upgrade session finishes. Root object = SPFarm=<Name of Configuration
Database>, recursive = True. 0 errors and 0 warnings encountered.
If you find these entries, the installation was successful.
5. If you do not find the entries from the previous step, you can identify specific issues that
may have contributed to the failure by searching, or visually scanning, through the
Upgrade.log file for the following terms:
216
fail
error
After you identify and resolve the blocking issues, use the "To force a software update"
procedure later in this section.
In some configurations, the SharePoint Timer Service (OWStimer) accountwhich, by default, is
the same account used by the SharePoint Central Administration v3 application pool account
is configured with credentials that do not have permission to access the LOGS folder in
%COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case,
part of the Upgrade.log is stored in the temporary storage folder of the account that is running the
SharePoint Timer service.
To write all available logging information, including verbose output and detailed debugging
information, to the log files for the software update installation, run the following command:
msiexec /p <PatchPackage> /l*vx %temp%\patch.log
Where PatchPackage is the path to the software update file.
You can find the log file in the temporary file location with the file name msi*.log.
Note:
You can enable Windows Installer logging before you start the software update
installation again. To enable logging for Windows Installer, see Microsoft Knowledge Base
article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/?
LinkID=99206).
In addition to the previous procedure, verify that the update was successful by using the
SharePoint Central Administration Web site to view the version number on the Servers in Farm
page.
To view the Servers in Farm page
1. Use one of the following methods to open the Servers in Farm page:
On the Central Administration home page, click Operations. Then, on the Operations
page, in the Topology and Services section, click Servers in farm.
2. On the Servers in Farm page, next to Version, verify the version number of each server
in the farm to verify that each one has been updated to the new binary version.
The following Windows SharePoint Services 3.0 version numbers are correct:
Release 12.0.0.4518
217
If the version number matches the version number for the software update, you have
succeeded in updating the server. If the version number is not correct, the software
update installation did not complete successfully. To identify and resolve the blocking
issues, follow the "To view the upgrade log file" procedure earlier in this article.
If you need to investigate the success of the software update installation in more depth, use the
following procedure to verify version numbers on certain files and verify certain keys in the
registry.
To perform advanced installation verification
1. You can examine the version number of certain files in %COMMONPROGRAMFILES
%\Microsoft Shared\Web server extensions\12\ISAPI
The following Windows SharePoint Services 3.0 owssvr.dll version numbers are correct:
Release 12.0.4518.1016
2. Verify that the value is correct in the Version key in the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
Extensions\12.0
You can also verify that the software update installation was successful by using SQL Query
Analyzer to examine the SQL Server schema. Although the version of the DLL files and the
registry are updated during the first part of an upgradewhen the files are being copiedthe
SQL Server schema is only upgraded after the SharePoint Products and Technologies
Configuration Wizard is run.
Note:
The SSP databases could have different version numbers and the SSO databases do not
have a versions table.
You should use the following procedure to determine if the SharePoint Products and Technologies
Configuration Wizard was run after the software update.
To verify through direct examination of the SQL schema
This SQL Server query can be run on any SharePoint Products and Technologies
database to track all the upgrades run on the database in the GUID 00000000-00000000-0000-000000000000:
SELECT * FROM Versions
218
The highest value that maps to the GUID above should equal the current version of the
product. For Service Pack 1 the version should include 6211.
If the installation did not succeed, you can run the SharePoint Products and Technologies
Configuration Wizard again, or you can use the following procedure to complete the configuration
from the command line.
Note:
You can enable Windows Installer logging before you start the software update
installation again. For information, see Microsoft Knowledge Base article 99206: How to
enable Windows Installer logging (http://go.microsoft.com/fwlink/?LinkID=99206).
To force a software update
1. Open a Command Prompt window and change to the following directory:
%COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin
2. Type the following command:
psconfig cmd upgrade inplace b2b wait force
You can create an installation source location that already contains the software updates that
match those installed on your server farm by using the updates folder. For more information, see
the topic Create an installation source that includes software updates (Windows SharePoint
Services 3.0).
If you need to build a new server to join an existing server farm, but you have not created an
updated installation source, you must use the following procedure.
To build a server to join an existing farm
1. Install the product without any software updates and do not run the SharePoint Products
and Technologies Configuration Wizard.
Note:
By not running the SharePoint Products and Technologies Configuration Wizard
219
you do not define the location for the configuration database by creating the
registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared
Tools\Web server extensions\12.0\Secure\ConfigDB.
2. Install the software update.
3. Run the SharePoint Products and Technologies Configuration Wizard at the prompt.
If you do not follow this process and you do run the SharePoint Products and Technologies
Configuration Wizard after you install the released product, the SharePoint Products and
Technologies Configuration Wizard reads the ConfigDB registry key and the SharePoint
Products and Technologies Configuration Wizard displays: Exception:
System.InvalidOperationException: Operation is not valid due to the current state of the
object. To address this problem, you must either modify the registry or use the command line to
force the configuration to complete successfully.
Use registry editor to modify the contents of the ConfigDB registry key and then run the
SharePoint Products and Technologies Configuration Wizard.
To force an install after a failed configuration by modifying the registry
1. Install the software update and do not allow the SharePoint Products and Technologies
Configuration Wizard to run.
2. Use a registry editor to modify the setup type to a clean install. Change the registry key to
the following:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web server
extensions\12.0\WSS\SETUPTYPE=CLEAN_INSTALL
3. Run SharePoint Products and Technologies Configuration Wizard to perform a
disconnect operation.
4. Run SharePoint Products and Technologies Configuration Wizard to connect to your
server farm.
Use the Psconfig command-line tool.
Note:
For more information about using Psconfig, see Command-line reference for the
SharePoint Products and Technologies Configuration Wizard
(http://technet.microsoft.com/en-us/library/cc263093.aspx).
To force an install after a failed configuration (command line)
1. Install the product without any software updates and do not run the SharePoint Products
and Technologies Configuration Wizard.
2. Install the software update and do not run the SharePoint Products and Technologies
Configuration Wizard.
3. Open a Command Prompt window and run the following command:
psconfig -cmd configdb -connect -server <SQLServerName> -database
SharePoint_Config_<dbname> -user <domainusername> -password <password>
220
Known issues
This section describes common errors you might encounter and what you need to do to fix them.
221
222
Software updates for GroupBoard Workspace 2007 that were released before Service Pack 1
were not installed on your Web servers running Windows SharePoint Services 3.0.
GroupBoard Workspace 2007 is installed on your Web servers running Windows SharePoint
Services 3.0.
To verify that this issue was the reason that the software update installation failed, you can
review the upgrade log file for the following error message:
[SPManager] [ERROR] [2/5/2008 4:36:23 PM]: The specified SPContentDatabase
Name=SharePoint_AdminContent_913f064d-579e-4029-9522-ec21ecc6f0c1
Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE has been upgraded to a
newer version of SharePoint. Please upgrade this SharePoint application server before
attempting to access this object.
To resolve this issue, follow one these processes:
Apply the GroupBoard Workspace 2007 patch, install the Windows SharePoint Services
3.0 software update, and then run the SharePoint Products and Technologies
Configuration Wizard.
Remove GroupBoard Workspace 2007, install the Windows SharePoint Services 3.0
software update, run the SharePoint Products and Technologies Configuration Wizard,
and then reinstall GroupBoard Workspace 2007.
To manually run the SharePoint Products and Technologies Configuration Wizard from the
command line, you can use the following command from the %COMMONPROGRAMFILES
%\Microsoft Shared\Web server extensions\12\Bin directory:
psconfig -cmd upgrade -inplace b2b -wait force
The GroupBoard product team has developed a software update to enable you to install the
Windows SharePoint Services 3.0 software update with GroupBoard installed. For more
information, see Microsoft Knowledge Base article 941678: The SharePoint Products and
Technologies Configuration Wizard does not finish successfully on a computer that also has
GroupBoard Workspace 2007 installed (http://go.microsoft.com/fwlink/?
LinkId=102051&clcid=0x409).
See Also
223
224
4. Copy the files that you extracted from the Windows SharePoint Services 3.0 software
update package to the updates folder you created in the previous step.
5. You can now use this location as an installation point, or you can create an image of this
source that you can burn to a CD-ROM.
Note:
If you extracted the software update files to a location to which you had
previously copied the source for a released version, the source is updated and is
ready to use.
As an alternative to creating an updated installation source, you can download Windows
SharePoint Services 3.0 with Service Pack 1 (SP1) as an updated version at the following
location:
225
You will need to address any installation issues on the computer running Windows Server 2003
before preparing Windows SharePoint Services 3.0 for the upgrade.
226
Turn off LUA and then repeat the instructions in this step.
Run Setup.exe from an installation point (where you have extracted the SP1 files to
the Updates folder). When Setup prompts you to choose an action, choose Repair.
227
you must grant the Windows SharePoint Services Timer (SPTimerV3) service permission to read
from Internet Information Services (IIS) 7.0. Examples of symptoms that you might experience if
the SPTimerV3 service does not have the appropriate permissions include:
Web application creation could fail in server farms with more than one Web application.
Operations that use the timer job to query for IIS Web site properties could fail.
To grant the SPTimerV3 service permission to read from IIS 7.0
1. Log on to the computer with a domain account that is a member of the Administrators
group on the local computer.
2. Open an elevated command prompt window. Click Start, point to All Programs, click
Accessories, right-click Command Prompt, and then click Run as administrator.
3. Change directory to %COMMONPROGRAMFILES%\Microsoft Shared\Web server
extensions\12\BIN.
4. Run the command:
stsadm -o grantiis7permission
The following messages confirm the changes:
Granting permission to SPTimerV3 service to read from IIS 7.0 or above.
Operation completed successfully.
Known issues
Repair not allowed when Least User Access is enabled
After the Windows Server 2008 installation is complete, when you open Programs and Features
to repair Windows SharePoint Services 3.0 or language template packs, you will not be able to
run the repair operation if LUA is enabled (the default setting). Before running repair, make sure
LUA is disabled.
228
2. Open a command prompt window and restart IIS with the following command:
restartiis
3. To install Windows Internal Database, included with Windows Server 2008, open Server
Manager, click Features, click Add Features, select the Windows Internal Database
check box, and then click Install to complete the Add Features Wizard.
4. Use the Microsoft SQL Server 2005 Command Line Query Utility (sqlcmd) to start the
Windows Internal Database:
sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E
Note:
The sqlcmd utility is a free download, but because sqlcmd requires Microsoft
SQL Server Native Client, we recommend that you download the entire Feature
Pack for Microsoft SQL Server 2005 (http://go.microsoft.com/fwlink/?
LinkId=70728). For more information about the sqlcmd utility, see sqlcmd Utility
(http://go.microsoft.com/fwlink/?LinkId=81183).
5. Run the following command for each Windows SharePoint Services 3.0 database (*.mdf)
and log file (*_log.ldf). By default, all files will be in the following folder:
%Windows%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data
EXEC sp_attach_db @dbname = '<dbname>', @filename1 =
'<drive:\path\Data>\<dbname>.mdf', @filename2 =
<drive:\path\Data>\<dbname>_log.ldf'
Go
Note:
You should see, at a minimum, these databases: configdb, contentdb, admin
contentdb, and searchdb.
229
If the Windows SharePoint Services Search service was running before you started this step,
you must restart it by running the following command:
stsadm -o spsearch -action start -databaseserver %_be% -databasename wsssearch
8. If you completed a binary repair in the "Perform post-installation procedures" section you
can skip this step. Otherwise, to perform a binary repair, click Start, click Control Panel,
click Programs and Features, select Windows SharePoint Services 3.0, and then click
Change.
9. Run the SharePoint Products and Technologies Configuration Wizard to configure
Windows SharePoint Services 3.0.
230
231