SharePoint 2013

SharePoint 2010

MOSS 2007
Web/Application Server(s)
Processor 64 bit, 4 Cores 64 bit, 4 Cores Dual processors that are each 3 GHz or faster
RAM

8 GB for developer or evaluation use

12 GB for Production use in a single server or multiple server farm

4 GB for developer or evaluation use

8 GB for Production use in a single server or multiple server farm

2 GB for developer or evaluation use

6-8 GB for Production use in a single server or multiple server farm
Hard disk

80 GB for system drive (C:)

20 GB for Logs (L:)

10 GB for Index (I:)

80 GB for system drive (C:)

20 GB for Logs (L:)

10 GB for Index (I:)

80 GB for system drive (C:)

20 GB for Logs (L:)

10 GB for Index (I:)
Drive(s) C:, L:, I: C:, L:, I: C:, L:, I:
Operating System The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Standard or Datacenter The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2; the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server; or the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server. If you are running Windows Server 2008 with SP1, the Microsoft SharePoint Products Preparation Tool installs Windows Server 2008 SP2 The initial release of Windows SharePoint Services 3.0 runs on Windows Server 2003 with SP1.We recommend that you apply all critical updates and Service Packs when You use Windows Server 2003, Standard, Enterprise, Datacenter and Web Editions.The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2; the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server; or the 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, Data Center, or Web Server.
.Net Framework 4.5 3.5 SP1 3.0 (ASP.NET 2.0 is enabled)
PowerShell 3.0 2.0 STSADM
IIS 7.5 7.0 7.0, 6.0
Virtualization Recommended Yes Yes Yes
32 Bit No Yes Yes
64 Bit Yes Yes No
Installed by the preparation tool
  • Microsoft .NET Framework version 4.5
  • Windows Management Framework 3.0
  • Application Server Role, Web Server (IIS) Role
  • Microsoft SQL Server 2008 R2 SP1 Native Client
  • Windows Identity Foundation (KB974405)
  • Microsoft Sync Framework Runtime v1.0 SP1 (x64)
  • Windows Identity Extensions
  • Microsoft Information Protection and Control Client
  • Microsoft WCF Data Services 5.0
  • Windows Server AppFabric
  • Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)
  • Web Server (IIS) role
  • Application Server role
  • Microsoft .NET Framework version 3.5 SP1
  • SQL Server 2008 Express with SP1
  • Microsoft Sync Framework Runtime v1.0 (x64)
  • Microsoft Filter Pack 2.0
  • Microsoft Chart Controls for the Microsoft .NET Framework 3.5
  • Windows PowerShell 2.0
  • SQL Server 2008 Native Client
  • Microsoft SQL Server 2008 Analysis Services ADOMD.NET
  • ADO.NET Data Services Update for .NET Framework 3.5 SP1
  • A hotfix for the .NET Framework 3.5 SP1 that provides a method to support token authentication without transport security or message encryption in WCF.
  • Windows Identity Foundation (WIF)
  
Single Server Installation Processor:64 Bit, 4 CoresRAM: 24 GBHard disk: 80 GB Processor:64 Bit, 4 CoresRAM: 16 GBHard disk: 80 GB Processor: Dual processors that are each 3 GHz or fasterRAM: 4 GBHard disk: 80 GB
Download ServerFoundationSharePoint Designer  ServerFoundationSharePoint Designer (32 bit)SharePoint Designer (64 bit)  Server (X86)Server (X64)WSS 3.0SharePoint Designer
       
Database Server(s)
Processor

64-bit, four cores for small deployments

64-bit, eight cores for medium deployments

64-bit, four cores for small deployments

64-bit, eight cores for medium deployments

  
RAM

8 GB for small deployments

16 GB for medium deployments

8 GB for small deployments

16 GB for medium deployments

  
Hard disk 80 GB for system drive 80 GB for system drive 80 GB for system drive
Drive(s) C:, D:, I:, T:, E:, F: C:, D:, I:, T:, E:, F: C:, D:, I:, T:, E:, F:
Operating System The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Standard or Datacenter The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Standard or Datacenter  
SQL Server

The 64-bit edition of Microsoft SQL Server 2012 Service Pack 1.

The 64-bit edition of SQL Server 2008 R2 Service Pack 1

The 64-bit edition of Microsoft SQL Server 2012 Service Pack 1. (you must be running SharePoint Foundation 2010 SP1 or a later version of SharePoint Foundation 2010)

The 64-bit edition of SQL Server 2008 R2

The 64-bit edition of SQL Server 2008 R2 Service Pack 1 and CU2, CU5 or later

The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3)

  
Download

SQL 2012 SP1:      Download

SQL 2008 R2 SP2: Download

SQL 2008 SP3:      Download

SQL 2005 SP3:      Download
       
Browser (Minimum Supported)
IE 8.0 7.0 (32 bit) (64 bit- supported with limitation) 6.0
Google Chrome Latest Released Version No No
Mozilla Firefox Latest Released Version No No
Safari Latest Released Version 4.04 (with Silverlight 3.0) No
       
Internet Protocol (IP) Support
  Supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6). Supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6).  
Supports
  • IPv4 only
  • Mixed IPv4 and IPv6
  • IPv6 only
  • Pure IPv4 environment
  • Mixed IPv4 and IPv6 environment
  • Pure IPv6 environment
  • Pure IPv4 environment
  • Mixed IPv4 and IPv6 environment
  • Pure IPv6 environment
