1 / 48

HMS304: WSS V3 and SharePoint Server 2007 Planning and Deployment: The Basics

Session Objectives. HMC 304: Detailed understanding of product architecture Understand admin components

joaquin
Télécharger la présentation

HMS304: WSS V3 and SharePoint Server 2007 Planning and Deployment: The Basics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. HMS304: WSS V3 and SharePoint Server 2007 Planning and Deployment: The Basics Joel Oleson, Sr. Product Manager Microsoft Corporation http://blogs.msdn.com/joelo

    2. Session Objectives HMC 304: Detailed understanding of product architecture Understand admin components & their uses Understand admin security Understanding your deployment options Topology Options 4 Servings of Pudding! HMS305 Part 2 Introduction to advanced deployments Practical examples for deploying and administering an installation Demonstrate key concepts and UI 3 Servings of Pudding!

    3. SharePoint Technology Used by Office

    4. Single Infrastructure for Intranet, Internet, and Extranet Portals

    5. Topics SharePoint 101 The New World Administration Design Goals Logical Architecture Re-architecting SharePoint Admin Security Map Physical Architecture Picking your topology Multi-farm topologies Hardware Requirements Putting it all Together

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

    7. Fundamental Principle #1

    8. Fundamental Principle #2 WSS v3 Site Collections Sites Templates MOSS 2007 Site Collections Sites Templates Shared Services EVERYTHING IS A SITE

    9. Fundamental Principle #3 Shared services Grouped, high-value, resource intensive services One to many per farm Inter-farm capable Shared Services must: expect to be used by multiple Web applications from multiple farms make themselves able to be surfaced in and managed via SharePoint Central Administration allow themselves to be managed by delegated administrators Windows SharePoint Services doesnt ship with shared services, but Microsoft Office SharePoint Server provides many SSP = Shared Service Provider = A Site that Provides MOSS Shared Services

    10. Fundamental Principle #4 What happened to Portals? Just a WSS Site + MOSS Template + Shared Services

    11. Fundamental Principle #5 NO MORE TOPOLOGY RESTRICTIONS!!! Servers have Roles Web Front End (WFE) Application Server Database Server You can create a Farm of any size of each Server Role! There are some guidelines and best practices You need to have at least 1 server specified as an Index Server. Suggested no more than 8 WFEs for each SQL Server

    12. The MOSS Portal Template & Creating a New Site

    13. POP QUIZ!!!! What is the new name for a SharePoint Virtual Server?

    14. You Pass SharePoint 101 The New World

    15. Topics SharePoint 101 The New World Logical Architecture Re-architecting SharePoint Admin Security Map Physical Architecture Picking your topology Multi-farm topologies Hardware Requirements Putting it all Together

    16. Administration Design Goals Windows SharePoint Services Simplicity Consistency Extensibility Microsoft Office SharePoint Server Windows SharePoint Services goals + Resource Optimization Delegation Consistency w/ extended Business Processes and Information

    17. Re-Architecting Admin Key concepts SharePoint farm Servers App servers have all services installed WFEs are always mirrors Config DB: Heart & soul of the farm Takes place of registry 1 per farm SPTimer Service: Heartbeat of farm SharePoint Administration Service Used to propagate config changes across farm - as box admin Shared Services A grouping of Services for Sites to use. Admin sites Central administration: 1 per farm Shared services administration: special content site

    18. Administrative Architecture

    19. Tier 1: Central Administration Goals Reduce administrator time Quickly identify what must be done Rapidly locate UI to do whats 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

    20. 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 & 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

    21. A Stroll through Central Administration

    22. Tier 2: Shared Services Key concepts Shared Services = SharePoint Server Only! 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 web service hosting Shared Services

    23. Shared Services Associations SSPDefault == 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

    24. Shared Services

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

    26. Shared Services Customer benefits Resource optimization Security isolation Flexibility Delegation of administration Power users administer Shared Service Instance ? Central admin rights Can be shared across farms Watch-outs Farm: SSP web apps app pool account cannot be Network Service 1 SSP admin site allowed in a single web application \admin\ssp Central admin operators ? SSP site administrators Closely manage security when switching associations

    27. A Stroll through SSP Administration

    28. Tier 3: Site Settings UI for users to manage their sites: Permissions & 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

    29. A Stroll through Site Settings

    30. Infrastructure Object Map

    31. Infrastructure Security Map

    32. Security Best Practices Unique accounts for the following: Farm account SSP process account NOTE: Cannot be Network Service in a farm config. Can be same as 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 & server to server Warning provided on credentials pages if SSL is off SPAdmin service: Single server: Off (recommend On for OSS) Farm: On

    33. Topics SharePoint 101 The New World Logical Architecture Re-architecting SharePoint Admin Security Map Physical Architecture Picking your topology Multi-farm topologies Hardware Requirements Putting it all Together

    34. 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 & 64-bit Server roles Web front end App server: Indexing, Search, Excel Calc, Project Database Network capabilities Extranet as a 1st tier feature Span Domains Multiple authentication providers SQL auth support SSL, IPSec, etc.

    35. Picking Your Topology Factors to consider Data composition User load Long-running operations Performance Availability & reliability Network considerations No topology restrictions

    36. Picking Your Topology

    37. Multi-Farm Topologies Security and process isolation Dev / test / prod Business demands Content Management Staging environments in different networks Authoring in Intranet with AD auth Production in premier network with forms auth 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

    38. Multi-Farm Topology

    39. Hardware Recommendations Single box installation * CPU: 2.5 GHz Memory: 2+ GB recommended, 1 GB minimum HDD: Scenario dependent Farm Deployment * Web server: 2.5 GHz, 2+ GB RAM App server: Dual proc 2.5 GHz, 2+ GB RAM SQL: Dual proc 2.5 GHz; 2+ GB RAM Support both 32 & 64-bit

    40. Topics SharePoint 101 The New World Logical Architecture Re-architecting SharePoint Admin Security Map Physical Architecture Picking your topology Multi-farm topologies Hardware Requirements Putting it all Together

    41. Logical ? Physical Mapping Single server Server 1: Content Sites SSP SSP admin site Shared services Shared web services Central admin All databases

    42. Logical ? Physical Mapping XxY Farm (Small example) Server 1 & 2: Content Sites SSP SSP admin site Shared services Shared web services Central admin (only svr 1) Server 3 All databases

    43. Logical ? Physical Mapping XxYxZ Farm (Medium example) Servers 1 & 2: Content Sites SSP SSP admin site Shared services (-) Shared web services Server 3 SSP Shared service (Index) Shared web services Central Admin Server 4 & 5 All databases

    44. Logical ? Physical Mapping XxYxZ Farm (Large example)

    45. Summary Product Architecture 3-Tier Administration Architecture Deployment Options Machine Roles Picking Your Topologies Have a Good Time in VEGAS!

    46. Resources

    48. Slide Title Please use this template for your slides Please DO NOT change the format of this template Please DO NOT use special formatting such as shadowing for code, or shadows behind boxes, etc. That screws up the printed books. Your slides are due September 8, 2006 Please send completed slides to materials@devconnections.com Filename for slides should be: lastname_conference_sessionnum_sessiontitle.ppt Please zip all files before sending them. Include sample code for the attendee disk in a subfolder.

More Related