SharePoint Best Practices

Microsoft is a best case study for the largest SharePoint implementation to date. As part of the Microsoft IT Showcase. Big brother published a large IT show related information in the form of a webcast, presentations and TWPs (Technical White Paper). All these give us better guidelines for how-to scenarios. Especially the bit SharePoint is very interesting. Microsoft Office SharePoint Server 2007 Hosting - Book of implementing the technique overall experience pleasant run White contains best practices and lessons learned. I would recommend this Technical Working Group to anyone in the area of SharePoint. Here is an excerpt (a big one!) The TWP.Best practices for initial activities.

Perform a thorough audit of all products and platforms that can affect the update, including Windows Server, SQL Server, IIS, Windows SharePoint Services, and earlier versions of SharePoint products and technologies, as well as portals and content sites.
Optimize and clean up current environments. These activities include: Merger and division of databases to optimize sizes. Load balancing of content between databases consolidation of server farms where possible.
Make sure that level settings are consistent across the environment to be updated.
Identify and install missing language packs. Doing so during the upgrade itself is inefficient and can cause problems.
Document initial activities and discoveries made during the process, creating a personal reference if necessary to look back during the upgrade to see what actions were carried out and to help make future upgrades easier.

Best Practices for Planning

• Opening and analyzing the pre-exploration by using the pre-analysis tool (prescan.exe) at least two days before each update.
• Leave space on the calendar to catch up after unexpected events. Upgrading is a complex process with a major impact on the business. It should be completed efficiently but not rushed.
• Updates can fail for a variety of reasons. Have a contingency plan in case of minor or major roadblocks occur.
• Plan Update based on the database free space.
• Determine the priority of exceptions and to what extent they will influence the timing. Communicate this information to affected users.
• Regularly update the calendar and give all the teams involved.
• Schedule backups, perform, and confirm before making updates. Ensure that backups and upgrades are not scheduled to run at the same time, because this will cause upgrade failure.
• Schedule time and resources for testing and previews of the new functionality.
• In performing a database attach, the number of sites is the most important factor in how long the update will take. If there are many sites on a farm, schedule upgrades based on the number of sites. If there are fewer sites (as may be the case with the equipment and portals), schedule them based on the amount of data.
• Before upgrading, communicate that sites can not be accessed or reverted during upgrade.
  Define the upgrade process thoroughly before sending communications on the timetable and procedure. Not doing so may confuse end users and may encourage them to schedule negotiable.
• Avoid committing to specific dates where possible.
• Use images in communications to explain the update process for non-technical staff.
• Send notices to owners and managers often before, during and after the upgrade.
• Finish the upgrade is not the end of the upgrade process. Define, convey and implement a communication plan later update. Define the support process for exceptions and escalations. If some technical issues that are not compatible, make sure that users know in advance.

Best Practices for Validation

• Document the entire process in as much detail as possible. This will allow staff to monitor problems back to their sources and make future updates easier.
• Develop custom user guides to help users understand the details of their environment of Office SharePoint Server 2007.
• Earlier versions of the site after the update lock to prevent users from making changes to the sites of old. This not only prevents general confusion, but also helps to avoid a situation in which misapplied updates are lost when the previous versions are taken offline.