NotesTo determine what version is being used, you can use the IPConfig.exe tool. By default, the IPv6 protocol and the IPv4 protocol are both installed and enabled in Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008. When both IPv4 and IPv6 are enabled, IPv6 is preferred over IPv4 when you are using names and Domain Name System (DNS) name query responses contain both types of addresses. Additionally, you can remove the IPv4 protocol so that the computer runs only IPv6. By default, the IPv6 protocol and the IPv4 protocol are both installed and enabled in Windows Server 2008 and Windows Server 2008 R2. When both IPv4 and IPv6 are enabled, IPv6 is given preference over IPv4. Additionally, you can remove the IPv4 protocol so that the computer runs IPv6 exclusively. Windows Server 2008: By default, the IPv6 protocol and the IPv4 protocol are both installed and enabled. When both IPv4 and IPv6 are enabled, IPv6 is given preference over IPv4. Additionally, you can remove the IPv4 protocol so that the computer runs IPv6 exclusively. Windows Server 2003: By default, the IPv6 protocol is not installed. However, it can be added.
Important Considerations
  • For any computer that is authenticated by using a domain controller and is only running IPv6 in a SharePoint 2013 environment, the domain controller must be running Windows Server 2012, Windows Server 2008, or Windows Server 2008 R2. Ensure that you use the correct service pack and any additional software prerequisites
  • All versions of SQL Server supported for SharePoint 2013 also support IPv6.
  • When SharePoint 2013 uses the IPv6 protocol, all end-user URLs must be based on DNS names with AAAA records.
  • Browsing to SharePoint URLs that use IPv6 literal addresses is not supported.
  • When specifying an outbound Simple Mail Transfer Protocol (SMTP) server, SharePoint does not support the configuration of IPv6 literal addresses. The recommendation is to specify a DNS name for the SMTP server, which can resolve to an IPv4 address, an IPv6 address, or both. If you do not have a DNS name for the SMTP server and must supply an IPv6 address, you can configure the corresponding ipv6-literal.net name for the address.
  • Some SharePoint features or components integrate with cloud services—such as SharePoint Help, SharePoint Translation Service, and SharePoint apps that use the Windows Azure Access Control Service (ACS)—which might not yet be IPv6-capable. Therefore, make sure that that your SharePoint servers are IPv4-capable, which includes both IPv4-only and mixed IPv4 and IPv6 environments, until all of the SharePoint-dependent cloud services become IPv6-capable.
  • For any computer that is authenticated by using a domain controller and is only running IPv6 within a SharePoint 2010 Products environment, the domain controller must be running Windows Server 2008 or Windows Server 2008 R2. Ensure that you use the correct service pack and any additional software prerequisites.
  • All versions of Microsoft SQL Server supported for SharePoint 2010 Products also support IPv6.
  • In SharePoint 2010 Products, when using IPv6 protocol, all end-user Uniform Resource Locators (URLs) must be based on DNS names with AAAA records. Browsing to SharePoint URLs that use IPv6 literal addresses is not supported
  • IPV4

Windows Server 2003

You cannot uninstall the IPv4 protocol, and it is still the preferred protocol, even if IPv6 is installed.

  • IPV6

Windows Server 2008

For any computer that is authenticated by using a domain server and is only running IPv6 within a SharePoint Products and Technologies environment, the domain controller must be running Windows Server 2008. This is because certain domain services in Windows Server 2003 did not support IPv6. For a mixed IPv4 and IPv6 environment, both Windows Server 2003 and Windows Server 2008 are supported.

Microsoft SQL Server

SharePoint Product and Technologies use Microsoft SQL Server as a back-end database support. Therefore, if you need a pure IPv6 environment, you must make sure that you use a version of SQL Server 2005 or later versions. If you are installing SQL Server 2005 on Windows Server 2008, you must install SQL Server 2005 Service Pack 2 or later versions.

  • When in a SharePoint Products and Technologies environment, using any type of IPv6 protocol, all end-user Uniform Resource Locators (URL) must be based on DNS names with AAAA records.

For all installation scenarios, you must have sufficient hard disk space for the base installation and sufficient space for diagnostics such as logging, debugging, creating memory dumps, and so on.

For production use, you must also have additional free disk space for day-to-day operations.

In addition, maintain two times as much free space as you have RAM for production environments.

Hardware requirements—location of physical servers

All servers that belong to a server farm, including database servers, must physically reside in the same datacenter. Redundancy and failover between closely located data centers that are configured as a single farm (“stretched farm”) is not supported in SharePoint 2013.

Hardware and software requirements for other capabilities

SharePoint 2013

If you plan to use capabilities (BI, Project Server, eDiscovery etc…) that are offered through SharePoint 2013 or through other integration channels, such as SQL Server or Exchange Server, you also need to meet the hardware and software requirements that are specific to that capability.

* Need to evaluate depending on components planned to use.

Ref: http://www.khamis.net/blog/Lists/Posts/Post.aspx?ID=92

 

SharePoint 2010

Our definitions of small and medium deployments are those described in the “Reference Architectures” section in

Capacity management and sizing for SharePoint Server 2010

&

Storage and SQL Server capacity planning and configuration (SharePoint Server 2010).

 

Mobile device browsers in SharePoint 2013

SharePoint Server 2013 provides browser support for multiple mobile devices.

Windows Phone

  • Windows Phone 7.5 or later versions
  • Internet Explorer Mobile

IOS

  • 5.0 Or later versions
  • Safari

Important:

Office Web Apps full functionality is supported on iPad versions 2 and 3 using iOS 6.0 or later versions. Limited viewing and editing functionality is also supported on iPad versions 1, 2, 3 using iOS version 5.1.

Android

  • 4.0 Or later versions
  • Android Browser

….. WIP