Hardware & Software requirement’s, Browser Support for SharePoint (2013/2010/2007).

 

	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

SQL Build Version

How to determine the version and edition of SQL Server and its components.

It’s important to be able to determine SQL Server version number. DBA’s need to know what SQL Server version numbers they are supporting so that during patching windows, they can source and apply the correct patches or service packs.

This information is useful as a reference to what issues may be contained in a certain build that could affect production

Ways to determine SQL Server version number

1. “SELECT @@VERSION”

Connect to the instance of SQL Server and simply execute the below query:

SELECT @@VERSION

The output will look something like:

Microsoft SQL Server 2008 R2 (SP2) – 10.50.4270.0 (X64)   Nov 30 2012 17:11:43   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2)

This returns the version, processor architecture; build date of SQL Server and the operating system it is running on.

2. “XP_MSVER”

This one provides quite a lot of useful information about your SQL Server installation and server configuration

EXEC xp_msver

The output from my SQL Server 2008 R2 install:

3. “SELECT SERVERPROPERTY”

You run SELECT SERVERPROPERTY against your server and pass in some parameters to get back the information you want.

SELECT

SERVERPROPERTY (‘productversion’) AS ProductVersion,

SERVERPROPERTY (‘productlevel’) AS ProductLevel,

SERVERPROPERTY (‘edition’) AS ProductEdition

The output will look something like…

ProductVersion        ProductLevel          ProductEdition

——————– ——————– ——————————
10.50.4270.0                SP2                 Enterprise Edition (64-bit)

4. USE MANAGEMENT STUDIO (Client Tools)

You can access the Help menu in Management Studio and goto “About” to ascertain which SQL Server versions of the client tools you have installed on your workstation or SQL Server.

The SQL Versions Table:

SQL 2012:

Release	Product Version
SQL Server 2012   Service Pack 1	11.00.3000.00
SQL Server 2012 RTM	11.00.2100.60

How to obtain the latest service pack for SQL Server 2012.

SQL 2008 R2:

Release	Product version
SQL Server 2008 R2   Service Pack 2	10.50.4000.0
SQL Server 2008 R2   Service Pack 1	10.50.2500.0
SQL Server 2008 R2 RTM	10.50.1600.1

How to obtain the latest service pack for SQL Server 2008 R2.

SQL 2008:

Release	Product version
SQL Server 2008   Service Pack 3	10.00.5500.00
SQL Server 2008   Service Pack 2	10.00.4000.00
SQL Server 2008   Service Pack 1	10.00.2531.00
SQL Server 2008 RTM	10.00.1600.22

How to obtain the latest service pack for SQL Server 2008.

SQL 2005:

Release	Product version
SQL Server 2005   Service Pack 4	9.00.5000.00
SQL Server 2005   Service Pack 3	9.00.4035
SQL Server 2005   Service Pack 2	9.00.3042
SQL Server 2005   Service Pack 1	9.00.2047
SQL Server 2005 RTM	9.00.1399

How to obtain the latest service pack for SQL Server 2005.

SQL Server common build numbers and service packs

Note These tables use the following format and are ordered by the build number.

Build number or version

Version description, (KB number for   that update), release date

SQL Server 2012

11.0.3349.00	SP1 CU #3 (2812412) March 18,   2013
11.0.3339.00	SP1 CU #2 (2790947) January 21,   2013
11.0.3321.00	SP1 CU #1 (2765331) November 20,   2012
11.0.3000.00	SP1 RTW/PCU 1(2674319), November   07, 2012
11.0.2401.00	RTM CU #6 (2728897) February 18,   2013
11.0.2395.00	RTM CU #5 (2777772) Dec 17, 2012
11.0.2383.00	RTM CU #4 (2758687) October 15,   2012
11.0.2332.00	RTM CU #3 (2723749) August 31,   2012
11.0.2325.00	RTM CU #2 (2703275) June 18,   2012
11.0.2316.00	RTM CU #1 (2679368) April 12,   2012
11.0.2100.60	RTM – March 6, 2012

SQL Server 2008 R2

