PDF’s – in Versions of SharePoint (2013 & 2010/2007 )

Leave a comment

1.  Out of Box PDF Support for SharePoint 2013

2. Configuring Adobe PDF iFilter 9 for 64-bit platforms for SharePoint 2010

 

Out of Box PDF Support for SharePoint 2013

There are two major end-user experiences one should know about PDF support in SharePoint 2013.

After 4 iteration of SharePoint products, finally SharePoint 2013 natively supports PDF files. PDF icon is natively supported in SharePoint 2013 results and document libraries without any additional configuration or installation of software in SharePoint 2013 farm. There is no need to install Adobe’s free PDF ifilter or Foxit PDF iFilter like SharePoint 2010 or MOSS 2007. This is simply available in out of the box configuration.

Apart from native support of PDF icon, Microsoft even takes it one step further and allows end user to open PDF file without saving them on your machine if you have Adobe Reader 10.0.2 or later installed. If you click on the PDF file with proper version of Adobe Reader installed from IE 9 or later, SharePoint will try to open PDF file in the Adobe Reader and provide software users will an option to directly check out and check in documents from the Adobe Reader.

 It is nice to see Microsoft implementing this simple yet very useful feature in SharePoint 2013 as Out of the Box feature.Microsoft has worked really hard to integrate SharePoint functionality in the Adobe Reader software. This would definitely make PDF file viewing and management experience much better in coming years.

 Having native PDF support in SharePoint 2013 – PDF Icon & Opening PDF files without saving them first would be one of the most welcome feature from many IT shops.

 This is one of those requirements which made SP2010 looks bad…many were always surprised to see SharePoint doesn’t support PDF natively in earlier versions…

 P1

So SharePoint 2013 now has Out of box PDF Support which is awesome for End Users.

In a nutshell, here are some of the Features: 

  •          PDF icon is natively supported in SharePoint 2013 results
  •          No need to install Adobe’s free PDF ifilter or Foxit PDF iFilter
  •          You can Open PDF file without saving them on your machine if you have Adobe Reader 10.0.2 or later is installed.
  •          SharePoint will try to open PDF file in the Adobe Reader and prompt user to either checkout & open or open the PDF file directly.

 Notice below how in SharePoint 2013 both of those problems are finally resolved. While setting up some search demos, I dropped some PDF files into a document library, just to see what happens. I was pleasantly surprised to see this:

 P2.png

Configuring Adobe PDF iFilter 9 for 64-bit platforms for SharePoint 2010

Adobe® PDF iFilter is designed for end users or administrators who wish to index Adobe PDF documents using Microsoft indexing clients. This allows the user to easily search for text within Adobe PDF documents.

Download: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025

  1.        First, install the Adobe PDF 64 bit IFilter version 9 from this location: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
  2.       Now add PDF as a file type:
  •          Run Central Administration.
  •          Click Manage service applications under “Application Management”:

P3

  •          Click the Search Service Application link in the list of applications.

P4

  •          Click File Types  under “Crawling” in the left navigation area:P5
  •          Click New File Type.
  •          Enter pdf for the “File Name Extension” and click OK.

P6

3.       Using Regedit on the server and navigate to

\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\Filters

  •           Right-click the Filters folder and select New Key. Enter “.pdf” for the key value.
  •          Add the following values to this key:

<REG_SZ> Default = <value not set>
<REG_SZ> Extension = pdf
<REG_DWORD> FileTypeBucket = 1
<REG_SZ> MimeTypes = application/pdf

 The key should look like:

P7

4.       Navigate to: \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension

  •          Right-click the Filters folder and select New Key. Enter “.pdf” for the key value.
  •          Set the “default” value to {E8978DA6-047F-4E3D-9C78-CDBE46041603}

 The key should look like:

P8

5.       Exit Registry editor

6.       Restart SharePoint Search Service

7.       Restart all the SharePoint servers in the farm

