Getting Started With Windows Share Point Services 3.0

Getting Started with Windows SharePoint
Services 3.0
Microsoft Corporation
Published: March 2009
Author: Microsoft Office System and Servers Team (o12ITdx@microsoft.com)
Abstract
This book provides basic information about capabilities of and requirements for Windows
SharePoint Services 3.0. The audiences for this book include application specialists, line-of-
business application specialists, information architects, IT generalists, program managers, and
infrastructure specialists who are just starting to learn about Windows SharePoint Services 3.0
and want a quick introduction plus installation steps.
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 publication date. For the
most current content, see the technical library on the Web.
2
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 White Paper 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, email address, logo, person, place
or event is intended or should be inferred.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Microsoft, Access, Active Directory, Excel, Groove, InfoPath, Internet Explorer,
OneNote, Outlook, 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 Started with Windows SharePoint Services 3.0.....................................................1
Abstract.......................................................................................................................1
Contents............................................................................................................................iii
Getting Help.......................................................................................................................v
Introduction to Getting Started with Windows SharePoint Services 3.0 technology...........1
What's new for IT professionals in Windows SharePoint Services 3.0...............................2

Administration model enhancements.................................................................................2
Centralized configuration and management................................................................2
Two-tier administration model......................................................................................3
Farm-based Central Administration user interface.......................................................3
Delegation of administrative responsibilities and roles................................................3
New and improved compliance features and capabilities...................................................4
Policy management.....................................................................................................4
Auditing and logging....................................................................................................4
Item-level access control.............................................................................................4
Administrator access control........................................................................................4
New and improved operational tools and capabilities........................................................4
Backup and recovery support......................................................................................5
Upgrade and migration support...................................................................................5
Monitoring support.......................................................................................................5
Host header mode.......................................................................................................5
Server renaming..........................................................................................................6
Credential management..............................................................................................6
Improved support for network configuration.......................................................................6
Alternate access mappings..........................................................................................6
Pluggable authentication.............................................................................................6
Extensibility enhancements................................................................................................7
For further reading: Evaluation guide for Windows SharePoint Services 3.0 technology...8
Determine hardware and software requirements...............................................................9

About hardware and software requirements......................................................................9
Stand-alone installation....................................................................................................10
Hardware requirements.............................................................................................10
Software requirements...............................................................................................11
Server farm installation....................................................................................................13
Front-end Web server................................................................................................13
Database server........................................................................................................16
iii
Plan browser support ......................................................................................................17
About browser support.....................................................................................................17
Levels of browser support................................................................................................17
Level 1 Web browsers...............................................................................................17
Level 2 Web browsers...............................................................................................17
Feature-specific compatibility listed by Web browser.......................................................18
Install Windows SharePoint Services 3.0 on a stand-alone computer.............................21

Hardware and software requirements..............................................................................22
Configure the server as a Web server..............................................................................22
Install and configure IIS.............................................................................................22
Install the Microsoft .NET Framework version 3.0.....................................................23
Enable ASP.NET 2.0..................................................................................................23
Install and configure Windows SharePoint Services 3.0 with Windows Internal Database
......................................................................................................................................23
Post-installation steps......................................................................................................26
Deploy in a simple server farm.........................................................................................28

Deployment overview.......................................................................................................28
Suggested topologies................................................................................................29
Before you begin deployment....................................................................................29
Overview of the deployment process.........................................................................30
Deploy and configure the server infrastructure.................................................................30
Prepare the database server.....................................................................................30
Verify that servers meet hardware and software requirements..................................32
Run Setup on all servers in the farm..........................................................................34
Start the Windows SharePoint Services Search service............................................39
Perform additional configuration tasks.............................................................................40
Create a site collection and a SharePoint site..................................................................41
Configure the trace log..............................................................................................46
Roadmap to Windows SharePoint Services 3.0 content..................................................48

Windows SharePoint Services 3.0 content by audience..................................................48
Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle...49
Evaluate.....................................................................................................................50
Plan...........................................................................................................................50
Deploy.......................................................................................................................51
Operate......................................................................................................................53
Security and Protection..............................................................................................53
Technical Reference..................................................................................................54
Solutions....................................................................................................................54
iv
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
v
Introduction to Getting Started with Windows
SharePoint Services 3.0 technology
Windows SharePoint Services 3.0 is a versatile technology that organizations and business units
of all sizes can use to increase the efficiency of business processes and improve team
productivity. Windows SharePoint Services 3.0 gives people access to information they need by
using tools for collaboration that help people stay connected across organizational and
geographic boundaries.
This Getting Started guide for Windows SharePoint Services 3.0 covers what's new in Windows
SharePoint Services 3.0, provides references to evaluation content, and includes several end-to-
end deployment scenarios to get you started quickly with an evaluation environment for Windows
SharePoint Services 3.0. The following list describes each topic in this guide.
• What's new for IT professionals in Windows SharePoint Services 3.0 introduces the new
capabilities and features in Windows SharePoint Services 3.0.
• Φο ρ φ υ ρ τ η ε ρ ρ ε α δ ι ν γ: Εϖα λ υ α τ ι ο ν γ υ ι δ ε φ ο ρ
Ω ι ν δ ο ω σ Σ η α ρ ε Π ο ι ν τ Σ ε ρ ϖ ι χ ε σ 3.0 τ ε χ η ν ο λ ο γ ψ
provides a reference to a download location for the evaluation guide for Windows SharePoint
Services 3.0. The evaluation guide covers key features, overviews of the product, and a
product tour.
• ∆ ε τ ε ρ µ ι ν ε ηα ρ δωα ρ ε α ν δ σ ο φ τ ωα ρ ε
ρ ε θ υ ι ρ ε µ ε ν τ σ describes the minimum and recommended hardware and
software that are required to run Windows SharePoint Services 3.0.
• Π λ α ν β ρ ο ω σ ε ρ σ υ π π ο ρ τ describes the functionality available and level
of support for Windows SharePoint Services 3.0 features that you can expect when using
several common Web browsers.
• Ι ν σ τ α λ λ Ω ι ν δ ο ω σ Σ η α ρ ε Π ο ι ν τ Σ ε ρ ϖ ι χ ε σ 3.0 ο ν α
σ τ α ν δ − α λ ο ν ε χ ο µ π υ τ ε ρ provides end-to-end installation instructions for
setting up Windows SharePoint Services 3.0 in a stand-alone environment. This installation
scenario is ideal for evaluating Windows SharePoint Services 3.0 functionality, or for hosting
a very small installation of Windows SharePoint Services 3.0.
• ∆ ε π λ ο ψ ι ν α σ ι µ π λ ε σ ε ρ ϖ ε ρ φ α ρ µ provides end-to-end
instructions for installing Windows SharePoint Services 3.0 in a simple server farm. A simple
server farm consists of one or more Web servers and one or more database servers running
Microsoft SQL Server 2000 or SQL Server 2005 database software.
• Ρ ο α δ µ α π τ ο Ω ι ν δ ο ω σ Σ η α ρ ε Π ο ι ν τ Σ ε ρ ϖ ι χ ε σ 3.0
χ ο ν τ ε ν τ provides you with an overview of the content available on the Microsoft.com
Web site that can help you understand and use Windows SharePoint Services 3.0 as you go
beyond the basics that are presented in this guide.
1
What's new for IT professionals in Windows
SharePoint Services 3.0
Windows SharePoint Services 3.0 has many new features and enhancements that can help IT
professionals deploy and maintain Windows SharePoint Services solutions. Together, these new
features and enhancements provide IT organizations with better control over information
resources; individually these new features and enhancements provide functional benefits that
help reduce administrative overhead and help IT administrators work more efficiently and
effectively. The changes that impact IT organizations and IT professionals the most include:
• An improved administration model that centralizes configuration and management tasks,
and helps IT organizations delineate and delegate administrative roles.
• New and improved compliance features and capabilities that help organizations secure
resources and manage business-critical processes.
• New and improved operational tools and capabilities that drive down the total cost of
ownership (TCO).
• Improved support for network configuration.
Improved extensibility of the object model that makes custom applications and components
easier to deploy and manage.
Administration model enhancements

