Microsoft: Sharepoint Server 2010

Microsoft SharePoint Server 2010: A Comprehensive Retrospective and Technical Deep Dive

In the ever-evolving landscape of enterprise content management (ECM) and collaboration platforms, few releases have been as pivotal—or as polarizing—as Microsoft SharePoint Server 2010. Launched in May 2010, this iteration arrived as the successor to the troubled MOSS 2007 (Microsoft Office SharePoint Server). It was Microsoft’s bold attempt to bridge the gap between on-premises server administration and the emerging "cloud-aware" enterprise.

This article provides a complete overview of SharePoint Server 2010, including its historical context, standout features, system requirements, upgrade paths, support lifecycle, and why it remains relevant in certain legacy environments today. microsoft sharepoint server 2010

Minimum requirements

• OS: Windows Server 2008 SP2 64-bit (R2 recommended)
• SQL: SQL Server 2008 R2 or 2012
• RAM: 8 GB minimum (12+ GB for production)
• .NET Framework 3.5 SP1
• IIS 7.0+

2.3 Service Application Architecture

Replaces SSP from MOSS 2007. Each service (e.g., Managed Metadata, Search, User Profile) runs as a separate service application that can be shared across web applications. OS: Windows Server 2008 SP2 64-bit (R2 recommended)

Part 6: Developer Landscape – The Silverlight Era

Developers in 2010 had a confusing array of options—some progressive, others dead ends in hindsight. Installation steps (high-level)

Supported Development Models:

1. Full Trust Solutions (WSPs): Deployed via central admin, ran with elevated privileges. Powerful but risky; could crash the entire farm.
2. Sandboxed Solutions: User-code run in a partial trust environment, monitored by resource quotas. The precursor to the SharePoint App Model (2013).
3. Client-Side Object Model (CSOM): A major innovation. For the first time, .NET, Silverlight, and JavaScript (ECMAScript) could interact with SharePoint remotely without SOAP.
4. REST/OData Endpoint: /_vti_bin/ListData.svc exposed list data as Atom feeds. This was the seed for the modern Graph API.
5. Workflow Foundation 4.0: Visio 2010 could design workflows and export them directly to SharePoint. No more coding in SharePoint Designer 2007’s crusty interface.

5. Business Intelligence Integration

SharePoint 2010 became the central hub for data visualization:

• Excel Services: Allowed users to publish Excel workbooks to the web and display interactive charts and tables in a browser.
• PerformancePoint Services: Integrated dashboarding and scorecarding for KPI tracking.
• PowerPivot: Enabled massive data analysis directly within SharePoint.

Start/stop a service instance

Start-SPServiceInstance -Identity "Microsoft SharePoint Foundation Search"

Installation steps (high-level)

1. Install prerequisites (via Prerequisite Installer tool)
2. Run SharePoint Products Configuration Wizard
3. Choose “Complete” or “Standalone” (Complete recommended for production)
4. Create a new farm or join existing farm
5. Configure database connection
6. Configure Central Administration port and authentication