Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Suguk nottm sept 2010 share point 2010 farm design considerations


Published on

Presentation by Mark Macrae at SUGUK Nottingham September 2010.

It begins by asking the question: Is a Single Server Sufficient for a SharePoint Deployment?

The asnwer is 'It Depends!' but the presentation explains all the considerations.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Suguk nottm sept 2010 share point 2010 farm design considerations

  1. 1. Is a Single Server Sufficient for a SharePoint Deployment?<br />Brainstorm SharePoint Deployment Planning<br />Mark Macrae<br />
  2. 2. Director Intelligent Decisioning Ltd<br />7 Years SharePoint Exp<br />SUGUK Organiser for Midlands<br />SharePoint Saturday<br />( West Ham)<br />About Me<br />
  3. 3. It Depends!<br />
  4. 4. Considerations<br />SLAs<br />Users<br />Authentication<br />Licensing<br />Location <br />Hardware<br />Software (client and server)<br />SQL Server<br />SharePoint Features<br />Information Architecture<br />Staff / Roles<br />
  5. 5. SLAs<br />SLAs affect everything<br />Recovery plan<br />Topology<br />Server spec<br />At least:<br />Approx Users<br />Max down time (RTO)<br />Max data loss (RPO)<br />Item Level Recovery<br />Disaster Recovery<br />High Availability<br />
  6. 6. SLAs<br />Define RTO/RPO targets and design a solution to meet these<br />RTO (Recovery Time Objective) <br />Maximum acceptable duration of time of system inoperability (Downtime)<br />RPO (Recovery Point Objective) <br />Maximum amount of acceptable data loss<br />
  7. 7. Users<br />Who are your users?<br />You know them individually (Intranet)<br />You know them as partners/customers (Extranet)<br />You don’t know them (Internet)<br />Define who will be using the system<br />How will they use it?<br />Which browsers?<br />Mobile?<br />Where are your users base?<br />Local?, Global?, Both?<br />How many users?<br />How will they be using it?<br />
  8. 8. Authentication<br />How will you authenticate your users?<br />Depends largely on previous slide<br />Classic Authentication<br />Active Directory authenticates a user, provides an NT Token. The token is used to authenticate to SharePoint. SharePoint consumes that token and it's converted into an SPUser object for authorization<br />Claims Authentication<br />SharePoint redirects a client to the associated trusted identity provider. The identity provider authenticates clients and provides a security token e.g.<br />NT, SAML, FBA<br />Kerberos – when and why would you need it? …….<br />
  9. 9. Licensing<br />Foundation<br />Standard<br />Enterprise<br />CALs vs External Connector<br />
  10. 10. Location<br />On Premise vs Hosted?<br />Capacity?<br />Staff / Administrators<br />Skills<br />Costs<br />Worry<br />Next session may help<br />
  11. 11. Hardware<br />Physical vs Virtual?<br />Skills<br />Recovery plan<br />Budget<br />SharePoint 2010 & Foundation <br />X64 Quad core processor<br />4GB for Dev/8GB for production<br />80GB System Partition<br />SQL Server 2008 X64<br />Prices<br />
  12. 12. Naming Conventions<br />Databases<br />Web Applications<br />User/Service Accounts<br />Servers<br />
  13. 13. SQL<br />Which version?<br />Disk – lots!<br />RAID Configuration<br />Instances<br />Business Intelligence<br />SSRS<br />
  14. 14. SQL<br />Temp<br />Logs<br />Search<br />Data<br />
  15. 15. Recovery Plan<br />Disaster Recovery<br />Not just about Backup/Restore!<br />List all possible scenarios and plan for each one with SLAs in mind<br />Hardware, Software, User error, environmental etc<br />Backup Tools<br />SharePoint vs SQL<br />3rd Party?<br />Hosted – do you need to worry?<br />
  16. 16. Recovery Plan<br />High Availability<br />Servers<br />Services<br />Topology<br />Load Balancing solution<br />Database Availability<br />Backup/Restore is not HA<br />Not quick enough<br />
  17. 17. SharePoint Feature Set<br />PerformancePoint Services<br />Excel Services<br />Access Services<br />Visio Services<br />SQL Reporting Services<br />….<br />= More of everything!!!<br />
  18. 18. SharePoint Databases<br />SharePoint 2010<br />SharePoint 2007<br />There are a lot more databases in 2010!<br />
  19. 19. Domain Account Considerations<br />Best Practise of Least Privileges<br />SharePoint 2010 requires even more accounts!<br />Basic Accounts<br />Farm Account (Database Access Account)<br />Install/Setup Account<br />Web Application App Pool Accounts<br />Service Application Accounts<br />App Pool Identities <br />Unattended Service Accounts<br />
  20. 20. Environments<br />Which environments do you REALLY need?<br />Dev<br />Continuous Build<br />UAT<br />Production<br />More environments = <br />More maintenance = More resources<br />Patching<br />SDLC!!<br />
  21. 21. Resources / Roles<br />Most organisations have the familiar role of <br /> ‘The SharePoint Guy’<br />
  22. 22. Resources / Roles<br />Network Administrator<br />SQL DBA<br />SharePoint Farm Administrator<br />Site Collection Administrators<br />Business ‘Champions’<br />Designer<br />Developers<br />
  23. 23. Scared?<br />Governance<br />Security / Authorisation<br />Patching/Service Packs<br />Developed Solutions<br />….<br />