7 Tips for Managing a Successful Transition to SharePoint 2010

28
presented by Dave Healey [email protected] m (206) 734-9414 12/07/2011 Successful SharePoint 7 Tips for Managing a Successful Transition to SharePoint 2010

Transcript of 7 Tips for Managing a Successful Transition to SharePoint 2010

Page 1: 7 Tips for Managing a Successful Transition to SharePoint 2010

presented by

Dave [email protected]

(206) 734-9414

12/07/2011

Successful SharePoint7 Tips for Managing a Successful Transition

to SharePoint 2010

Page 2: 7 Tips for Managing a Successful Transition to SharePoint 2010

Welcome

Dave HealeyManaging Partner, Chrysalis | BTSDave has spent twenty years delivering Enterprise Information Management solutions to large and complex organizations and has built a number of successful technology solution companies.

[email protected]

Eric SchubertSolutions Engineer, Tier 3Eric has over 15 years of experience in the IT industry. He specializes in project planning, new environment sizing and architecture—and has scoped, architected, and performed hundreds of IT deployments on-premise and in the cloud.

[email protected]

Page 3: 7 Tips for Managing a Successful Transition to SharePoint 2010

3

SHAREPOINT 2010INTRODUCTION

Successful SharePoint

Page 4: 7 Tips for Managing a Successful Transition to SharePoint 2010

4

Architectural OverviewSharePoint 2010

Search Services

Excel Services

User Profiles

BCS

Forms Services

Visio Services

Access Services

Managed Metadata

PerformancePoint

Word Automation

Sandbox Solutions

Content

Workflow

Collaboration

Browsers

MS Office Clients

Mobile Devices

ISV Applications

Web Application Service

Fast Search Service

Third Party Services

Project Web Access

SharePoint Server 2010

SharePoint Service Applications

SharePoint Foundation

ClientApplications

Page 5: 7 Tips for Managing a Successful Transition to SharePoint 2010

5

Sites Content Communities Search Composites Insights

• Collaboration• Web Parts• Office Integration• Workspace• Mobile• Outlook Sync• Alerts

• Approval• IM Policy• Web Publishing• Content

Deployment• Managed

Metadata• Content Types• Doc Conversion

• My Sites• People Profiles• Presence• Targeting• Social Search• Tags• Ratings• Wikis

• Indexing• Relevance• Metadata• Expertise• Federation• Alerts

• Access Services• BCS• Workflow• Forms Services• Visio Services• Sandboxed

Solutions

• PerformancePoint• Analytics• Excel Services• Web Rendering• Dashboards• Carts

Core Services

Storage• Repository• Metadata• Versioning• Backup

Security• Rights/Roles• Authentication• Rights Trimming

Management• Admin UX• Delegation• Provisioning• Monitoring• Powershell

Topology• Configuration• Service

Application Management

• Feature Policy• Extranet

Site Model• Rendering• Templates• Navigation• Visual Blueprint

APIs• Fields/Forms• Web Services• Client Object

Model• Features• Solutions

Web Parts | Personalization | Master Pages | Provider Framework

Database Services Workflow Services

Operating System Services

Key Elements and New FeaturesSharePoint 2010

Page 6: 7 Tips for Managing a Successful Transition to SharePoint 2010

6

• Server farm: The top-level element of a logical architecture design for SharePoint Server

• Web application: An IIS Web site that is created and used by SharePoint Server 2010

• Content database: Provides storage Web application content

• Site collection: A set of web sites that have the same owner and share administration settings

• Site: One or more related Web pages and other items (such as lists, libraries, and documents) that are hosted inside a site collection

Key Structural ElementsEnvironmental Overview

Page 7: 7 Tips for Managing a Successful Transition to SharePoint 2010

7

For Web Servers, Application Servers and Single Server Installations:• Processor: 64-bit, four cores• RAM: 4 GB for developer or evaluation use• 8 GB for production use in a single server or multiple server farm• Hard disk: 80 GB for system drive

For Database Servers:• Processor: 64-bit, four cores for small deployments• 64-bit, eight cores for medium deployments• RAM: 8 GB for small deployments

16 GB for medium deployments>16 GB for large deployments

• Hard disk: 80 GB for system driveHard disk space is dependent on the size of the SharePoint content

Hardware RequirementsTip 1: Design The Environment

Page 8: 7 Tips for Managing a Successful Transition to SharePoint 2010

8

Environment Minimum Requirement

Database serverin a Farm

One of the following:• The 64-bit edition of Microsoft SQL Server 2008 R2• The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1

(SP1) and Cumulative Update 2• The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3

(SP3)Single server withbuilt-in database

Front-end webservers and applicationserver in a farm

• The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server

• The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server

Client computer • A supported browser

Software RequirementsTip 1: Design The Environment

Page 9: 7 Tips for Managing a Successful Transition to SharePoint 2010

9

Scenario Description

Single server with SQL Server

• A single server farm• Evaluation, team, departmental application

Single server with a built-in database

• A single server with a built-in database• Evaluating SharePoint Server 2010• Small number of sites and you want to minimize overhead

Multiple servers for a three-tier farm

