For Part IV in my SharePoint 2010 Licensing mini-series, I have put together several different licensing scenarios and detailed the requisite licensing for each. SharePoint is very flexible in both licensing and capability. As with any large company, understanding exactly which licenses you need can be quite perplexing! Hopefully this will shed some light on different scenarios to help you get your SharePoint 2010 environment licensed correctly.
The previous posts in this mini-series include explanations of the different products involved with SharePoint 2010:
As a SharePoint consultant and architect, I get a lot of questions about “What SharePoint licenses do I need?”. These example scenarios detail the products that you will need to purchase specific to SharePoint 2010. For simplicity, these scenarios are limited to Windows, SQL, and SharePoint licenses. These examples do not detail antivirus software, backup software, management software, or any other ITC-type software packages. Also, this page is specific to SharePoint 2010 only. A later post in this series will describe example scenarios for other options as well, such as FAST Search for SharePoint, Office Web Applications, Project Server 2010, Microsoft Online, and more.
Scenario A. SharePoint Foundation 2010 Intranet Site on a single Stand Alone Server. Corporate, internal-only use for 20 employees. For this environment, this would be a single server configuration running only SharePoint Foundation 2010 on the included SQL Server 2008 Express (which would automatically be installed during the SharePoint Foundation install).
That’s it! All you need is Windows Server and CALs for your users. If you have an existing Windows shop, you likely already have the Windows CALs, so all you would need is another Windows Server. Furthermore, for a 20 user environment, you could just run SharePoint 2010 on an existing, under-utilized server and thus would need no new licenses to install and run SharePoint.
Scenario B. SharePoint Foundation 2010 based Internet Site (Public Facing or External Facing). Public facing assumes anonymous access, and external facing assumes that the sites are not for Staff-only. This means this could be an Extranet, working with clients, vendors, customers, members, volunteers or any other non-staff. Again, this example will be installed as a Stand Alone Server. For Internet facing sites, you don’t need any CALs at all.
Scenario C. SharePoint Server 2010 Intranet Site. I would consider this a very small site. Stand Alone Server. Corporate, internal-only use for 20 employees. All employees only using Standard Edition functionality. Single server configuration running only SharePoint Server 2010, Standard, on the included SQL Server 2008 Express.
Scenario D. SharePoint Server 2010 Intranet Site. This one is a little larger environment running on a two Server Farm. This site would still be corporate-only use for 20 employees, two (2) server configuration with a web server running SharePoint Server 2010 and a database server running SQL Server 2008 (or 2005). For this sample configuration, all 20 employees will utilize SharePoint 2010 Standard features, while only 10 of these employees will utilize SharePoint 2010 Enterprise features.
Scenario E: SharePoint Server 2010 Intranet and Extranet Site(s). This example assumes a single farm consisting of both public facing Internet site and a Corporate use site for 20 employees. This would be a two (2) server farm with a web server running SharePoint 2010 and a database server running SQL Server 2008. For this sample configuration, all 20 employees and the anonymous users (or authenticated non-staff users) will utilize Enterprise features. NOTE: In addition to the SharePoint Server 2010 for Internet Sites, this environment requires a SharePoint Server 2010 license and appropriate CALs because there are STAFF-ONLY sites running in addition to the other sites.
Scenario F: SharePoint 2010 Standard, Internet-Only Site, two (2) server configuration with web server running SharePoint Server 2010, Standard, and database server running SQL 2008.
Scenario G: SharePoint 2010 for an Internet-Only Site running on a five (5) server farm configuration running SharePoint 2010, Enterprise, and SQL 2010. For this sample configuration, there are 2 SQL, 2 SharePoint 2010 WFE, and 1 SharePoint 2010 backend (Index).
Scenario H: SharePoint 2010 Enterprise Internet, Intranet, and Extranet Sites, on a five (5) server farm configuration running SharePoint 2010 Enterprise and SQL 2008. For this sample configuration, all 20 employees will utilize Enterprise features on this farm consisting of 2 SQL, 2 SharePoint 2010 WFE, and 1 SharePoint 2010 backend (Index). Again, this environment assumes that there are STAFF only sites running, therefore all Staff require CALs.