Windows SharePoint Services 3.0 includes several enhancements to the administration model
that help IT organizations implement management plans and perform administrative tasks more
effectively and efficiently.
Centralized configuration and management

Windows SharePoint Services 3.0 now has a centralized configuration and management model,
which includes a centralized configuration database and two new services that automatically
propagate and synchronize the centrally-stored configuration settings across all of the servers in
your server farm. The new configuration and management model allows you to centrally manage
your server farm without having to manage farm settings on a server-by-server basis. For
example, if you create a Web application on one of your Web servers, the Web application is
automatically propagated to all of your Web servers. You no longer have to create and configure
individual Web applications on each of your Web servers.
To facilitate this centralized configuration model, Windows SharePoint Services 3.0 relies on two
new and enhanced services: the Windows SharePoint Services Administration service and the
Windows SharePoint Services Timer service. The Windows SharePoint Services Timer service
acts as the heartbeat for the server farm and is responsible for running timer jobs that propagate
configuration settings across a server farm. The Windows SharePoint Services Administration
2
service works hand in hand with the Windows SharePoint Services Timer service and is
responsible for carrying out the actual configuration changes on each of the servers in your
server farm.
Two-tier administration model

Windows SharePoint Services 3.0 now has a two-tier administration model that makes it easier
for IT organizations to differentiate administrative roles and assign administrative responsibilities.
Tier 1 Encompasses all of the administrative features and functionality for centrally managing
the server farm. Tier 1 administrative tasks are typically performed by an organization's IT
administrators and can include a wide range of tasks such as farm-level resource management
tasks, farm-level status checks and monitoring, and farm-level security configuration. For
example, a tier 1 administrator might be responsible for creating new Web applications and site
collections, managing incoming and outgoing e-mail settings for the farm, and managing server
farm topology.
Tier 2 Encompasses all of the administrative features and functionality for managing sites within
a server farm. Tier 2 administrative tasks are typically performed by a business unit site
administrator and can include a wide range of site-specific management tasks such as Web Part
management, access management, and content management. For example, a tier 2
administrator might be responsible for creating a new list on a site, configuring access
permissions for users, and modifying site hierarchy.
Farm-based Central Administration user interface

The SharePoint Central Administration Web pages have been redesigned and reorganized,
allowing easier implementation of administrative tasks and procedures. These changes include
the following new features:
Administrative task list Shows you the key tasks that need to be done, explains why the
actions are needed, and provides a link directly to the SharePoint Central Administration Web
page where the task can be performed.
Home page topology view Provides a concise view of the servers that are running in a farm
and the services that are running on each server.
Services on Server Web page Provides an easy way to manage the services that are running
on an individual server.
Flat menu structure The SharePoint Central Administration home page consists of just two
top-level navigation pages: an Operations page that lists tasks affecting farm resource usage,
and an Application Management page that lists tasks specific to a single application or service
within the farm.
Delegation of administrative responsibilities and roles

Because the multi-tier administration model provides a clear delineation of administrative tasks,
IT managers can better delegate administrative responsibilities to the appropriate users and
administrators within an organization.
3
New and improved compliance features and
capabilities
Windows SharePoint Services 3.0 includes new and enhanced features that provide IT
organizations with better control over information resources. These new and enhanced
compliance features include:
Policy management
You can now configure policies for Web applications based on the domain or the server
authentication zone. For example, you can create intranet and extranet authentication zones to
restrict access to information based on how users access information. You can also use
authentication zones to create access control lists (ACLs) that include a group of users from
different authentication providers.
Auditing and logging

Auditing and logging can now be configured for all actions on sites, content, and workflows.
Item-level access control

Windows SharePoint Services 3.0 provides item-level access control and security settings that
allow site administrators and IT administrators to control which people or groups have access to
sites, document libraries, lists, folders, documents, and list items. In addition to controlling access
to Web page content, item-level access also allows administrators to control which user interface
(UI) elements are visible or actionable. This feature, known as UI trimming, also reduces Web
page clutter and makes Web pages easier to navigate.
Administrator access control

Windows SharePoint Services 3.0 now prohibits IT administrators from viewing site content
unless the IT administrator is granted site collection administrator privileges. In addition, an event
is written to the Event Viewer application log whenever an IT administrator changes site collection
administrator privileges.
New and improved operational tools and

capabilities
Windows SharePoint Services 3.0 includes several new and improved tools and capabilities that
help IT organizations implement operational plans and tasks. These features and capabilities
include:
4
Backup and recovery support
Several new and improved features make it easier to perform backup and recovery tasks. A multi-
stage recycle bin allows users to retrieve inadvertently deleted documents, reducing dependence
on IT departments for document retrieval functions. The recycle bin also allows administrators to
manage the lifecycle of deleted items in the recycle bin.
The backup and restore functionality is also enhanced, providing support for Volume Shadow
Copy Service (VSS), which allows better integration with non-Microsoft backup and recovery
programs. In addition, the backup and restore functionality in Windows SharePoint Services 3.0
allows you to back up and restore the data that is stored in your SQL database, such as your
configuration database, content and configuration data for Web applications, and search
databases. Also, backup and recovery functionality is provided natively at the command line
through the Stsadm command, and it is provided in the user interface.
Upgrade and migration support

The following features have been added to make upgrades faster and easier:
Gradual upgrade support By performing a gradual upgrade you can gradually upgrade data
and functionality on a server that is running Microsoft Windows SharePoint Services (version 2)
and Windows SharePoint Services 3.0. This is particularly useful if you are upgrading a complex
environment and you do not want to interrupt business processes.
Migration support Windows SharePoint Services 3.0 provides support for migrating content.
You can migrate content for an entire Web site or you can migrate content on a more granular
basis, such as lists and documents. In addition, you can migrate content incrementally. Migration
mode support cannot be used to migrate customized settings, features, solutions, or computer
settings; migration mode support can only be used to migrate content.
Reparenting This allows you to dynamically rearrange a hierarchy of SharePoint sites and is
typically used during a migration. Previously, in Window SharePoint Services (version 2), you
needed to back up and then delete a site from its current location, and then restore the site in the
new location to move a site.
Monitoring support
Improved instrumentation is provided through Microsoft Operations Manager (MOM)
management packs. MOM packages support centralized monitoring and management of
configurations ranging from single server and small server farms to very large server farms.
Host header mode

Host header mode, a new feature in Windows SharePoint Services 3.0, allows you to create
multiple domain-named sites in a single Web application. In Windows SharePoint Services
version 2, when scalable hosting mode was enabled, you could extend only one Microsoft
Internet Information Services (IIS) Web site. Now, with host header mode, you can have host
header-based site collections on multiple Web applications, so you're no longer limited to
extending just one IIS Web site. In fact, you can have a mix of path-based and host header-based
5
site collections in the same Web application. In addition, you do not need to specify whether you
want to use host header site collections when creating the configuration database. Instead, you
can now specify whether site collections should be host header-based or path-based when
creating the site collection.
Server renaming
Windows SharePoint Services 3.0 now has the command Stsadm renameserver command that
makes it easier to rename your Web servers and your back-end database servers. When you run
Stsadm renameserver, the configuration database for your farm is updated so that any URLs or
references to the old server name are now mapped to the new server name.
Credential management
You can now manage service account credentials, such as the application pool identity for your
application pools, through the SharePoint Central Administration site. In addition, when you
change the user account under which a service runs, Windows SharePoint Services 3.0 uses the
Windows SharePoint Services Administration service and the Windows SharePoint Services
Timer service to stop and start Microsoft Internet Information Services (IIS) services across your
farm so that the credential changes immediately take effect. You can also change just the
password for a service account through the command line.
Improved support for network configuration

Windows SharePoint Services 3.0 includes enhanced support for network configuration,
including:
Alternate access mappings

