Getting Started With Office Share Point Server

Getting Started with Office SharePoint Server
Microsoft Corporation
Published: June 2008
Author: Windows SharePoint Services IT User Assistance (o12ITdx@microsoft.com)
Abstract
This book provides basic information about the capabilities of and requirements for Microsoft Office
SharePoint Server 2007. 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 Office SharePoint Server 2007 and want a quick introduction
plus installation steps.
The content in this book is a copy of selected content in the Office SharePoint Server technical library
(http://go.microsoft.com/fwlink/?LinkId=84739) as of the publication date. For the most current content, see
the technical library on the Web.
Contents
Introduction to Getting Started for Office SharePoint Server 2007............................................. .....4
What's new for IT professionals in Office SharePoint Server 2007................................. ................4

Administration model enhancements..................................................................................... ......5
Centralized configuration and management................................................................... ..........5
Three-tier administration model.......................................................................................... ......5
Farm-based Central Administration user interface............................................ .......................6
Delegation of administrative responsibilities and roles................................................ .............6
New and improved compliance features and capabilities.......................................... ..................6
Policy management.......................................................................................................... ........6
Auditing and logging......................................................................................................... ........6
Item-level access control................................................................................................ ..........6
Document lifecycle management...................................................................... .......................7
Administrator access control.............................................................................. ......................7
New and improved operational tools and capabilities...................................................... ............7
Backup and recovery support............................................................................................. ......7
Upgrade and migration support..................................................................................... ...........7
Monitoring support.................................................................................................................. ..8
Host header mode............................................................................................................. .......8
Server renaming................................................................................................................ .......8
Credential management............................................................................................ ...............8
Improved support for network configuration.............................................................................. ...8
Alternate access mappings................................................................................. .....................8
Pluggable authentication........................................................................................... ...............9
1
SQL Server authentication.............................................................................. .........................9
Extensibility enhancements..................................................................................... ....................9
Determine hardware and software requirements (Office SharePoint Server).................................9

About hardware and software requirements.................................................................. ..............9
Stand-alone installation..................................................................................... ........................10
Hardware requirements................................................................................................ ..........10
Software requirements...................................................................................... .....................10
Database...................................................................................................................... .......11
Operating system................................................................................................ ................11
Windows components............................................................................................... ..........12
Microsoft .NET Framework 3.0................................................................ ...........................12
Server farm installation................................................................................................. .............13
Application server........................................................................................................... ........13
Hardware requirements.......................................................................... ............................13
Software requirements............................................................................................. ...........13
Front-end Web server................................................................................ ............................15
Hardware requirements.......................................................................... ............................15
Software requirements............................................................................................. ...........15
Database server........................................................................................................ .............15
Plan browser support (Office SharePoint Server).................................................. .......................16

About browser support............................................................................................................. ..16
Levels of browser support....................................................................................................... ...16
Level 1 Web browsers................................................................................................. ...........16
Level 2 Web browsers................................................................................................. ...........17
Feature-specific compatibility listed by Web browser....................................... .........................17
Install Office SharePoint Server 2007 on a stand-alone computer........................................... .....19

Hardware and software requirements................................................................................. .......20
Configure the server as a Web server................................................................... ....................20
Install and configure IIS................................................................................................ ..........20
Install the Microsoft .NET Framework version 3.0................................................... ...............21
Enable ASP.NET 2.0.............................................................................................................. .21
Install and configure Office SharePoint Server 2007 with Microsoft SQL Server 2005 Express
Edition............................................................................................................... .....................21
Post-installation steps......................................................................................................... .......23
Download this book............................................................................................ .......................24
Deploy in a simple server farm (Office SharePoint Server).................................................. .........24

Deployment overview........................................................................................ ........................24
Deploying Office SharePoint Server 2007 in a DBA environment.......................................25
Suggested topologies.................................................................................................... .........25
Before you begin deployment........................................................................................... ......25
Overview of the deployment process........................................................... ..........................26
Phase 1: Deploy and configure the server infrastructure.............................. ......................26
Phase 2: Create and configure a Shared Services Provider................................... ............27
2
Phase 3: Create site collections and SharePoint sites.............................................. ..........27
Deploy and configure the server infrastructure.......................................................... ................27
Security account requirements................................................................................... ............27
Prepare the database server....................................................................................... ...........27
SQL Server and database collation................................................................................... ..28
Required accounts............................................................................................... ...............28
Verify that servers meet hardware and software requirements............................................... 29
Install and configure IIS.......................................................................... ............................29
Install the Microsoft .NET Framework version 3.0.......................................................... .....30
Enable ASP.NET 2.0........................................................................................ ...................30
Run Setup and build the farm........................................................................................... ......31
Recommended order of configuration....................................................................... ..........31
Add servers to the farm.................................................................................................. .....32
Run Setup on the first server............................................................................................ ......32
Run the SharePoint Products and Technologies Configuration Wizard..................................33
Add the SharePoint Central Administration Web site to the list of trusted sites......................35
Configure proxy server settings to bypass the proxy server for local addresses....................35
Add servers to the farm........................................................................................... ...............35
Run the SharePoint Products and Technologies Configuration Wizard on additional servers 37
Start the Windows SharePoint Services Search service (optional)........................................37
Stop the Central Administration service on all index servers....................................... ...........38
Disable the Windows SharePoint Services Web Application service on all servers not serving
content............................................................................................................... .................38
Create and configure a Shared Services Provider............................................................... ......38
Start the Office SharePoint Server Search service............................................................. ....39
Create a Web application to host the SSP and create the SSP.............................................40
Perform additional configuration tasks................................................................................ .......41
Create a site collection and a SharePoint site...................................................... .....................42
Configure the trace log...................................................................................... ........................45
Download this book............................................................................................ .......................46
Roadmap to Office SharePoint Server 2007 content............................................. .......................46

Office SharePoint Server 2007 content by audience.............................................. ...................47
Office SharePoint Server 2007 IT professional content by stage of the IT life cycle..................48
Evaluate............................................................................................................ .....................48
Plan.......................................................................................................................... ..............48
Deploy..................................................................................................................... ...............49
Operate............................................................................................................. .....................50
Security and Protection..................................................................................... .....................50
Technical Reference....................................................................................................... ........50
Solutions..................................................................................................... ...........................50
White paper: Evaluation guide for Office SharePoint Server 2007.......................................... ......51
White paper: Evaluation guide for search in Office SharePoint Server 2007................................51
3
Introduction to Getting Started for Office SharePoint Server 2007
Microsoft Office SharePoint Server 2007 is a rich server application for the enterprise that facilitates collaboration, provides
full content management features, implements business processes, and provides access to information essential to
organizational goals and processes. It provides an integrated platform to plan, deploy, and manage intranet, extranet, and
Internet applications across and beyond the enterprise.
This Getting Started guide for Office SharePoint Server 2007 covers what's new in Office SharePoint Server 2007, provides
references to evaluation content, and includes several end-to-end deployment scenarios to get you started quickly with an
evaluation environment for Office SharePoint Server 2007. The following list describes each topic in this guide.
• "What's new for IT professionals in Office SharePoint Server 2007" introduces the new capabilities and features
in Office SharePoint Server 2007. Although Office SharePoint Server 2007 is a new product, it is based on the
Windows SharePoint Services 3.0 platform, and includes the capabilities of Microsoft Office SharePoint Portal
Server 2003. This topic highlights the differences between Office SharePoint Server 2007 and those technologies.
• "White paper: Evaluation guide for Office SharePoint Server 2007" provides a reference to a download location
for the evaluation guide for Office SharePoint Server 2007. The evaluation guide covers key features, overviews of
the product, and a product tour.
• "White paper: Evaluation guide for search in Office SharePoint Server 2007" provides a reference to a
download location for evaluation content that describes the search capabilities in Office SharePoint Server 2007.
The Evaluation guide for search covers overviews of search functionality and a tour of the search features.
• "Determine hardware and software requirements (Office SharePoint Server)" describes the minimum and
recommended hardware and software that are required to run Office SharePoint Server 2007.
• "Plan browser support (Office SharePoint Server)" describes the functionality available and level of support for
Office SharePoint Server 2007 features that you can expect when using several common Web browsers.
• "Install Office SharePoint Server 2007 on a stand-alone computer" provides end-to-end installation instructions
for setting up Office SharePoint Server 2007 in a stand-alone environment. This installation scenario is ideal for
evaluating Office SharePoint Server 2007 functionality or for hosting a very small installation of Office SharePoint
Server 2007.
• "Deploy in a simple server farm (Office SharePoint Server)" provides end-to-end instructions for installing Office
SharePoint Server 2007 in a simple server farm. A simple server farm consists of one or more Web servers, one or
more application servers, and one or more database servers running Microsoft SQL Server 2000 or Microsoft SQL
Server 2005 database software.
• "Roadmap to Office SharePoint Server 2007 content" provides you with an overview of the content available on
the Microsoft.com Web site that can help you understand and use Office SharePoint Server 2007 as you go beyond
the basics that are presented in this guide.
What's new for IT professionals in Office SharePoint Server 2007
Microsoft Office SharePoint Server 2007 has many new features and enhancements that can help IT professionals deploy
and maintain Office SharePoint Server 2007 solutions. Together, these new features and enhancements provide IT
organizations with better control over information resources; individually these new features and enhancements provide
4
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

Office SharePoint Server 2007 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

Office SharePoint Server 2007 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, Office SharePoint Server 2007 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 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.
Three-tier administration model

Architecturally, Office SharePoint Server 2007 now has a three-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 shared services across a
server farm. Tier 2 administrative tasks are typically performed by a business unit IT administrator and can include a
wide range of management tasks at the service level such as configuring search, indexing, or usage reporting. Tier
2 is relevant only if you are running Office SharePoint Server 2007.
5
• Tier 3 Encompasses all of the administrative features and functionality for managing sites within a server
farm. Tier 3 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 3 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. In addition, Office SharePoint Server 2007 provides a topology validator that
examines your server farm topology and reports any inconsistencies or configuration problems.
• 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. In addition,
delegation capability is further enhanced in Office SharePoint Server 2007 by providing site owners a secure, scalable, and
centrally managed set of administrative rights that can be granted to users and site administrators.
New and improved compliance features and capabilities

Office SharePoint Server 2007 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

Office SharePoint Server 2007 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
6
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.
Document lifecycle management

Using Office SharePoint Server 2007, you can take advantage of a stable, scalable, and efficient document management
system that includes: a specialized Records Repository site template; a records vault with capabilities that help ensure the
integrity of the files stored in the repository; information management policies that consistently and uniformly enforce the
labeling, auditing, and expiration of records; hold capabilities that make it possible for IT, lawyers, and records managers to
apply one or more holds that suspend the records management policies on items to help ensure that they remain unchanged
during litigation, audits, or other investigations; records Collection Interface that helps people and automated systems easily
submit content to a records repository—supporting "write only" access without requiring direct access to the records in the
repository; record routing that enables automated routing of content to its proper location within the records management
system, based on its content type.
Administrator access control

Office SharePoint Server 2007 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

Office SharePoint Server 2007 includes several new and improved tools and capabilities that help IT organizations
implement operational plans and tasks. These features and capabilities include:
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 Office SharePoint Server 2007 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 from
Microsoft SharePoint Portal Server 2003 to Office SharePoint Server 2007 on the same server. This is particularly useful if
you are upgrading a complex environment and you do not want to interrupt business processes.
Migration support Office SharePoint Server 2007 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
7
migrate content incrementally. Migration support cannot be used to migrate customized settings, features, solutions, or
computer settings; migration 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.
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 Office SharePoint Server 2007, allows you to create multiple domain-named sites in a
single Web application. With host header mode, you can have host header-based site collections on multiple Web
applications, and you can have a mix of path-based and host header-based site collections in the same Web application. 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
Office SharePoint Server 2007 now has the command Stsadm renameserver, which 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, Office
SharePoint Server 2007 uses the Windows SharePoint Services Administration service and the Windows SharePoint
Services Timer service to stop and start 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

Office SharePoint Server 2007 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 Office SharePoint Server 2007 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.
8
Pluggable authentication
Office SharePoint Server 2007 adds support for non-Windows-based identity systems by integrating with the pluggable
ASP.NET forms authentication system. Microsoft ASP.NET authentication allows Office SharePoint Server 2007 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.
SQL Server authentication

In previous versions of Microsoft SharePoint Portal Server, you did not have the ability to bypass Windows authentication and
authenticate directly with the SQL Server. Now, in Office SharePoint Server 2007, you can authenticate using SQL Server
authentication. This is useful if you are using Office SharePoint Server 2007 in a workgroup environment or an environment
that does not use Active Directory directory service.
Extensibility enhancements
Office SharePoint Server 2007 has several extensibility enhancements that make it easier to create custom applications that
are well integrated with Office SharePoint Server 2007 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 by using 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 Office SharePoint Server 2007, 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, Office SharePoint Server 2007 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 Office
SharePoint Server 2007 application templates, the Windows Workflow Foundation allows you to create robust workflow-
enabled business applications.
Determine hardware and software requirements (Office SharePoint Server)
In this article:
• About hardware and software requirements
• Stand-alone installation
• Server farm installation
This article describes the hardware and software requirements for installing Microsoft Office SharePoint Server 2007.
About hardware and software requirements

An installation of Office SharePoint Server 2007 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 article describes the minimum and recommended hardware requirements based on whether you are deploying
9
a stand-alone installation or a server farm. This article also lists the software prerequisites for installing Office SharePoint
Server 2007.
This article 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 availability.
The hardware and software requirements described in this article 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 Office
SharePoint Server 2007. To install either 32-bit or 64-bit Office SharePoint Server 2007 you must run IIS in 64-bit mode.
Note
Itanium-based systems are not supported.
Stand-alone installation
You can install Office SharePoint Server 2007 on a single computer by using either of the following methods:
• By selecting Basic.
• By selecting Advanced, and then selecting Stand-alone in Office SharePoint Server 2007 Setup.
Hardware requirements
The following table lists the minimum and recommended hardware requirements for deploying Office SharePoint Server
2007, including the deployment of Microsoft SQL Server 2005 Express Edition, 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 partition with a NTFS file system–formatted partition with 3 GB of free
minimum of 3 GB of free space 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 monitor
Network 56 kilobits per second (Kbps) connection 56 Kbps or faster connection between client computers and
between client computers and server server
Software requirements
Because Office SharePoint Server 2007 is built on Windows SharePoint Services 3.0, the requirements that apply to
Windows SharePoint Services 3.0 also apply to Office SharePoint Server 2007.
10
Note
Because the Office SharePoint Server 2007 installation and configuration wizard marshals many components, if you
uninstall Office SharePoint Server 2007, and then later install Office SharePoint Server 2007 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.
2007 Microsoft Office system uses a common installer, and the features that are available in your Office SharePoint Server
2007 installation depend on the product identification (PID) key that you specify during installation. This means that even with
the same installation source, if you specify a different PID key (for example, a PID key for a different Office SharePoint
Server 2007 edition), a different feature set will be available for installation.
Database
When you perform a Basic installation, SQL Server 2005 Express Edition 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
article.
Note
If you are installing Office SharePoint Server 2007 with Service Pack 1 (SP 1) 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 Office SharePoint Server 2007. Windows
Server 2003, Web edition does not support Basic installation of Office SharePoint Server 2007. However, you can install SQL
Server 2005 Express Edition or SQL Server 2000 Desktop Engine (Windows) (WMSDE).
Operating system
Office SharePoint Server 2007 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
Office SharePoint Server 2007 administration functions require Microsoft Internet Explorer 6.0 with the most recent service
packs or Internet Explorer 7.0.
11
Important
Office SharePoint Server 2007 requires Active Directory directory services for farm deployments. Therefore Office
SharePoint Server 2007 cannot be installed in a farm on a Windows NT 4.0 domain.
As of Office SharePoint Server 2007 with SP1, you can now install Office SharePoint Server 2007 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 Office SharePoint Server 2007 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 Internet Information Services (IIS) 7.0 installed to install Office SharePoint Server 2007 with SP1 on
Windows Server 2008.
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 Office SharePoint Server 2007 to run correctly: the Web Server role, the
Microsoft .NET Framework version 3.0, and Windows Internal Database. Do not uninstall them or Office SharePoint
Server 2007 will cease to run.
Microsoft .NET Framework 3.0

Before installing Office SharePoint Server 2007, 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.
12
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:
• Application server
• 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.
Application server
The following table lists the minimum and recommended hardware requirements for deploying an Office SharePoint Server
2007 application server.
Processor 2.5 GHz Dual processors that are each faster than 2.5 GHz
RAM 2 GB 4 GB
Disk NTFS file system–formatted partition with a NTFS file system–formatted partition with 3 GB of free space
minimum of 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
Network • 56 Kbps connection between • 56 Kbps or faster connection between client

client computers and server computers and server
• For connections between • For connections between computers in your
computers in your server farm, server farm, 1 gigabit per second (Gbps) connection
100 megabits per second (Mbps)
connection
Because Office SharePoint Server 2007 is built on Windows SharePoint Services 3.0, the requirements that apply to
Windows SharePoint Services 3.0 also apply to Office SharePoint Server 2007.
We recommend that you install Office SharePoint Server 2007 on a computer that has a new installation of Windows Server
2003 with SP1 or later and all critical updates.
2007 Microsoft Office system uses a common installer, and the features that are available in your Office SharePoint Server
2007 installation depend on the PID that you specify during installation. This means that even with the same installation
13
source, if you specify a different PID key (for example, a PID key for a different Office SharePoint Server 2007 edition), a
different feature set will be available for installation.
Operating system
Office SharePoint Server 2007 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
Office SharePoint Server 2007 administration functions require Internet Explorer 6.0 with the most recent service packs or
Internet Explorer 7.0.
As of Office SharePoint Server 2007 with SP1, you can now install Office SharePoint Server 2007 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 Office SharePoint Server 2007 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 Office SharePoint Server 2007 with SP1 on Windows Server 2008.
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 Office SharePoint Server 2007 to run correctly: the Web Server role, and
the Microsoft .NET Framework version 3.0. Do not uninstall them, or Office SharePoint Server 2007 will cease to
run.
Microsoft .NET Framework 3.0

After you have configured the server as a Web server, you must install the Microsoft .NET Framework 3.0 and then ensure
that ASP.NET 2.0 is enabled.
14
Note
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.
Front-end Web server
The following table lists the minimum and recommended hardware requirements for deploying an Office SharePoint Server
2007 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 partition NTFS file system–formatted partition with 3 GB of free space
with a minimum of 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
Network • 56 Kbps connection • 56 Kbps or faster connection between client

between client computers and computers and server
server • For connections between computers in your
• For connections between server farm, 1 Gbps connection
computers in your server farm,
100 Mbps connection
Because a front-end Web server is a subset of an application server, all features on a front-end Web server are available on
an application server. The software requirements for the front-end Web server are the same as the software requirements for
the application server before you add specific resources to meet the demands that you forecast as a result of your capacity
planning phase.
Database server
The computer that hosts the database server role must have SQL Server 2000 with SP3a or later or Microsoft SQL Server
2005 SP1 or later. Some advanced features required SQL Server 2005 Analysis Services SP1 or later. 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).
15
Plan browser support (Office SharePoint Server)
In this article:
• About browser support
• Levels of browser support
• Feature-specific compatibility list by Web browser
About browser support