• Two front-end Web servers, an application server, and a database server

• A foundation for more complex farmsSingle server in an isolated virtual environment

• Test the features and behavior of SharePoint Server 2010• Minimal hardware resources• Isolates test system from production environment

Deploy in a virtual environment

Configuration impacts performance / functionality• Virtual networking• Each virtual machine• Interaction with virtualization host• Stop and restart behavior

Deployment ScenariosTip 1: Design The Environment

Page 10: 7 Tips for Managing a Successful Transition to SharePoint 2010

10

Upgrade OptionsTip 2: Determine Upgrade Approach

Approach Description

In-place upgrade • Same hardware as previous version• Upgrades the complete installation in a fixed order

Database attach upgrade

• Move to new hardware or a new farm• All content databases are detached from existing farm and

then attached to the new server farm• The upgrade process then runs and upgrades the data in place

Hybridapproach 1:Read-only databases

• Enables continuous read-only access to data whileupgrade is in progress

• Databases in original farm are set to read-only and copies of the databases are upgraded on the new farm

Hybridapproach 2: Detach databases

• In-place upgrade facilitates multiple databaseupgrades at the same time

• Optionally another farm can be used to perform the upgrade and then attach the upgraded databases to the original farm

• Original farm cannot serve requests during the upgrade process

Page 11: 7 Tips for Managing a Successful Transition to SharePoint 2010

11

Pros and ConsTip 2: Determine Upgrade Approach

Approach Pros Cons

In-place upgrade

• Farm-wide settingsare upgraded

• Customizations are available in the environment after the upgrade

• Servers and farms are offline• Enough time must be allocated

for all content to be upgraded in sequence

Database attach upgrade

• Faster upgrade times overall than an in-place upgrade

• Multiple farms can be combined into one farm

• Farm settings are not upgraded• Copying databases over a

network takes time and bandwidth

• Requires direct access to the database server

Page 12: 7 Tips for Managing a Successful Transition to SharePoint 2010

12

In SharePoint Server 2010, many services that stored data in the SSP database have their own databases — in some cases, several

databases. When you enable new services, new databases are also created to store the data for those services.

Considerations for Services UpgradeTip 2: Determine Upgrade Approach

Page 13: 7 Tips for Managing a Successful Transition to SharePoint 2010

13

Service Description

Profiles • Two services now used for user profiles and taxonomy information: User Profile service, Managed Metadata service

My Sites • Upgrade the My Site host at the same time that you upgrade the profile services. You do not need to upgrade the My Sites themselves at the same time.

• For best results, upgrade My Sites (or at least the My Site host) at the same time as your main intranet site.

Search • Search service now uses three databases• Cannot upgrade Search data by using the database attach

• Must configure Search in new farm either before or after upgrading other content

Forms • If using database attach export any administrator-deployed form templates (XSN files) and data connection files (UDCX files) before migrating, then import them to the new farm after migrating.

Considerations for Specific ServicesTip 2: Determine Upgrade Approach

Page 14: 7 Tips for Managing a Successful Transition to SharePoint 2010

14

Service Description

Excel Services • For in-place upgrade, any configuration information stored in the SSP database for Excel Services is upgraded and moved into the configuration database.

• For the database attach upgrade approach, reconfigure Excel Services in the new farm

Business Data Catalog

• In-place upgrade, data that was stored in the SSP database is moved and upgraded to a separate database

• The Business Data Catalog is not upgraded when using the database attach upgrade approach

Single Sign-On • The Single Sign-On (SSO) service is being replaced with the Secure Store Service in SharePoint Server 2010. Upgrade application definitions from SSO to the Secure Store Service, use Windows PowerShell cmdlets

• Passwords are not upgraded

Considerations for Specific ServicesTip 2: Determine Upgrade Approach

Page 15: 7 Tips for Managing a Successful Transition to SharePoint 2010

GovernanceTip 3: Managing the Tension Between Empowerment and Control

A Governance Plan helps• reduce cost of ownership,• ensure consistency, and• deliver service standards

by aligning people, process, technology, and policy,and thereby resolving ambiguityand mitigating potential forconflict within the organization.

People

Process

Technology

Policy

Individual and teamroles and responsibilities

How to accomplish commontasks such as creating a new

site or requesting new services

Leveraging technologyfeatures to enforce policies

Principles and practicesguiding what site stakeholders

should and shouldn’t do

Page 16: 7 Tips for Managing a Successful Transition to SharePoint 2010

Content Strategy

Find and share information

Optimize business processes

Legal & compliance requirements

Managedcontent lifecycle

Content Management PlanTip 4: A Planned Approach to Managing The Information Lifecycle

A well defined Content Plan forms the foundation of an organizations information management strategy and helps facilitate user adoption, support knowledge development and optimize and resource utilization.

Page 17: 7 Tips for Managing a Successful Transition to SharePoint 2010

17

User Adoption PlanTip 5: Effective Change Management

• Long term success depends on active engagement from key stakeholders across the organization• Engage key audiences early to build

buy-in, investment and ownership

Best Practice:• Develop Adoption Plan• Engage key audiences and users

early, during Phase 0:, Discovery and throughout the project

