SharePoint

From Wikipedia, the free encyclopedia
  (Redirected from SharePoint 2010)
Jump to: navigation, search
SharePoint
SharePoint logo 2013.png
Microsoft SharePoint 2010 Foundation.png
SharePoint 2010 web interface
Developer(s) Microsoft Corporation
Initial release 2001; 13 years ago (2001)
Stable release 2013 SP1 / April 22, 2014; 4 months ago (2014-04-22)
Development status Active
Operating system Windows Server 2008 R2 and Windows Server 2012[1]
Platform x64 / ASP.net 4.5
Available in Arabic, Basque, Bulgarian, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, Galician, German, Greek, Hebrew, Hindi, Hungarian, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Norwegian (Bokmål), Polish, Portuguese, Romanian, Russian, Serbian (Latin), Slovak, Slovenian, South Africa, Spanish, Swedish, Thai, Turkish and Ukrainian[2]
Type Content Management Systems
License Proprietary software
SharePoint Foundation: Freeware
Other editions: Trialware
Website sharepoint.microsoft.com

SharePoint is a web application framework and platform developed by Microsoft. First launched in 2001,[3] SharePoint integrates intranet, content management and document management, but recent versions have broader capabilities.[4]

SharePoint comprises a multipurpose set of Web technologies backed by a common technical infrastructure. By default, SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite. The web tools are intended for non-technical users. SharePoint can provide intranet portals, document & file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence.[5] It also has system integration, process integration, and workflow automation capabilities.

Enterprise application software (e.g. ERP or CRM packages) often provide some SharePoint integration capability, and SharePoint also incorporates a complete development stack based on web technologies and standards-based APIs. As an application platform, SharePoint provides central management, governance, and security controls for implementation of these requirements.[6] The SharePoint platform integrates directly into IIS - enabling bulk management, scaling, and provisioning of servers, as is often required by large organizations or cloud hosting providers.

According to Microsoft, SharePoint is used by 78% of Fortune 500 companies.[7] Between 2006 and 2011, Microsoft sold over 36.5 million user licenses.[citation needed] Microsoft has two versions of SharePoint available at no cost, but it sells premium editions with additional functionality, and provides a cloud service edition as part of their Office 365 platform (previously BPOS). The product is also sold through a cloud model by many third-party vendors.[citation needed]

The SharePoint Wheel[edit]

In Microsoft advertising material the "SharePoint Wheel" describes what they consider the SharePoint's tools can facilitate inside organizations. The wheel refers to six outcomes:[6]

  • Sites: A site is a contextual work environment. Once SharePoint is configured, these sites can be created without any requirement for specialized knowledge. A context for a site may be organization-wide, or it may be specific to an individual team or group.
  • Communities: A community is a place for group communication. Communities can occur around any context, and typically develop around either shared knowledge, or shared activities (such as collaboration).
  • Content: SharePoint provides document management and storage for work items.
  • Search: Look for relevant communities, content, people, or sites: search is based on keywords, refinement, and content analysis.
  • Insights: Information from any part of the organization can be surfaced inside useful contexts, providing information that can improve effectiveness.
  • Composites: SharePoint enables no-code integration of data, documents and processes to provide composite applications ("mash-ups" based on internal data).

Applications[edit]

The most common uses of SharePoint include:

Intranet portals[edit]

Main article: Intranet portal

A SharePoint intranet or intranet portal is a way to centralize access to enterprise information and applications on a corporate network. It is a tool that helps a company manage its data, applications and information more easily. Microsoft claims that this has organizational benefits such as increased employee engagement, centralizing process management, reducing new staff on-boarding costs, and providing the means to capture and share tacit knowledge (e.g. via tools such as wikis/blogs).

Enterprise content and document management[edit]

SharePoint is often used to store and track electronic documents or images of paper documents. It is usually also capable of keeping track of the different versions created by different users. In addition to being a platform for digital record management systems that meet government and industry compliance standards, SharePoint also provides the benefit of a central location for storing and collaborating on documents, which can significantly reduce emails and duplicated work in an organization.