10.50.4276.00	SP2 CU #5 (2797460) February 18,   2013
10.50.4270.00	SP2 CU #4 (2777358) Dec 17, 2012
10.50.4266.00	SP2 CU #3 (2754552) October 15,   2012
10.50.4263.00	SP2 CU #2 (2740411) August 31,   2012
10.50.4260.00	SP2 CU #1 (2720425) July 24,   2012
10.50.2869.00	SP1 CU #11 (2812683) February   18, 2013
10.50.2868.00	SP1 CU #10 (2783135) Dec 17,   2012
10.50.2866.00	SP1 CU #9 (2756574) October 15,   2012
10.50.2822.00	SP1 CU #8 (2723743) August 31,   2012
10.50.2817.00	SP1 CU #7 (2703282) June 18,   2012
10.50.2811.00	SP1 CU #6 (2679367) Apr 16, 2012
10.50.2806.00	SP1 CU #5 (2659694) Feb 22, 2012
10.50.2796.00	SP1 CU #4 (2633146) Dec 19, 2011
10.50.2789.00	SP1 CU #3 (2591748) Oct 17, 2011
10.50.2772.00	SP1 CU #2 (2567714) Aug 15, 2011
10.50.2769.00	SP1 CU #1 (2544793) Jul 18, 2011
10.50.2500.0	SP1 RTW/PCU 1(2528583), July 12,   2011
10.50.1815.00	RTM CU #13 (2679366) Apr 16,   2012
10.50.1810.00	RTM CU #12 (2659692) Feb 21,   2012
10.50.1809.00	RTM CU #11 (2633145) Dec 19,   2011
10.50.1807.00	RTM CU #10 (2591746) Oct 17,   2011
10.50.1804.00	RTM CU #9 (2567713) Aug 15, 2011
10.50.1797.00	RTM CU #8 (2534352) June 20,   2011
10.50.1777.00	RTM CU #7 (2507770) Apr 18, 2011
10.50.1765.00	RTM CU #6 (2489376) Feb 21, 2011
10.50.1753.00	RTM CU #5 (2438347) Dec 20, 2010
10.50.1746.00	RTM CU #4 (2345451) Oct 18, 2010
10.50.1734.00	RTM CU #3 (2261464) Aug 16, 2010
10.50.1720.00	RTM CU #2 (2072493) Jun 21, 2010
10.50.1702.00	RTM CU #1 (981355) May 18, 2010
10.50.1617.00	GDR Security Update (2494088), June 21, 2011
10.50.1600.1	RTM – May 10, 2010

SQL Server 2008

10.00.5835.00	SP3 CU #10 (2814783) March 18,   2013
10.00.5829.00	SP3 CU #9 (2799883) January 21,   2013
10.00.5828.00	SP3 CU #8 (2771833) November 19,   2012
10.00.5794.00	SP3 CU #7 (2738350) September   17, 2012
10.00.5788.00	SP3 CU #6 (2715953) July 16,   2012
10.00.5785.00	SP3 CU #5 (2696626) May 21, 2012
10.00.5775.00	SP3 CU #4 (2673383) Mar 19, 2012
10.00.5770.00	SP3 CU #3 (2648098) Jan 16, 2012
10.00.5768.00	SP3 CU #2 (2633143) Nov 21, 2011
10.00.5766.00	SP3 CU #1 (2617146) Oct 17, 2011
10.00.5500.00	SP3 RTW / PCU 3 (2546951) Oct 6, 2011
10.00.4333.00	SP2 CU #11 (2715951) July 16,   2012
10.00.4332.00	SP2 CU #10 (2696625) May 21,   2012
10.00.4330.00	SP2 CU #9 (2673382) Mar 19, 2012
10.00.4326.00	SP2 CU #8 (2648096) Jan 16, 2012
10.00.4323.00	SP2 CU #7 (2617148) Nov 21, 2011
10.00.4321.00	SP2 CU #6 (2582285) Sep 19, 2011
10.00.4316.00	SP2 CU #5 (2555408) Jul 18, 2011
10.00.4285.00	SP2 CU #4 (2527180) May 16, 2011
10.00.4279.00	SP2 CU #3 (2498535) Mar 17, 2011
10.00.4272.00	SP2 CU #2 (2467239) Jan 17, 2011
10.00.4266.00	SP2 CU #1 ( 2289254) Nov 15,   2010
10.00.4064.00	GDR Security Update (2494089), June 14, 2011
10.00.4000.00	SP2 RTW / PCU 2 (2285068) Sep 29, 2010
10.00.2850.0	SP1 CU #16 (2582282) Sep 19,   2011
10.00.2847.0	SP1 CU #15 (2555406) Jul 18,   2011
10.00.2821.00	SP1 CU #14 (2527187) May 16,   2011
10.00.2816.00	SP1 CU #13 (2497673) Mar 17,   2011
10.00.2808.00	SP1 CU #12 (2467236) Jan 17,   2011
10.00.2804.00	SP1 CU #11 (2413738) Nov 15,   2010
10.00.2799.00	SP1 CU #10 (2279604) Sep 20,   2010
10.00.2789.00	SP1 CU #9 (2083921) July 19,   2010
10.00.2775.00	SP1 CU #8 (981702) May 17, 2010
10.00.2766.00	SP1 CU #7 (979065) Mar 26, 2010
10.00.2757.00	SP1 CU #6 (977443) Jan 18, 2010
10.00.2746.00	SP1 CU #5 (975977) Nov 16, 2009
10.00.2734.00	SP1 CU #4 (973602) Sep 21, 2009
10.00.2723.00	SP1 CU #3 (971491) Jul 20, 2009
10.00.2714.00	SP1 CU #2 (970315) May 18, 2009
10.00.2710.00	SP1 CU #1 (969099) Apr 16, 2009
10.00.2573.00	GDR Security update (2494096), June 14, 2011
10.00.2531.00	SP1 RTW / PCU 1 April, 2009
10.00.1835.00	RTM CU #10 (979064) Mar 15, 2010
10.00.1828.00	RTM CU #9 (977444) Jan 18, 2010
10.00.1823.00	RTM CU #8 (975976) Nov 16, 2009
10.00.1818.00	RTM CU #7 (973601) Sep 21, 2009
10.00.1812.00	RTM CU #6 (971490) Jul 20, 2009
10.00.1806.00	RTM CU #5 (969531) May 18, 2009   SP1
10.00.1798.00	RTM CU #4 (963036) Mar 16, 2009
10.00.1787.00	RTM CU #3 (960484) Jan 19, 2009
10.00.1779.00	RTM CU #2 (958186) Nov 19, 2008
10.00.1763.00	RTM CU #1 (956717) Sept 22, 2008
10.00.1600.22	RTM – Aug 6, 2008

