changes in sharepoint 2010 from moss 2007

http://www.sptechcon.com/SanFrancisco2011

Changes in Farm Architecture from MOSS 2007 to SharePoint 2010

Michael NoelConvergent ComputingTwitter: @MichaelTNoel


Michael Noel Author of SAMS Publishing titles “SharePoint 2010 Unleashed,” “SharePoint

2007 Unleashed,” “SharePoint 2003 Unleashed”, “Teach Yourself SharePoint 2003 in 10 Minutes,” “Windows Server 2008 R2 Unleashed,” “Exchange Server 2010 Unleashed”, “ISA Server 2006 Unleashed”, and many other titles .

Partner at Convergent Computing (www.cco.com / +1(510)444-5700) – San Francisco Bay Area based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security


What we will cover

Detailed Look at SharePoint 2010 Infrastructure Concepts

SharePoint 2010 Version Changes Infrastructure Changes Architectural Concepts New Database Model Physical Architectural Samples SharePoint 2010 Virtualization Detailed Look at the Service Application

Structure Authentication Options FAST Search


SharePoint 2010Version Changes


SharePoint 2007 SharePoint 2010

Windows SharePoint Services (WSS) 3.0

SharePoint Foundation 2010

Microsoft Office SharePoint Server (MOSS) 2007: Standard

SharePoint Server 2010: Standard Client Access License

Microsoft Office SharePoint Server (MOSS) 2007: Enterprise

SharePoint Server 2010: Enterprise Client Access License

SharePoint Internet Connector License

SharePoint Server 2010 for Internet Sites, Standard

* SharePoint Server 2010 for Internet Sites, Enterprise

FAST Search for SharePoint* FAST Search Server 2010 for SharePoint

SharePoint Designer 2007 SharePoint Designer 2010

Office Groove 2007 SharePoint Workspace 2010

SharePoint 2010 Infrastructure Improvements

Version and Edition Changes


SharePoint 2010 Infrastructure

Changes


SSP concept replaced with Service Applications

Each service runs independently, providing application isolation

All SSP functionality moved to databases, so they can be consumed from multiple servers more easily

New products use this framework Get-SPServiceApplication cmdlet shows

list of Service Applications

SharePoint 2010 Infrastructure ChangesGoodbye Shared Services Provider! (and good riddance…)


Web, Service App, and Data Tiers

Web

Service Apps

Data


Ribbon interface added Still a Site Collection in a dedicated Content

DB, so Best practices still apply as follows: Make redundant (install on multiple web role

servers and Load Balance) Configure for Kerberos Configure for SSL (to protect PWs)

PowerShell is Critical, highly consider as a *primary* administration tool.

SharePoint 2010 Infrastructure ChangesImprovements to Central Admin Interface and PowerShell


SharePoint 2010Architecture Concepts


Farms

Top-level Architectural Component Similar to the Forest in AD Typically multiple farms exist, i.e. Dev,

Test, Prod Other reasons to create farms include:

Dedicated Service App farm Admin / Operational / Financial

Requirements (separate groups) Geographic (multiple sites) Security / Industry requirements for isolation


Web Applications

Same concept as in MOSS 2007 Web Applications are represented by IIS

Web Sites Multiple Web Apps created for the following

reasons: Separate anonymous content from

authenticated content Isolate users Enforce permissions Optimize performance Optimize manageability


Site Collections

Same concept as in MOSS 2007 Highest level of logical site structure Used at top level of sites and at managed paths

(i.e. /sites) My Sites are all individual site collections Disadvantages of multiple site collections are

that master pages, page layouts, templates, web parts, and default navigation is not shared across them

Advantages of multiple site collections are that the data can be spread among content databases and administered separately


SharePoint 2010 Databases


Proliferation of Databases

SharePoint 2010 has moved a large number of services to the data tier

End result is a significantly higher number of databases, often more than 20 in a single farm

Database IO needs also increase


SharePoint Databases by Version (1 of 3)

SharePoint Foundation

SharePoint Server 2010 Standard

SharePoint Server 2010 Enterprise

Project Server 2010

PowerPivot

FAST Search

Configuration X X XCentral Administration content

X X X

