This document discusses the steps for deploying a SharePoint farm. It involves: 1. Preparing servers by installing software and configuring authentication and security. 2. Creating the farm by deploying the databases, services, and front-end servers. 3. Configuring settings, services, solutions and sites on the farm. The deployment process includes planning the farm topology and security, installing prerequisites, and configuring services and sites on application servers, database servers, and front-end servers. Additional environments like authoring and services farms may also be deployed.

1. Directory
Synchronization
Administrative and
service accounts
required for initial
deployment SharePoint Server 2010 does not
Harden SQL Server for SharePoint environments support single label domain names
Deploy by using DBA-created databases
Domain controller
Hardware and software requirements
Deploy the farm.
Database server
Plan security hardening Deploy the solution.
Farm configuration steps are not isolated to Implement the operations plan.
System requirements Application servers and front-end Web servers
a specific tier in the server infrastructure.
If required, deploy additional environments such as
Installing software prerequisites Configure global settings Configure farm settings authoring and staging farms, and services farms.
Plan authentication Deployment scenarios
Configure services
Database server
1.Prepare the servers
Application server Deploy solutions and customizations Infrastructure
Front-end Web server 2.Create the farm design
Create and populate the sites Capacity
After you add and configure all the front-end Web
servers, you can add any additional application servers management
that are part of your topology design to the farm. assumptions
Prepare to host sites
3.Configure settings,
services, solutions, and sites Site and solution
architecture
Solution usage
assumptions
The farm that you create and deploy will undergo
In a single-tier deployment, SharePoint Server and significant changes in size, topology, and complexity
the database server are installed on one computer. as you move through the different deployment stages Virtualization provides a good platform for
illustrated in the SharePoint 2010 Products evaluating SharePoint Server because a
Deployment model. This is typical and the expected Production virtual environment provides flexibility, rapid
result of a phased deployment. This is why we deployment capability, and the ability to roll
In a two-tier deployment, SharePoint Server components and User acceptance test (UAT)
recommend that you follow all of the stages described back virtual machines to previous states.
the database are installed on separate servers. This kind of
deployment maps to what is called a small farm. The front- in the "Deployment stages" section of this article. Installation and Pilot
end Web servers are on the first tier and the database server configuration An infrastructure design to support your solution
Proof of concept (POC)
is located on the second tier. In the computer industry, the A detailed description of how you will
first tier is known as the Web tier. The database server is Development implement the farm and the solution
known as the database tier or database back-end.
Planning A plan for testing and validating the solution
A site and solution architecture
In a three-tier deployment, the front-end Web servers are on the first
tier, the application servers are on the second tier, which is known as An understanding of the monitoring
the application tier, and the database server is located on the third and sustained engineering
tier. A three-tier deployment is used for medium and large farms. Deployment stages requirements to support the solution
A record of how the solution will be governed
Wednesday, July 14, 2010 An understanding of how the solution will be
messaged to the user to drive adoption of the solution
Topology
Resource and time issues may pressure you to be less rigorous during the planning
stage. We recommend that you try to be as diligent as possible because missed or
lightly touched planning elements can resurface as significant issues after you are
in production. These issues can create much additional work, consume unbudgeted
resources, and potentially take away from the success of your SharePoint Server.
A large server farm can be the logical result of scaling out a medium farm to meet capacity and
performance requirements or by design before a SharePoint Server solution is implemented. A
One or more related Web pages and other items (such as lists,
three-tier topology environment typically uses dedicated servers on all the tiers. Additionally,
Site libraries, and documents) that are hosted inside a site collection.
these servers are often grouped according to their role in the farm. For example, all client-
related services can be grouped onto one or two servers and then scaled out by adding
servers to this group as needed in response to user demand for these services.
A set of Web sites that have the same
A medium server farm typically consists of two or more Web servers, two application servers, Site collection owner and share administration settings.
and more than one database servers. We recommend that you start with the preceding
configuration and then scale out to accommodate the workload placed on the servers. Physical
In scenarios where services are known to use a disproportionate amount of resources, you can
scale out the application tier. Performance data will indicate which services you should
architecture
Deployment
Provides storage Web application content. You can separate
consider off-loading to a dedicated server.
Size Concepts Content database content into multiple content databases at the site collection level.
A small server farm typically consists of at least two Web servers and a
database server. One of the Web servers hosts the Central Administration
site and the other handles additional farm-related tasks, such as serving An IIS Web site that is created and
content to users. The small farm can be scaled out to three tiers using a Web application used by SharePoint Server 2010.
dedicated application server in response to the number of users, the number
of content items, and the number of services that are required.
The top-level element of a logical
The recommendation for scaling out a farm is to group services or databases Server farm architecture design for SharePoint Server.
with similar performance characteristics onto dedicated servers and then scale
out the servers as a group. In large environments, the specific groups that
evolve for a farm depend on the specific demands for each service in a farm.
SharePoint 2010 Deployment
MindMap Page 1
Installer switches
and arguments
To identify
prerequisites Download and
consolidate the Administrative and
prerequisites on a service accounts
file share Prepare for required for initial
deployment deployment
To consolidate
prerequisites
Install the Harden SQL Server
prerequisites from Install prerequisites for SharePoint
the command line from a network share environments
Hardware and
Install the software
prerequisites using requirements
an arguments file
Known issues