5 tips for SharePoint 2010 deployment and configuration

As businesses prioritize SharePoint usage, here's how to start your implementation the right way

Page 2 of 2

To run the tool, you have to first make sure SharePoint 2007 is upgraded to SP2. Then you navigate through an administrative command prompt to the %COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin, type stsadm.exe -o preupgradecheck, and read the results.

SharePoint 2010 tip 4: Extending the Web application for alternate access mappings
One cool feature of SharePoint 2010 is its ability to provide different URLs to access the same site or site collection. This is done through a feature called Alternate Access Mappings. AAMs are great for when you want to load balance SharePoint or make it work with reverse proxies like Forefront TMG. They're also well-suited for providing access to the same sites through different authentication methods.

However, to accomplish this, you need to perform a task called extending (or cloning) your Web application. By extending the Web application, you can provide different authentication methods through five separate zones (Default, Intranet, Internet, Extranet, and Custom) with different URLs. This is incredibly helpful if you have a site that is, for example, aimed at both intranet and extranet users, but you want to provide only HTTP access for intranet users and deploy claims-based authentication for extranet users. By extending the Web application and establishing a new zone for extranet users, you can establish unique authentication and a unique URL for those users.

SharePoint 2010 tip 5: Achieving a 1:1 site collection/content database ratio
In SharePoint 2010, you'll find interesting scalability facts about content databases and site collections. For example, although you can place multiple site collections in a single content database within SQL, the typical size recommendation per site collection is 100GB, and 200GB is the recommended maximum size for a content database. That 200GB recommendation is not a cap: Content databases can grow, but for the sake of performance, Microsoft recommends the 200GB limit. However, 200GB goes quickly, so the wise move is to create additional content databases and move site collections into them so that you have a 1:1 ratio of site collection and content database.

I hope these tips point you in the right direction as you begin your journey in working with SharePoint.

This article, "5 tips for SharePoint 2010 deployment and configuration," was originally published at InfoWorld.com. Read more of J. Peter Bruzzese's Enterprise Windows blog and follow the latest developments in Windows at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.

| 1 2 Page 2