8.       You can now add an image to be used for the icon for PDF documents:

  •          Add an image (typically .gif or .png, use Google images to find an example or http://www.adobe.com/misc/linking.html ) for the PDF icon to the folder: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES
  •           Open the file docicon.xml from the location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML
  •           Add a link to map the pdf extension to the image by adding a link like the following to the ByExtension element:

                 <Mapping Key=”pdf” Value=”pdf_icon.gif” OpenControl=””/>

9.        Finally, issue an IISReset and restart the Windows services “SharePoint Foundation Search V4” and “SharePoint Server Search 14”.

Your PDF documents should now be indexed on the next indexing crawl.

SharePoint Service Accounts Explained

2 Comments

Service Accounts play an important role while installing almost every version of SharePoint because if they are not set up correctly they can open big security holes in your organization or give problems down the road , however everyone have their own different ways of setting them up. I believe that once a SharePoint is installed with a set of service accounts, it’s easier to do a clean install than to change them all.

Every SharePoint admin will probably have a different view of how many service accounts you need, their naming convention, and what permissions are required for each one of them. Depending on the level of security you want to achieve in your SharePoint Farm, you can install everything with only one account (not recommended), and one can make as many as 10 to 15 accounts.   Even if all the SharePoint administrators have different views and different ways, it doesn’t mean one of them is wrong and one of them has the golden solution for every SharePoint farm.

 You can read the original article here; however I will do a little summary. I read the accounts and the permissions few times, and although they weren’t wrong… I didn’t think it was right, I think that it isn’t well balanced.

Here are the proposed accounts:

  • SQL_Service, for the SQL Server service.
  • SQL_Admin, for the SQL Server administrator.
  • SP_Admin, for the SharePoint administrator and setup user.
  • SP_Farm, for the SharePoint farm service.
  • SP_WebApps, for the user-facing web application app pool.
  • SP_ServiceApps, for the service application app pool.
  • SP_Crawl, default content access account.
  • SP_UserSync, user profile synchronization account.
  • SP_EnterpriseAdmin, powerful account for handling all kinds of high privilege operations.
  • Farm administrators, normal admin user accounts are used as SharePoint Farm Administrators.

Here is what I propose :

To install SharePoint in a proper manner, we should use two SQL accounts, the SQL administrator and other to run SQL Agent and Database Engine services, and 8 SharePoint accounts: The Farm Administrator, the Web Application pool account, the MySite Web Application pool account, the SharePoint Service Application Pool account, the Crawl and Search account and the User Profile Synchronization account.

Note:

  • By giving fewer rights to each account you limit the possible damage in case an account gets hacked and also follow Microsoft’s recommendation of installing SharePoint 2013 with least-privilege administration.
  • That this post only covers the basic Service Accounts needed for SharePoint 2013 and that other Service Accounts will be needed for some Service Application (ex: Excel Unattended Service, Visio, etc )

 For SQL Server:

Name

Description

Local Rights

Domain Rights

SQL_Admin SQL Admin on the SQL Server. Used to Install the SQL Server. Local Administrator on the SQL Server Domain User
SQL_Services It is the service account for the following SQL Server services: MSSQLSERVER SQLSERVERAGENT. None Domain User

Note that we are using two different accounts for SQL: The SQL_Admin and the SQL_Services. The big security improvement is that the account running the Agent and Database Engine services is not a local administrator anymore.

SQL_Admin: This will be your main SQL Administrator!. It needs Local Administrator rights in order to install the SQL server.

 SQL_Services: This account does not have any local rights; it is only used to run the SQL Agent and Database Engine windows services.

 For SharePoint Server:

Name

Description

Local Rights

Domain Rights

SP_Farm The server farm account is used to perform the following tasks:- Configure and manage the server farm.

– Act as the application pool identity for the SharePoint Central Administration Web site.

– Run the Microsoft SharePoint Foundation Workflow Timer Service.

SecurityAdmin and DB_Creator rights on the SQL Instance. Domain User
SP_Admin The server farm account is used to perform the following tasks:- Setup

– SharePoint Products Configuration Wizard 

Local Administrator on all the SharePoint Servers.SecurityAdmin and DB_Creator rights on the SQL Instance. Domain User
SP_Pool The Pool account is used to run the Web Application Pools (except for MySite). None Domain User
SP_Services The Services Account is used to run the Service Application Pool. None Domain User
SP_Crawl The Default Content Access Account for the Search Service Application. None Domain User
SP_Search Service Account to run the SharePoint Search “Windows Service”. None Domain User
SP_MySitesPool Used for the My Sites Web Application. None Domain User
SP_UserProfiles The User Profile Synchronization Account. None Replicate Directory Changes permission on the domain.

Instead of giving all the Farm Administration power to the SP_Farm account, the SP_Admin will be the one that installs and configures SharePoint 2013 and have the local administrator rights, while the SP_Farm will only run the services and connect to the database.

Next, instead of letting the SP_Crawl account run both the Windows Service and have FULL-READ rights on all the web applications, the SP_Search will now run the Windows Service.

 SP_Farm is a domain account that the SharePoint Timer service and the web application for Central Administration use to access the SharePoint content database. This account does not need to be a local administrator. The SharePoint configuration wizard grants the proper minimal privilege in the back-end SQL Server database. The minimum SQL Server privilege configuration is membership in the roles securityadmin and dbcreator.

 SP_admin is a domain account you use to install and configure the farm. It is the account used to run the SharePoint Configuration Wizard for SharePoint 2013.The SP_Admin account is the only account that requires local Administrator rights. To configure the SP_Admin account in a minimum privilege scenario, it should be a member of the roles securityadmin and dbcreator on the SQL server.

 SP_Pool is a domain account used for application pool identity. Ex: When you create a Web Application, and you create a pool for it, you select this account (except for MySite)!

 SP_Services is a domain account used for the Service Applications Pools. Ex: When you create a Managed Metadata Service application and create a pool for it, you select this account!

 SP_Crawl is used within the Search Service Application to crawl content. The Search Service Application will automatically grant this account read access on all Web Applications.

 SP_Search Is used to run the SharePoint Windows Search Service.

 SP_UserProfiles is the account used for the User Profile Synchronization between your Service Application and your Active Directory. This account does not need any local rights; however you need to give it Replicate Directory Changes rights on the Active Directory in order to allow the synchronization.

 SP_MySitePool is a domain account used for the My Sites Web Application Pool Identity. It’s very similar to the SP_Pool; however it is only used for the My Sites Web Application.

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

Leave a comment

 
 

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

SharePoint Build Version

Leave a comment

SharePoint Build Version

SharePoint Build version can be identified using:

  1. PowerShell Script
  2. CentralAdmnistration
  3. SQL Select query against SharePoint Admin Database Version table.

1.       PowerShell Script:

                        Get-SPFarm | Select BuildVersion

spversion_ps

2.       CentralAdministration:

spversion_ca

3.       SQL Select query against SharePoint Admin Database ‘Version’ table.

 Login to SharePoint Database Server using SQL Management Studio.

 Select SharePoint Admin Database.

 Open Query Window

 Execute “Select * from Versions”

 spversion_db

Now what !! How does the above results help or where do we stand in the queue of the listed Service packs and Cumulative updates ?

Before we determine where do we stand will it not be better to know what’s the difference between a  PU, CU, COD, SP  ?

Public Update (PU): A public update usually includes security fixes for the product or fixes for problems which affect a broad number of customers.

Cumulative Update (CU):  A cumulative update includes fixes for problems with a product that have been reported by customer in context of support cases.

Critical On Demand Fix (COD):A COD is a fix which is provided only to a small number of customers affected by a critical problem directly through Microsoft Support to provide a quick relief. The code changes in the COD gets included in next CUs and it is advised to install that CU on top of the COD as soon as it has been released.

Service Pack: A service pack is a combination of previously released fixes, fixes which have only been released in context of the service pack and potentially new functionality added to the product and tested.

Type What’s Included Prerequisite When to Install Multilingual
PU please review the KB article for each public update in detail to see which fixes are included. Usually the oldest supported service pack. As a PU includes security fixes it is recommended to evaluate and install PUs as soon as possible. Yes. The PU package includes fixes for all languages
CU new and all previously released fixes (CUs and PUs) since the oldest supported service pack. The oldest supported service pack. Within the first 12 months after releasing a SP you can install on the latest SP and the previous one. CUs released more than 12 months after the newest SP require the newest SP to be installed. CUs should only be installed to resolve specific issues fixed with the CUs as mentioned in each CU KB article Or if advised to install by Microsoft Support Yes. The CU package includes fixes for all languages.
COD only the specific fix for a specific issue. Usually the CU that was used as the baseline to develop the COD. Microsoft Support will provide guidance which CU is required to be install as a prerequisite for the COD. Only if advised by Microsoft Support. Usually not.
SP new fixes, new functionality, all previously released fixes (older Service Packs, CUs, PUs) usually there is no prerequisite to install a service pack. recommended to evaluate and install Service Packs as soon as possible. No. You need separate Service Packs for each installed language
The SharePoint Versions Table:

SharePoint 2013:

Release Version KB
SharePoint   Foundation 2013
RTM 15.0.4420.1017 n/a
March 2013 CU 15.0.4481.1005 2768000
SharePoint Server   2013
RTM 15.0.4420.1017 n/a
Dec 2012 Hotfix 15.0.4433.1506 2752058
March 2010 CU 15.0.4481.1005 2767999

SharePoint Foundation 2010 & SharePoint Server 2010:

Release Version KB
SharePoint   Foundation 2010
RTM 14.0.4762.1000 n/a
June 2010 CU 14.0.5114.5003 n/a
Aug 2010 CU 14.0.5123.5000 2352346
Oct 2010 CU 14.0.5128.5000 2394323
Dec 2010 CU 14.0.5130.5002 2459125
Feb 2011 CU 14.0.5136.5002 2475880
April 2011 CU 14.0.5138.5001 2512804
Service Pack 1 14.0.6029.1000 2460058
June 2011 CU 14.0.6106.5000 2536601
June 2011 CU (Refresh) 14.0.6106.5002 2536601
Aug 2011 CU 14.0.6109.5002 2553117
Oct 2011 CU 14.0.6112.5000 2596508
Dec 2011 CU 14.0.6114.5000 2596998
Feb 2012 CU 14.0.6117.5002 2597132
April 2012 CU 14.0.6120.5000 2598321
April 2012 CU (Refresh) 14.0.6120.5006 2598321
June 2012 CU 14.0.6123.5002 2598373
August 2012 CU 14.0.6126.5000 2687355
October 2012 CU 14.0.6129.5000 2687566
December 2012 CU 14.0.6131.5001 2596957
SharePoint Server   2010
RTM 14.0.4762.1000 n/a
June 2010 CU 14.0.5114.5003 n/a
Aug 2010 CU 14.0.5123.5000 2352342
Oct 2010 CU 14.0.5128.2003 2394320
Dec 2010 CU 14.0.5130.5002 2459257
Feb 2011 CU 14.0.5136.5002 2475878
April 2011 CU 14.0.5138.5001 2512800
Service Pack 1 14.0.6029.1000 2460045
June 2011 CU 14.0.6106.5000 2536599
June 2011 CU (Refresh) 14.0.6106.5002 2536599
Aug 2011 CU 14.0.6109.5002 2553048
Oct 2011 CU 14.0.6112.5000 2596505
Dec 2011 CU 14.0.6114.5000 2597014
Feb 2012 CU 14.0.6117.5002 2597150
April 2012 CU 14.0.6120.5000 2598151
April 2012 CU (Refresh) 14.0.6120.5006 2598151
June 2012 CU 14.0.6123.5002 2598354
August 2012 CU 14.0.6126.5000 2687353
October 2012 CU 14.0.6129.5003 2687564
December 2012 CU 14.0.6131.5003 2596955

WSS 3.0 & MOSS 2007:

WSS 3.0
RTM 12.0.4518.1016 n/a
Public DST 12.0.6039.5000 934525
SP1 12.0.6219.1000 936988
Post SP1 (Jan) (Global) 12.0.6300.5000 941422
Post SP1 (Jan) 12.0.6300.5000 941653
Post SP1 (Feb) 12.0.6303.5000 948945
Post SP1 (Feb) (Global) 12.0.6304.5000 949399
Post SP1 (Mar) (Global) 12.0.6305.5000 949749
Post SP1 (Mar) (Global) 12.0.6306.5000 949956
Post SP1 (Mar) (Global) 12.0.6307.5000 950279
Post SP1 (Mar) (Global) 12.0.6308.5000 950484
Post SP1 (May) (Global) 12.0.6314.5000 952288
Post SP1 (May) 12.0.6314.5000 952292
Post SP1 (May) (Global) 12.0.6315.5000 952698
Post SP1 (May) (Global) 12.0.6316.5000 953137
Post SP1 (June) (Global) 12.0.6317.5000 953473
Post SP1 (June) 12.0.6317.5000 953484
Infra Update (Global) 12.0.6318.5000 951695
Post SP1 (July) 12.0.6324.5000 955594
Post SP1 (AAM) 12.0.6324.5001 956248
Aug CU (Global) 12.0.6327.5000 956057
Aug CU 12.0.6327.5000 957109
Oct CU (Global) 12.0.6332.5000 957691
Dec COD (Global) 12.0.6335.5000 959644
Dec CU 12.0.6335.5000 960010
Dec COD (Global) 12.0.6336.5001 961175
Feb 2009 CU 12.0.6341.5000 961755
SP2 12.0.6421.1000 953338
April 2009 CU 12.0.6504.5000 968850
Jun 2009 CU 12.0.6510.5001 971538
Aug 2009 CU 12.0.6514.5004 973400
Oct 2009 CU 12.0.6520.5000 974989
Dec 2009 CU 12.0.6524.5000 977027
Feb 2010 CU 12.0.6529.5000 978396
April 2010 CU 12.0.6535.5002 981043
Jun 2010 CU 12.0.6539.5000 983311
Aug 2010 CU 12.0.6545.5001 2276474
Oct 2010 CU 12.0.6548.5000 2412268
Dec 2010 CU 12.0.6550.5002 2458606
Feb 2011 CU 12.0.6554.5000 2475886
April 2011 CU 12.0.6557.5000 2512783
June 2011 CU 12.0.6562.5000 2544399
Aug 2011 CU 12.0.6565.5001 2553022
SP3 12.0.6608.1000 2526305
Oct 2011 CU 12.0.6654.5000 2596541
Dec 2011 CU 12.0.6656.5000 2596987
Feb 2012 CU 12.0.6658.5000 2597959
April 2012 CU 12.0.6661.5000 2598130
June 2012 CU 12.0.6662.5000 2687257
August 2012 CU 12.0.6665.5000 2687331
October 2012 CU 12.0.6668.5000 2687535
December 2012 CU 12.0.6670.5002 2760571
MOSS 2007
RTM 12.0.4518.1016 n/a
Public DST 12.0.6034.5000 937832
SP1 12.0.6219.1000 936984
Post SP1 (Jan) (Global) 12.0.6300.5000 942819
Post SP1 (Jan) (Global) 12.0.6301.5000 945089
Post SP1 (Jan) (Global) 12.0.6301.5000 941274
Post SP1 (Feb) (Global) 12.0.6303.5000 948947
Post SP1 (Feb) (Global) 12.0.6304.5000 949402
Post SP1 (Mar) (Global) 12.0.6306.5000 949955
Post SP1 (Mar) (Global) 12.0.6307.5000 950280
Post SP1 (Mar) (Global) 12.0.6307.5000 950292
Post SP1 (Mar) (Global) 12.0.6308.5000 950487
Post SP1 (May) (Global) 12.0.6314.5000 952294
Post SP1 (May) (Global) 12.0.6315.5000 952704
Post SP1 (May) (Global) 12.0.6316.5000 953138
Post SP1 (June) (Global) 12.0.6317.5000 953471
Infra Update (Global) 12.0.6318.5000 951297
Post SP1 (July) (Global) 12.0.6324.5000 955593
Post SP1 (July) 12.0.6324.5000 955586
Exel Security fix   (Global) 12.0.6317.5000 953397
Aug CU (Global) 12.0.6327.5000 956056
Oct CU 12.0.6331.5000 957693
Oct CU 12.0.6331.5000 958569
Dec COD (Global) 12.0.6335.5000 959637
Dec CU 12.0.6335.5000 960011
Dec COD 12.0.6336.5001 961176
Dec COD 12.0.6336.5002 963022
Feb 2009 CU 12.0.6341.5001 961756
SP2 12.0.6421.1000 953334
April 2009 CU 12.0.6504.5000 968851
Jun 2009 CU 12.0.6510.5003 971537
Aug 2009 CU 12.0.6514.5002 973399
Oct 2009 CU 12.0.6520.5000 974988
Dec 2009 CU 12.0.6524.5001 977026
Feb 2010 CU 12.0.6529.5000 978395
April 2010 CU 12.0.6535.5002 981042
Jun 2010 CU 12.0.6539.5000 983310
Aug 2010 CU 12.0.6545.5001 2276472
Oct 2010 CU 12.0.6548.5000 2412267
Dec 2010 CU 12.0.6550.5000 2458605
Feb 2011 CU 12.0.6554.5000 2475885
April 2011 CU 12.0.6557.5000 2512782
June 2011 CU 12.0.6562.5000 2544398
Aug 2011 CU 12.0.6565.5000 2553020
SP3 12.0.6608.1000 2526299
Oct 2011 CU 12.0.6654.5002 2596540
Dec 2011 CU 12.0.6656.5001 2596986
Feb 2012 CU 12.0.6658.5000 2597958
April 2012 CU 12.0.6661.5000 2598129
June 2012 CU 12.0.6662.5000 2687256
August 2012 CU 12.0.6645.5001 2276472
October 2012 CU 12.0.6668.5000 2687533
December 2012 CU 12.0.6670.5002 2760570