Presented at SPTechCon San Francisco, February, 2011.

1. Changes in Farm Architecture from MOSS 2007 to SharePoint 2010 Michael Noel Convergent Computing Twitter: @MichaelTNoel

2. 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

3. 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

4. SharePoint 2010Version Changes

5. SharePoint 2010 Infrastructure ImprovementsVersion and Edition Changes

6. SharePoint 2010 Infrastructure Changes

7. SharePoint 2010 Infrastructure ChangesGoodbye Shared Services Provider! (and good riddance…) 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-SPServiceApplicationcmdlet shows list of Service Applications

8. Web, Service App, and Data Tiers

9. SharePoint 2010 Infrastructure ChangesImprovements to Central Admin Interface and PowerShell 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.

10. SharePoint 2010Architecture Concepts

11. 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

12. 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

13. 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

15. SharePoint 2010 Databases

16. 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

17. SharePoint Databases by Version (1 of 3)

18. SharePoint Databases by Version (2 of 3)

19. SharePoint Databases by Version (3 of 3)

20. SharePoint 2010 Service Applications

21. Service Application Matrix

22. Additional Service Applications Office Web Apps Excel Calculation Services Word Viewing Service PowerPoint Service Project Server 2010

23. 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

24. 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)

25. Cross-farm Service Applications Service Applications can be shared across multiple farms Create cross-farm service application connections

26. 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

27. 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.

28. Service App Architecture Example:Simple Farm

29. Service App Architecture Example:Distributed Admin

30. Service App Architecture Example:Distributed Admin

31. Service App Architecture Example:Intranet / Complex

32. Service App Architecture Example:Dedicated Service App Farm

33. Service App Architecture Example:Central Corporate Services Model

34. SharePoint 2010 Physical ArchitectureSamples

35. SharePoint 2010 ArchitectureSmall Farms ‘All-in-One’ (Avoid) DB and SP Roles Separate

36. SharePoint 2010 Architecture“Smallest Highly Available Farm” 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

37. SharePoint 2010 Architecture“The Six Server 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

38. 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

39. SharePoint 2010 Virtualization Guidelines

40. SP2010 Role Virtualization

41. SharePoint Guest Guidelines

42. SharePoint 2010 Authentication

43. Types of Authentication

44. 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

45. Traditional FBA vs. Claims based Auth

46. 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

47. Multiple Auth Types on Default Zone

48. One Zone Per Auth Type

49. 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)

50. 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.

51. FAST Search Feature Matrix

52. Killer Feature? Thumbnail Previews

53. FAST Logical Architecture

54. 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

55. Thanks for attending! Michael Noel Twitter: @MichaelTNoel www.cco.com