Alternate access mappings (AAM) provides a mechanism for mapping newly-added front-end
Web servers to your Web application. For example, if you install and configure Windows
SharePoint Services 3.0 on a single front-end server, and a user browses to your server, the
server will render the content that is in your Web application. However, if you add subsequent
Web servers to your server farm, the newly-added servers will not have alternate access
mappings configured to your Web application.
Pluggable authentication
Windows SharePoint Services 3.0 adds support for non-Windows-based identity systems by
integrating with the pluggable Microsoft ASP.NET forms authentication system. ASP.NET
authentication allows Windows SharePoint Services 3.0 to work with identity management
systems that implement the MembershipProvider interface. You do not need to rewrite the
security administration pages or manage shadow Active Directory directory service accounts.
6
Extensibility enhancements
Windows SharePoint Services 3.0 has several extensibility enhancements that make it easier to
create custom applications that are well integrated with Windows SharePoint Services 3.0
features, functionality, and user interface elements.
• Site definitions have been enhanced so that sites are no longer locked or bound to your
original template choice. For example, you can now enhance a document workspace site with
features from a team site.
• Administration tasks and functionality can be extended to custom applications. For
example, if you create a custom database by extending a database that was created by
Windows SharePoint Services 3.0, you can have the custom database automatically appear
in the backup and restore user interface.
• Enhancements to the Windows SharePoint Services Timer service make it easier to
create and manage timer jobs that control custom services.
In addition, Windows SharePoint Services 3.0 hosts the Windows Workflow Foundation, which
allows the creation of customized workflow solutions and the use of structured workflows on
document library and list items. In conjunction with the Windows SharePoint Services 3.0
application templates, the Windows Workflow Foundation allows you to create robust workflow-
enabled business applications.
7
For further reading: Evaluation guide for
Windows SharePoint Services 3.0
technology
This evaluation guide is designed to give you a solid understanding of the design goals and
feature set for Windows SharePoint Services 3.0 and a familiarity with the product
implementation. It provides an overview of the solutions and benefits enabled by Windows
SharePoint Services 3.0 as well as descriptions of new and improved features in the areas of
collaboration, storage and security, deployment and management, user interface, and platform
extensibility. It also provides a hands-on tour of the main feature areas of Windows SharePoint
Services 3.0 and includes useful information for administrators and developers.
The ultimate goal of this guide is to aid the reader in performing a thorough and effective
evaluation of Windows SharePoint Services 3.0. This guide is intended for anyone who is
interested in learning more about Windows SharePoint Services 3.0 and wants hands-on
experience.
Download this guide as a Microsoft Word document (.doc).
Windows SharePoint Services 3.0 Evaluation Guide (http://go.microsoft.com/fwlink/?
LinkId=86962&clcid=0x409)
8
Determine hardware and software
requirements
In this section:
• About hardware and software requirements
• Stand-alone installation
• Server farm installation
This section describes the hardware and software requirements for installing Windows
SharePoint Services 3.0.
About hardware and software requirements

An installation of Windows SharePoint Services 3.0 can range from a single computer (stand-
alone installation) to many computers (server farm). The requirements for your installation will
depend on the availability and scale requirements for your solution. This section describes the
minimum and recommended hardware requirements based on whether you are deploying a
stand-alone installation or a server farm. This section also lists the software prerequisites for
installing Windows SharePoint Services 3.0.
This section does not provide guidance about choosing a farm topology or hardware based on
availability requirements or performance and capacity requirements. For more information about
designing your solution to address these requirements, see Plan for performance and capacity
(http://technet.microsoft.com/en-us/library/cc288124.aspx).
The hardware and software requirements described in this section apply to both x32-bit–based
and x64-bit–based systems. However, if you installed the 64-bit version of Windows Server 2008
and then modified the Enable32bitAppOnWin64 registry key so that Internet Information Server
(IIS) is running in 32-bit emulation mode, you cannot install Windows SharePoint Services 3.0.
To install either 32-bit or 64-bit Windows SharePoint Services 3.0 you must run IIS in 64-bit mode.
Note:
Itanium-based systems are not supported.
Using a mix of 32-bit servers and 64-bit servers in a server farm is supported. However, this
scenario is not recommended because of the potential performance issues that could occur. For
example:
• With a clustered front-end Web server that uses round robin, the 32-bit server will be the
bottleneck.
• If a 64-bit front-end Web server is making calls to a 32-bit SQL Server database, there
may be a bottleneck if SQL Server does not have adequate resources. This also applies to a
64-bit indexer that is working against a 32-bit SQL Server database.
9
If circumstances require a heterogeneous server architecture, we recommend that you use
homogeneous (32-bit or 64-bit) servers on each application tier, for example, 32-bit servers for all
the front-end Web servers.
If server farm performance in a heterogeneous environment becomes an issue, the
recommended solution is to migrate all of the SharePoint farm servers to the 64-bit architecture.
We highly recommend that you have a migration plan in place to move to a 64-bit only
environment as soon as possible. Our support and test data shows that SharePoint products and
technologies that are installed on 64-bit servers have significant gains in system throughput and
performance during peak loads.
Note:
While migrating 32-bit servers to 64-bit servers there will be times during the migration
process that you cannot maintain homogenous servers on each tier. However,
performance issues will only occur during the migration process.
Stand-alone installation
You can install Windows SharePoint Services 3.0 on a single computer by using either of the
following methods:
• By selecting Basic.
• By selecting Advanced, and then selecting Stand-alone in Windows SharePoint
Services 3.0 Setup.
Hardware requirements
The following table lists the minimum and recommended hardware requirements for deploying
Windows SharePoint Services 3.0, including the deployment of Windows Internal Database, for a
stand-alone installation.
Component Minimum Recommended
Processor 2.5 gigahertz (GHz) Dual processors that are each

3 GHz or faster
RAM 1 gigabyte (GB) 2 GB
Disk NTFS file system–formatted NTFS file system–formatted

partition with a minimum of partition with 3 GB of free space
3 GB of free space plus adequate free space for
your Web sites
Drive DVD drive DVD drive or the source copied

to a local or network-accessible
drive
Display 1024 × 768 1024 × 768 or higher resolution
10
monitor
Network 56 kilobits per second (Kbps) 56 Kbps or faster connection

connection between client between client computers and
computers and server server
Software requirements
The Windows SharePoint Services 3.0 installation and configuration wizard marshals many
components. 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, which would cause the entire installation process to fail. You can prevent
this failure by deleting the existing configuration database or by using the psconfig command to
create a new configuration database.
Database
When you perform a Basic installation, Windows Internal Database is automatically installed.
When you perform an Advanced installation on a stand-alone computer that already has Microsoft
SQL Server installed, ensure that the computer meets the hardware and software requirements
for a database server. For more information, see Database server later in this section.
Note:
If you are installing Windows SharePoint Services 3.0 with Service Pack 1 (SP1) on
Windows Server 2008, setup installs Windows Internal Database with Service Pack 2
(SP2).
Because of Windows licensing restrictions, if you are using Windows Server 2003, Web Edition in
a single server environment, you can only perform an Advanced, front-end Web server
installation. This is because the full SQL Server editions cannot be installed on Windows Server
2003, Web Edition. In this scenario, you need to have a full SQL Server edition installed on a
compatible edition of Windows Server 2003 for use with Windows SharePoint Services 3.0.
Windows Server 2003, Web edition does not support Basic installation of Windows SharePoint
Services 3.0.
Operating system
Windows SharePoint Services 3.0 runs on Windows Server 2003 with SP1 or later. We
recommend that you apply all critical updates. You can use the following Windows Server 2003
editions:
• Windows Server 2003, Standard Edition
• Windows Server 2003, Enterprise Edition
• Windows Server 2003, Datacenter Edition
11
• Windows Server 2003, Web Edition
Because of Windows licensing restrictions, if you are using Windows Server 2003, Web
Edition in a single server environment, you can only perform an Advanced, front-end Web
server installation. This is because the full SQL Server editions cannot be installed on
Windows Server 2003, Web Edition. In this scenario, you need to have a full SQL Server
edition installed on a compatible edition of Windows Server 2003 for use with Windows
SharePoint Services 3.0. Windows Server 2003, Web edition does not support Basic
installation of Windows SharePoint Services 3.0.
Windows SharePoint Services 3.0 administration functions require Microsoft Internet Explorer 6.0
with the most recent service packs or Internet Explorer 7.0.
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 Windows NT 4.0 domain.
As of Windows SharePoint Services 3.0 with 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.
Windows components
After you have installed the operating system and applied all critical updates, you must configure
the computer to be a Web server by enabling Internet Information Services (IIS) 6.0, including:
• Common files
• WWW
• Simple Mail Transfer Protocol (SMTP)
You must configure the server to use IIS 6.0 worker process isolation mode. This is the default
setting in new installations. However, if you have upgraded from IIS 5.0 on Windows Server 2000,
Run WWW in IIS 5.0 isolation mode is enabled, and you must change this setting to use IIS 6.0
worker process isolation mode.
Note:
You must have IIS 7.0 installed to install Windows SharePoint Services 3.0 with SP1 on
Windows Server 2008. Windows SharePoint Services 3.0 does not support IIS 7.0
shared configuration.
To enable e-mail notifications, you need to configure incoming and outgoing e-mail settings. To
configure sending e-mail alerts and notifications, you must specify an SMTP e-mail server. To
configure your installation so that your SharePoint sites can accept and archive incoming e-mail,
you must install the IIS SMTP service.
12
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.
Microsoft .NET Framework 3.0

Before installing Windows SharePoint Services 3.0, you must install the Microsoft .NET
Framework 3.0 and then ensure that ASP.NET 2.0 is enabled.
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).
To enable ASP.NET v2.0.50727, open the Web service extension in the IIS snap-in on the
Microsoft Management Console (MMC). If ASP.NET 2.0 is installed on the computer before IIS is
enabled, you must enable ASP.NET 2.0 by running the command aspnet_regiis -i.
Server farm installation