Usage and Health Data Collection

X X X

Business Data Connectivity X X XApplication Registry service * (BDC Upgrade)

X X X

Subscription Settings service * (PowerShell Enabled)

X X X

Content Database(s) X X XSearch – Search Administration

X X

Search - Crawl X XSearch - Property X X






Project Server 2010

PowerPivot

FAST Search

User Profile - Profile X X

User Profile - Synchronization

X X

User Profile – Social Tagging X X

Web Analytics - Staging X X

Web Analytics - Reporting X X

Secure Store X X

Stage X X

Managed Metadata X X

Word Automation Services X X

PerformancePoint X






Project Server 2010

PowerPivot

FAST Search

Project Server - Draft X

Project Server - Published X

Project Server - Archive X

Project Server - Reporting X

PowerPivot Application DB X

Search Administration X


SharePoint 2010 Service Applications


Service Application Matrix

Service applications Description SharePoint Foundation 2010



Access ServicesLets users view, edit, and interact with Access 2010 databases in a Web browser.

X

Business Data Connectivity service

Gives access to line-of-business data systems. X X X

Excel Services Application Lets users view and interact withExcel 2010 files in a Web browser. X

Managed Metadata serviceManages taxonomy hierarchies, keywords and social tagging infrastructure, and publish content types across site collections.

X X

PerformancePoint Service Application

Provides the capabilities of PerformancePoint.

Search service Crawls content, produces index partitions, and serves search queries. X X

Secure Store serviceProvides single sign-on authentication to access multiple applications or services.

X X

State serviceProvides temporary storage of user session data for SharePoint Server components.

X X

Usage and Health Data Collection service

Collects farm wide usage and health data, and provides the ability to view various usage and health reports.

X X X

User Profile serviceAdds support for My Site Web sites, profile pages, social tagging and other social computing features.

X X

Visio Graphics Service Lets users view and refresh published Visio 2010 diagrams in a Web browser. X

Web Analytics service Provides Web service interfaces. X X

Word Automation Services Performs automated bulk document conversions. X X

Microsoft SharePoint Foundation Subscription Settings Service

Provides multi-tenant functionality for service applications. Tracks subscription IDs and settings for services that are deployed in partitioned mode. Deployed through Windows PowerShell only.

X X X


Additional Service Applications

Office Web Apps Excel Calculation Services Word Viewing Service PowerPoint Service

Project Server 2010


Service Application Groups Can be granular per Web

Application Multiple Instances of a

Service App can be Deployed in a Farm

Can create custom Service App ‘Group’ to target specific ones to Web Apps


Physical Isolation for Service Apps

Use different application pools to isolate the service app pool.

Uses significantly more resources for each app pool (800MB+ RAM)


Cross-farm Service Applications

Service Applications can be shared across multiple farms

Create cross-farm service application connections


Service Apps that Access External Data Sources

Delegated Windows Identity used for the following Service Apps: Excel Services PerformancePoint Services InfoPath Forms Services Visio Services

If not in the same domain, access to external data will fail from these data sources

Use the Secure Store Service to store service credentials to access these data sources


Caution: Do NOT Enable All Service Applications unless Needed!

Do NOT use the Configuration Wizard for production farms

Configuration Wizard assumes defaults, creates GUID databases, etc.

Too easy to enable all Service Applications Only turn on those Service Applications

that you need! Memory and Proc are used for every one that is turned on

Just because you’ve purchased it doesn’t mean it needs to be turned on.


Service App Architecture Example:Simple Farm


Service App Architecture Example:Distributed Admin


Service App Architecture Example:Intranet / Complex


Service App Architecture Example:Dedicated Service App Farm


Service App Architecture Example:Central Corporate Services Model


SharePoint 2010 Physical Architecture Samples


‘All-in-One’ (Avoid)

SharePoint 2010 ArchitectureSmall Farms

DB and SP Roles Separate


2 SharePoint Servers running Web and Service Apps

2 Database Servers (Clustered or Mirrored)

1 or 2 Index Partitions with equivalent query components

Smallest farm size that is fully highly available

SharePoint 2010 Architecture“Smallest Highly Available Farm”


