From SharePoint 2003 to 2010: Designing the Backbone of Enterprise IT
From SharePoint 2003 to 2010: Designing the Backbone of Enterprise IT Reflecting on my 30-year journey in IT, a significant chapter that stands out in my nostalgic journey is the era of on-premises server infrastructure and the evolution of Microsoft SharePoint from its 2003 version through to SharePoint 2010. This period was marked by rapid technological advancements, complex challenges, and the exhilarating task of designing and deploying solutions that became the backbone of many enterprises before the advent of cloud computing. This era defined so many elements of what we have today. The Dawn of SharePoint 2003 In the early 2000s, businesses were seeking robust solutions for collaboration, content management, and intranet portals. The journey in my history began with SharePoint Portal Server 2003, released on October 21st 2003, it emerged as a pivotal platform that addressed these needs. It introduced features like document libraries, lists, and basic workflows, enabling teams to collaborate more effectively and introducing easier content management; completely different to ageing file server “Shared–File” drives accessible in “File Explorer“. However, SharePoint 2003 was not without its challenges. Deployment required meticulous purchasing and planning, especially in configuring server farms (purchasing hardware, networks, backup functionality etc.) and ensuring compatibility with existing infrastructure within business “Data Centres” and offices. Transitioning to SharePoint 2007 Microsoft introduced Microsoft Office SharePoint Server (MOSS) 2007 on January 27th 2007 – often referred to as SharePoint 2007 (or just MOSS), MOSS represented a significant leap forward. It expanded on the foundational features of its predecessor by incorporating enhanced collaboration tools, content management systems, business intelligence capabilities, workflows, enterprise search, and the introduction of Excel Services and InfoPath Forms Services (who can forget those beauties?). The user interface was revamped to be more intuitive, and integration with other Microsoft Office products was significantly improved. Migrating from SharePoint 2003 to 2007 presented its own set of difficulties. Data migration tools were still maturing, and compatibility issues often arose. The database attach approach to migrations was often used however, development and deployment required a deep understanding of both versions to ensure a smooth transition. The shift also highlighted the growing need for specialised SharePoint developers and administrators, as the platform’s complexity increased. Embracing SharePoint 2010 Microsoft SharePoint Server 2010 was released on May 12th, 2010 (this kick-started the now historic release frequency of 3 years still relevant today) and built upon the previous versions. It introduced a multitude of new functionalities. It was the first version to offer a user interface with the now-familiar “ribbon” simplifying the user experience (familiar to other Microsoft Office applications). It brought improved business intelligence capabilities with integration to SQL Server Reporting Services (SSRS), allowing users to extract actionable insights from their data. The 2010 version expanded on social collaboration with features like tags, notes, and the My Site personalisation, changes that really encapsulated the growing need for more connected workplace environments. Finally, one new component that I remember with “fun” memories was the introduction of Sandboxed Solutions for safer deployment of custom code and improved APIs for developers. The migration to SharePoint 2010 was a significant undertaking. It required not just technical infrastructure upgrades but also a shift in organisational culture to embrace the new features fully. Deployment challenges included ensuring hardware compatibility, as the system requirements were more demanding. Licensing models began to shift slightly towards operational expenditure especially with the introduction of Software Assurance and other subscription-based models. Migration Challenges: SharePoint 2003 to 2010 Migrating between these versions was a complex process with a plethora of challenges. Upgrading from SharePoint 2003 to SharePoint 2007 often required a complete overhaul of the existing infrastructure. The shift from 32-bit to 64-bit architecture in SharePoint 2010 added another layer of complexity for organisations making the transition. Each version shift required a substantial re-evaluation of existing and required infrastructure and often demanded a multi-step upgrade process, particularly for environments that jumped across multiple versions. The in-place upgrade paths and database attach methods at that time often meant downtime for businesses and a need for skilled IT resources to manage compatibility issues. Key challenges included: Data Integrity: Ensuring that all documents, lists, and libraries migrated without loss or corruption. Customisations: Redeveloping custom solutions and web parts to be compatible with the new version. Downtime Management: Planning migrations to minimise impact on business operations. Training: Updating IT staff and end-users on new features and interfaces. Deployment and Design: Crafting On-Premises Farms The challenge was not just about upgrading versions; it was also about infrastructure. Building a robust on-premises farm required planning. SharePoint needed to work seamlessly with Active Directory Domain Services (ADDS), SQL Server for its databases, Exchange for integration with mail capabilities, and even SQL Server Reporting Services (SSRS) for business intelligence. Architecting these environments to be scalable, reliable, and high-performing meant careful allocation of hardware, storage, and network resources. Building on-premises server farms was a meticulous process. It involved: Planning the Architecture: Determining the number of servers, their roles (e.g., web front-end, application server, database server), and how they would interact. Infrastructure Setup: Active Directory Domain Services (AD DS) for authentication and user management. SQL Server as the backbone for SharePoint databases, requiring optimisation for performance and reliability. Exchange Server integration for email alerts and messaging. SQL Server Reporting Services and PerformancePoint Services for business intelligence and reporting functionalities. Microsoft Office Integration ensuring seamless interaction between SharePoint and Microsoft Office desktop applications. Deployment of SharePoint: Installing SharePoint on the configured servers, applying necessary patches, and configuring required services. Development and Customisation: Creating custom solutions using SharePoint Designer and Visual Studio, developing web parts, workflows, and integration with other systems. Testing and Optimisation: Rigorous testing to ensure performance, security, and reliability before going live. Development, Licensing, and Cost Considerations Development and deployment on these versions involved complex customisation—custom workflows, web parts, and extensive use of Visual Studio to build tailor-made solutions. The licensing model was, of course, different from today’s Operational Expenditure (OpEx) approach of the cloud. Back then, businesses were very much