Extranet portal[edit]

Main article: Extranet

SharePoint can be used to provide password-protected, web-facing access to people outside an organization. Organizations often use functionality like this to integrate third parties into supply chain or business processes, or to provide a shared collaboration environment.[8]

SharePoint provides an Alternative Access Mapping, or AAM, which allows the same 'site' to be surfaced via a number of different URLs, each URL can have its own authentication technology allowing the same site to be both an intranet on one network while an extranet to outside users.

Internet sites[edit]

Using the 'Publishing' features, SharePoint can be used to manage larger public websites.[8]

Software framework[edit]

Main article: Software framework

SharePoint is built upon the ASP.Net framework and provides an additional layer of services and codebase to greatly reduce the amount of custom development required to provide a working application.[9] It may also be referred to as a web application framework.

Configuration and customization[edit]

Web-based configuration[edit]

SharePoint offers a ribbon user-interface that is similar to Microsoft Office 2007 and later. This interface provides a general user interface for manipulating data, page editing ability, and the ability to add functionality to sites.

  • Manipulate content in lists & libraries, pages and sites.
  • Copy, create, delete, or rename lists & libraries, pages, sites and web-parts
  • Manage user permissions, and view document/page version histories
  • Manage definitions and properties of lists & libraries, pages, sites and web-parts and many others[10]

SharePoint Designer[edit]

Main article: SharePoint Designer
  • The SharePoint 'Client Object Model' (available for JavaScript, Silverlight, and .NET), and REST/SOAP APIs can be referenced from within a custom page or feature.[11]
  • 'Sand-boxed' plugins can be uploaded by any end-user who has been granted permission. These are security-restricted, and can be governed at multiple levels (including resource consumption management). In multi-tenant cloud environments, these are the only customizations that are typically allowed.
  • Farm features are typically fully trusted code that need to be installed at a farm-level.
  • Service applications — It is possible to integrate directly into the SharePoint SOA bus, at a farm level.

Customizations may be surfaced via

  • Application-to-application integration with SharePoint
  • Extensions to SharePoint functionality (e.g. custom workflow actions)
  • 'Web Parts' (also known as "portlets", "widgets", or "gadgets") that provide new functionality when added to a page
  • Pages/sites or page/site templates[11]

Core functionality[edit]

Sites[edit]

A SharePoint Site is a collection of pages, site templates, lists, and libraries configured for the purpose of achieving an express goal. A site may contain sub-sites, and those sites may contain further sub-sites. Typically, sites need to be created from scratch, but sites can also be created according to packaged functionality. Examples of Site templates in SharePoint include: blogs, collaboration (team) sites, documents, and meetings.

Lists and libraries[edit]

Lists and libraries have the same properties. This could be considered similar to a database table. For instance, you can have a list of links called "my links", where each item has a URL, a name, and a description.[citation needed]

Lists have many features such as workflows, item-level or list-level permission, version history tracking, multiple content-types, external data sources and many more features. Some of these features depend on the version of SharePoint that is installed.[citation needed]

SharePoint supports the creation of multiple views of a list or library, including Gantt chart and calendar views. Views can define columns to show rankings, aggregation and establish criteria for inclusion in the list. Views can be personal or distributed to a group of users.[citation needed]

From 2007 on, lists also support item (document or record) level security permissions, where each list item can have a unique permission level. This feature can cause problems in viewing large lists and Microsoft recommends that for 2007 a list have no more than 1,000 unique permissions defined, and in 2010 that limit is 5,000.[citation needed]

A Library is a list where each item in the list refers to a file that is stored in SharePoint. Libraries have all the same behaviors as lists, but because libraries contain files, they have extra features. One of these is the ability to be opened and modified through a compatible WebDAV client (e.g. Windows Explorer).

Microsoft SharePoint comes with some pre-defined list and library definitions. These include: Announcement Lists, Blogs, Contacts, Discussion Boards, Document Libraries, External Content (BCS) lists, Pages, Surveys, and Tasks.[citation needed]

