Professional Documents
Culture Documents
Getting Started With Windows Sharepoint Services 3.0: Microsoft Office System and Servers Team
Getting Started With Windows Sharepoint Services 3.0: Microsoft Office System and Servers Team
Getting Started With Windows Sharepoint Services 3.0: Microsoft Office System and Servers Team
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
For further reading: Evaluation guide for Windows SharePoint Services 3.0 technology...8
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
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.
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.
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.
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.
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.
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.
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.
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.
10
Component Minimum Recommended
monitor
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.
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.
Hardware requirements
The following table lists the minimum and recommended hardware requirements for deploying a
Windows SharePoint Services 3.0 front-end Web server.
13
Component Minimum Recommended
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.
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 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
SharePoint Services 3.0.
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
Note:
Level 1 browser support is only available for computers running the Windows operating
system.
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.
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.
Context menu Y Y Y Y Y
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
Part to Part N N N N N
Connections
Web Discussions N N N N N
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
(http://technet.microsoft.com/en-us/library/cc287813.aspx).
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.
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:
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).
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.
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.
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
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Connections tab, in the Local Area Network (LAN) settings area, click
LAN Settings.
3. In the Automatic configuration section, clear the Automatically detect settings
check box.
4. In the Proxy Server section, select the Use a proxy server for your LAN check
box.
5. Type the address of the proxy server in the Address box.
6. Type the port number of the proxy server in the Port box.
7. Select the Bypass proxy server for local addresses check box.
8. Click OK to close the Local Area Network (LAN) Settings dialog box.
9. Click OK to close the Internet Options dialog box.
Post-installation steps
After Setup finishes, your browser window opens to the home page of your new SharePoint site.
Although you can start adding content to the site or you can start customizing the site, we
recommend that you perform the following administrative tasks by using the SharePoint Central
Administration Web site.
• Configure incoming e-mail settings You can configure incoming e-mail settings so
that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-
mail settings so that SharePoint sites can archive e-mail discussions as they happen, save 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
(http://technet.microsoft.com/en-us/library/cc288649.aspx).
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).
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
(http://technet.microsoft.com/en-us/library/cc303309.aspx).
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).
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.
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.
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.
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
(http://technet.microsoft.com/en-us/library/cc288210.aspx).
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
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.
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.
33
version 3.0 download contains the Windows Workflow Foundation technology, which is required
by workflow features.
Note:
You can also use the Microsoft .NET Framework version 3.5. You can download the .NET
Framework version 3.5 from the Microsoft Web site (http://go.microsoft.com/fwlink/?
LinkId=110508).
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.
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.
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.
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
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 for the SharePoint Central
Administration Web 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.
Configure proxy server settings to bypass the proxy server for local addresses
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Connections tab, in the Local Area Network (LAN) settings area, click
LAN Settings.
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.
9. Click OK to close the Internet Options dialog box.
Important:
If you uninstall Windows SharePoint Services 3.0 from the first server on which you
installed it, your farm might experience problems.
38
Windows SharePoint Services 3.0 services. Use the following instructions to run the SharePoint
Products and Technologies Configuration Wizard.
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).
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.
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.
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-
us/library/cc288475.aspx).
b. In the Allow Anonymous section, choose Yes or No. If you choose to allow
anonymous access, this enables anonymous access to the Web site by using the
computer-specific anonymous access account (that is, IUSR_<computername>).
Note:
If you want users to be able to access any site content anonymously, you
must enable anonymous access for the entire Web application. Later, site
owners can configure how anonymous access is used within their sites. For
more information about anonymous access, see Choose which security
groups to use (http://technet.microsoft.com/en-us/library/cc288957.aspx).
c. In the Use Secure Sockets Layer (SSL) section, select Yes or No. If you
choose to enable SSL for the Web site, you must configure SSL by requesting and
installing an SSL certificate.
Important:
If you use SSL, you must add the appropriate certificate on each server by
using IIS administration tools. For more information about using SSL, see
Plan for secure communication within a server farm
(http://technet.microsoft.com/en-us/library/cc288488.aspx).
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
Item Action
9. Click OK to create the new Web application, or click Cancel to cancel the process
and return to the Application Management page.
For information about how to perform this procedure using the Stsadm command-line tool, see
Createsiteinnewdb: Stsadm operation (http://technet.microsoft.com/en-us/library/cc288051.aspx).
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.
For information about how to perform this procedure using the Stsadm command-line tool, see
Createsite: Stsadm operation (http://technet.microsoft.com/en-us/library/cc287992.aspx).
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).
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
For information about how to perform this procedure using the Stsadm command-line tool, see
Logging and Events: Stsadm operations (http://technet.microsoft.com/en-
us/library/cc288075.aspx).
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
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.
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.
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.
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
SharePoint Services 3.0.
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.
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
SharePoint Services 3.0.
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.
52
Content Description Links
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.
53
Content Description Links
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