2. Installing and Configuring SharePoint Technology Ryan Duguid Technical Specialist Microsoft New Zealand APAC Microsoft SharePoint Conference 2007 May 14th to 15th, 2007 Sydney, Australia

3. Session Objectives Detailed understanding of product architecture Understand admin components and their uses Understand admin security Understanding your deployment options Determine topology Build your deployment plan

4. Topics Design Goals Logical Architecture Re-architecting SharePoint administration Security Map Physical Architecture Picking your topology Multi-farm topologies Hardware requirements

5. Key Customer Pain Points Inconsistent setup between products Central admin just too hard Topology restrictions Farms of various sizes and shapes Flexibility in renaming and repurposing servers Network support NT authentication only Reverse proxies, SSL termination, IP-bound IIS virtual servers Poor resource utilization and isolation Portal services model very inflexible Upgrade

6. Administration Design Goals Windows SharePoint Services Simplicity Consistency Extensibility Office SharePoint Server = WSS goals + Resource Optimization Delegation

7. Topics Design Goals Logical Architecture Re-architecting SharePoint Admin Security Map Physical Architecture Picking your topology Multi-farm topologies HW Requirements

8. Re-Architecting Admin Key Concepts SharePoint “farm” Servers App servers: Generic server – all services installed WFEs: Web bits only Config DB: Heart and soul of the farm SPTimer Service: Heartbeat of farm SharePoint Administration Service Repeats tasks done in SharePoint by box admins across the farm Shared services Grouped, high-value, resource intensive services One to many per farm Inter-farm capable Admin sites Central administration: 1 per farm Shared services administration: “special” content site

9. Central Admin IT Administrators Farm-level Resource management Status One per farm E.g. Create new site Administrative Architecture Three Tier Admin Web-based Role and Task Delineated Controlled Delegation Secure Isolation Site Settings Business site owner Site specific configuration and tasks E.g. Create new list Shared Services Business unit IT Up to one per business group Service level config E.g. Create search content source

10. Tier 1: Central Administration Goals Reduce administrator time Quickly identify what must be done Rapidly locate UI to do what’s needed Single point administration Manage the application Single change updates all servers in farm Extensible platform for SharePoint admin Consistent UI experience for all products

11. Central Administration Major Elements Administrative task list Informs operators what must be done Explains action needed, and provides link to UI Home page topology view Quick view of farm servers and what is running on them Services on Server page Manage the components running on a single server Flat menu structure Operations: tasks affecting farm resource usage App Management: tasks specific to a single application or service within the farm Security trimming reduces UI clutter Remote administration Web-based administration UI Timer-based system updates

12. Central Administration

13. Tier 2: Shared Services Key Concepts “Shared Services” = Office SharePoint Server Infrastructure Goal Separation of services from Portals Remove scale limitation for # of portals Required for site and cross site-level Office Server features Logical/secure partition of farm Services act as a group SSP Components SSP admin site SSP databases Shared Services Office Server Search Directory import User profile synch Audiences Targeting Business data catalog Excel calculation service Usage reporting

14. Shared Services Associations SSP Default = 1st SSP Can be changed to different SSP Cannot be deleted New, existing web apps auto-associated Content web applications ALWAYS associated to 1 and only 1 SSP Security implications Content app pool granted rights across SSP Disassociation: Accounts NOT auto-cleaned up Actions auto-started/stopped: Search: Add start address to portal content source People: User Profile Synch

15. Shared Services Web App CorpWeb FinWeb HRWeb LegalWeb Office Server Search Directory import User profile synch Audiences Targeting Business data catalog Excel calculation service Usage Reporting Shared Services

16. Office Server Search Directory import User profile synch Audiences Targeting Business data catalog Excel calculation service Usage reporting Shared Services – # 2 Shared Services Multiple SSPs? Vast majority of installs = 1 SSP Use cases for multiple SSPs Secure isolation of services and service data Hosted environments Restricted sites Organizational/Political concerns Web App CorpWeb FinWeb HRWebLegalWeb Office Server Search Directory import User profile synch Audiences Targeting Business data catalog Excel calculation service Usage reporting Shared Services Office Server Search Directory import User profile synch Audiences Targeting Business data catalog Excel calculation service Usage reporting Shared Services