Microsoft Office SharePoint Server 2007 supports several Web browsers that are commonly used. However, there are certain
browsers that might cause some Office SharePoint Server 2007 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 Office SharePoint Server 2007, we recommend that you review the browsers used in
your organization to ensure optimal performance with Office SharePoint Server 2007.
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, Office SharePoint Server 2007 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.
16
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 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 7.2 X
Netscape Navigator 8.1 X
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 Navigator 7.2 Navigator 8.1 Safari 2.0
Connect to Outlook/Client Y (1) Y (1) Y (1) Y (1) Y (1)
Context menu Y Y Y Y Y
Drag and Drop (of Web Parts) Y (2) Y (2) Y (2) Y (2) Y (2)
Edit in Datasheet view N N N N N
Edit In (Microsoft Office application) N N N N N
Explorer view N N N N N
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 Connections N N N N N
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)
17
Feature Firefox 1.5 Mozilla 1.7 Navigator 7.2 Navigator 8.1 Safari 2.0
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 Spreadsheet Y (9) Y (9) Y (9) Y (9) Y (9)
Date Picker Control N(10) N(10) N(10) N(10) N(10)
Summary Links Web Part Y Y Y Y Y (11)
Excel Calculation Services Y Y Y Y N
Slide Library N N N N N
Excel Web Access Y(12) N Y(12) Y(13) N
Open in Excel N N N N N
Open Snapshot N N N N N
Sorting and Filtering (Excel Services) N N N N N
Signing forms (Forms Server) Y (14) Y (14) Y (14) Y (14) Y (14)
Rich Text (InfoPath) N (15) N (15) N (15) N (15) N (15)
Rich text editing in Forms Server forms 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.
18
(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.
(11) When you click for a new link, the pop-up dialog box is the wrong size and the OK and Cancel buttons are partially
obscured.
(12) You cannot sort or filter Pivot Tables. There is no work around for this.
(13) The Navigator 8.1 browser must be configured to render in Internet Explorer mode. For more information about
switching modes, see the browser documentation.
(14) You cannot sign documents, but you can view signatures.
(15) The rich text is read-only by default. If you try to edit the text, all rich-text formatting is lost.
Install Office SharePoint Server 2007 on a stand-alone computer
In this article:
• Hardware and software requirements
• Configure the server as a Web server
• Install and configure Office SharePoint Server 2007 with Microsoft SQL Server 2005 Express Edition
Post-installation steps
Important
This article discusses how to install Microsoft Office SharePoint Server 2007 on a single computer as a stand-alone
installation. It does not cover installing Office SharePoint Server 2007 in a farm environment, upgrading from
previous releases of Office SharePoint Server 2007, or how to upgrade from SharePoint Portal Server 2003. For
information about how to do this, see the following articles:
Deploy in a simple server farm (Office SharePoint Server)
Upgrading to Office SharePoint Server 2007
You can quickly publish a SharePoint site by deploying Office SharePoint Server 2007 on a single server computer. A stand-
alone configuration is useful if you want to evaluate Office SharePoint Server 2007 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 Office SharePoint Server 2007 on
a single server using the default settings, the Setup program automatically installs Microsoft SQL Server 2005 Express
Edition and uses it to create the configuration database and content database for your SharePoint sites. In addition, the
Setup program creates a Shared Services Provider (SSP), installs the SharePoint Central Administration Web site and
creates your first SharePoint site collection and site.
19
Note
There is no direct upgrade from a stand-alone installation to a farm installation.
Hardware and software requirements

Before you install and configure Office SharePoint Server 2007, be sure that your servers have the required hardware and
software. For more information about these requirements, see Determine hardware and software requirements (Office
SharePoint Server).
Configure the server as a Web server

Before you install and configure Office SharePoint Server 2007, 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.
8. Click Start, point to All Programs, point to Administrative Tools, and then click 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.
20
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
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 Office SharePoint Server 2007.
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 Office SharePoint Server 2007 with Microsoft SQL Server 2005 Express Edition
When you install Office SharePoint Server 2007 on a single server, run the Setup program using the Basic option. This
option uses the Setup program's default parameters to install Office SharePoint Server 2007 and SQL Server 2005 Express
Edition.
Notes
• If you uninstall Office SharePoint Server 2007 and then later install Office SharePoint Server 2007 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 Office
SharePoint Server 2007 databases on the computer or by creating a new configuration database. You can
create a new configuration database by running the following command:
• psconfig -cmd configdb -create -database <uniquename>
Run Setup
1. From the product disc, run Setup.exe, or from the product download, run Officeserver.exe.
2. On the Enter your Product Key page, enter your product key, and then click Continue.
Note
Setup automatically verifies the product key, places a green check mark next to the text box, and
enables the Continue button after it validates the key. If the key is not valid, Setup places a red
circle next to the text box and displays a message that the key is incorrect.
21
3. 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.
4. 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 File Location tab, specify the location
you want to install to and finish the installation.
5. 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.
6. Click Close to start the configuration wizard.
Run the SharePoint Products and Technologies Configuration Wizard
1. On the Welcome to SharePoint Products and Technologies page, click Next.

2. In the dialog box that notifies you that some services might need to be restarted or reset during
configuration, click Yes.
3. On the Configuration Successful page, click Finish. Your new SharePoint site opens.
Note
If you are prompted for your user name and password, you might need to add the SharePoint site
to the list of trusted sites and configure user authentication settings in Internet Explorer.
Instructions for configuring these settings are provided in the following procedure.
Note
If you see a proxy server error message, you might need to configure your proxy server settings
so that local addresses bypass the proxy server. Instructions for configuring proxy server settings
are provided later in this section.
Add the SharePoint site to the list of trusted sites
1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Security tab, in the Select a Web content zone to specify its security settings box,
click Trusted Sites, and then click Sites.
3. Clear the Require server verification (https:) for all sites in this zone check box.
4. In the Add this Web site to the zone box, type the URL to your site, and then click Add.
5. Click Close to close the Trusted Sites dialog box.
6. Click OK to close the Internet Options dialog box.
If you are using a proxy server in your organization, use the following steps to configure Internet Explorer to bypass the proxy
server for local addresses.
Configure proxy server settings to bypass the proxy server for local addresses

2. On the Connections tab, in the Local Area Network (LAN) settings area, click LAN Settings.
22
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 .
• 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 .
• 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.
• Configure Workflow settings Specify whether users can assemble new workflows and if participants without
site access should be sent documents in email attachments so they can participate in document workflows. For
more information, see Configure workflow settings.
• Configure diagnostic logging settings You can configure several diagnostic logging settings to help with
troubleshooting. This includes enabling and configuring trace logs, event messages, user-mode error messages,
and Customer Experience Improvement Program events. For more information, see Configure diagnostic logging
settings .
• Configure antivirus protection settings You can configure several antivirus settings if you have an antivirus
program that is designed for Office SharePoint Server 2007. 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 antivirus protection .
• Configure search You can configure several search and index settings to customize how Office SharePoint
Server 2007 crawls your site content or external content. For more information, see Configure the Office SharePoint
Server Search service (Office SharePoint Server).
• Configure Excel Services Before you can use Excel Services, you must start the service and add at least
one trusted location. For more information about doing this, see Configure Excel Services .
23
Perform administrator tasks by using the Central Administration site
1. Click Start, point to All Programs, point to Microsoft Office Server, 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.
Download this book

This topic is included in the following downloadable book for easier reading and printing:
• Installation Guide for Microsoft Office SharePoint Server 2007
See the full list of available books at Downloadable books for Office SharePoint Server 2007.
Deploy in a simple server farm (Office SharePoint Server)
In this article:
• Deployment overview
• Deploy and configure the server infrastructure
• Create and configure a Shared Services Provider
• Perform additional configuration tasks
• Create a site collection and a SharePoint site
• Configure the trace log
Deployment overview
Important
This article discusses how to do a clean installation of Microsoft Office SharePoint Server 2007 in a server farm
environment. It does not cover upgrading from previous releases of Office SharePoint Server 2007 or how to
upgrade from Microsoft SharePoint Portal Server 2003. For more information about upgrading from Microsoft Office
SharePoint Portal Server 2003, see Upgrading to Office SharePoint Server 2007.
Note
This article does not cover installing Office SharePoint Server 2007 on a single computer as a stand-alone
installation. For more information, see Install Office SharePoint Server 2007 on a stand-alone computer.
You can deploy Office SharePoint Server 2007 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 Office SharePoint Server 2007 application.
Note
There is no direct upgrade from a stand-alone installation to a farm installation.
24
Because a server farm deployment of Office SharePoint Server 2007 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
Office SharePoint Server 2007.
Deploying Office SharePoint Server 2007 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 Office SharePoint Server 2007. This topic
provides details about how the DBA can create these databases before beginning the Office SharePoint Server 2007
installation or creation of a Shared Services Provider (SSP). For more information about deploying using DBA-created
databases, including detailed procedures, see Deploy using DBA-created databases (Office SharePoint Server).
Suggested topologies
Server farm environments can encompass a wide range of topologies and can include many servers or as few as two
servers.
A small 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 Office
SharePoint Server 2007. In this configuration, the front-end servers are configured as Web servers and application servers.
The Web server role provides Web content to clients. The application server role provides Office SharePoint Server 2007
services such as servicing search queries, and crawling and indexing content.
A medium server farm typically consists of a database server, an application server running Office SharePoint Server 2007,
and one or two front-end Web servers running Office SharePoint Server 2007 and IIS. In this configuration, the application
server provides indexing services and Excel Calculation Services, and the front-end Web servers service search queries and
provide Web content.
A large server farm typically consists of two or more clustered database servers, several load-balanced front-end Web
servers running Office SharePoint Server 2007, and two or more application servers running Office SharePoint Server 2007.
In this configuration, each of the application servers provides specific Office SharePoint Server 2007 services such as
indexing or Excel Calculation Services, and the front-end servers provide Web content.
Note
All of the Web servers in your server farm must have the same SharePoint Products and Technologies installed. For
example, if all of the servers in your server farm are running Office SharePoint Server 2007, you cannot add to your
farm a server that is running only Microsoft Office Project Server 2007. To run Office Project Server 2007 and Office
SharePoint Server 2007 on your server farm, you must install Office Project Server 2007 and Office SharePoint
Server 2007 on each of your Web servers. To enhance the security of your farm and reduce the surface area that is
exposed to a potential attack, you can turn off services on particular servers after you install SharePoint Products
and Technologies.
Before you begin deployment

This section provides information about actions that you must perform before you begin deployment.
25
Important
• The account that you select for installing Office SharePoint Server 2007 needs to be a member of the
Administrators group on every server on which you install Office SharePoint Server 2007. You can,
however, remove this account from the Administrators group on the servers after installation.
• For information about assigning users to be SSP administrators, see "Shared Services Providers" in
Plan for security roles (Office SharePoint Server).
• To deploy Office SharePoint Server 2007 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 in the
Planning and architecture for Office SharePoint Server 2007 guide.
• You must install Office SharePoint Server 2007 on the same drive on all load-balanced front-end Web servers.
• You must install Office SharePoint Server 2007 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 Office SharePoint Server
2007, and then install Office SharePoint Server 2007, Setup might fail to create the configuration database and the
installation will fail.
Note
We recommend that you read the Known Issues/Readme documentation before you install Office SharePoint
Server 2007 on a domain controller. Installing Office SharePoint Server 2007 on a domain controller requires
additional configuration steps that are not discussed in this document.
• You must install the same language packs on all servers in the farm. For more information about installing
language packs, see Deploy language packs (Office SharePoint Server).
• All the instances of Office SharePoint Server 2007 in the farm must be in the same language. For example, you
cannot have both an English version of Office SharePoint Server 2007 and a Japanese version of Office SharePoint
Server 2007 in the same farm.
• You must use the Complete installation option on all computers you want to be index servers, query servers, or
servers that run Excel Calculation Services.
• If you place a query server beyond a firewall from its index server, you must open the NetBIOS ports (TCP/User
Datagram Protocol (UDP) ports 137, 138, and 139) on all firewalls that separate these servers. If your environment
does not use NetBIOS, you must use direct-hosted server message block (SMB). This requires that you open the
TCP/UDP 445 port.
• If you want to have more than one index server in a farm, you must use a different Shared Services Provider
(SSP) for each index server.
Overview of the deployment process

The deployment process consists of three phases: deploying and configuring the server infrastructure, creating and
configuring one or more Shared Services Providers (SSPs), and deploying and configuring SharePoint sites.
Phase 1: Deploy and configure the server infrastructure

Deploying and configuring the server infrastructure consists of the following steps:
• Preparing the database server.
• Verifying that the servers meet hardware and software requirements.
26
• Running Setup on each server you want to be in the farm, including running the SharePoint Products and
Technologies Configuration Wizard.
• If you want to search over the Help content for Office SharePoint Server 2007, starting the Windows SharePoint
Services Search service.
Phase 2: Create and configure a Shared Services Provider

Creating and configuring a Shared Services Provider consists of the following steps:
• Creating a Web application to host the SSP.
• Creating the SSP.
• Configuring the Web application and the SSP.
• Configuring services on servers.
Phase 3: Create site collections and SharePoint sites

Creating SharePoint site collections and SharePoint sites consists of the following steps:
• Creating a Web Application to host the site collections and SharePoint sites.
• Creating site collections.
• Creating SharePoint sites.
Deploy and configure the server infrastructure
Security account requirements

To deploy Office SharePoint Server 2007 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 in the Planning and
architecture for Office SharePoint Server 2007 guide.
Prepare the database server

The database server must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with the most recent service
pack.
The Office SharePoint Server 2007 Setup program automatically creates the necessary databases when you install and
configure Office SharePoint Server 2007. 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 (Office SharePoint Server).
If you are using SQL Server 2005, you must also change the surface area settings.
Configure surface area settings in SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration
Tools, and then click SQL Server Surface Area Configuration.
2. In the SQL Server 2005 Surface Area Configuration dialog box, click Surface Area
Configuration for Services and Connections.
3. In the tree view, expand the node for your instance of SQL Server, expand the Database Engine
27
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 Microsoft SQL Server and to install Office SharePoint
Server 2007. For more information about the required accounts, including specific privileges required for these accounts, see
Plan for administrative and service accounts (Office SharePoint Server).
Account Purpose Requirements
SQL Server Service This account is used as the SQL Server prompts for this account during SQL Server Setup. You
Account service account for the following have two options:
SQL Server services: • Assign one of the built-in system accounts (Local
• MSSQLSERVER System, Network Service, or Local Service) to the logon
• for the configurable SQL Server services. For more
information about these accounts and security
SQLSERVERAGENT considerations, refer to the Setting Up Windows Service
If you are not using the default Accounts topic
instance, these services will be (http://go.microsoft.com/fwlink/?LinkId=121664&clcid=0x40
shown as: 9) in the SQL Server documentation.
• • Assign a domain user account to the logon for the

service. However, if you use this option you must take the
MSSQL$InstanceNam additional steps required to configure Service Principal
e Names (SPNs) in Active Directory in order to support
• Kerberos authentication, which SQL Server uses.
SQLAgent$InstanceNa
me
Setup user account The Setup user account is used • Domain user account
to run the following: • Member of the Administrators group on each server
• Setup on each on which Setup is run
server • SQL Server login on the computer running SQL
• The SharePoint Server
Products and
28
Account Purpose Requirements
Technologies • Member of the following SQL Server security roles:

Configuration Wizard • securityadmin fixed server role
• The PSConfig • dbcreator fixed server role
command-line tool
If you run Stsadm command-line tool commands that read from or
• The Stsadm write to a database, this account must be a member of the
command-line tool db_owner fixed database role for the database.
Server farm The Server farm account is used • Domain user account.
account/Database to: • If the server farm is a child farm with Web applications
access account • Act as the that consume shared services from a larger farm, this
application pool identity account must be a member of the db_owner fixed
for the SharePoint database role on the configuration database of the larger
Central Administration farm.
application pool. Additional permissions are automatically granted for this account on
• Run the Windows Web servers and application servers that are joined to a server
SharePoint Services farm.
Timer service. This account is automatically added as a SQL Server login on the
computer running SQL Server and added 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 Office SharePoint Server 2007, 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 (Office SharePoint
Server).
Important
Office SharePoint Server 2007 requires Active Directory directory services for farm deployments. Therefore Office
SharePoint Server 2007 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.
29
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.
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). 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 version 3.0 download
contains the Windows Workflow Foundation technology, which is required by workflow features.
Note
Enable ASP.NET 2.0

