Released in May 2010, marked a significant evolution in enterprise content management (ECM) and collaboration platforms . Building upon the foundation of its predecessor (MOSS 2007), SharePoint 2010 introduced a more modern user interface, improved scalability, and enhanced social networking features, fundamentally changing how organizations manage knowledge and work together.
As of October 13, 2015 , Microsoft officially ended Extended Support for SharePoint Server 2010.
In MOSS 2007, shared services were clunky (Shared Services Provider or SSP). SharePoint 2010 replaced SSP with , each running in its own worker process. This meant: microsoft sharepoint server 2010
Microsoft SharePoint Server 2010 represents one of the most significant milestones in the evolution of enterprise collaborative software. Released in May 2010 as the successor to Office SharePoint Server 2007 (MOSS 2007), this version fundamentally changed how organizations managed content, automated workflows, and built internal networks. It shifted SharePoint from a basic document repository into a robust, enterprise-grade development platform.
FAST brought SharePoint search into competition with Google Search Appliance (now discontinued) and Autonomy. However, its complexity and licensing cost meant most mid-market orgs stuck with Standard search. Released in May 2010, marked a significant evolution
Real-time updates on what colleagues were working on.
SharePoint 2010 moved away from folder-based organization toward metadata navigation. The introduction of the allowed organizations to define a centralized taxonomy (tags and hierarchies) that could be applied across the entire enterprise, making search and retrieval significantly faster. In MOSS 2007, shared services were clunky (Shared
: Borrowing from the Microsoft Office desktop suite, it replaced convoluted drop-down menus with a standardized, task-based tab system.
Declaring a document as a record without moving it to a separate archive site.
One notorious limitation: Search topology changes required a full crawl reset. Moving a search component between servers was a multi-hour operation—not for the faint of heart.
The site template supported file plan definitions, retention schedules, and automated disposition. A document declared a record could be locked, audited, and eventually deleted—or moved to a long-term archive.