SharePoint Web Content Management Licensing was Botched
If you ask the experts, the primary target market for SharePoint is small and medium businesses (SMBs). If you ask SMBs you might get a different answer though — as the licensing model alone is enough to send most of them running, with tails tucked tightly between their legs.
What if you are a SMB who just wants a solid Web CMS for your external website? Has SharePoint been priced out of your space? What about the companies who bought into Microsoft CMS (MCMS) and were expecting to continue playing with Wild Billy and Redmond Content Wranglers?
The SMB Web CMS market, we assert, has been left high and dry by Microsoft.
The SharePoint licensing model is typical for Microsoft — it’s confusing. It’s been discussed across the web more than a few times, which is not surprising considering MOSS’ to-date popularity and buzz factor.
CMSWire had an opportunity to talk with Tom Rizzo, Director of Microsoft Office SharePoint Server and he provided us with some insights into the MOSS licensing story and the decision to combine MCMS and the SharePoint Portal Server.
|
SPONSORSHIP |
A Little Background on Microsoft Web Content Management
Prior to SharePoint 2007, if you wanted web content management from MS, you bought Microsoft Content Management Server (MCMS). It cost a little over US$ 6k for a per processor standard license and US$ 20-25K for an per processor enterprise license.
The primary difference in the licensing was related to scalability. A standard license could only be used on a server with a single CPU. With an enterprise license you could have an unlimited number of licenses on a single server and you could load balance your servers giving you high availability, etc.
So for standard license owners, they only paid the piper US$ 6k. For enterprise license owners they paid a minimum of US$ 24k and were likely paying at least double that for a dual processor server.
If you wanted portal capabilities you bought SharePoint Portal Server 2003 and a special MCMS connector to push content from MCMS to SharePoint.
Microsoft Web Content Management Today
Today, you cannot buy a standalone Web CMS product from Microsoft. Somewhere along the line, someone decided that SharePoint and MCMS needed to be integrated into a single product. That product is Microsoft Office SharePoint Server 2007 — note the missing “portal” word —, more fondly and efficiently known as MOSS (see our review here).
Tom Rizzo said that the decision to combine the two products was partly driven by Microsoft customers who didn’t want to have two separate products that were not very similar or complimentary things. He also said Microsoft looked at the two products and identified a lot of synergies such as workflow, search and versioning, deciding that rolling the two together made the most sense.
So to get SharePoint here’s what you need to buy:
- You pay a set license fee per server (not a per processor)
- You can purchase a standard or enterprise license
- A Standard license gets you WCM, document management, collaboration and search
- An Enterprise license adds Excel Services, Business Data Catalog and eForms
- If you want to build your public site with SharePoint, you must buy Office SharePoint Server 2007 for Internet sites
Take a look at the following table for a breakdown of costs:
| Product | Cost |
| MOSS Standard | $4424 |
| MOSS For Search Standard | $8213 |
| MOSS For Search Enterprise | $57,670 |
| MOSS For Internet Sites | $40,943 |
This is the basic licensing model for SharePoint; we haven’t even touched all the other components that can be packaged with it — SharePoint Designer, Forms Server and SQL Server — nor have we included the whole Client Access License (CAL) fun.
From this information we glean the following:
- If you want WCM, you have to buy the entire package
- If you want WCM for your public site you have to buy the Internet Sites license.
- If you want WCM for both your internet and intranet, you have to buy two separate licenses, plus a bunch of CALs.
Up until September 2007, you couldn’t put an Internet Sites license and an intranet license on the same server. This kind of defeated the purpose of giving SharePoint a “Extend a Web Application” feature now didn’t it?
But Microsoft smartened up and changed that rule. Let’s give them a bonus point for matching their licensing model to their software’s capability.
So do the numbers now: For a company to have web content management for their public site only they are looking at roughly US$ 40-80,000 (2 servers) for licenses alone. Now if they also want to have web content management for their intranet add another US$ 4500 minimum (1 license). That’s a total of $85,000 for something they previously paid between $6 to $48k for (1-2 servers).
How Were MCMS Customers Upgraded?
According to Tom Rizzo, Microsoft was very “generous” for MCMS owners, thinking carefully through all the different scenarios that could occur. For those customers who had purchased Software Assurance the upgraded was fairly painless.
For customers using MCMS for the Internet, their licenses were automatically transitioned to the SharePoint Internet Connector license at no extra cost. For those using MCMS for their Intranet, Microsoft transitioned their license to the SharePoint Standard License and then gave them all the CALs they needed (based on their current MCMS use) for free (if they were also using MS Office). The goal was to ensure that these customers lost no functionality when they upgrade.
Rizzo also stated that he had heard of no complaints with the upgrade to SharePoint for MCMS customers, from a licensing/pricing standpoint.
According to Ryan Duguid, Technical Product Manager, SharePoint Server group:
“We moved from per processor to per server licensing so customers can have as many processors and cores as they want, whereas in MCMS 2002 they had to buy a license for each processor. Customers with Software Assurance and a single processor license were provided with a step up to a full server license at no additional cost, otherwise the model involved a 2 processor for one server license exchange. Given the advances in hardware between MCMS and MOSS 2007, this meant that customers could leverage 4, 8 processor systems with multiple cores at no extra cost. MCMS customers migrating to MOSS can now provide end users with a seamless experience across internet, extranet and intranet facing environments. For those customers only interested in WCM, they have a far richer feature set under MOSS”.
The Marketplace for Web Content Management
Is SharePoint 2007 WCM targeted at the SMB? Well let’s put their pricing in perspective of other .NET WCM products same market:
| Vendor | License (approx. starting price) |
| Ektron CMS400.Net | US$ 10k |
| Sitecore CMS | US$ 11k |
| Quantum Art | US$ 9-15k / CPU |
Yes, SharePoint offers a lot of other features, but so do some of these other products, especially in the Web 2.0 arena. Still, we only want WCM and we can’t get SharePoint WCM independently. So we have to buy the entire cow when we only wanted a good jug of milk.
Add to this that WCM is still considered the weakest component of SharePoint and that the customization costs for a visually appealing site are the most expensive part of the solution. When you put these pieces together one might start to wonder why any small business would consider buying it.
What Microsoft Thinks
When we asked Tom Rizzo about their competition he responded that there will always be niche vendors who can under price SharePoint. He believes SharePoint offers a broad appeal and a level of functional richness which will compel customers.
In addition, he did acknowledge that the SharePoint Internet Connector License was aimed more at enterprise customers and that small to medium sized businesses are more likely to use only Windows SharePoint Services (WSS) or go through 3rd party hosting providers to bring the costs down.
An Affordable MOSS WCM?
There are ways to get MOSS WCM more cheaply. There are a number of providers of hosted SharePoint services that a company can use — including Microsoft’s own (and fairly shallow) Office Live Workspace, which can be used for both external and internal websites.
However, when comparing licensing models and Web CMS features, we’re not sure what would drive a company to go with SharePoint, when there are a number of viable and more cost effective solutions just waiting in the wings.
Your Thoughts?
The ex-MCMS and SharePoint community is large and dynamic. We want to hear from you. If you were a former MCMS customer tell us about your transition to MOSS or your shift to a new solution. If you are actively considering a SharePoint purchase, continue the conversation and share your thoughts on MOSS licensing.
The Latest Headlines
- How Design Impacts the Bottom Line
- Study Reveals Digital Media Growth Abounds
- Introducing Easy File Sharing With Drop.io
- Blinkx Gets Rosy for Video Content Management
- What's in your Xobni?
- CM Pros to Host 2008 Spring Summit
- A Multilingual Deki Wiki for Mozilla
- List Websites by Audience Demographics with Quantcast
- Away From Print Towards A Better Life Online
- GoogleReader Challenges Others like FriendFeed
Comments
MOSS used exclusively as an external CMS for 1 website is quite pricey. MOSS used as a platform for dozens of internal AND external sites/applications is FANTASTIC and CHEAP.
BTW, my company is a Sharepoint - MOSS specialist in Italy
Posted by: stefan demetz on February 23, 2008 6:03 PMBrice, very strong article on MOSS and its licensing model. What I see is that organisations that already have a (business) partnership with Microsoft simply upgrade their MCMS to MOSS while taking the fees for granted. Large enterprises do not seem to care about that kind of money. But if your company is operating in the SMB market, there are better and cheaper alternatives to MOSS. But is this not the same with, for example, Tridion?
Posted by: Johan Klein on February 25, 2008 3:31 AMI used to work for a web-development company which built websites based on MS CMS (2000-2003 approx). As it became clear that the product would not evolve any more, we switched to Ektron CMS 400, and later to Sitecore CMS.
We did re-examine our choice when MOSS was launched, but did not see many reasons to switch to that environment for stand-alone internet websites. Based on this (and other) article(s) it seems this indeed was the right decision.
Posted by: frank on February 25, 2008 7:21 AMYou actually did get into the CALs when you mentioned the following:
# A Standard license gets you WCM, document management, collaboration and search
# An Enterprise license adds Excel Services, Business Data Catalog and eForms
Those actually refer to Standard and Enterprise CALs, not Standard and Enterprise Server licenses. Of course, I'm not at all surprised that you're confused--you probably relied on the information on Microsoft's own SharePoint Web site, didn't you? Well, even Microsoft doesn't understand its own SharePoint licensing, because that information is wrong.
If you download the SharePointProductsComparison spreadsheet, for example, you'll see that the features checked for Office SharePoint Server 2007 Standard CAL and for Office SharePoint Server 2007 Enterprise CAL are identical, except in the Business Intelligence tab, where only the Enterprise CAL is marked.
This implies very clearly that the Enterpise CAL is a superset of the Standard CAL. In fact, the Enterprise CAL is NOT a superset of the Standard CAL, but licenses a discrete set of features.
You must purchase BOTH CALs to get all of these featrues. So, to see one of dozens of incorrect entries, look at the spreadsheet's first tab (collaboration), first row (Real-Time Presence and Communication), which you see is checked both Standard and Enterprise.
One would assume from this that if you bought the Enterprise CAL, you would license this feature. In fact, you must have the Standard CAL to license this feature. It is not licensed by the Enterprise CAL. (I pointed this out to Microsoft about 2 years ago, by the way. Maybe their content management team hasn't figured out how to change it.)
Posted by: Paul DeGroot on February 28, 2008 2:44 PMThe licensing costs are only part of the story. A sharepoint solution is also much more expensive because it takes a LOT more effort to build a website with MOSS than it does with other CMS products, and development costs can easily double or triple the licensing costs of Sharepoint. Sharepoint is also not very fast so you likely need more servers than with other CMS products
Posted by: John on February 29, 2008 10:48 AMWe are a small development team that built dozens of MCMS-based websites for our customers quickly and efficiently. Then MOSS came along and destroyed that entire revenue stream by being far too complicated to setup and use, expensive to license and extremely time-consuming to develop with. We have yet to sell a MOSS-based solution. It is just too expensive and now, even though we are a MS Gold partner, find ourselves selling other Web CMS products instead. MS really shot their WCM business in the foot with MOSS.
Posted by: Craig on March 5, 2008 8:47 AMI hate to break this to you guys that think that this "Internet Connection" license actually exists, but it does not. This was something early on with SharePoint licensing that got dropped. Officially, you need to talk to your LAR but here is the skinny on Internet licensing for SharePoint:
Internet facing MOSS 2007 with two servers (2 front-end and 1 index server)
- Internet sites license and windows server license for each of the three servers (no CAL’s, no base SharePoint license) (So ~$41,000 + windows license)
- SQL Server licenses as appropriate
- No CAL’s are required as long as the internal content editors are just doing web content management
Internet facing MOSS 2007 with two servers and some authentication area for external users (2 front-end and 1 index server)
- Internet sites license and windows server license for each of the three servers
- For the two front-end servers you would need a Windows Server External Connector license (something like $1,700 to enable authentication)
- SQL Server licenses as appropriate
- No CAL’s are required as long as the internal content editors are just doing web content management
Internet facing MOSS 2007 with two servers plus some additional “rich” areas of collaboration, etc. (2 front-end and 1 index server)
- Internet sites license and windows server license for each of the three servers (no CAL’s, no base SharePoint license)
- For the two MOSS front-end servers would ALSO need a base SharePoint server license and either a standard or enterprise CAL for each user that is using the “rich” collaboration
See, easy and non-complicated...
Posted by: Seth Moupre on March 5, 2008 4:34 PMHi,
Everyone giving thier own suggestions which almost make me confused about licenses and severs.
I just want to ask you guys that i had one intranet portal and one internet portal. Which licenses i have to purchase.
This is the list of my other questions:
1. Can i use one front end server for both of my portal server (itleast at staging server).
2. How it will be if i will use one Farm for both of portals with different web applications?
Please suggest me.....thanks in advance
Kuldeep Singh Kadyan
Posted by: Kuldeep Singh on March 6, 2008 7:37 AMSorry John I can develop quite quickly in SharePoint. Not to mention so can all the .Net developers around here.
SharePoint is very quick even on older servers. Maybe you dont know how to set them up (clicking the next button isn't that hard I know but maybe you need some help with your db admin skills).
Posted by: James on March 7, 2008 5:19 PMI'm working with a client who used MCMS 2002 for their Intranet who unfortunately didn't have software assurance and have 15,000+ user base and are now reviewing alternatives. Ideally it would be good to see a change in the licensing to allow more options for MOSS WCM for Intranets.
Posted by: Joe on March 26, 2008 7:51 AMAdd a Comment
Latest Job Postings
(View All
|
Feed
| Post a Job)
- Web Systems Developer at 3M
- Marketing Specialist at Honeywell International, Inc.
- Market Development Specialist at Ingram Micro, Inc.
- Sr Mgr Business Intelligence at Ingram Micro, Inc.
- Principle Web Architect at Ingram Micro, Inc.
- Senior Editor, EverydayHealth.com at Waterfront Media
- Interaction Designer at Hotwiare, Inc.
- Zope Consultant at Persel Gardner


Are you hiring? Target top talent on our
Tell a Friend
Digg It
Reddit
Tag It
Stumble It

This doesn't really help explain SharePoint licensing at all!
To license a small scale internet site (.com) with MOSS you would need:
A frontend web server with MOSS - probably a dual proc machine = 1 standard server license ($4424)
A SQL Standard Server probably dual per CPU licensing.
CAL's for your internal users (~$60 each)
An external connector license ($40,943)
As long as you ran your search on the front end which for a small site would be fine that's it.
This is more than the cost of the small players you mention, but is highly competitive with any solution that is even vaguely close in functionality.
If you want to scale out the environment you might want another frontend ($4424) and a seperate query and index server ($4424). To make the solution fault tolerant you could also add a passive SQL node (at no extra cost).
This would scale to really heavy loads allowing between 12 and 20 separate web applications (web sites) to run on the same farm (based on RAM in the machines). This isn't just cheap it's a BARGAIN!!
The way you list off what you call the 'breakdown of costs' would suggest that you need to buy at least one of each - this would never happen. The two search products you list are sold separately and are for organizations who only want to use search (ie no web content management or doc man etc). They are priced to complete with Google Search applicances. If you have purchased MOSS standard and user CALs you have already got all of the features of the enterprise search products.
I hope this helps others from being mislead - if you can make your article a bit more clear it will no-doubt help lots of people becoming confused.
Posted by: D on February 22, 2008 5:13 PM