You must enable ASP.NET 2.0 on all Office SharePoint Server 2007 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.
30
3. In the details pane, click ASP.NET v2.0.50727, and then click Allow.
Run Setup and build the farm

Run Setup and then the SharePoint Products and Technologies Configuration Wizard on all your farm servers. Do this on all
farm servers before going on to create a Shared Services Provider (SSP).
Note
We recommend that you run Setup on all the servers that will be in the farm before configuring the farm.
You can add servers to the farm at this point, or after you have created and configured an SSP. You can add servers after
you have created and configured an SSP to add redundancy, such as additional load-balanced Web servers or additional
query servers. It is recommended that you run Setup and the configuration wizard on all your application servers before you
create and configure the SSP.
Recommended order of configuration

We recommend that you configure Office SharePoint Server 2007 in the order listed below. This order makes configuration
easier and ensures that services and applications are in place before they are required by server types.
Recommended Order of installation
1. We recommend that the Central Administration site be installed on an application server. In a server farm that
includes more than one application server, install the Central Administration site on the application server with the
least overall performance load. If your farm will have an application server, install Office SharePoint Server 2007 on
that server first. This also installs the Central Administration site.
2. All your front-end Web servers.
3. The index server (if using a separate server for search queries and indexing).
4. The query servers, if separate from the index server.
Note
To configure more than one query server in your farm, you cannot configure your index server as a query
server.
5. Other application servers (optional).
Because the SSP configuration requires an index server, you must start the Office SharePoint Server Search service on the
computer that you want to be the index server, and configure it as an index server before you can create an SSP. Because of
this, you must deploy and configure an index server before other servers. You can choose any server to be the first server on
which you install Office SharePoint Server 2007. However, the Central Administration Web site is automatically installed on
the first server on which you install Office SharePoint Server 2007.
You can configure different features on different servers. The following table shows which installation type you should use for
each feature set.
Server type Installation type
Central Administration Web application Complete or Web Front End
Application server (such as Excel Calculation Services) Complete
31
Server type Installation type
Search index server Complete
Search query server Complete
Web server Web Front End (subsequent servers must join an existing farm)
or Complete
Note
If you choose the Web Front End installation option you
will not be able to run additional services, such as
search, on the server.
When you install Office SharePoint Server 2007 on the first server, you establish the farm. Any servers that you add you will
join to this farm.
Setting up the first server involves two steps: installing the Office SharePoint Server 2007 components on the server, and
configuring the farm. After Setup finishes, you can use the SharePoint Products and Technologies Configuration Wizard to
configure Office SharePoint Server 2007. The SharePoint Products and Technologies Configuration Wizard automates
several configuration tasks, including: installing and configuring the configuration database, installing Office SharePoint
Server 2007 services, and creating the Central Administration Web site.
Add servers to the farm