Some of these pre-defined lists have additional integration. For example, lists based on the contact content-type, and lists created using the calendar list template can be synced directly with Microsoft Outlook.[citation needed]

Web-parts[edit]

Web-parts are sections that can be inserted into Pages in SharePoint sites. These sections are UI Widgets whose typical uses are

Web-parts based on completely custom code can be built in Microsoft Visual Studio 2010 and uploaded by end-users to SharePoint as packaged, sandboxed features. Due to the prevalence of SharePoint, third-party vendors often provide SharePoint web-parts for intranet sites.

Web-parts also support connections to other web-parts on the page, providing the ability to construct relatively complex pages without the need to build additional code.

SharePoint web-parts were formerly implemented separately from ASP.NET web-parts, but as of SharePoint 2007, SharePoint's web-parts are now based on ASP.NET's.

Pages[edit]

SharePoint provides three primary page content-types:

  • Wiki page
  • Web-part page
  • Publishing pages

In newer SharePoint versions, the default page type is wiki page, which enables free-form editing access from the ribbon toolbar. Users can also insert web-parts into any page type.

Search[edit]

SharePoint Foundation contains a limited search engine. Microsoft produces a free product called Microsoft Search Server Express to complement SharePoint Foundation. Different SharePoint search versions offer different features, including the ability to search within documents and — except in cloud environments — across external data sources (such as file systems). You can read a SharePoint Enterprise Search features deep comparison.[12]

Compliance, standards and integration[edit]

  • SharePoint integrates with Microsoft Office 2007 and 2010. "Microsoft Office SharePoint Server 2007" (MOSS 2007), the previous version of SharePoint, was considered part of the Microsoft Office Suite.
  • SharePoint uses Microsoft's OpenXML document standard for integration with Microsoft Office. Document metadata is also stored using this format.
  • SharePoint 2010 provides various application programming interfaces (APIs: client-side, server-side, JavaScript) and REST, SOAP and OData based interfaces.
  • SharePoint 2010 can be used to achieve compliance with many document retention, record management, document ID and discovery laws.[13]
  • SharePoint 2007 and 2010 are compatible with CMIS - the Content Management Interoperability Standard, using Microsoft's CMIS Connector.
  • SharePoint 2010 by default produces valid XHTML 1.0 that is compliant with WCAG 2.0 AA accessibility standards.
  • SharePoint 2010's server control output is primarily driven by XSLT and can be modified using the proprietary SharePoint Designer tool, or with any text editor.
  • SharePoint 2010 can use claims-based authentication, relying on SAML tokens for security assertions. SharePoint provides an open authentication plugin model.
  • SharePoint 2013 adds support for XLIFF to support the localization of content in SharePoint.[14] Also added support for AppFabric.[15]

Architecture[edit]

The SharePoint platform is a flexible, n-tier service-oriented architecture (SOA). It can be scaled down to operate entirely from one machine, or scaled up to be managed across hundreds of machines.[16]

Farms[edit]