Communicate

Gather FeedbackTraining

People

Process

Tools

Page 18: 7 Tips for Managing a Successful Transition to SharePoint 2010

18

Process OptimizationTip 6: Understand and Employ SharePoint Advanced Capabilities to Enhance the Business

SharePointAdoption

BusinessValue

KeyCapabilities

AdaptiveEffectiveEstablishedRudimentary

• Insight In-Context• Improved

Decision Making• Increased Agility

• Integration• Composite and

Industry Applications

Business Solutions

• Broaden Adoption• Drive Compliance• Reduce multiple system

maintenance costs

• Content Management• Social Computing• Enterprise-Class Search• Business Intelligence

Broad Adoption

• Productivity Gains• Effective Teaming• Lightweight

Project Management

• Team Collaboration• Document Management• Search

Initial DeploymentPre-Deployment

• Inconsistent Teaming• Ad-hoc Collaboration• Informal, Inefficient

Processes• Significant IP & Legal Risk

• File shares• Email• USB Drive• Cloud shares

Business Value ApproachPerformanceMaturity

How is SharePoint being used?

1. Team Collaboration

(60% of all SharePoint sites)

2. Document Management

3. File Share Replacement

4. Portals

5. Intranets

Page 19: 7 Tips for Managing a Successful Transition to SharePoint 2010

19

SharePoint and The CloudTip 7: Consider Your Deployment Options

Technology• Elasticity• Flexibility• Automation

Business• Agility• Improved cost structure• Mobility

Team• Focus on innovation

and creating new value• Reduce time to market

Considerations• Security• Privacy• Access• Compliance

Page 20: 7 Tips for Managing a Successful Transition to SharePoint 2010

20

SHAREPOINT AND THE CLOUD WHY A CLOUD DEPLOYMENT MAY BE YOUR BEST OPTION

Successful SharePoint

Page 21: 7 Tips for Managing a Successful Transition to SharePoint 2010

Business and IT Leaders Say Cloud Enables Agility

SOURCE: Global Business Agility Survey, February 2011

• 80%+ associate business agility with revenue growth, cost reduction, and risk management

• 63% agree cloud can have a significant impact in making business more agile and responsive

• Companies with enterprise-wide cloud deployments are 3x more likely to achieve business agility that is “much better than competition”

Page 22: 7 Tips for Managing a Successful Transition to SharePoint 2010

Enterprise Hybrid Cloud: Solving the IT Dilemma

Internal IT

ControlHas full control over

environment

SecureKnown security,

predictable performance

LeverageInvestment in technology,

people and process

Hybrid Cloud

AgilityRespond quickly to the

demands

CostTransparent and

controllable costs

ElasticityScalable Capacity

Needs Control

Wants Agility

Page 23: 7 Tips for Managing a Successful Transition to SharePoint 2010

MARKET CHALLENGE

IMPACT

Delivering application performance to meet customer expectations

Right performance for each application

Higher user satisfaction

Increased adoption, customer loyalty, and revenue

Proximity< 5ms

< 50km

Real-Time< 50ms

< 500km

Priority<100ms

< 2000km

Best Effort>100ms

>2000km

BUSI

NES

S CR

ITIC

ALIT

Y

LATENCY SENSITIVITY

Performance matters for end user experience

Application Performance Matters

Page 24: 7 Tips for Managing a Successful Transition to SharePoint 2010

Assess your existing situation: infrastructure, licensing, staffing

Consider which of your apps could leverage unique cloud capabilities

Assess your security requirements to understand implications

Plan migration to minimize impact/downtime—practice good change management

SharePoint Migration: Getting Started

Page 25: 7 Tips for Managing a Successful Transition to SharePoint 2010

Enterprise Cloud Provider Checklist

Availability Five 9s SLA covering servers, network and storage

Performance Unique virtualization tech delivering comparable to on-premise performance for apps (not 20% less)

Automated, predictive optimization and hypervisor auto-tuning

Security Secure, multi-tenant architecture that segregates data SAS 70 Type II audited, HIPAA and PCI compliant, SSAE16 cert underway Secure connection (point-to-point or client VPN, direct connection) Strong physical security policies for data centers

Business Continuity

Disaster recovery built-in: automated 14-day backups replicated to geographically diverse datacenters

Control Choice of API or control panel enables you to control every server instance

Immediate, automatic monitoring of all resources and predictive cost estimates

Support Dedicated level 3 engineers on call 24/7

Flexibility/Cost Charged for resources (CPU, memory, storage) allocated by the hour

Page 26: 7 Tips for Managing a Successful Transition to SharePoint 2010

Tier 3: An Enterprise Cloud Innovator

Time-tested TechnologyContinuously innovating on five years of unique IP in enterprise virtualization

Proven Results>100 enterprises trust their mission critical apps, sites and development environments to our cloud

Zone FootprintThree zones across the Americas by Q4

Page 27: 7 Tips for Managing a Successful Transition to SharePoint 2010

Chrysalis BTS: Delivering Impact

27

Page 28: 7 Tips for Managing a Successful Transition to SharePoint 2010

28

presented by

Dave [email protected]

(206) 734-9414