2 Dedicated Web Servers (NLB)

2 Service Application Servers

2 Database Servers (Clustered or Mirrored)

1 or 2 Index Partitions with equivalent query components

SharePoint 2010 Architecture“The Six Server Farm”


SharePoint 2010 ArchitectureLarge Farm

Multiple Dedicated Web Servers

Multiple Dedicated Query Servers

Multiple Dedicated Crawl Servers, with multiple Crawl DBs to increase parallelization of the crawl process

Multiple distributed Index partitions (max of 10 million items per index partition)

Two query components for each Index partition, spread among servers


SharePoint 2010 Virtualization Guidelines


SP2010 Role Virtualization

• Excellent Virtualization Candidate• Can be easily provisioned via templatesWeb

• Higher proc/mem requirements, but still good candidate

• Often paired with SP2010 Web Role• Requires 2nd Disk for Index

Search Service

App

• Higher proc/mem requirements, but still good candidate

• Low disk requirements compared to other roles

Other Service Apps

• Requires the most memory, proc, and disk IO• Be cautious when virtualizing, make sure host is

scaled• Remember, Virtualization for Virtualization’s sake is

bad

DB


vCPU RAM (Minimum)

RAM (Recommended)

Web Only* 2 6GB 8GB

Service Application Roles Only

2 6GB 8GB

Dedicated Search Service App

2 8GB 10GB

Combined Web/Search/Service Apps

4 10GB 12GB

Database* 4 10GB 16GB

SharePoint Guest Guidelines


SharePoint 2010 Authentication


Types of Authentication

Type Classic-mode authentication

Claims-based authentication

• Windows• NTLM• Kerberos• Anonymous• Basic• Digest

Yes Yes

• Forms based authentication• LDAP• SQL database or other database• Custom or third-party

membership and role providers

No Yes

• SAML token-based authentication• AD FS 2.0• Third-party identity provider• LDAP

No Yes


Claims-Based Authentication Replaces Forms-based Authentication in

MOSS 2007 Used to allow access to SharePoint sites from

accounts in non-Windows auth sources (LDAP, SQL, etc.)

Allows for multiple authentication types per Web Application / Zone


Traditional FBA vs. Claims based Auth


Zones

Represent logical paths for gaining access to same sites in a Web Application

Single Web App can contain up to five zones

MOSS 2007 required zones for different auth types, SharePoint 2010 Claims-based auth allows for multiple auth types in a single zone


Multiple Auth Types on Default Zone


One Zone Per Auth Type


Content Deployment

Similar to MOSS 2007 Content Deployment

Used to ‘push’ content from one farm to another

Not a two-way synch (third party needed for that)


FAST Search

Previously a third party product ($$$$)

More reasonable pricing now Highly tuned and specialized search

engine for SharePoint and also as an enterprise search platform

Replaces SharePoint 2010 Native Search if used

‘Net new’ features built-in.


FAST Search Feature MatrixFeature


2010

Search Server 2010 Express

Search Server 2010

SharePoint Server 2010

FAST Search Server 2010

for SharePoint

Basic search X X X X XBest Bets X X X XSearch Scopes X X X XCrawled and Managed Properties X X X XQuery Federation X X X XQuery Suggestions X X X XRelevancy Tuning by Document or Site Promotions

X X X XShallow Results Refinement X X X XWindows 7 Federation X X X XPeople Search X XSocial Search X XTaxonomy Integration X XMulti-Tenant Hosting X XVisual Best Bets XSimilar Results XDuplicate Results XSearch Enhancement based on user context XSort Results on Managed Properties or Rank Profiles

XDeep Results Refinement XDocument Preview XRich Web Indexing Support X


Killer Feature? Thumbnail Previews


FAST Logical Architecture


Session Takeaways

Understand the Service Application Architecture in SharePoint 2010

Use Service Apps sparingly and only when needed

Consider FAST Search server for enhanced search

Architect for scalability and give sufficient resources to systems

Contact us at CCO.com for questions or @MichaelTNoel on Twitter


Thanks for attending!

Michael NoelTwitter: @MichaelTNoel

www.cco.com

changes in sharepoint 2010 from moss 2007

Technology