Deployment Share Point Products

8/2/2019 Deployment Share Point Products

1/1

SharePoint 2010 Products: Deployment

2010 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].

Requirements

For server farm installations of SharePoint Server2010 and SharePoint Foundation 2010, you must berunning 64-bit versions of Microsoft SQL Server2005 or Microsoft SQL Server 2008 (each with theappropriate service packs and updates) on yourdatabase servers.

SharePoint Server 2010 and SharePoint Foundation2010 are 64-bit applications and can only run on a 64-bit edition of the Windows Server 2008 operatingsystem. You must have hardware that supports theuse of a 64-bit operating system and 64-bit SQLServer.

Har dware r equir ement : 64-b it Operating syst em r equirement: WindowsServer 2008 or Windows Server 2008 R2

Database requirement: 64-bit SQL Server2005 SP2 or 64-bit SQL Server 2008

Before you can deploy Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010, you must meet the followingrequirements:

SharePoint Server 2010 and SharePoint Foundation2010 must be run on a 64-bit edition of WindowsServer 2008 with Service Pack 2 or Windows Server2008 R2.

For more information, see the article Determine hardware and software requirements on TechNet.

Perform business analysis Determine goals and objectives

Determine infrastructure requirements

Steps Output

Solution plan Topology and resource

requirements

Deploy developmentcomputers orfarm Develop solution

Testand evaluate solution Refine solution

Solution

Deploy pilotfarm Deploy pilotsolution Collectbenchmark data

Evaluate pilot

Refine goals and infrastructure requirements Determine operations plan

Updated solution plan

Updated topology andresource requirements

Operations plan

Deploy production farm

Deploy production solution Implementoperations plan Deploy additional environments:

Authoring and staging farms

Geo-distributed farms Services farms (Search,Taxonomy)

Deployed production farms

Over the course of planning, developing, testing, and rolling out SharePoint 2010Products, you perform several deployments, such as an initial proof of concept, a pilotor pre-production environment, and your production environment.

Proof of concept (POC)

Pilot (small scale test)

User acceptance test (UAT)

Production

POCs are often created during evaluation phase to testthe productorsolution. A POC can be hosted on adevelopmentenvironmentoron a small scale productioncomputer.Sometimes the POC moves through severalstages in continuous development.

Example topologies

SmallscaleAll server roles installed on a single

physical server.

A limited setof users has access to the environmenttotestthe functionality and performance ofthe solution andinfrastructure.

Topology should be as similarto production environmentas possible.

Testers ensure thatall solution elements function asexpected in network and security conditions thatmatchthe conditions of the production environment.

Itis business critical and appropriate service-levelagreements are in place.

Deployment stage and environment

DevelopmentCharacteristics

Deploy farm

Deploy solution

Collectbenchmark data Evaluate proofofconcept Refine goals and infrastructure requirements

Updated solution plan

Updated topology andresource requirements

Developmentenvironments exist throughoutthe lifecycleofthe project.Initial developmentofthe solution is

followed by testing and refining the solution.

Topologies vary,depending on the type of solution,the number ofpilotusers,and the type oftesting desired.Pilotenvironments are generally scaled down,butrepresentative versions ofthe planned production environment.

Topologies vary,depending on the business needs.For UAT testing,itis recommended thatthey be near the scaleofthe production environment.Ifload testing is the goal,then the hardware should be identical.For productionenvironments, topologies vary depending on the solution and performance character istics thatwer e validated in thepre-production environments.

Expected duration and stability

Characteristics

Characteristics

Characteristics

Characteristics





Exists throughoutsolution lifecycle Nota stable environment no service-

level agreementfor users

Setup, reviewed,and then discarded Nota stable environment no service-

level agreementfor users

Limited time frame

Limited service-level agreementforsolution readiness testing

Production service-level agreementforproduction testing

Long-term availability this is a stablepre-production environment

Limited service-level agreementforusers

Long-term availability this should be astable environment

Full service-level agreementforusers,appropriate to the solution and businessrequirements

Topologies vary, ranging from solution developmentcomputers running Windows 7 to large scale pilotand UATenvironments.

Client development computersAll server roles installed on a single

physical clientcomputer.

Medium-large developmentenvironments

Similar to pilotor UAT environments.

or

Topology is usually a single server or small farm.

SmallscaleEach server role on its own server.

Medium scaleCloser to planned production

environment.

SmallscaleEach server role on its own server.

Large scaleMultiple servers for each server role,

may include multiple farms for specificpurposes.

Medium scaleMultiple servers for mostserver r oles.

Related modelsThis model covers planning for deployment of SharePoint Server 2010 orSharePoint Foundation 2010. For further information about planning yourinfrastructure for these products, see the following models:

Topologies for SharePoint Server 2010

Services in SharePoint 2010 Products

Cross-farm Services in SharePoint 2010 Products

Hosting Environments in SharePoint 2010 Products

Upgrade (1-4)

Deploy UATfarm

Deploy UATsolution Implementoperations plan Evaluate solution

Evaluate operations plan

Testfor capacity and performance

Updated operations plan

Medium scaleTwo tiers application/Web servers

and database server

Deployment stages and environments Installation and configuration

These steps include only a high-level overview of the process. To successfully plan and perform your deployment, follow the recommendationsand procedures in the Planning Guide and the Deployment Guide for SharePoint Server 2010 or SharePoint Foundation 2010.