A SharePoint farm is a logical grouping of SharePoint servers that share common resources.[17] A farm typically operates stand-alone, but can also subscribe to functions from another farm, or provide functions to another farm. Each farm has its own central configuration database, which is managed through either a PowerShell interface, or a Central Administration website (which relies partly on PowerShell's infrastructure). Each server in the farm is able to directly interface with the central configuration database. Servers use this to configure services (e.g. IIS, windows features, database connections) to match the requirements of the farm, and to report server health issues, resource allocation issues, etc.

Web applications[edit]

Web Applications (WAs) are top-level containers for content in a SharePoint farm, and are typically the interface through which a user interacts with SharePoint. A web application is associated with a set of access mappings or URLs defined in the SharePoint central management console, then automatically replicated into the IIS configuration of every server configured in the farm. WAs are typically independent of each other, have their own application pools, and can be restarted independently in Internet Information Services.[16]

Site collections[edit]

A site collection is used to provide a grouping of 'SharePoint Sites'. Each web application typically has at least one site collection. Site collections may be associated with their own content databases, or they may share a content database with other site collections in the same web application.[16] A site collection may contain one or more sites. A site collection is a group of sites that are functionally, navigationally, and administratively related to one another.

Service applications[edit]

Service Applications (SAs) provide granular pieces of SharePoint functionality to other web and service applications in the farm. Examples of service applications include the User Profile Sync service, and the Search Indexing service. An SA can be turned off, exist on one server, or be load-balanced across many servers in a farm. SAs are designed to be as independent as possible, so that — depending on the SA — restarting an SA, experiencing an SA failure, or misconfiguring an SA may not necessarily prevent the farm from operating. Each SA enabled on the farm typically has its own process that requires a certain amount of RAM to operate, and typically also has its own configuration database and Active Directory (AD) service account. SharePoint Server and SharePoint Enterprise include all the SharePoint Foundation SAs, as well as additional SAs.[16]

Administration and security[edit]

The modular nature of SharePoint's architecture enables a secure 'least-privileges' execution permission best practice.[18]

SharePoint Central Administration (the CA) is a web application that typically exists on a single server in the farm, however it is also able to be deployed for redundancy to multiple servers.[16] This application provides a complete centralized management interface for web & service applications in the SharePoint farm, including AD account management for web & service applications. In the event of the failure of the CA, Windows PowerShell is typically used on the CA server to reconfigure the farm.

The structure of the SharePoint platform enables multiple WAs to exist on a single farm. In a shared (cloud) hosting environment, owners of these WAs may require their own management console. The SharePoint 'Tenant Administration' (TA) is an optional web application used by web application owners to manage how their web application interacts with the shared resources in the farm.[16]

SharePoint editions[edit]

A summary of the SharePoint versions can be found here.[19]

Microsoft SharePoint Foundation[edit]

The underlying technology for all SharePoint sites. SharePoint Foundation is available for free on-premises deployment and was called Windows SharePoint Services in previous versions. You can use SharePoint Foundation to quickly create many types of sites where you can collaborate on Web pages, documents, lists, calendars, and data. It is dependent on various hardware/software requirements, including a proper license for Microsoft Windows Server.[20] It contains much of the core functionality and architecture drawn on by the commercial version of the package.[21] Downloading SharePoint Foundation 2010 requires a mandatory registration,[22] but this has been omitted for the 2013 version.[23]

Microsoft Search Server Express[edit]

Microsoft's Search Server Express is a free, modified distribution of SharePoint 2010 Foundation. The installer for this package installs SharePoint 2010 Foundation, plus a limited subset of enterprise search features and enterprise document management features typically only found in paid versions of SharePoint.

Microsoft SharePoint Standard[edit]

Microsoft SharePoint Standard builds on the Microsoft SharePoint Foundation in a few key product areas.

Sites: Audience targeting, governance tools, Secure store service, web analytics functionality[24]

Communities: 'MySites' (personal profiles including skills management, and search tools), enterprise wikis, organization hierarchy browser, tags and notes[25]

Content: Improved tooling and compliance for document & record management, managed metadata, word automation services, content type management[26]

Search: Better search results, search customization abilities, mobile search, 'Did you mean?', OS search integration, Faceted Search, and metadata/relevancy/date/location based refinement options[27]

Composites: Pre-built workflow templates, BCS profile pages[28]

Note: some search features are available in Search Server Express - a no-cost add-in for Microsoft SharePoint Foundation.

SharePoint Standard licensing includes a CAL (client access license) component and a server fee. SharePoint Standard may also be licensed through a cloud model.

It is possible to upgrade a SharePoint farm from Foundation to Standard.[29] The product is equivalent to Microsoft Office SharePoint Server (MOSS) 2007.

Microsoft SharePoint Enterprise[edit]

Built upon SharePoint Standard, Microsoft SharePoint Enterprise features can be unlocked simply by providing an additional license key. The product is the equivalent to MOSS 2007 Enterprise.

Extra features in SharePoint Enterprise includes:

  • Search thumbnails and previews, rich web indexing, better search results
  • BI Integration, Dashboards, and Business Data surfacing
  • PowerPivot
  • PerformancePoint
  • Microsoft Office Access, Visio, Excel, and InfoPath Forms services
  • SharePoint Enterprise Search extensions[30]

SharePoint Enterprise licensing includes a CAL component and a server fee that must be purchased in addition to SharePoint Server licensing. SharePoint Enterprise may also be licensed through a cloud model.

Office 365 - SharePoint Online[edit]

A cloud-based service, hosted by Microsoft, for businesses of all sizes. Instead of installing and deploying SharePoint Server on premises, any business can now simply subscribe to a service offering such as Office 365 and their employees can use SharePoint Online for creating sites to share documents and information with colleagues, partners, and customers. Microsoft Office 365- SharePoint has inserted many new features in its latest Version.

Related products[edit]

Product name Description Status
Search Server An enterprise search platform based on the search capabilities of SharePoint. A freeware Express edition was once available. Discontinued
FAST Search Server 2010 for SharePoint Search product that can be implemented on SharePoint Foundation Discontinued [31][32][33]
SharePoint Designer A free, client-side customization and configuration tool for SharePoint Active
Office Web Apps Web-based, online, cross-browser compatible versions of Excel, Word, PowerPoint and OneNote. These integrate directly into SharePoint's document management functionality. Active
Project Server An extension to SharePoint providing integration with Microsoft Project Active
InfoPath Forms Services Allows InfoPath forms to be hosted in a SharePoint web site and served via web browser Discontinued
Excel Services A server technology included in SharePoint 2010 and SharePoint 2007 that enables users to load, calculate, and display Excel 2010 workbooks on SharePoint Server 2010 Active
SharePoint Workspace A client-side document management synchronization component included in Microsoft Office 2010 (Professional Plus edition and higher). Discontinued
Team Foundation Server A free download of core SharePoint functionality, without all of the Server functionality[further explanation needed] Active

History[edit]

Origins[edit]

SharePoint evolved from projects codenamed "Office Server” and “Tahoe” during the Office XP development cycle.

“Office Server” evolved out of the FrontPage and Office Server Extensions and “Team Pages”. It targeted simple, bottom-up collaboration.

“Tahoe”, built on shared technology with Exchange and the “Digital Dashboard”, targeted top-down portals, search and document management.[34]

Versions[edit]

Successive versions (in chronological order):

  • Microsoft SharePoint Portal Server 2001
  • Microsoft SharePoint Team Services (2002)
  • Windows SharePoint Services 2.0 (free license) - Microsoft SharePoint Portal Server 2003 (commercial release)
  • Windows SharePoint Services 3.0 (free license) - plus Microsoft Office SharePoint Server 2007 (commercial extension)[3]
  • Microsoft SharePoint Foundation 2010 (free) - plus Microsoft SharePoint Server 2010 (commercial extension for Foundation), and SharePoint Enterprise 2010 (commercial extension for Server)
  • Microsoft SharePoint Foundation 2013 (free) - plus Microsoft SharePoint Server 2013 (extension on top of Foundation) SharePoint 2013 has been available to Microsoft volume licensees and TechNet and MSDN subscribers since late 2012

A next SharePoint release is announced for 2015, but Microsoft will go "Cloud First". Jeff Teper, the Corporate Vice President of Office Service and Servers group at Microsoft, noted: "Our server releases will include some, but not all, of the experience you saw today due to the computational power and integrated aspects that only come with Office 365."[35]

Changes in SharePoint Foundation 2010[edit]

Changes in end-user functionality added in the 2010 version of SharePoint include:

Major server-side or developer changes include:

Additional changes exist in paid/advanced versions of SharePoint 2010.

Changes in SharePoint 2013[edit]

System requirements[edit]

The following are the various requirements for deploying Microsoft SharePoint 2010.[37]

Server hardware[edit]

Processor 64-bit, four cores
RAM
  • 8 GB for developer evaluation use
  • At least 24 GB for production use in one server or multiple server farm
Hard disk 80 GB for system drive, varies for production environment depending on application size

Server software[edit]

Operating system
  • Windows Server 2012 (64-bit) Standard, Data Center, or Web Server
  • Windows Server 2008 R2 (64-bit) Standard, Enterprise, Data Center, or Web Server
  • Windows 7 (64-bit) or Windows Vista (64-bit) (for test and development purposes only, requires package modification)[38]
Database server
  • Microsoft SQL Server 2012 (64-bit) With Service Pack 1
  • Microsoft SQL Server 2008 (64-bit) R2
  • Microsoft SQL Server 2008 (64-bit) with Service Pack 1 and Cumulative Update 2 (Reporting Services Integration requires Cumulative Update 8)
  • Microsoft SQL Server 2005 (64-bit) SP3

Versions of Microsoft SQL Server Express are also supported but only up to 4 GB for a database

Web browser support[edit]

Supported web browsers:[39]

IE 6 is not supported for SharePoint 2010 or later, but works with SharePoint up to 2007. IE 8 and below has issues with SharePoint 2013 and below. Some functionality in SharePoint 2013 requires ActiveX controls, which restricts browser versions that are not Internet Explorer with 32 bit. Internet Explorer 10 must be in desktop mode.

Open source equivalents[edit]

Some potential SharePoint users arrive from open source world and initially struggle to understand SharePoint in terms of related open source software they used previously. "SharePoint" refers to a large stack of Microsoft software, not a single program, and does not translate to a single system in open source world. However many parts of the stack have equivalents. The low-level frameworks map to web libraries such as Django and Rails while the higher level platforms (e.g. CMS, wikis, forums) map to systems using those libraries such as django-cms, django-wiki, django-blogs and similar Rails-using libraries. Other open source tools produce only high level aspects of the stack such as standalone wiki (e.g. MediaWiki), CMS (e.g. Drupal, Alfresco), or social network (e.g. Diaspora) software.

See also[edit]

References[edit]

  1. ^ "Hardware and software requirements for SharePoint 2013". Microsoft TechNet. Microsoft Corporation. January 29, 2013. Retrieved 27 March 2013. 
  2. ^ "Language Offerings for SharePoint 2010 Products". Microsoft SharePoint Team Blog. Microsoft Corporation. Retrieved 13 August 2011. 
  3. ^ a b Oleson, Joel (28 December 2007). "7 Years of SharePoint - A History Lesson". Joel Oleson's Blog - SharePoint Land (Microsoft Corporation). MSDN Blogs. Retrieved 13 August 2011. 
  4. ^ Gilbert, Mark R.; Shegda, Karen M.; Phifer, Gene; Mann, Jeffrey (19 October 2009). "SharePoint 2010 Is Poised for Broader Enterprise Adoption". Gartner. Retrieved 13 August 2011. 
  5. ^ What is sharepoint?
  6. ^ a b "SharePoint 2010 Overview Evaluation Guide" (PDF). Microsoft Corporation. 7 May 2010. Retrieved 13 August 2011. 
  7. ^ "Microsoft market research article". Microsoft Corporation. 7 April 2011. Retrieved 15 May 2013. 
  8. ^ a b "Capabilities - Sites". Product Information. Microsoft Corporation. Retrieved 13 August 2011. 
  9. ^ SharePoint 2013 development overview. Msdn.microsoft.com (2012-07-16). Retrieved on 2014-02-22.
  10. ^ "Video: Ribbon highlights In SharePoint 2010". Microsoft Office website (Microsoft). 30 November 2009. Retrieved 13 August 2010. 
  11. ^ a b "SharePoint 2010 for Developers". SharePoint website (Microsoft Corporation). Retrieved 13 August 2011. 
  12. ^ Quinto Zamora, José (February 2012). "SharePoint 2010 Enterprise Search Features: From Search Express to FAST". The SolidQ Journal. 
  13. ^ McNelis, Zack. "SharePoint 2010 – Compliance Everywhere". Technet Blogs - Zach McNelis. Microsoft. Retrieved 13 August 2011. 
  14. ^ Kate Kelly, Jesus Barrera Ramos, and Marcus Reid. October 16, 2012. XLIFF in SharePoint 2013. Presentation at FEISGILTT 2012. <http://www.localizationworld.com/lwseattle2012/feisgiltt/FEISGILTT_2012_Program.pdf>
  15. ^ <http://technet.microsoft.com/en-us/library/jj219613.aspx>
  16. ^ a b c d e f "Logical architecture components (SharePoint Server 2010)". Technet. Microsoft. Retrieved 13 August 2011. 
  17. ^ "MSDN Conceptual Overview". 
  18. ^ Holme, Dan. "Least Privilege Service Accounts for SharePoint 2010". SharePoint Pro Magazine. Penton Media. Retrieved 13 August 2011. 
  19. ^ "What is SharePoint". Microsoft.com. Microsoft Corporation. Retrieved 26 March 2013. 
  20. ^ "Licensing Details". Microsoft.com. Microsoft Corporation. Retrieved 13 August 2011. 
  21. ^ "Compare SharePoint Editions". Microsoft.com. Microsoft Corporation. Retrieved 13 August 2011. 
  22. ^ "Microsoft SharePoint Foundation 2010". Microsoft Download Center. Microsoft Corporation. 10 May 2010. Retrieved 13 August 2011. 
  23. ^ "Microsoft SharePoint Foundation 2013". Microsoft.com. Microsoft Corporation. Retrieved 25 June 2013. 
  24. ^ "SharePoint 2010 Editions Comparison -Sites". Microsoft SharePoint 2010 Marketing Website. Microsoft. Retrieved 13 August 2011. 
  25. ^ "SharePoint 2010 Editions Comparison - Communities". Microsoft SharePoint 2010 Marketing Website. Microsoft. Retrieved 13 August 2011. 
  26. ^ "SharePoint 2010 Editions Comparison - Content". Microsoft SharePoint 2010 Marketing Website. Microsoft. Retrieved 13 August 2011. 
  27. ^ "SharePoint 2010 Editions Comparison-earch". Microsoft SharePoint 2010 Marketing Website. Microsoft. Retrieved 13 August 2011. 
  28. ^ "SharePoint 2010 Editions Comparison -Composites". Microsoft SharePoint 2010 Marketing Website. Microsoft. Retrieved 13 August 2011. 
  29. ^ "Upgrade from SharePoint Foundation 2010 to SharePoint Server 2010". Technet.microsoft.com. 2010-06-10. Retrieved 2013-06-15. 
  30. ^ "SharePoint 2010 Editions Comparison". Microsoft SharePoint 2010 Marketing Website. Microsoft. Retrieved 13 August 2011. 
  31. ^ "FAST Solution Center". Support. Microsoft. Retrieved 2 February 2014. 
  32. ^ "FAST Search Server 2010 for SharePoint". Microsoft TechNet. Microsoft. 12 May 2010. Retrieved 2 February 2014. 
  33. ^ "Manupatra Information Solutions". Microsoft Case Study. Microsoft. 17 February 2013. Retrieved 2 February 2014. 
  34. ^ "Sharepoint History". MSDN. Microsoft corporation. 5 October 2009. Retrieved 2 December 2010. 
  35. ^ Jeff, Teper. "Technology is enabling new ways of working". Microsoft Office Blogs. Microsoft Corporation. Retrieved 17 June 2014. 
  36. ^ How-To Videos - Microsoft Office. Microsoft.com. Retrieved on 2014-02-22.
  37. ^ "Hardware and software requirements (SharePoint Server 2010)". TechNet. Microsoft Corporation. 8 July 2010. Retrieved 3 September 2011. 
  38. ^ "Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008". Microsoft Developer Network. Microsoft. May 2010. 
  39. ^ "Plan browser support (SharePoint Server 2010)". TechNet. Microsoft. 8 May 2012. 

External links[edit]