Best Practices Resource Center for MOSS 2007
Let’s face it, best practices are good for any product but when Microsoft puts together a complete Resource Center for Microsoft Office SharePoint Server (MOSS) 2007 best practices that’s awesome. Check out this Best Practice Resource Center for MOSS 2007. There are lots of great suggestions. Here are just a few examples.
- You must clean up custom SharePoint timer jobs as part of the deactivation routines associated with the Feature that created the job. If you do not clean up custom timer jobs, the remaining timer jobs could reference assemblies that no longer exist in the environment.
- A poorly performing IFilter can have a negative impact on the indexing crawl time in a large environment and can also cause a memory leak. Also, when you install an IFilter, make sure you install on every server running indexing services. One challenge you might face is that your IFilters may not be available for 64-bit versions. Therefore, when deploying on 64-bit server farms you might want to keep that in mind.
- Except for a few well-defined files such as the web.config or docicon.xml files, you should never modify the built-in files included with SharePoint Products and Technologies except through official supported software updates, service packs, or product upgrades. Modifying the files that are installed by SharePoint is not supported. However, there are some scenarios in which you may have to modify these files to achieve consistent branding or other customizations. When you modify these files, you must consider that they may be replaced by future updates and service packs.
Best Practices for Team Collaboration Sites
1. Deploy 64-bit architecture across the farm.
2. Plan and allocate database servers to support collaboration.
3. Monitor sites and content and perform clean-ups regularly.
4. Enforce site and content size limits.
5. Plan for capacity plus one for front-end Web servers.
6. Set application pool recycling settings for better availability.
7. Manage security and permissions.
8. Test custom code and customizations.
9. Watch out for network latency.
10. Teach end-users how to get the most out of the tools.
11. Comply with operational excellence best practices and have a governance policy.
For details on these above topics click here.
For additional best practices, follow the links below.