The primary difference between a single server and a server farm topology is that you can use
one or more computers to host the following server roles:
• Front-end Web server
• Database server
This section describes the minimum and recommended system requirements for each server
role. If you install more than one role on a single computer, ensure that the computer meets the
minimum requirements for all server roles.
Front-end Web server
Hardware requirements
The following table lists the minimum and recommended hardware requirements for deploying a
Windows SharePoint Services 3.0 front-end Web server.
Processor 2.5 GHz Dual processors that are each

3 GHz or faster
RAM 2 GB More than 2 GB
Disk NTFS file system–formatted NTFS file system–formatted

partition with a minimum of partition with 3 GB of free space
13
3 GB of free space plus adequate free space for

your data storage requirements
Drive DVD drive DVD drive or the source copied

to a local or network-accessible
drive
Display 1024 × 768 1024 × 768 or higher resolution

monitor
Network • 56 Kbps connection • 56 Kbps or faster

between client computers connection between client
and server computers and server
• For connections • For connections
between computers in between computers in your
your server farm, server farm, 1 Gbps
100 Mbps connection connection
Software requirements
We recommend that you perform the installation on a computer that has a new installation of the
Microsoft Windows Server 2003 operating system with Service Pack 1 (SP1) or later and all
critical updates.
Operating system
Windows SharePoint Services 3.0 runs on Windows Server 2003 with SP1 or later. We
recommend that you apply all critical updates. You can use the following Windows Server 2003
editions:
• Windows Server 2003, Standard Edition
• Windows Server 2003, Enterprise Edition
• Windows Server 2003, Datacenter Edition
• Windows Server 2003, Web Edition
Because of Windows licensing restrictions, if you are using Windows Server 2003, Web
Edition in a single server environment, you can only perform an Advanced, front-end Web
server installation. This is because the full SQL Server editions cannot be installed on
Windows Server 2003, Web Edition. In this scenario, you need to have a full SQL Server
edition installed on a compatible edition of Windows Server 2003 for use with Windows
SharePoint Services 3.0. Windows Server 2003, Web edition does not support Basic
installation of Windows SharePoint Services 3.0.
Windows SharePoint Services 3.0 administration functions require Microsoft Internet Explorer 6.0
with the most recent service packs or Internet Explorer 7.0.
14
As of Windows SharePoint Services 3.0 with 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.
Windows components
After you have installed the operating system and applied all critical updates, you must configure
the computer to be a Web server by enabling IIS 6.0, including:
• Common files
• WWW
• SMTP
You must configure the server to use IIS 6.0 worker process isolation mode. This is the default
setting in new installations. However, if you have upgraded from IIS 5.0 on Windows Server 2000,
Run WWW in IIS 5.0 isolation mode is enabled, and you must change this setting to use IIS 6.0
worker process isolation mode.
Note:
You must have IIS 7.0 installed to install Windows SharePoint Services 3.0 with SP1 on
Windows Server 2008. Windows SharePoint Services 3.0 does not support IIS 7.0
shared configuration.
To enable e-mail notifications, you need to configure incoming and outgoing e-mail settings. To
configure sending e-mail alerts and notifications, you must specify an SMTP e-mail server. To
configure your installation so that your SharePoint sites can accept and archive incoming e-mail,
you must install the IIS SMTP service.
Important:
The following components are required for Windows SharePoint Services 3.0 to run
correctly: the Web Server role, and the Microsoft .NET Framework version 3.0. Do not
uninstall them, or Windows SharePoint Services 3.0 will cease to run.
Microsoft .NET Framework 3.0

