Monday, 2 September 2013

Pubishing infrastructure Feature Comparison Sharepoint 2013 vs Sharepoint 2010

  Publishing features in SharePoint 2010  Publishing features in SharePoint 2013 
1 publishing site templates like  Publishing Site,Publishing Site with Workflow,Enterprise Wiki will be available only with Publishing sites

same as 2010
top link bar is replaced with the global navigation menu
same as 2010
3 Content deployment same as 2010
Default settings for the global navigation menu and the Quick Launch menu are specified.
same as 2010
5 Additional files and folders are added to the Master Page Gallery library same as 2010
6 Content and Structure Reports same as 2010
7 Following libraries are additionally added(Design Manager,Reusable Content,Site Collection Documents ,Site Collection Images) same as 2010
8 Additional webparts are available (Content Query Web Part,Media Web Part,Summary Links Web Part,
Table Of Contents Web Part)
same as 2010
9 Additional timer jobs gets added to the site. same as 2010
10 Regional settings same as 2010
11 Variations same as 2010
12 Object and Output Cashing same as 2010
13   Cross Site Publishing
14   Device Channel
15   Design Manager

Thursday, 28 February 2013

SharePoint 2013 Multiple Content Hub and Multiple Managed Metadata Service

SharePoint 2013 Multiple Content Hub and Multiple Managed Metadata Service
1.    Can I have more than one Managed MetaData service assigned to a web application?
Yes (pls refer screen shot below

2.    Can I assign one “Managed MetaData service” and another one “Managed MetaData service proxy” to a same web application?
3.    Can I assign multiple content Hubs to a web application?
           Yes by creating multiple managed Metadata services.

4.    Can I have the same content Type name in two content Hubs and assign the same to a web  application?
        Yes, However Sharepoint takes only one incase you have the same content Type names.
5.    In the above scenario 4, is based on what sharepoint picks the “Managed MetaData service” from the available list?
        Don’t Know, sorry.


SharePoint 2013 Search Issue - Index was out of range

SharePoint 2013 Search Issue

The content processing pipeline failed to process the item. ( Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index; )

After doing a  index reset on a cross farm scenario, we started getting the following error. Tried most of the items mentioned in the blogs but sorry to say nothing worked for me and finally end up in recreating the search service application

SharePoint 2013 Cross Farm Service configuration steps

Farm1 needs to consume the Managed Metadata(or any service) service which is hosted in Farm 2. Following steps will provide the details (Assuming that both the servers are in the same domain.


Farm 1 is called the Consuming farm and Farm 2 will be called as the publishing farm in the below section.

Following Steps are required

  1. consuming farm
    1. root certificate
    2. security token service (STS) certificate
  2. Publishing Farm
    1. root certificate

$rootCert = (Get-SPCertificateAuthority).RootCertificate

$rootCert.Export("Cert") | Set-Content <C:\ConsumingFarmRoot.cer> -Encoding byte

$stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate

$stsCert.Export("Cert") | Set-Content <C:\ConsumingFarmSTS.cer> -Encoding byte

Either use Central admin or PowerShell to achieve the same

Once generated add the certificates to the farm via Manage Trust as highlighted in the below screen shot or use powershell for the same as listed below in section2



Publishing Farm

Add-PsSnapin Microsoft.SharePoint.PowerShell

$trustCert = Get-PfxCertificate 'D:\certif.cer'

New-SPTrustedRootAuthority Farm1Server -Certificate $trustCert

Publishing Farm STS certificate addition

$stsCert = Get-PfxCertificate 'D:\ConsumingFarmSTSFinal.cer'

New-SPTrustedServiceTokenIssuer Farm1STS -Certificate $stsCert

Consumer Farm

Add-PsSnapin Microsoft.SharePoint.PowerShell

$trustCert = Get-PfxCertificate 'D:\certif.cer'

New-SPTrustedRootAuthority Farm1Server -Certificate $trustCert

Establish a relationship between the publishing farm and the consuming farm by giving the consuming farm permission to the Application Discovery and Load Balancing Service Application on the publishing farm.

Find the consumer farm id  by using the following powershell command

Get-SPFarm | Select Id

Add the same FarmId(GUID)  to the publishing farms Application discovery and load balancing service as shown in the below screen shot.

Similarly we can add the farmId to the Managed Metadata service or any other service

Please note that in the case of User Profile service application, we need to give the consuming farm's web application pool identity instead of the consuming farm ID.

On the publishing farm, publish the service application

*Below steps are optional

To set permission to the Application Discovery and Load Balancing Service Application for a consuming farm by using Windows PowerShell

Get the farm id from the consumer farm and execute the same in the Publishing farm

$security=Get-SPTopologyServiceApplication | Get-SPServiceApplicationSecurity

$claimprovider=(Get-SPClaimProvider System).ClaimProvider

$principal=New-SPClaimsPrincipal -ClaimType "" -ClaimProvider $claimprovider -ClaimValue <consumingfarmid>

Grant-SPObjectSecurity -Identity $security -Principal $principal -Rights "Full Control"

Get-SPTopologyServiceApplication | Set-SPServiceApplicationSecurity -ObjectSecurity $security

Reference Links