SQL Server 2005

9.00.5266	SP4 CU #3 (2507769) Mar 22, 2011
9.00.5259	SP4 CU #2 (2489409) Feb 21, 2010
9.00.5254	SP4 CU #1 (2464079) Dec 23, 2010
9.00.5000	SP4 RTW (PCU4) Dec 16, 2010
9.00.4325	SP3 CU #15 (2507766) Mar 22 ,   2011
9.00.4317	SP3 CU #14 (2489375) Feb 21,   2011
9.00.4315	SP3 CU #13 (2438344) Dec 20,   2010
9.00.4311	SP3 CU #12 (2345449) Oct 18,   2010SP3
9.00.4309	SP3 CU #11 (2258854) Aug 16,   2010
9.00.4305	SP3 CU #10 (983329) Jun 21, 2010
9.00.4294	SP3 CU #9 (980176) Apr 19, 2010
9.00.4285	SP3 CU #8 (978915) Feb 16, 2010
9.00.4273	SP3 CU #7 (976951) Dec 21, 2009
9.00.4266	SP3 CU #6 (974648) Oct 19, 2009
9.00.4230	SP3 CU #5 (972511) Aug 17, 2009
9.00.4226	SP3 CU #4 (970279) June 15, 2009
9.00.4220	SP3 CU #3 (967909) Apr 20, 2009
9.00.4211	SP3 CU #2 (961930) Feb 16, 2009
9.00.4207	SP3 CU #1 (959195) Dec 19, 2008
9.00.4053	Security update (970892) Oct 12, 2009
9.00.4035	SP3 RTW (955706) Dec 15, 2008
9.00.3356	SP2 CU #17 (976952) Dec 21, 2009
9.00.3355	SP2 CU #16 (974647) Oct 19, 2009
9.00.3330	SP2 CU #15 (972510) Aug 17, 2009
9.00.3328	SP2 CU #14 (970278) June 15,   2009
9.00.3325	SP2 CU #13 (967908) Apr 20, 2009
9.00.3315	SP2 CU #12 (960485) Feb 16, 2009
9.00.3301	SP2 CU #11 (958735) Dec 15, 2008
9.00.3294	SP2 CU #10 (956854) Oct 21, 2008
9.00.3282	SP2 CU #9 (953752) Aug 18, 2008
9.00.3257	SP2 CU #8 (951217) Jun 16, 2008
9.00.3239	SP2 CU #7 (949095) Apr 14, 2008
9.00.3228	SP2 CU #6 (946608) Feb 18, 2008
9.00.3215	SP2 CU #5 (943656) Dec 17, 2007
9.00.3200	SP2 CU #4 (941450) Oct 15, 2007
9.00.3186	SP2 CU #3 (939537) Aug 20, 2007
9.00.3175	SP2 CU #2 (936305) June 18, 2007
9.00.3161	SP2 CU #1 (935356) April 16,   2007
9.00.3152	SP2 Rollup (933097) May 15, 2007
9.00.3068	Security update (948109) Jul 8, 2008
9.00.3042	SP2 (937137)
9.00.2047	SP1
9.00.1399	RTM