Before installing Windows SharePoint Services 3.0, you must install the Microsoft .NET
Framework 3.0 and then ensure that ASP.NET 2.0 is enabled.
Note:
LinkId=110508).
To enable ASP.NET v2.0.50727, open the Web service extension in the IIS snap-in on the MMC.
If ASP.NET 2.0 is installed on the computer before IIS is enabled, you must enable ASP.NET 2.0
by running the command aspnet_regiis -i.
15
Database server
The computer that hosts the database server role must have SQL Server 2000 with the latest
service pack or Microsoft SQL Server 2005 SP1 or later. Some advanced features require SQL
Server 2005 Analysis Services SP1 or later.
Important:
You must update SQL Server 2000 to the latest service pack, which is SQL Server 2000
Service Pack 4. For more information, see Microsoft SQL Server 2000 Service Pack 4
(http://go.microsoft.com/fwlink/?LinkId=86989&clcid=0x409)
Note:
We recommend that you install SQL Server 2005 SP2 before upgrading to Windows
Note:
Windows SharePoint Services 3.0 supports SQL Server 2008. However, you must install
Windows SharePoint Services 3.0 SP1 or later before you install SQL Server 2008.
For information about the hardware and software required to deploy a database server, see SQL
Server 2005 System Requirements (http://go.microsoft.com/fwlink/?LinkID=75010&clcid=0x409).
Because of Windows licensing restrictions, if you are using Windows Server 2003, Web Edition in
a single server environment, you can only perform an Advanced, front-end Web server
installation. This is because the full SQL Server editions cannot be installed on Windows Server
2003, Web Edition. In this scenario, you need to have a full SQL Server edition installed on a
compatible edition of Windows Server 2003 for use with Windows SharePoint Services 3.0.
Windows Server 2003, Web edition does not support Basic installation of Windows SharePoint
Services 3.0.
16
Plan browser support
In this section:
• About browser support
• Levels of browser support
• Feature-specific compatibility list by Web browser
About browser support

Windows SharePoint Services 3.0 supports several Web browsers that are commonly used.
However, there are certain browsers that might cause some Windows SharePoint Services 3.0
functionality to be downgraded, limited, or available only through alternative steps. In some
cases, functionality might be unavailable for noncritical administrative tasks.
As part of planning your deployment of Windows SharePoint Services 3.0, we recommend that
you review the browsers used in your organization to ensure optimal performance with Windows
Levels of browser support

Web browser support is divided into two levels: level 1 and level 2. Although administrative tasks
on SharePoint sites are optimized for level 1 browsers, Windows SharePoint Services 3.0 also
provides support for other browsers that are commonly used. To ensure that you have complete
access to all the functionality, we recommend that you use a level 1 browser for administrative
tasks.
Level 1 Web browsers

Level 1 Web browsers take advantage of advanced features provided by ActiveX controls and
provide the most complete user experience. Level 1 browsers offer full functionality on all
SharePoint sites, including the SharePoint Central Administration Web site. Level 1 browsers are:
• Microsoft Internet Explorer 6.x (32-bit)
• Windows Internet Explorer 7.x (32-bit)
Note:
Level 1 browser support is only available for computers running the Windows operating
system.
Level 2 Web browsers

Level 2 Web browsers provide basic functionality, so that users can both read and write in
SharePoint sites and perform site administration. However, because ActiveX controls are
17
supported only in level 1 browsers and due to the functionality differences within different
browsers, a different user experience might be provided and there could be some variances from
the user experience from the level 1 browsers. Level 2 browsers are listed in the following table.
Browser Windows Linux/Unix Macintosh OSX
Firefox 1.5 X X X
Mozilla 1.7 X
Netscape Navigator X
7.2
Netscape Navigator X
8.1
Safari 2.0 X
If a browser is not listed in either level 1 or level 2, it is not supported. For example, older
browsers — such as Internet Explorer 5.01, Internet Explorer 5.5x, Internet Explorer for
Macintosh, and versions of third-party Web browsers that are earlier than the ones listed as level
2 browsers — are not supported.
Feature-specific compatibility listed by Web

browser
The following table lists more specific feature compatibilities by browser. The compatibility is
listed as either completely compatible (Y) or not compatible (N). Detailed notes for some entries
are provided immediately following the table.
Feature Firefox 1.5 Mozilla 1.7 Netscape Netscape Safari 2.0

Navigator 7.2 Navigator 8.1
Connect to Y (1) Y (1) Y (1) Y (1) Y (1)

Outlook/Client
Context menu Y Y Y Y Y
Drag and Drop (of Y (2) Y (2) Y (2) Y (2) Y (2)

Web Parts)
Edit in Datasheet N N N N N
view
Edit In (Microsoft N N N N N
Office application)
Explorer view N N N N N
18
Feature Firefox 1.5 Mozilla 1.7 Netscape Netscape Safari 2.0
Navigator 7.2 Navigator 8.1
List attachments Y Y Y Y N (3)
Multiple file upload N N N N N
New Document Y (4) Y (4) Y (4) Y (4) Y (4)
Part to Part N N N N N
Connections
People Picker Y (5) Y (5) Y (5) Y (5) Y (5)
Rich text Toolbar N (6) N (6) N (6) N (6) N (6)
Send To Y (7) Y (7) Y (7) Y (7) Y (7)
Web Discussions N N N N N
Web Part menu Y (8) Y (8) Y (8) Y (8) Y (8)
Export to Y (9) Y (9) Y (9) Y (9) Y (9)

Spreadsheet
Date Picker N(10) N(10) N(10) N(10) N(10)

Control
Table Key:
Y - Compatible. All or most aspects of the user experience are equivalent. See Numbered Notes
for any differences in user experience.
N - Not compatible. Item either is not available from the menu or will not function. Unless
otherwise noted, this feature requires ActiveX controls, which run only in Internet Explorer.
Numbered Notes:
(1) These browsers will use the Connect to Client menu item on the Actions menu. This will
open a client application that is registered to handle the stssync:// protocol, such as Microsoft
Outlook.
(2) Web Parts cannot be placed by using drag and drop. You must click edit on the Web Part,
select Modify Web Part, and select the zone from the Layout section of the Web Part properties
page.
(3) This functionality is not supported because of an issue with the browser.
(4) Although the New button will not work, you can use the Upload Document button.
(5) Does not convert DOMAIN\Username to display name. If the name is not recognized, an error
will be displayed.
(6) The toolbar will not be displayed; however, you can use HTML tags to display styled text. A
link to a Help topic that describes the HTML tags supported will be provided under the rich-text
field.
19
(7) With these browsers, and with Internet Explorer without the Microsoft Office client application
installed, files cannot be sent from one farm to another farm. For files sent from a server to
another server in the same farm, ASPX pages will be used instead of Windows dialog boxes.
(8) The drop-down list menu (triangle on the side of the control) has a different user experience,
but the functionality is similar.
(9) This feature might work properly in these browsers. It downloads a file that has the .iqy
extension to the browser. If Microsoft Office Excel is not installed, and no other application is
configured to open this file, this feature will not work.
(10) Users can still enter dates into the date fields.
20
Install Windows SharePoint Services 3.0 on a
stand-alone computer
In this section:
• Hardware and software requirements
• Configure the server as a Web server
• Install and configure Windows SharePoint Services 3.0 with Windows Internal Database
• Post-installation steps
This information applies to Microsoft Windows Server 2003. If you are in a
Windows Server® 2008 environment, the steps to install and configure Internet Information
Services (IIS), the Microsoft .NET Framework version 3.0, and Windows SharePoint Services 3.0
are different. For more information, see Install a stand-alone server on Windows Server 2008
Important:
This document discusses how to install Windows SharePoint Services 3.0 on a single
computer as a stand-alone installation. It does not cover installing Windows SharePoint
Services 3.0 in a farm environment, upgrading from previous releases of Windows
SharePoint Services 3.0, or how to upgrade from SharePoint Portal Server 2003. For
information about how to do this, see the following sections:
• Deploy in a simple server farm
• Upgrading to Windows SharePoint Services 3.0 (http://technet.microsoft.com/en-
us/library/cc303309.aspx)
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.
21
Hardware and software requirements
Before you install and configure Windows SharePoint Services 3.0, be sure that your servers
have the required hardware and software. For more information about these requirements, see
Determine hardware and software requirements.
Configure the server as a Web server

Before you install and configure Windows SharePoint Services 3.0, you must install and configure
the required software. This includes installing and configuring Internet Information Services (IIS)
so your computer acts as a Web server, installing the Microsoft .NET Framework version 3.0, and
enabling ASP.NET 2.0.
Install and configure IIS

Internet Information Services (IIS) is not installed or enabled by default in the Microsoft Windows
Server 2003 operating system. To make your server a Web server, you must install and enable
IIS, and you must ensure that IIS is running in IIS 6.0 worker process isolation mode.

1. Click Start, point to All Programs, point to Administrative Tools, and then click
Configure Your Server Wizard.
2. On the Welcome to the Configure Your Server Wizard page, click Next.
3. On the Preliminary Steps page, click Next.
4. On the Server Role page, click Application server (IIS, ASP.NET), and then click
Next.
5. On the Application Server Options page, click Next.
6. On the Summary of Selections page, click Next.
7. Click Finish.
Internet Information Services (IIS) Manager.
9. In the IIS Manager tree, click the plus sign (+) next to the server name, right-click the
Web Sites folder, and then click Properties.
10. In the Web Sites Properties dialog box, click the Service tab.
11. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation
mode check box, and then click OK.
Note:
The Run WWW in IIS 5.0 isolation mode check box is only selected if you have
upgraded to IIS 6.0 on Windows Server 2003 from IIS 5.0 on Microsoft Windows
2000. New installations of IIS 6.0 use IIS 6.0 worker process isolation mode by
default.
22
Install the Microsoft .NET Framework version 3.0
Go to the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?
LinkID=72322&clcid=0x409), and on the Microsoft .NET Framework 3.0 Redistributable Package
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:
LinkId=110508).
Enable ASP.NET 2.0

ASP.NET 2.0 is required for proper functioning of Web content, the Central Administration Web
Site, and many other features and functions of Windows SharePoint Services 3.0.
Enable ASP.NET 2.0