We recommend that you install and configure Office SharePoint Server 2007 on all of the farm servers before you configure
Office SharePoint Server 2007 services and create sites.
Regardless of how many Web servers you have in your server farm, you must have SQL Server running on at least one
database server before you install Office SharePoint Server 2007 on your Web servers. By default, when you add servers to
the farm and run the SharePoint Products and Technologies Configuration Wizard, the wizard does not create additional
Central Administration sites on the servers that you add, nor does it create any databases on your database server. However,
you can use the wizard to create additional Central Administration sites on the servers that you add.
Run Setup on the first server
Important
If you uninstall Office SharePoint Server 2007 from the first server on which you installed it, your farm might
experience problems. It is not recommended that you install Office SharePoint Server 2007 on an index server first.
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 Office SharePoint Server 2007 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 Officeserver.exe, on one of your
Web server computers.
32
Note
Setup automatically verifies the product key, places a green check mark next to the text box, and enables
the Continue button after it validates the key. If the key is not valid, Setup displays a red circle next to the
text box and prompts you that the key is incorrect.
3. 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.
4. On the Choose the installation you want page, click Advanced. The Basic option is for stand-alone
installations.
5. On the Server Type tab, select Complete.
6. Optionally, to install Office SharePoint Server 2007 at a custom location, select the File Location tab, and
then type the location or Browse to the location.
7. 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.
8. When you have chosen the correct options, click Install Now.
9. 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.
10. 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 Office
SharePoint Server 2007. The configuration wizard automates several configuration tasks, including: installing and configuring
the configuration database, installing Office SharePoint Server 2007 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, 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.)
33
Important
The server farm account is used to access your configuration database. It also acts as the application pool
identity for the SharePoint Central Administration application pool, and it is the account under which the
Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies
Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator
server role, and the SQL Server Security Administrators server role. The user account that you specify 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. In 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, 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
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.
34
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.
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 Office SharePoint Server 2007 on all of your Web servers and the index server
before you configure Office SharePoint Server 2007 services and create sites. If you want to build a minimal server farm
configuration, and incrementally add Web servers to expand the farm, you can install and configure Office SharePoint Server
2007 on a single Web server and configure the Web server as both a Web server and an application server. Regardless how
many Web servers you have in your server farm, you must have SQL Server running on at least one back-end database
server before you install Office SharePoint Server 2007 on your Web servers.
Important
If you uninstall Office SharePoint Server 2007 from the first server on which you installed it, your farm might
experience problems. It is not recommended that you install Office SharePoint Server 2007 on an index server first.
Run Setup on additional servers — front-end Web servers
35
Note
4. On the Choose the installation you want page, click Advanced.
5. On the Server Type tab, click Web Front End.
selected.
10. Click Close to start the configuration wizard. Instructions for completing the wizard are provided in the
following section.
Run Setup on additional servers — index or query server
Note
4. On the Choose the installation you want page, click Advanced.
5. On the Server Type tab, click Complete.
36
selected.
10. 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, you can use the SharePoint Products and Technologies Configuration Wizard to configure Office
SharePoint Server 2007. The configuration wizard automates several configuration tasks, including installing Office
SharePoint Server 2007 services. Use the following instructions to run the SharePoint Products and Technologies
Configuration Wizard.
Run the SharePoint Products and Technologies Configuration Wizard on additional servers

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 (optional)