There are three phases in the process of installing and configuring your environment:

In this phase, you get your servers ready tohost the product.

In this phase, you install the product and assign roles toeach server. You also create the configuration databaseand the SharePoint Central Administration Web site.

Prepare the servers

Databaseservers

Domaincontroller

Install and build the farm

Ifnot pre-installing databases,theconfiguration database is created whenyou run the SharePointProducts 2010Configuration Wizard.All otherdatabases are created when you createthe service applications and Webapplications thatrequire them.

Setup and harden

database servers

Cube Builder

Service? Install

SQL AnalysisServices

Pre-installed

databases? Create

databases

Setup and

configure farmaccounts

1 2

Configure directory

synchronization

Configure settings, services, solutions, and sites

In this phase, you prepare the farm to host your site content by configuring global settings, creatingservices applications, deploying customizations, and creating and populating the sites.

You can use the Farm Configuration Wizard to these configuration steps, or you can perform themby using either the SharePoint Central Administration Web site or Windows PowerShell.Configuration steps are not isolated to a specific tier in the server infrastructure.

Settings Services Deploy solutions

(Optional)Configure

incoming e-mail

settings

Configure outgoing

e-mail settings

Configure

diagnostic logging

settings andHealth Analyzer

Configure usage

and health datacollection

Configure mobileaccountaccess

Create Service

Applications

Create proxygroups?

Enable specificservices on

application servers

Create Web applicationsand sites

Create Web

applications

Configure Web

applicationsettings

Configure

authentication

Deploy customsolutions

Deploy custom site

definitions

Configure quotas

Configure

alternate accessmapping

Configureapplication pool

recycling?

Create site

collection

3

Add anti-virus

protection

Monitoring(SCOM)

Throttling

Deploy custom

features

Create sandboxed

solutions

Applicationservers

Ifusing IRM, install the Rights

ManagementServer (RMS)client

Ifusing Cube BuilderService, install

decision supportobjects and createan OLAP Administratoraccount

Verify hardwarerequirements

Install and harden

Windows Server2008 or Windows

Server 2008 R2

Install and

configurenetworking &

security protocols

Install,configure,and harden pre-

requisites

Run Setup onapplication servers

in the farm

Install any

additionalcomponents

needed

Run theConfiguration wizard

on the remainingapplication servers to

join the farm

Run theConfiguration wizard

to create the farmand SharePoint

CentralAdministration

Webservers Verify hardware

requirements

Install and hardenWindows Server

2008 or Windows

Server 2008 R2

Install andconfigure

networking &

security protocols

Install,configure,

and harden pre-

requisites

Run Setup on Web

servers in the farm

Install language

packs on all Web

servers in the farm

Run Configurationwizard on Web

servers to join the

farm

Upgrading? Run

the pre-upgradechecker

Configure

elements required

for authentication

Note thatSharePointWorkspaces can beused to keep developmentenvironmentssynchronized.

Best practices for maintaining multiple environments

Keep your environments synchronized by using the following:

Profile replication engine a tool for keeping profile and social data synchronized across

farms.

Contentdeployment a method ofmoving contentbetween authoring,staging,and live

environments.

Mirroring and log shipping two techniques forkeeping contentchanges synchronized

across farms.

Keep your environments clean by using the following bestpractices:

Be sure to reformat yourcomputers before re-using hardware betweenenvironments orwithin an environment.Do notsimply uninstall and reinstall.Ifthere are old customizations orconfigurations,they can affecthow thatcomputerworks and introduce errors into your environment.

Purpose

Steps Output

Steps Output

Steps Output

Steps Output

Used fordeveloping applications andsolutions forSharePoint2010 Products.

Purpose

Used fordetermining whethera solution willmeetbusiness needs and to determine anappropriate infrastructure plan.

Purpose

Used to testa solution on a small scale.

Pilots are used to test solution readiness(no real data,justfunctionality testing).Apilotcan also be used to testfor productioncharacteristics (real data, actual work);this

is recommended.

Purpose

A pre-production environmentused fortesting solutions againsta subsetorcomplete copy ofproduction data.

Also used forvalidating the backups oroperational procedures.

Purpose

This is the live environmentthat yourusersinteractwith.

Steps Output

If you are using the same hardware to move through these phases, be sure toreformat each computer between each phase. The number of environments belowmight seem intimidating, but note that some are temporary, and many can bevirtualized.

Before you can deploy,you mustplan thesolution you wantto deploy.Afterthe planningstage,you move through the deploymentstages in the following table,updating andrevising yourplans as you test.

Always use development best practices for managing your solutions throughout theirlifecycle. For more information, see the Application Lifecycle Management ResourceCenter on MSDN.

PlanningPurpose

Getexecutive sponsorship fortheproject.

Establish a clearschedule.

Make the environmentproduction-class,but smallerscale.

Limitthe pilottesting to no morethan a few hundred users.

Tips for asuccessfulpilot project

Testoperational tasks (backup andrecovery,health monitoring)as wellas solution elements.

Perform surveys ofthe users to getfeedback on the solution and theoperation ofthe environment.

Establish an appropriate service-level agreement.

Treatthe pilot as business-critical,notas a lab environment.In otherwords,if the environmentwere togo offline,it would stop work forthe pilotusers.

Documents

Deployment Share Point Products