2. In the Internet Information Services tree, click the plus sign (+) next to the server
name, and then click the Web Service Extensions folder.
3. In the details pane, right-click ASP.NET v2.0.50727, and then click Allow.
Install and configure Windows SharePoint

Services 3.0 with Windows Internal Database
When you install Windows SharePoint Services 3.0 on a single server, run the Setup program
using the Basic option. This option uses the Setup program's default parameters to install
Windows SharePoint Services 3.0 and Windows Internal Database. 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..
Notes
• 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:
23
• psconfig -cmd configdb -create -database <uniquename>
Run Setup
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 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.
24
25
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
2. On the Connections tab, in the Local Area Network (LAN) settings area, click
LAN Settings.
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.
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 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 (http://technet.microsoft.com/en-us/library/cc287879.aspx)
• 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 (http://technet.microsoft.com/en-us/library/cc288949.aspx).
• 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
26
• 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 (http://technet.microsoft.com/en-us/library/cc288959.aspx).
• 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 (http://technet.microsoft.com/en-us/library/cc303306.aspx).
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.
27
Deploy in a simple server farm
In this section:
• Deployment overview
• Deploy and configure the server infrastructure
• Perform additional configuration tasks
• Create a site collection and a SharePoint site
• Configure the trace log
This information applies to Microsoft Windows Server 2003. If you are in a
Windows Server® 2008 environment, the steps to install and configure Internet Information
Services (IIS), the Microsoft .NET Framework version 3.0, and Windows SharePoint Services 3.0
are different. For more information, see Deploy a simple farm on the Windows Server 2008
operating system (http://technet.microsoft.com/en-us/library/cc287748.aspx).
Deployment overview
Important:
This section 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 section 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
28
Windows SharePoint Services 3.0 technology (http://technet.microsoft.com/en-
us/library/cc288426.aspx).
Deploying Windows SharePoint Services 3.0 in a DBA environment

In many IT environments, database creation and management are handled by the database
administrator (DBA). Security and other policies might require that the DBA create the databases
required by Windows SharePoint Services 3.0. For more information about deploying using DBA-
created databases, including detailed procedures that describe how the DBA can create these
databases, see Deploy using DBA-created databases (http://technet.microsoft.com/en-
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 load-
balanced front-end Web servers running IIS and Windows SharePoint Services 3.0, and two or
more servers providing search services.
Before you begin deployment

This section provides information about actions that you must perform before you begin
deployment.
• 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/en-
• 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.
29
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 section.
Overview of the deployment process

The deployment process consists of two phases: deploying and configuring the server
infrastructure, and deploying and configuring SharePoint site collections and sites.
Phase 1: Deploy and configure the server infrastructure

Deploying and configuring the server infrastructure consists of the following steps:
• Preparing the database server.
• Preinstalling databases (optional).
• Verifying that the servers meet hardware and software requirements.
• Running Setup on all servers you want to be in the farm, including running the
SharePoint Products and Technologies Configuration Wizard.
• Starting the Windows SharePoint Services Search service.
Phase 2: Deploy and configure SharePoint site collections and sites

Deploying and configuring SharePoint site collections and sites consists of the following steps:
• Creating site collections.
• Creating SharePoint sites.
Deploy and configure the server infrastructure

Prepare the database server
The database server computer must be running Microsoft SQL Server 2005 or Microsoft SQL
Server 2000 with Service Pack 3a (SP3a) or later.
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.
30
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.
SQL Server and database collation

The SQL Server collation must be configured for case-insensitive. The SQL Server database
collation must be configured for case-insensitive, accent-sensitive, Kana-sensitive, and width-
sensitive. This is used to ensure file name uniqueness consistent with the Windows operating
system. For more information about collations, see Selecting a SQL Collation
(http://go.microsoft.com/fwlink/?LinkId=121667&clcid=0x409) or Collation Settings in Setup
(http://go.microsoft.com/fwlink/?LinkId=121669&clcid=0x409) in SQL Server 2005 Books Online.
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
Account Purpose Requirements
SQL Server This account is used as SQL Server prompts for this account during SQL
Service the service account for Server Setup. You have two options:
Account the following SQL Server • Assign one of the built-in system accounts
services: (Local System, Network Service, or Local
• Service) to the logon for the configurable SQL
Server services. For more information about
MSSQLSERVER these accounts and security considerations, refer
•SQLSERVERAGEN to the Setting Up Windows Service Accounts
T topic (http://go.microsoft.com/fwlink/?
If you are not using the LinkId=121664&clcid=0x409) in the SQL Server
default instance, these documentation.
services will be shown • Assign a domain user account to the logon
as: for the service. However, if you use this option
•MSSQL$InstanceN you must take the additional steps required to
ame configure Service Principal Names (SPNs) in
Active Directory in order to support Kerberos
•SQLAgent$Instanc
authentication, which SQL Server uses.
eName
31
Account Purpose Requirements
Setup user The Setup user account • Domain user account

account is used to run the • Member of the Administrators group on each
following: server on which Setup is run
• Setup on each • SQL Server login on the computer running
server SQL Server
• The SharePoint • Member of the following SQL Server security
Products and roles:
Technologies
• securityadmin fixed server role
Configuration Wizard
• dbcreator fixed server role
• The PSConfig
If you run Stsadm command-line tool commands that
command-line tool
read from or write to a database, this account must
• The Stsadm
be a member of the db_owner fixed database role for
command-line tool
the database.
Server farm The Server farm account • Domain user account.

account/Datab is used to: • If the server farm is a child farm with Web
ase access • Act as the applications that consume shared services from a
account application pool larger farm, this account must be a member of
identity for the the db_owner fixed database role on the
SharePoint Central configuration database of the larger farm.
Administration Additional permissions are automatically granted for
application pool. this account on Web servers and application servers
• Run the that are joined to a server farm.
Windows SharePoint This account is automatically added as a SQL Server
Services Timer login on the computer running SQL Server and added
service. to the following SQL Server security roles:
• dbcreator fixed server role
• securityadmin fixed server role
• db_owner fixed database role for all
databases in the server farm
Verify that servers meet hardware and software requirements

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 computer acting as a Web server and an application server, and one server computer
acting as a database server. For more information about these requirements, see Determine
hardware and software requirements.
32
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.

Internet Information Services (IIS) is not installed or enabled by default in the Microsoft Windows
Server 2003 operating system. To make your server a Web server, you must install and enable
IIS, and you must ensure that IIS is running in IIS 6.0 worker process isolation mode.

Configure Your Server Wizard.
2. On the Welcome to the Configure Your Server Wizard page, click Next.
3. On the Preliminary Steps page, click Next.
4. On the Server Role page, click Application server (IIS, ASP.NET), and then click
Next.
5. On the Application Server Options page, click Next.
6. On the Summary of Selections page, click Next.
7. Click Finish.
9. In the IIS Manager tree, click the plus sign (+) next to the server name, right-click the
Web Sites folder, and then click Properties.
10. In the Web Sites Properties dialog box, click the Service tab.
11. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation
mode check box, and then click OK.
Note:
The Run WWW in IIS 5.0 isolation mode check box is only selected if you have
upgraded to IIS 6.0 on Windows Server 2003 from IIS 5.0 on Microsoft Windows
2000. New installations of IIS 6.0 use IIS 6.0 worker process isolation mode by
default.
Install the Microsoft .NET Framework version 3.0

Go to the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?
LinkID=72322&clcid=0x409), and on the Microsoft .NET Framework 3.0 Redistributable Package
page, follow the instructions for downloading and installing the Microsoft .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 Microsoft .NET Framework
33
version 3.0 download contains the Windows Workflow Foundation technology, which is required
by workflow features.
Note:
LinkId=110508).
Enable ASP.NET 2.0

You must enable ASP.NET 2.0 on all servers.
Enable ASP.NET 2.0

2. In the IIS Manager tree, click the plus sign (+) next to the server name, and then click
the Web Service Extensions folder.
3. In the details pane, click ASP.NET v2.0.50727, and then click Allow.
Run Setup on all servers in the farm

Run Setup and then the SharePoint Products and Technologies Configuration Wizard on all your
farm servers. Adding servers to the farm can be done at any time to add redundancy, such as
additional load-balanced Web servers.
Note:
We recommend that you run Setup on all the servers that will be in the farm before you
configure the farm.
When you install Windows SharePoint Services 3.0 on the first server, you establish the farm. Any
additional servers that you add must be joined to this farm.
Setting up the first server involves two steps: installing the Windows SharePoint Services 3.0
components on the server, and configuring the farm. After Setup finishes, you can use the
SharePoint Products and Technologies Configuration Wizard to configure Windows SharePoint
Services 3.0. The SharePoint Products and Technologies Configuration Wizard automates
several configuration tasks, including: installing and configuring the configuration database,
installing Windows SharePoint Services 3.0 services, and creating the Central Administration
Web site.
Run Setup on the first server

We recommend that you install and configure Windows SharePoint Services 3.0 on all of your
farm servers before you configure Windows SharePoint Services 3.0 services and create sites.
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.
34
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.
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 stand-
alone 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.

After Setup finishes, you can use the SharePoint Products and Technologies Configuration
Wizard to configure Windows SharePoint Services 3.0. The configuration wizard automates
several configuration tasks, including: installing and configuring the configuration database,
installing Windows SharePoint Services 3.0 services, and creating the Central Administration
Web site. Use the following instructions to run the SharePoint Products and Technologies
Configuration Wizard.

2. Click Yes in the dialog box that notifies you that some services might need to be
restarted during configuration.
3. On the Connect to a server farm page, click No, I want to create a new server farm,
35
and then click Next.
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 NTLM authentication (the default), click Next.
• 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).
36
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
user authentication settings in Internet Explorer. Instructions for configuring these
settings are provided in the next set of steps.
Note:
If a proxy server error message appears, you might need to configure your proxy
server settings so that local addresses bypass the proxy server. Instructions for
configuring this setting are provided later in this section.
Add the SharePoint Central Administration Web site to the list of trusted sites
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 for the SharePoint Central
Administration Web site, and then click Add.
5. Click Close to close the Trusted sites dialog box.
Configure proxy server settings to bypass the proxy server for local addresses
2. On the Connections tab, in the Local Area Network (LAN) settings area, click
LAN Settings.
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.
37
7. Select the Bypass proxy server for local addresses check box.
8. Click OK to close the Local Area Network (LAN) Settings dialog box.
Add servers to the farm

We recommend that you install and configure Windows SharePoint Services 3.0 on all of your
farm servers before you configure Windows SharePoint Services 3.0 services and create sites.
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.
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 stand-
alone 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.
Run the SharePoint Products and Technologies Configuration Wizard on

additional servers
After Setup finishes, use the SharePoint Products and Technologies Configuration Wizard to
configure Windows SharePoint Services 3.0. The configuration wizard automates several
configuration tasks, including: installing and configuring the configuration database, and installing
38
Windows SharePoint Services 3.0 services. Use the following instructions to run the SharePoint
Products and Technologies Configuration Wizard.

2. Click Yes in the dialog box that notifies you that some services might need to be
restarted during configuration.
3. On the Connect to a server farm page, click Yes, I want to connect to an existing
server farm, and then click Next.
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.
Start the Windows SharePoint Services Search service

You must start the Windows SharePoint Services Search service on every computer that you
want to search over content. You must start it on at least one of your servers.
Start the Windows SharePoint Services Search service

1. On the SharePoint Central Administration home page, click the Operations tab on
the top link bar.
2. On the Operations page, in the Topology and Services section, click Servers in
farm.
3. On the Servers in Farm page, click the server on which you want to start the
Windows SharePoint Services Search service.
4. Next to Window SharePoint Services Search, click Start.
5. On the Configure Windows SharePoint Services Search Service Settings page, in the
Service Account section, specify the user name and password for the user account
under which the search service will run.
6. In the Content Access Account section, specify the user name and password for
the user account that the search service will use to search over content. This account
must have read access to all the content you want it to search over. If you do not enter
39
credentials, the same account used for the search service will be used.
7. In the Indexing Schedule section, either accept the default settings, or specify the
schedule that you want the search service to use when searching over content.
8. After you have configured all the settings, click Start.
For information about how to perform this procedure using the Stsadm command-line tool, see
Spsearch (http://technet.microsoft.com/en-us/library/cc288507.aspx).
Perform additional configuration tasks

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 customizing the site, we recommend that you
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 (http://technet.microsoft.com/en-us/library/cc287879.aspx).
• 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 (http://technet.microsoft.com/en-us/library/cc288949.aspx).
• 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 (http://technet.microsoft.com/en-us/library/cc288959.aspx)
Perform administrator tasks by using the Central Administration site

SharePoint 3.0 Central Administration.
40
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.
Create a site collection and a SharePoint site

This section guides you through the process of creating a single site collection containing a single
SharePoint site. You can create many site collections and many sites under each site collection.
For more information, see Chapter overview: Deploy and configure SharePoint sites
(http://technet.microsoft.com/en-us/library/cc288441.aspx)
You can create new portal sites or migrate pre-existing sites or content from a previous version of
Windows SharePoint Services. For information about planning SharePoint sites and site
collections, see Plan Web site structure and publishing (http://technet.microsoft.com/en-
us/library/cc288423.aspx). For information about migrating content, see Deploy a new server
farm, then migrate content databases (http://technet.microsoft.com/en-us/library/cc303311.aspx).
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
41
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-
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
42
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 (http://technet.microsoft.com/en-us/library/cc287954.aspx).
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.
43
Item Action
Database Server Type the name of the database server and

Microsoft SQL Server instance you want to
use in the format
<SERVERNAME\instance>. You can also
use the default entry.
Database Name Type the name of the database, or use the

default entry.
Item Action
Database Authentication Choose whether to use Windows

authentication (recommended) or SQL
authentication.
• If you want to use Windows
authentication, leave this option
selected.
• If you want to use SQL
authentication, select SQL
authentication. In the Account
box, type the name of the account
you want the Web application to
use to authenticate to the SQL
Server database, and then type the
password in the Password box.
9. Click OK to create the new Web application, or click Cancel to cancel the process
and return to the Application Management page.
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.
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
44
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.
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
requests to the correct Web applications and sites, and they enable Windows SharePoint
45
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).
Configure the trace log

The trace log can be useful for analyzing problems that might occur. You can use events that are
written to the trace log to determine what configuration changes were made in Windows
SharePoint Services 3.0 before the problem occurred.
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 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:
• In the Number of log files box, type 336.
• In the Number of minutes to use a log file box, type 30.
Tip:
To save 10,080 minutes (seven days) of events, you can use any
combination of number of log files and minutes to store in each log file.
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.
46
Logging and Events: Stsadm operations (http://technet.microsoft.com/en-
47
Roadmap to Windows SharePoint Services
3.0 content
In this section:
• Windows SharePoint Services 3.0 content by audience
• Windows SharePoint Services 3.0 IT professional content by stage of the IT life cycle
Windows SharePoint Services 3.0 content by

audience
Each audience for Windows SharePoint Services 3.0 can go to a specific Web site for content
that is tailored to that audience. The following table lists the audiences and provides links to the
content for each audience.
Information Workers IT Professionals Developers
Content available on Content available on: Content available on:

Office Online TechNet MSDN
• Home page — a • TechCenter — a • Developer Center — a

central portal for central portal for IT central portal for Developer
Information Worker professional resources resources
resources (http://go.microsoft.com/fwl (http://go.microsoft.com/fwl
(http://go.microsoft.com/fw ink/? ink/?
link/? LinkID=73953&clcid=0x40 LinkId=88910&clcid=0x409
LinkId=88898&clcid=0x40 9) )
9) • Technical Library — an • MSDN Library — an
• Help and How-to — an index for IT professional index for Developer
index for Information content content
Worker content (http://go.microsoft.com/fwl (http://go.microsoft.com/fwl
(http://go.microsoft.com/fw ink/? ink/?
link/? LinkId=88902&clcid=0x40 LinkID=86923&clcid=0x40
LinkId=88899&clcid=0x40 9) 9)
9) • Newly published
content — an article that
lists new or updated
content in the Technical
Library
(http://go.microsoft.com/fwl
ink/?
48
Information Workers IT Professionals Developers
LinkId=88906&clcid=0x40
9)
• Downloadable
books — an article that
lists the books available for
download
(http://go.microsoft.com/fwl
ink/?
LinkId=88907&clcid=0x40
9)
Additionally, there is information for all users of SharePoint Products and Technologies at the
community and blog sites listed in the following table.
Community content and blogs
• SharePoint Products and Technologies community portal — a central

place for community information (blogs, newsgroups, etc.) about
SharePoint Products and Technologies (http://go.microsoft.com/fwlink/?
LinkId=88915&clcid=0x409)
• SharePoint Products and Technologies team blog — a group blog
from the teams who develop the SharePoint Products and Technologies
• Support Center for Microsoft Windows SharePoint Services 3.0 — a
central place for issues and solutions from Microsoft Help and Support
Windows SharePoint Services 3.0 IT professional

content by stage of the IT life cycle
IT Professional content for Windows SharePoint Services 3.0 includes content appropriate for
each stage of the IT life cycle — evaluate, plan, deploy, and operate — plus technical reference
content. The following sections describe each stage in the IT life cycle and list the content
available to assist IT professionals during that stage. The most up-to-date content is always
available on the TechNet Web site.
We also offer downloadable books that cover each stage of the IT life cycle, plus books that cover
all stages of the life cycle for a specific solution. For an updated list, see Downloadable books for
Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkId=88907&clcid=0x409).
49
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 Includes the most Evaluation for Windows SharePoint Services 3.0 technology
up-to-date (http://go.microsoft.com/fwlink/?LinkID=88902&clcid=0x409)
content. The
Technical Library
on TechNet is
continually
refreshed with
new and updated
content.
Evaluation Provides an Windows SharePoint Services 3.0 Evaluation Guide

Guide overview, (http://go.microsoft.com/fwlink/?LinkId=86962&clcid=0x409)
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.
50
The following table lists resources that are available to help you plan for using Windows
Online content Includes the most Planning and architecture for Windows SharePoint Services
up-to-date content. 3.0 (http://go.microsoft.com/fwlink/?
The Technical LinkId=88954&clcid=0x409)
Library on TechNet
is continually
refreshed with new
and updated
content.
Planning Provides in-depth Planning and architecture for Windows SharePoint

Guide, Part 1 planning Services, part 1 (http://go.microsoft.com/fwlink/?
information for LinkId=79600)
application
administrators who
are designing a
solution based on
Windows
SharePoint
Services 3.0.
Planning Provides in-depth Planning and architecture for Windows SharePoint

Guide, Part 2 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.
51
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
Online content Includes the Deployment for Windows SharePoint Services 3.0
most up-to-date (http://go.microsoft.com/fwlink/?LinkID=80752&clcid=0x409)
content. The
Technical
Library on
TechNet is
continually
refreshed with
new and
updated
content.
Deployment Provides in- Deployment for Windows SharePoint Services

Guide depth (http://go.microsoft.com/fwlink/?LinkID=79602)
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.
52
Migration and Provides cross- Migration and Upgrade Information for SharePoint
Upgrade for audience (IT Developers
SharePoint and developer) (http://go.microsoft.com/fwlink/?LinkId=89129&clcid=0x409)
Developers information for
migration and
upgrade from a
previous version
product to
Windows
SharePoint
Services 3.0.
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.
Online content Includes the most Operations for Windows SharePoint Services 3.0
up-to-date (http://go.microsoft.com/fwlink/?LinkId=89152&clcid=0x409)
content. The
Technical Library
on TechNet is
continually
refreshed with
new and updated
content.
Security and Protection

Because security and protection are concerns during all phases of the IT life cycle, appropriate
content for security and protection is included in the content for each life cycle stage. However, an
aggregate view of this content is provided in a Security and Protection section of the
documentation. The following table lists resources that are available to help you understand
security and protection for Windows SharePoint Services 3.0.
53
Online content Includes the most Security and protection for Windows SharePoint Services
up-to-date 3.0 (http://go.microsoft.com/fwlink/?
content. The LinkId=89154&clcid=0x409)
Technical Library
on TechNet is
continually
refreshed with
new and updated
content.
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.
Online content Includes the most Technical Reference for Windows SharePoint Services 3.0
up-to-date (http://go.microsoft.com/fwlink/?LinkID=88902&clcid=0x409)
content. The
Technical Library
on TechNet is
continually
refreshed with
new and updated
content.
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).
54

Getting Started With Windows Share Point Services 3.0

Cargado por

Información del documento

Descripción original:

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Getting Started With Windows Share Point Services 3.0

Cargado por

Copyright:

Formatos disponibles

Getting Started with Windows SharePoint

Introduction to Getting Started with Windows SharePoint Services 3.0 technology...........1

What's new for IT professionals in Windows SharePoint Services 3.0...............................2

Determine hardware and software requirements...............................................................9

Install Windows SharePoint Services 3.0 on a stand-alone computer.............................21

Deploy in a simple server farm.........................................................................................28

Roadmap to Windows SharePoint Services 3.0 content..................................................48

Administration model enhancements

Centralized configuration and management

Two-tier administration model

Farm-based Central Administration user interface

Delegation of administrative responsibilities and roles

Auditing and logging

Item-level access control

Administrator access control

New and improved operational tools and

Upgrade and migration support

Host header mode

Improved support for network configuration

Alternate access mappings

About hardware and software requirements

Component Minimum Recommended

Processor 2.5 gigahertz (GHz) Dual processors that are each

RAM 1 gigabyte (GB) 2 GB

Disk NTFS file system–formatted NTFS file system–formatted

Drive DVD drive DVD drive or the source copied

Display 1024 × 768 1024 × 768 or higher resolution

Network 56 kilobits per second (Kbps) 56 Kbps or faster connection

Microsoft .NET Framework 3.0

Server farm installation

Front-end Web server

Component Minimum Recommended

Processor 2.5 GHz Dual processors that are each

RAM 2 GB More than 2 GB

Disk NTFS file system–formatted NTFS file system–formatted

3 GB of free space plus adequate free space for

Drive DVD drive DVD drive or the source copied

Display 1024 × 768 1024 × 768 or higher resolution

Network • 56 Kbps connection • 56 Kbps or faster

Microsoft .NET Framework 3.0

About browser support

Levels of browser support

Level 1 Web browsers

Level 2 Web browsers

Browser Windows Linux/Unix Macintosh OSX

Feature-specific compatibility listed by Web

Feature Firefox 1.5 Mozilla 1.7 Netscape Netscape Safari 2.0

Connect to Y (1) Y (1) Y (1) Y (1) Y (1)

Drag and Drop (of Y (2) Y (2) Y (2) Y (2) Y (2)

List attachments Y Y Y Y N (3)

Multiple file upload N N N N N

New Document Y (4) Y (4) Y (4) Y (4) Y (4)

People Picker Y (5) Y (5) Y (5) Y (5) Y (5)

Rich text Toolbar N (6) N (6) N (6) N (6) N (6)

Send To Y (7) Y (7) Y (7) Y (7) Y (7)

Web Part menu Y (8) Y (8) Y (8) Y (8) Y (8)

Export to Y (9) Y (9) Y (9) Y (9) Y (9)

Date Picker N(10) N(10) N(10) N(10) N(10)

Configure the server as a Web server

Install and configure IIS

Install and configure IIS

Enable ASP.NET 2.0

Enable ASP.NET 2.0