You must start the Windows SharePoint Services Search service on every computer that you want to search over Help
content. If you do not want users to be able to search over Help content, you do not need to start this service.
Start the Windows SharePoint Services Search service (optional)
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 Services on server.
3. On the Services on Server page, next to Window SharePoint Services Search, click Start.
4. On the Configure Windows SharePoint Services Search Service Settings page, in the Service Account
section, type the user name and password for the user account under which the Windows SharePoint Services
Search service account will run.
37
5. In the Content Access Account section, type 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 specify credentials, the same account used for the search service will be used.
6. 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.
7. After you have configured all the settings, click Start.
Stop the Central Administration service on all index servers

In farms with more than one index server, you should stop the Central Administration service on all index servers. This
service is used for the Central Administration site and is not required on index servers. Stopping this service on index servers
can help avoid URL resolution problems with indexing. On the other hand, you must be sure that this service is started on the
server that hosts the Central Administration Web site, even if that server is also an index server. You do not need to stop this
service for installations where the farm has only one index server.
Before stopping the service on the index server, make sure that the service is running another server.
Stop the Central Administration service on an index server
1. On the Services on Server page, select the index server from the Server drop-down list.
2. Under Select server role to display services you will need to start in the table below, select the
Custom option.
3. In the table of services, next to Central Administration, in the Action column, click Stop.
Disable the Windows SharePoint Services Web Application service on all servers not serving content
You should disable the Windows SharePoint Service Web Application service on all servers that are not serving content,
especially index servers. On the other hand, you must be sure that this service is enabled on the servers that are serving
content.
Disable the Windows SharePoint Services Web Application service on a server
1. On the SharePoint Central Administration home page, click the Operations tab on the top link
bar.
3. On the Services on Server page, next to Window SharePoint Services Web Application,
click Stop.
Create and configure a Shared Services Provider

