Microsoft SharePoint server 2010 Governance v1


Published on

This document is Part 1 of SharePoint 2010 Governance Mini Series.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Microsoft SharePoint server 2010 Governance v1

  1. 1. Microsoft SharePoint Server 2010 Governance<br />Date: 05/26/2011<br />Presented By: Nilesh Mehta<br />Sr. SharePoint Architect<br />NGenious Solutions, Inc.<br />© 201-230-7922 | E-mail:<br />URL:<br />
  2. 2. Agenda<br />Defining SharePoint Governance<br />What should be governed?<br />Infrastructure Governance<br />Application Development Governance<br />
  3. 3. Microsoft Feedback<br />“very detailed and take into account many of the important aspects of a SharePoint implementation that organizations are challenged with when deploying SharePoint. I can tell from reviewing these documents and from our discussions, that the team that wrote these documents are knowledgeable and experienced with SharePoint governance planning.”<br />“that the governance documents provided are an outstanding foundation and starting point and will most certainly be very valuable during SharePoint farm implementation, and based on my personal experience and compared to other governance documentation that I have personally reviewed within other organizations, I would rate initial governance documents very high and above standard”<br />- Microsoft<br />
  4. 4. Defining Governance<br />Governance is the process of identifying rules and guidelines that allow us to better manage our environment<br />Governance is the process of defining what needs to happen and when it needs to happen<br />Governance is an on going process<br />
  5. 5. What needs to be governed?<br />Following are different areas where governance needs to be implemented for SharePoint:<br />Infrastructure<br />Application Development<br />Security and Compliance<br />Training<br />Communications<br />
  6. 6. Infrastructure<br />Server Build<br />Service Accounts<br />Services on the server<br />SQL Server<br />Web Applications<br />Site Collections / Content Database<br />Backup / Recovery<br />Disaster Recovery<br />Change Management<br />Security management<br />Managing multiple farms (DEV, QA, PROD)<br />Documentation<br />
  7. 7. Server Build<br />Access to servers and central administration should be limited to SharePoint administrators only<br />SharePoint 2010 uses the concept of Managed Accounts to run services on the server. Leverage different service accounts to run SharePoint services and DO NOT use individual user accounts for any SharePoint Services.<br />SharePoint 2010 can automatically manage password policies for managed accounts to. However, we recommend this not be done for the MAIN FARM administration account, as in case of major issues, it will be important to know this username / password information for any recovery. <br />SharePoint farm needs to leverage multiple service accounts. Grant permissions only as needed to these service accounts.<br />Server monitoring using perfmon or SCOM or any other tools that you use internally.<br />
  8. 8. Server Build<br />Different service accounts should be leveraged for each separate farm.<br />Servers should be kept up to date with latest service packs and security updates. Actually for SharePoint, I would recommend waiting at least a quarter before applying a service pack unless your immediate issues are being resolved by service pack.<br />Follow your companies policies in hardening server security.<br />Dedicate Servers for SharePoint usage only.<br />
  9. 9. Server Build<br />Services on the server:<br />Understand how to setup different services<br />In large environment, try to load balance services as much as possible<br />Identify most used service and make sure it can scale, example: Search<br />NOTE: User Profile Synchronization service cannot be load balanced<br />
  10. 10. SQL Server<br />If Possible and depending on your environment size, use a SQL Server cluster that will be dedicated for SharePoint usage only and will not be a shared environment, especially for Production environment<br />QA / Development environment may be on single SQL servers and maybe part of Shared resources<br />Maintaining enough free space on SQL will be one of the most important requirements for SharePoint, as it heavily depends on SQL.<br />Recommend allocating 3 drives (minimum) for SharePoint databases.<br />Drive 1: data<br />Drive 2: Transaction Logs<br />Drive 3: Backups<br />For the data drive, the recommendation would be to always keep 1.5x disk free space on SQL.<br />
  11. 11. Web Applications<br />Depending on size of farm, potentially have following web applications:<br />Collaboration<br />My Sites<br />Custom Applications<br />Do not create unnecessary web applications just for vanity URLs. Leverage Host Header site collections<br />
  12. 12. Site Collections / Content Databases<br />Define Site Quotas upfront<br />Group similar sites in a single content database. Some recommendations would be:<br />Group by High Priority Sites<br />Group by Large size sites<br />Group by Custom application sites<br />Group by regular collaboration sites<br />Keep large sites at a maximum of 20 GB<br />
  13. 13. Site Collections / Content Databases<br />Keep Content Databases to be around 200-250GB size maximum<br />For Example, at 2GB starting quota, you can host a 100 Site Collections within a single content database<br />2nd stage or Site collection recycle bin does not count against the site quota limit, so in this given example you could potentially gain another 100 GB of DB size if using the default recycle bin settings.<br />As the number of site collections in a content database grows, keep an eye out for sites that are growing larger in size.<br />Re-adjust your content database limits based on the size of each site at regular intervals.<br />
  14. 14. Site Maintenance<br />Implement a consistent Site Creation Process<br />If SharePoint is new within your organization or if your organization is new to Microsoft Solutions, maybe start with few site templates (Team Site, Blog, Wiki, Search) to begin with<br />Slowly start demonstrating features with Publishing, Business Intelligence, Content Management<br />Monitor Site requests and make sure end users are requesting site with legitimate usage and not just play grounds<br />Be able to generate report on who is requesting sites and how often are these used.<br />Identify SharePoint roles that will be made available: Site Collection Administrator, Owner, Designer, Approver, Contributor, Read Only, Custom<br />
  15. 15. Site Archival / Deletion<br />Implement a policy for:<br />Site Archival: <br />When can / will a site be archived?<br />What does archival mean? Backed up and deleted or will you be able to put a stub in place? If end users has links marked as favorites, what will be their experience?<br />Site Deletion:<br />When can / will a site be deleted?<br />What will be your SLA for maximum amount of time a backup is made available for restore?<br />What if end users only want certain parts of their sites restored?<br />
  16. 16. Backup / Recovery<br />NOTE: Keep at least 2 good backups on disk for quick data recovery<br />
  17. 17. Disaster / Recovery<br />Disaster recovery refers to restoration of services after hardware failure, man-made disasters, or natural disasters. To totally restore a server farm, the following SharePoint Server 2010 components must be backed up, scripted, or thoroughly documented:<br />Separate farm for disaster / recovery. Make sure SQL databases are replicated properly. Solutions are deployed to all farms equally and regularly test that at least all content and customization in the DR farm.<br />Central administration backups for entire farm<br />Configuration database and Central Administration content database via native SharePoint tools. NOTE: It is not supported to restore the configuration DB using a tool such as SQL from a point in time.<br />Content databases<br />SharePoint 14 hive customizations<br />Inetpub customizations such as web.config, and bin directory DLL’s<br />
  18. 18. Disaster / Recovery<br />Alternate Access Mappings (AAM) (cannot be restored via native tools)<br />IIS for every Web Front End server<br />Global Assembly Cache for each server<br />Recommendations:<br />All configuration changes and customizations must be documented to plan for disaster recovery scenarios and ensure adherence to governance policies (SharePoint 14 Hive, Inetpub, and alternate access mappings)<br />
  19. 19. Change Management<br />The purpose of change management governance is to:<br />Define how changes will be tracked, catalogued, and approved<br />Decide where older versions of configurations, code, and compiled components will be stored<br />
  20. 20. Manage Multiple Environments<br />Production / QA / Development:<br />Leverage different service accounts for each farm for security<br />Make sure QA mimics Production as much as possible<br />All environments should be same in terms of platform updates, service packs, hotfixes and SharePoint 2010 Feature Set, as far as possible<br />
  21. 21. Documentation<br />Following components should be documented as part of the initial build (includes but not limited to):<br />All documentation associated with the SharePoint environment should be stored in a central location. <br />All configuration and customization tasks to the SharePoint environment should not be closed until the appropriate documentation changes have been completed.<br />System infrastructure should be documented including:<br />Network and System administrators<br />Operating System installation specifics<br />Third-Party Software<br />Network Components<br />Switches<br />Routers<br />Firewalls<br />Storage area network (SAN)<br />Cabling and electrical topology<br />
  22. 22. Documentation<br />Document the installation, configuration, and customization of the system in its environment. The system must be documented well enough so as to be reinstalled and reconfigured to last known good operating standards, should it become necessary to do so.<br />Initial installation setup should be documented including:<br />Installations file location and license key. NOTE: It is recommended to build a slipstream media that has latest updates for SharePoint included to help build new servers.<br />Version number<br />Farm servers (name, role, IP information)<br />Service Accounts<br />IIS configurations including host headers, assigned IP addresses, and SSL certificates<br />Installation options<br />
  23. 23. Documentation<br />Initial farm configuration should be documented including:<br />Services on servers<br />Outgoing mail<br />Logging and reporting settings<br />Web applications (Include Web application general settings)<br />Farm administrators and web application security policies<br />Service application settings<br />My Site Settings<br />Search settings<br />Scheduled tasks (profile synchronization, Index crawl, audience compilation, backup, etc.)<br />Error resolution steps<br />
  24. 24. Documentation<br />Continually update server documentation with post-installation changes to your farm environment including:<br />Service packs and upgrades plus associated version number<br />Farm server additions or modifications (name, role, IP information)<br />Farm operation or application configuration setting modifications<br />Farm customizations should be documented including:<br />SharePoint 14 Hive modifications<br />IIS configurations including host headers, assigned IP addresses, and SSL certificates, web.config files, and other file customizations or additions to the Web application’s files<br />Custom solution and applications deployed to the farm(s)<br />Custom or 3rd-party web parts, add-ins, or solution deployment<br />
  25. 25. Documentation<br />Document custom solutions / applications that are deployed to the farm<br />Document information across various environments like Development, UAT and Production<br />Generate Site Owner information and share with Service Desk<br />Generate information on sites that have broken inheritance in terms of permissions and share with Service Desk Teams or these teams should have access to this information on an as needed basis.<br />
  26. 26. Questions?<br />Date: 05/26/2011<br />Presented By: Nilesh Mehta<br />Sr. SharePoint Architect<br />NGenious Solutions, Inc.<br />© 201-230-7922 | E-mail:<br />URL:<br />