17. Shared Services Demo

18. Tier 3: Site Settings UI for users to manage their sites Permissions and users of site Storage taken up within site Site hierarchy Key concepts Delegate management of common tasks to users Extensible Consistent experience Features merged directly into UI Operators lack permission for content Change from v2 Can take ownership or add policy (audited) Security trimmed UI improves usability

19. Site Settings

20. Security Best Practices Unique accounts for the following Farm account SSP process account NOTE: Cannot be Network Service in a farm config. SSP shared web service account Content app pool Kerberos on (default = NTLM) Each process account must be a registered SPN to work SSL enabled (default = off) Turn on for admin sites and server to server Warning provided on credentials pages if SSL is off SPAdmin service Single server: Off (recommend ‘On’ for OSS) Farm: On

21. Topics Design Goals Logical Architecture Re-architecting SharePoint Admin Security Map Physical Architecture Picking your topology Multi-farm topologies HW Requirements

22. Physical Architecture Key Concepts Topology Group services on hardware as needed Scale hardware based on your needs # servers/role 32 bit, 64 bit, mixed 32 and 64 bit Server “roles” Web front end App server: Indexing, Search, Excel Calc, Project No Job Server – replaced by SPTimer and SPAdmin service Database Network capabilities Extranet as a 1st tier “feature” Span Domains Multiple authentication providers SQL auth support SSL, IPSec, etc.

23. User requests Load balances web front end servers Application servers Clustered SQL server IndexSearchExcel Project Large Farm User requests Web front ends + application(s) Application(s) Clustered SQL server Medium Farm Small Farm User requests Each load-balanced server includes: Web front end Applications Dedicated SQL server Single Server Web front end Application Database One Server which contains: User Requests Picking Your Topology Availability Performance Strengths Fast & Easy Network considerations Limitations Limited data & user load capability Availability & reliability Single Server User Requests One Server which contains: Web front end Application Database Small Farm User requests Each load-balanced server includes: Web front end Applications Dedicated SQL server Strengths Data & user load capability Availability & reliability Exercise feature deployment Limitations Long running operations Network considerations Medium Farm Strengths Data & user load capability Availability & reliability Exercise feature deployment Performance Limitations Setup / configuration Network considerations User requests Web front ends + application(s) Application(s) Clustered SQL server Large Farm Strengths Data & user load capability Availability & reliability Exercise feature deployment Performance Limitations Setup / configuration Network considerations User requests Load balances web front end servers Application servers Clustered SQL server IndexSearchExcel Project

24. User requests Load balances web front end servers Application servers Clustered SQL server IndexSearchExcel Project Large Farm User requests Web front ends + application(s) Application(s) Clustered SQL server Medium Farm Small Farm User requests Each load-balanced server includes: Web front end Applications Dedicated SQL server Single Server Web front end Application Database One Server which contains: User Requests Picking Your Topology Availability Performance

25. Multi-Farm Topologies Security and process isolation Development, test, production Business demands Content Management Staging environments in different networks Authoring in intranet with AD authentication Production in premier network with forms authentication Content Deployment copies content between networks Path connects source and destination site collection Job defines schedule for incremental deployment Quick Deploy feature allows authors to expedite specific articles Inter-Farm Shared Services

26. Multi-Farm Topology

27. Hardware Recommendations Single box installation - recommended CPU: 2 x 3GHz Memory: 2GB + HDD: Scenario dependent Farm Deployment Web server: 2 x 3GHz, 2GB + RAM HDD – Sufficient storage for index if also a query server App server: 2 x 2.5GHz, 4GB RAM HDD – Sufficient storage for index file SQL: Dual proc 2.5GHz; 4GB RAM HDD – Sufficient storage for content data Support both 32 and 64 bit

28. Summary Product Architecture 3-Tier Administration Architecture Central Administration Shared Services – what are they; how do they work? Extensibility Delegation to power users Site Admin Deployment Options Machine “Roles” Picking Your Topologies Single box Small, medium, large farms Multi-Farm topologies (IFSS, Publishing)

29. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.