This section covers how to create and configure a single Shared Services Provider (SSP). An SSP is a logical grouping of
shared services and their supporting resources. In Office SharePoint Server 2007, the SSP enables sharing services across
multiple server farms, Web applications, and site collections. For more information about configuring and using SSPs, see
Chapter overview: Create and configure Shared Services Providers.
In this phase, you create one or more SSPs and configure them to meet the needs of your farm. Each server farm can host
one or more SSPs, or consume services provided by an SSP on another server farm. Each SSP runs in its own Web
38
application, which contains one or more site collections. Other Web applications on a server farm can be associated with any
of the SSPs on the farm. Shared services cannot be enabled or disabled separately from other shared services. Web
applications on a farm consume either all of the services of an SSP or none of them. For more information about SSPs, see
Plan Shared Services Providers.
Start the Office SharePoint Server Search service

You must start the Office SharePoint Server Search service on at least one computer that was set up by using the Complete
option during Setup. This service must be started on the computer that you want to use as your index server and optionally
as a query server before you can create an SSP.
Start the Office SharePoint Server Search service on the index server
3. In the Server list, select the server that you want to configure as an index server and — optionally — as a
query server.
4. On the Services on Server page, next to Office SharePoint Server Search, click Start.
5. Select the Use this server for indexing content check box. This expands the page and adds the Index
Server Default File Location, Indexer Performance, and Web Front End and Crawling sections.
6. If you want to use this server to service search queries, select the Use this server for servicing search
queries check box. This expands the page and adds the Query Server Index File Location section. If not,
skip to the next step.
7. In the Contact E-mail Address section, type the e-mail address you want external site administrators to
use to contact your organization if problems arise when their sites are being crawled by your index server.
8. In the Farm Search Service Account section, specify the User name and Password of the account
under which the search service will run. This domain account should not be a member of the Farm
Administrators group in the Central Administration Web site (the WSS_ADMIN_WPG Windows security group).
For least privilege scenarios, this should be a separate domain account, used only for this service. For more
information about this account, see Plan for administrative and service accounts (Office SharePoint Server).
9. Optionally, you can also configure other settings or accept the default settings.
10. When you have configured all the settings, click Start.
You can optionally use the following steps to start the Office SharePoint Server Search service on computers that were set
up by using the Complete option during Setup to deploy query servers.
Important
If you selected the Use this server for serving search queries option in step 6 of the previous procedure, you
cannot deploy additional query servers unless you first remove the query server role from the index server.
For information about how to perform this procedure using the Stsadm command-line tool, see Osearch.
Start the Office SharePoint Server Search service on query servers
39
3. In the Server list, select the server that you want to configure as a query server.
4. On the Services on Server page, next to Office SharePoint Server Search, click Start.
5. Select the Use this server for servicing search queries check box. This expands the page and adds the
Query Server Index File Location section.
6. In the Farm Search Service Account section, specify the User name and Password of the account
under which the search service will run. This domain account should not be a member of the Farm
Administrators group in the Central Administration Web site (the WSS_ADMIN_WPG Windows security group).
For least privilege scenarios, this should be a separate domain account, used only for this service. For more
information about this account, see Plan for administrative and service accounts (Office SharePoint Server)
7. In the Query Server Index File Location section, in the Query server index file location box, either type
the location on the local drive of the query server on which you want to store the propagated index, or accept
the default path.
8. In the Query Server Index File Location section, select one the following:
• Configure share automatically Select this option to automatically configure the share on which
you want to store the propagated index, and type the user name and password of the account that you
want to use to propagate the index (recommended).
Important
This account must a member of the Administrators group and a member of the WSS_ADM_WPG
group on the query server before you proceed to the next step, or propagation of the index will fail.
• I will configure the share with STSAdm Select this option if you want to use the Stsadm
command-line tool to create this share at a later time.
• Do nothing. The share is already configured Select this option if the share already exists and
the permissions to the share are configured as described above.
9. When you have configured all the settings, click Start.
For information about how to perform this procedure using the Stsadm command-line tool, see Osearch.
Create a Web application to host the SSP and create the SSP
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 Office SharePoint Server Shared Services section, click
Create or configure this farm's shared services.
3. On the Manage this Farm's Shared Services page, click New SSP.
4. On the New Shared Services Provider page, in the SSP Name section, click Create a new Web
application.
Note
If you see any items in the Web application drop-down list, a Web application has already been created.
You can either use this Web application or create another.
40
5. On the Create New Web Application page, in the Application Pool section, specify the User name and
Password for the user account that the Web application pool will run under.
6. You can also configure other settings on this page, or click OK to create the new Web application.
Note
By default, the Web application uses the default Web site in IIS and port 80. This port might be used by
other Web applications. Ensure that this port is open for use, or choose another port before you click OK.
Note
By default, Restart IIS Manually is selected. If you use this setting, you must restart the default Web site in
IIS, or restart the W3C service by using the command line.
7. On the New Shared Services Provider page, in the SSP Service Credentials section, type the user name
and password for the user account that the SSP service will run under.
8. Optionally, you can also configure other settings.
9. When you have configured all the settings, click OK.
10. If you used the same Web application for the SSP administration site and the My Sites site collection, you
will be prompted to use separate Web applications for these site collections. If you want to use the same Web
application, click OK. For more information about site planning, see Plan Web site structure and publishing
(Office SharePoint Server).
11. After the SSP has been created, click OK on the confirmation page that appears.
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 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.
• Configure outgoing e-mail settings You can configure outgoing e-mail settings so that your Simple Mail
Transfer Protocol (SMTP) server sends e-mail alerts to site users and notifications to site administrators. You can
configure both the "From" e-mail address and the "Reply" e-mail address that appear in outgoing alerts. For more
information, see Configure outgoing e-mail settings.
• Configure workflow settings Specify whether users can assemble new workflows, and if participants without
site access should be sent documents in e-mail attachments so they can participate in document workflows. For
more information, see Configure workflow settings.
• Configure diagnostic logging settings You can configure several diagnostic logging settings to help with
troubleshooting. This includes enabling and configuring trace logs, event messages, user-mode error messages,
and Customer Experience Improvement Program events. For more information, see Configure diagnostic logging
settings.
41
• Configure antivirus protection settings You can configure several antivirus settings if you have an antivirus
program that is designed for Office SharePoint Server 2007. 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 antivirus
settings.
• Configure search Before search queries can be serviced, content must first be crawled. You can configure
several search and index settings to customize how Office SharePoint Server 2007 crawls your site content or
external content. For more information, see Configure the Office SharePoint Server Search service (Office
SharePoint Server).
• Configure Excel Calculation Services Before you can use Excel Services, you must start the service and add
at least one trusted location. For more information, see Configure Excel Services.
Perform administrator tasks by using the Central Administration site
1. Click Start, point to All Programs, point to Microsoft Office Server, and then click SharePoint 3.0
Central Administration.
2. On the Central Administration home page, in the Administrator Tasks section, click the task you want to
perform.
3. On the Administrator Tasks page, next to Action, click the task.
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 Deploy and configure
SharePoint sites.
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
(Office SharePoint Server). For information about migrating content, see Deploy new server farm and migrate content.
You can also migrate content from a pre-existing Microsoft Content Management Server 2002 source. For information, see
Migrate from Microsoft Content Management Server 2002 to Office SharePoint Server 2007.
Before you can create a site collection or a site, you must first create a Web application. A Web application is comprised of an
Internet Information Services (IIS) site with a unique application pool.
Create a new Web application
1. Click the Start button, point to All Programs, then point to Microsoft Office Server, and then click
SharePoint 3.0 Central Administration.
2. On the Central Administration home page, click Application Management.
3. On the Application Management page, in the SharePoint Web Application Management section, click
Create or extend Web application.
4. On the Create or Extend Web Application page, in the Adding a SharePoint Web Application section,
click Create a new Web application.
5. On the Create New Web Application page, in the IIS Web Site section, you can configure the settings for
42
your new Web application.
a. To choose to use an existing Web site, select Use an existing Web site, and specify the Web site
on which to install your new Web application by selecting it from the drop-down menu.
b. To choose to create a new Web site, select Create a new IIS Web site, and type the name of the
Web site in the Description box.
c. In the Port box, type the port number you want to use to access the Web application. If you are
creating a new Web site, this field is populated with a suggested port number. If you are using an
existing Web site, this field is populated with the current port number.
d. In the Host Header box, type the URL you wish 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.
6. 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.
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>).
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.
7. In the Load Balanced URL section, type the URL for the domain name for all sites that users will access in
this Web application. This URL domain will be used in all links shown on pages within the Web application. By
default, the 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.
8. 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 wish 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 wish to
use, and type the password for the account into the Password box.
9. In the Reset Internet Information Services section, choose whether to allow Office SharePoint Server
2007 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
43
that action is completed. These choices are unavailable if your farm only contains a single server.
10. Under Database Name and Authentication, choose the database server, database name, and
authentication method for your new Web application.
Item Action
Database Server Type the name of the database server and SQL Server instance you want to
use in the format <SERVERNAME\instance>. You may also use the default
entry.
Database Name Type the name of the database, or use the default entry.
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.
11. 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
Createnewsiteinnewdb.
Create a site collection
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, either select a Web application to
host the site collection from the Web Application drop-down list, or create a new Web application to host the
site collection.
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, and specify 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, type the user account name 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 verify 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, type the user account for the user
44
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 verify 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.
Create a SharePoint site
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, specify 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 Office SharePoint Server 2007 (while browsing to the home page of a Office
SharePoint Server 2007 Web site, for example). Alternate access mappings enable Office SharePoint Server 2007 to map
Web requests to the correct Web applications and sites, and they enable Office SharePoint Server 2007 to serve the correct
content back to the user. For more information, see Plan alternate access mappings (Office SharePoint Server).
For information about how to perform this procedure using the Stsadm command-line tool, see Createsite.
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
identify what configuration changes were made in Office SharePoint Server 2007 before the problem occurred.
By default, Office SharePoint Server 2007 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. Whether you are using the Office SharePoint Server Search service
or 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.
45
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 either the Office SharePoint Server
Search service or 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.
For information about how to perform this procedure using the Stsadm command-line tool, see Logging and Events: Stsadm
operation.
Download this book

This topic is included in the following downloadable book for easier reading and printing:
• Installation Guide for Microsoft Office SharePoint Server 2007
See the full list of available books at Downloadable books for Office SharePoint Server 2007.
Roadmap to Office SharePoint Server 2007 content
In this article:
• Office SharePoint Server 2007 content by audience
• Office SharePoint Server 2007 IT professional content by stage of the IT life cycle
46
Office SharePoint Server 2007 content by audience
Each audience for Microsoft Office SharePoint Server 2007 can go to a specific Web site for content that is tailored for 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 • TechCenter — a central portal for IT • Developer Portal — a

page — a central professional resources central portal for developer
portal for (http://go.microsoft.com/fwlink/?LinkID=80125&cl resources
Information cid=0x409) (http://go.microsoft.com/fwli
Worker • Technical Library —an index for IT nk/?LinkID=88846&clcid=0x
resources professional content 409)
(http://go.microso (http://go.microsoft.com/fwlink/? • MSDN Library — an
ft.com/fwlink/?Lin LinkId=89168&clcid=0x409) index for developer content
kId=89166&clcid (http://go.microsoft.com/fwli
• Newly published content — an article that
=0x409 ) nk/?LinkID=88847&clcid=0x
lists new or updated content in the Technical
• Help and Library 409)
How To — an (http://go.microsoft.com/fwlink/?LinkId=89171&cl
index for cid=0x409)
Information
• Downloadable books — an article that lists
Worker content
the books available for download
(http://go.microso
(http://go.microsoft.com/fwlink/?LinkId=89172&cl
ft.com/fwlink/?Lin
cid=0x409)
kId=89167&clcid
=0x409)
Additionally, there is information for all users of SharePoint Products and Technologies at the community and blog sites listed
in the following table.
Community content and blogs
• SharePoint Products and Technologies community portal — a central place for community information
(blogs, newsgroups, and so on) 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 (http://go.microsoft.com/fwlink/?LinkId=88916&clcid=0x409)
• Support Center for Microsoft Office SharePoint Server 2007 — a central place for issues and solutions
from Microsoft Help and Support (http://go.microsoft.com/fwlink/?LinkId=89555&clcid=0x409)
47
Office SharePoint Server 2007 IT professional content by stage of the IT life cycle
IT Professional content for Office SharePoint Server 2007 follows the IT life cycle and includes content appropriate for each
stage in that 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 in the IT life cycle, plus books that cover all stages of the lifecycle
for a specific solution. For an updated list of all downloadable books available for Office SharePoint Server 2007, see
Downloadable books for Office SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkID=89172&clcid=0x409).
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 Office SharePoint Server 2007.
Content Description Links
Online content Includes the most up-to-date content. The Product evaluation for Office SharePoint Server 2007
Technical Library on TechNet is continually (http://go.microsoft.com/fwlink/?LinkId=89180&clcid=0x40
refreshed with new and updated content. 9)
Evaluation Guide Provides overview, what's new, and Evaluation guide for Office SharePoint Server 2007
conceptual information for understanding (http://go.microsoft.com/fwlink/?LinkId=83060&clcid=0x40
Office SharePoint Server 2007. 9)
Evaluation Guide Provides overview, what's new, and Evaluation guide for search in Office SharePoint Server
for Search conceptual information for understanding 2007
how searching works in Office SharePoint (http://go.microsoft.com/fwlink/?LinkID=79614&clcid=0x4
Server 2007. 09)
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 Office SharePoint Server 2007 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 Office
SharePoint Server 2007. We have planning content, including worksheets, to address both of these needs.
The following table lists resources that are available to help you plan for using Office SharePoint Server 2007.
Online content Includes the most up-to-date content. The Planning and architecture for Office SharePoint
Technical Library on TechNet is continually Server 2007
48
refreshed with new and updated content. (http://go.microsoft.com/fwlink/?LinkId=89404&clcid=0

x409)
Planning Guide, Provides in-depth planning information for Planning and architecture for Office SharePoint
Part 1 application administrators designing a solution Server, part 1
based on Office SharePoint Server 2007. (http://go.microsoft.com/fwlink/?LinkID=79552)
Planning Guide, Provides in-depth planning information for IT Planning and architecture for Office SharePoint
Part 2 professionals designing the environment to host Server, part 2
a solution based on Office SharePoint Server (http://go.microsoft.com/fwlink/?LinkID=85548)
2007.
Deploy
During the deployment stage, you configure your environment, install Office SharePoint Server 2007, and then start creating
SharePoint sites. Depending on your environment and your solution, you may have several configuration steps to perform for
your servers, for your Shared Services Providers, and for your sites. Additionally, you may have templates, features, or other
custom elements to deploy into your environment.
The process of upgrading from a previous version product, such as Microsoft Office SharePoint Portal Server 2003, Microsoft
Content Management Server 2002, or Windows SharePoint Services, is also part of the deployment stage of the IT life cycle,
and 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 Office SharePoint Server 2007.
Online content Includes the most up-to-date content. The Deployment for Office SharePoint Server 2007
Technical Library on TechNet is continually (http://go.microsoft.com/fwlink/?LinkID=76139&clcid
refreshed with new and updated content. =0x409)
Deployment Guide Provides in-depth deployment information for Deployment for Office SharePoint Server 2007
Office SharePoint Server 2007. (http://go.microsoft.com/fwlink/?LinkID=79589)
Upgrade Guide Provides overview and in-depth information Upgrading to Office SharePoint Server 2007
for upgrading from a previous version product (http://go.microsoft.com/fwlink/?LinkId=85556)
to Office SharePoint Server 2007.
Migration and Provides cross-audience (IT and developer) Migration and Upgrade Information for SharePoint
Upgrade for information for migration and upgrade from a Developers
SharePoint previous version product to Office SharePoint (http://go.microsoft.com/fwlink/?LinkId=89129&clcid=
Developers Server 2007. 0x409)
49
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 Office SharePoint Server 2007.
Online content Includes the most up-to-date content. The Operations for Office SharePoint Server 2007
Technical Library on TechNet is continually (http://go.microsoft.com/fwlink/?LinkId=89407&clcid=
refreshed with new and updated content. 0x409)
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 Office SharePoint Server 2007.
Online content Includes the most up-to-date content. The Security and protection for Office SharePoint Server
Technical Library on TechNet is continually 2007
refreshed with new and updated content. (http://go.microsoft.com/fwlink/?LinkId=89408&clcid=
0x409)
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 Office SharePoint Server 2007. 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 use Office SharePoint Server 2007.
Online content Includes the most up-to-date content. The Technical Reference for Office SharePoint Server 2007
Technical Library on TechNet is continually (http://go.microsoft.com/fwlink/?LinkId=89445&clcid=0x409)
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 Office SharePoint Server 2007. For a current list of solution guides for Office
50
SharePoint Server 2007, see Downloadable books for Office SharePoint Server 2007
White paper: Evaluation guide for Office SharePoint Server 2007
This evaluation guide is designed to give you a solid understanding of the design goals and feature set for Microsoft Office
SharePoint Server 2007 and a familiarity with the product implementation. It provides an overview of the solutions and
benefits provided by Office SharePoint Server 2007, along with descriptions of new and improved features in the areas of
portal, search, content management, business forms and integration, and business intelligence. It also provides a hands-on
tour of the product’s main feature areas and concludes with 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 Office SharePoint
Server 2007. This guide is intended for anyone who is interested in learning more about Office SharePoint Server 2007 and
wants hands-on experience.
Download this guide as a Microsoft Word document (.doc).
Evaluation guide for Office SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkId=83060&clcid=0x409)
White paper: Evaluation guide for search in Office SharePoint Server 2007
This evaluation guide is designed to present a solid understanding of the search capabilities in Microsoft Office SharePoint
Server 2007. It provides an overview of search solutions from Microsoft, gives a hands-on tour of the product, and concludes
with useful information for administrators and developers. IT professionals should use this guide to perform a thorough and
effective evaluation of Microsoft search functionality in Office SharePoint Server 2007.
Evaluation guide for search in Office SharePoint Server 2007 (http://go.microsoft.com/fwlink/?LinkID=79614&clcid=0x409)
51

Getting Started With Office Share Point Server

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Getting Started With Office Share Point Server

Enviado por

Direitos autorais:

Formatos disponíveis

Getting Started with Office SharePoint Server

Introduction to Getting Started for Office SharePoint Server 2007............................................. .....4

What's new for IT professionals in Office SharePoint Server 2007................................. ................4

Determine hardware and software requirements (Office SharePoint Server).................................9

Plan browser support (Office SharePoint Server).................................................. .......................16

Install Office SharePoint Server 2007 on a stand-alone computer........................................... .....19

Deploy in a simple server farm (Office SharePoint Server).................................................. .........24

Roadmap to Office SharePoint Server 2007 content............................................. .......................46

What's new for IT professionals in Office SharePoint Server 2007

Administration model enhancements

Centralized configuration and management

Three-tier administration model

Farm-based Central Administration user interface

Delegation of administrative responsibilities and roles

New and improved compliance features and capabilities

Auditing and logging

Item-level access control

Document lifecycle management

Administrator access control

New and improved operational tools and capabilities

Backup and recovery support

Upgrade and migration support

Host header mode

Improved support for network configuration

Alternate access mappings

SQL Server authentication

Determine hardware and software requirements (Office SharePoint Server)

About hardware and software requirements

Component Minimum Recommended

RAM 1 gigabyte (GB) 2 GB

Display 1024 × 768 1024 × 768 or higher resolution monitor

Microsoft .NET Framework 3.0

Component Minimum Recommended

Display 1024 × 768 1024 × 768 or higher resolution monitor

Network • 56 Kbps connection between • 56 Kbps or faster connection between client

Microsoft .NET Framework 3.0

Front-end Web server

Component Minimum Recommended

RAM 2 GB More than 2 GB

Display 1024 × 768 1024 × 768 or higher resolution monitor

Network • 56 Kbps connection • 56 Kbps or faster connection between client

Plan browser support (Office SharePoint Server)

About browser support

Levels of browser support

Level 1 Web browsers

Browser Windows Linux/Unix Macintosh OSX

Netscape Navigator 7.2 X

Netscape Navigator 8.1 X

Feature-specific compatibility listed by Web browser

Connect to Outlook/Client Y (1) Y (1) Y (1) Y (1) Y (1)

Edit in Datasheet view N N N N N

Edit In (Microsoft Office application) N N N N N

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 Connections N N N N N

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 Spreadsheet Y (9) Y (9) Y (9) Y (9) Y (9)

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

Summary Links Web Part Y Y Y Y Y (11)