Difference of Index Partition and Creating Service application in partitioned Mode

Hi All, 

I am sharing the response and question which I received on my mail based on past post : “Configure search topology in scale out mode in SharePoint 2013”  .

What I received is “If we are using index partition and replica, then why we are not creating Search service application in Partitioned Mode” . and shared me with a link of some other blog.

So what is the in and out of that is:

  1. There might that readers relate Index partition with Search Service application in Partitioned mode.
  2. It also might be possible that some experts combined and created Search Application in partitioned mode and Index partition in single Blog.

None of the above possibilities is wrong nor the experts blogs. But to clear the things is the main aim of this post.

So what is this Partitioned mode, Let’s understand with 2 examples:

  1. Suppose we have Search service application and metadata service application . If other division want separate metadata and search service, we create the same. But what to be done , If every other department want it separate service. In that case we will Create “Partitioned Service Application” . Which help us to create data separate in spite of using single service application and same database.

  2. Secondly if we are using Hosted SharePoint or SharePoint Online and we want separate search for every Tenant based on Site Subscription. In that case also we will create a Partitioned Service application.

This is what referred as Multi Tenancy in SharePoint.

Example of Creating a search application in partitioned mode. It just needed to add a switch (Partitioned) using PowerShell


To Create Search Service Application
$SPServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SPSearchServiceName -ApplicationPool “Learning\Test1” -DatabaseName $SPDatabaseName -Partitioned

To Create Search Service Application Proxy
New-SPEnterpriseSearchServiceApplicationProxy -Name $SPSearchServiceProxyName -SearchApplication $SPServiceApplication –Partitioned

For reference of this command you can refer the post: “How to Configure Search in SharePoint 2013”.

Note: Although Non-Partitioned service application can be created using CA or PowerShell. But Partitioned service application can be created only with PowerShell.

Now what is Index Partition and Replica

Index Architecture(component) is divided into Index Partition and Index Replica. Index can be divided into index partition or called as discrete portion which is stored in disk. It enable scaling in two ways:

  1.  Index partition are added to handle the Crawl load or Crawl Volume. It can be created based on your crawl volume of data.
  2. Index Replica are added to handle the Query load or volume. So if you are getting large query load you can create replica accordingly.

Hope, I am able to explain the difference between Index Partition and creating service application in Partitioned mode.

If you liked this post, do like on Facebook at : https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful

Hope this help

Posted in SharePoint 2013 | Tagged , , , , | Leave a comment

Configure Search Topology in ScaleOut Mode in SharePoint 2013 || Configure Search Service in SharePoint 2013

Hello Friends,

With a New Year and my earlier commitments. Below is the way to configure Search Service 2013 in Scale out mode.

Search Service configuration 2013 in Standalone mode can be viewed at: “How to Configure Search in SharePoint 2013”

 As described earlier, Microsoft is focusing more and more on Power Shell and this is what is done with Search in SharePoint 2013. Graphical interface in SharePoint Search application is not available. We cannot create and edit topology from Central administration. Only option is to use Power Shell.

We already have Search service Application, Proxy and Search and index component created in earlier post. To configure in scale out mode:

  • We just need to modify existing topology by making a clone. Or
  • Create a new topology with all components again.

There is no need to create Search service application and proxy again. As earlier was standalone I would prefer to create new topology.

But in production or already scale out mode it is preferred to modify the existing topology by making a clone of it. As we have to take care of:

Index component addition and removal, keeping in mind of search.

Removal and addition of Replica accordingly.

For current scenario:

  • We are using 4 servers which are holding(Admin, Crawl, Content, Analytics, Query & Index) in Redundant basis.
  • As per Microsoft Guidelines:
    Content Processing and Analytics processing should be together.
    Administration and crawl should be together.
    Index and query processing should be together.

So we would be configuring the search as per below description:

Description Of servers

Below are the directs commands for very component to be created:
Server Names
$AppServer1 = “servr2012-sql”
$AppServer2 = “servr2012-1″
$AppServer3 = “servr2012-2″
$AppServer4 = “servr2012-3″


Starting the Search service instance
Start-SPEnterpriseSearchServiceInstance $AppServer1 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchServiceInstance $AppServer2 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchServiceInstance $AppServer3 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchServiceInstance $AppServer4 -ErrorAction SilentlyContinue

Starting the query and site setting Service Instance
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $AppServer1 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $AppServer2 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $AppServer3 -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $AppServer4 -ErrorAction SilentlyContinue
Creating a New Topology with Search service Application
$searchapplication = Get-SPEnterpriseSearchServiceApplication
$newTopology = New-SPEnterpriseSearchTopology -SearchApplication $searchapplication

$AppInstance1 = Get-SPEnterpriseSearchServiceInstance -Identity $AppServer1
$AppInstance2 = Get-SPEnterpriseSearchServiceInstance -Identity $AppServer2
$AppInstance3 = Get-SPEnterpriseSearchServiceInstance -Identity $AppServer3
$AppInstance4 = Get-SPEnterpriseSearchServiceInstance -Identity $AppServer4

Creating the search components on appropriate servers:
New-SPEnterpriseSearchAdminComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance1
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance1
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance1
New-SPEnterpriseSearchCrawlComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance1


New-SPEnterpriseSearchAdminComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance3
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance3
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance3
New-SPEnterpriseSearchCrawlComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance3


Creating the Index and Query component:
New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance2
New-SPEnterpriseSearchIndexComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance2 -IndexPartition 0
New-SPEnterpriseSearchIndexComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance4 -IndexPartition 0


New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance4
New-SPEnterpriseSearchIndexComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance2 -IndexPartition 1
New-SPEnterpriseSearchIndexComponent –SearchTopology $newTopology -SearchServiceInstance $AppInstance4 -IndexPartition 1


To set New search topology as an active one
Set-SPEnterpriseSearchTopology -Identity $newTopology
Get-SPEnterpriseSearchServiceApplication -searchapplication $searchapplication

Topology New

Search Topology

Search Topology



I have created a topology for 4 Servers. It can be scaled as per the Crawl volume and Query volume .

If you liked this post, do like on Facebook at:https://www.facebook.com/Ashishsharepointblog


Feel free to Rate and provide feedback if you find post useful

Hope this help

Posted in SharePoint 2013, SQLServerPedia, Uncategorized | Tagged , , , , , , , , | 1 Comment

2014 in review

The WordPress.com stats helper monkeys prepared a 2014 annual report for this blog.

Here’s an excerpt:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 19,000 times in 2014. If it were a concert at Sydney Opera House, it would take about 7 sold-out performances for that many people to see it.

Click here to see the complete report.

Posted in Uncategorized | Leave a comment

How to Configure Search in SharePoint 2013 || Configure Search Topology in SharePoint 2013

Hello Friends,

I was getting lot of responses on blogs and mails. It will be difficult to cover all at once . So covering today the latest one “How to Configure Search in SharePoint 2013” and in Standalone server.

Microsoft is focusing more and more on Power Shell and this is what is done with Search in SharePoint 2013. Graphical interface in SharePoint Search application is not available. We cannot create and edit topology from Central administration. Only option is to use Power Shell.

Till SharePoint 2010 we have the option to configure and scale Search Service application using Central administration.

There is not much difference to configure Search in Standalone or farm mode. The thing in Farm mode is to scale out the all the component except (Search Admin Component) as it cannot be scaled out and the other is to create it in partitioned mode.

To Create Search in Farm and scale out mode. I will write the same after this article.

List of Components which need to be kept in mind while creating and Configuring Search Service Application are:

  1. To create a SharePoint Search Service Application( This is the only part which can also be done using Central Administration)
  2. To Create a SSA(Search Service Application) Proxy( It will be created automatically using GUI but need to create manually using Power Shell)
  3. Component of Search: Search administration component, Content processing Component, Crawl Component, Query component & web analytics(which is separate service application in SP 2010)
  4. Creating or scaling Index component and Index replica.

Below are series of steps to create and configure Search Service and its Topology using PowerShell.

My SharePoint server name: servr2012-sql

To Create a Search application we need: An Application Pool, A service account for app pool.

Below Snippet will create a Search Service application or SSA in short:
Open SharePoint Management Shell with Administrator permission.

$AppServer = “servr2012-sql”
$SPSearchAppPoolName = “Search_App”
$SPSearchAppPoolAccount = “learning\test1″
$SPSearchServiceName = “SharePoint Search Service Application”
$SPSearchServiceProxyName = “SharePoint Search Service Application Proxy”
$SPDatabaseName = “SharePoint-Search-db”

To Create a Search Service Application Pool
$AppPool = New-SPServiceApplicationPool -Name $SPSearchAppPoolName -Account $SPSearchAppPoolAccount -Verbose

To start Search Service Instance on Application or Standalone Servers
Start-SPEnterpriseSearchServiceInstance $AppServer -ErrorAction SilentlyContinue
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $AppServer -ErrorAction SilentlyContinue

Below is screenshot, which service are started with above command:
SearchServiceInstanceSearch Service Instance--Ashish banga

Search Query And Site Settings Service Instance--Ashish banga

To Create Search Service Application
$SPServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SPSearchServiceName -ApplicationPool “Learning\Test1” -DatabaseName $SPDatabaseName

To Create Search Service Application Proxy
New-SPEnterpriseSearchServiceApplicationProxy -Name $SPSearchServiceProxyName -SearchApplication $SPServiceApplication

Till this part you can also do with GUI Central admin. You will find 3 Service application in the list, below is screenshot for the same.

SharePoint Search Service Application Proxy--Ashish banga

Search Topology commandSearch Topology command-Ashish banga

Rest all configuration need to be done with power shell. With this a Search Topology is created and topology cannot be modified in active state. To create other component we need to create a clone of the current topology and work on it and once all things are finalized we can activate that topology.

Cloning the topology:
$Spclone = $SPServiceApplication.ActiveTopology.Clone()
$AppInstance = Get-SPEnterpriseSearchServiceInstance -Identity $AppServer

Now the clone is created and we can start creating other Search Components:

To create admin component
New-SPEnterpriseSearchAdminComponent –SearchTopology $Spclone -SearchServiceInstance $AppInstance

To Create content processing component
New-SPEnterpriseSearchContentProcessingComponent –SearchTopology $Spclone -SearchServiceInstance $AppInstance

To create Analytics processing component
New-SPEnterpriseSearchAnalyticsProcessingComponent –SearchTopology $Spclone -SearchServiceInstance $AppInstance

To Create crawl component
New-SPEnterpriseSearchCrawlComponent –SearchTopology $Spclone -SearchServiceInstance $AppInstance

To create Query processing component
New-SPEnterpriseSearchQueryProcessingComponent –SearchTopology $Spclone -SearchServiceInstance $AppInstance

As we are using Standalone environment there is no need for index partition and replica. We can directly create index component as others.
Note: For Scale out I will surely add a new article very soon.

$IndexprimaryLocation = “C:\Data”
New-SPEnterpriseSearchIndexComponent –SearchTopology $Spclone -SearchServiceInstance $AppInstance -RootDirectory $IndexprimaryLocation

Note: You have to create folder before using this command.

Search ComponentSearch Component-Ashish banga

As told earlier we have to activate this clone to show effect or have in place:

It will take time to finalize the change, So you can enjoy for a while.

When all things are done we can verify our topology with below command.

$searchapplication = Get-SPEnterpriseSearchServiceApplication
Get-SPEnterpriseSearchTopology -Active -SearchApplication $searchapplication

Below is the screenshot of activated component in the topology.

Topologytopology--Ashish banga

Goto your central admin and go to search application you will find your topology as below:

Search TopologySearch Toplogy--Ashish banga

I have created a topology on stand alone server but it is very easy to scale out your topology. In next section I will show to scale this same topology in N server farm.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful

Hope this help

Posted in SharePoint 2013, SQLServerPedia | Tagged , , , , , | 3 Comments

Wishing You a Very Happy Diwali

Wishing You a Very Happy Diwali…………….





Happy Diwali- Ashish Banga


दीपावली : अर्थात  दीपो की अवली या दीपो की पंक्ति। दीपो द्वारा उत्साह, त्यौहार या स्वागत ही दीपावली है। इस दीपावली बल्बावली की जगह दीपावली मनाये । इस दीपवली दीपो को प्रज्जवलित करके दीपावली मनाये और इस रोजगार में अपना सहयोग दे।
माता लक्ष्मी आप सबके के परिवार को सुख समृद्धि और ज्ञान प्रदान करे ।
हैप्पी दीपावली



Posted in Uncategorized | Leave a comment

Error while enabling NetFx3 feature || Alternate source path error

Hello Friends,
Life Is a struggle with Lot of If and buts. It’s being a many month I was out of touch with my blogging hunger. But there were lot of question which I was getting from time to time on my mails/blogs , which I will try to answer in couple of days or weeks.


Few weeks back, there was some one asking about an specific error “Error while enabling Windows feature : NetFx3 “. I have seen the error earlier also but this time I was interested to find it cause. So, while working it seems that this error occurs with other name also. Some are:


  1. Error installing Microsoft .NET Framework 3.5==>  While installing .NET 3.5 features or it needed as prerequisite.installing .NET 3.5 
  2. Specify Alternate source Path? One or more installation selection are missing source path==>While Installing Active Directory Domain services.Active Directory Domain services
  3. Error while enabling Windows feature : NetFx3==> Error while installing Sql.Sql server 2012


So, What is this error and why the demon is coming with different names in diff ways.

Problem came out is: It turns out that Windows Server 2012 does not include NetFx3 when it is installing.  It doesn’t mean that it is gone, but it does have to be installed separately.  So here we go, It is coming on 2012 window server as we all are fond to learn new thing on new version.


What we have to do to resolve the issue. There are 2 ways to resolve the same:

  1. By using the GUI . All of us favorite way.
  2. Or the Command prompt


  • Insert the window 2012 CD or if using Virtual way(VMware/Hyper-v) attach the ISO file. Check the drive letter it assign . D: in this caseIso file


  1. Go to Server Manager==> Manage==> Add roles and feature.
  2. Select .NET framework 3.5 features
  3. Click next. You need to enter Alternate source pathActive Directory Domain services 
  4. It was D drive in our case. Click specify alternate source path and type: D:\Sources\SxS . It is the place where the bits are present and which doesn’t install while installing window 2012source path 
  5. Click ok and install. Your error will not occur


  • If you want to go with cmd prompt and type: dism /online /enable-feature /featurename:netfx3 /all /source:d:\sources\sxscommand prompt

If any of the 2 process are done your issue will be resolved.


If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog


Feel free to Rate and provide feedback if you find post useful


Hope this help

Posted in SharePoint 2013, SharePoint2010, SQLServerPedia, Window Server | Tagged , , , , , | 1 Comment

Installing and Configuring Active Directory in Window Server 2012

Hello Friends,

Sometimes life is so uneasy that you didn’t get time for the work which you like the most. Now those days are gone so I am back.It’s been months I haven’t written anything . I have received lot of mails through blogs and LinkedIn which I tried to reply.
Days are gone and now the pet command “DCPROMO” which is used to install Active directory is now the thing of past. But command can go not the concept.


So, How to Install Active Directory in Windows Server 2012?. I will try to provide exact way to install and configure Active Directory in new world.

Screen which comes when we use “dcpromo” to install AD.


This means we need to go to Server Manager to Install AD.


a) How to Install AD.

1) Go to Server Manager.
2) On the server manager page dashboard . Click on  Add roles and features.

server Manager

3) Roles and Features Wizard will open which will allow to add different roles and features in Window server. On the Default page , click next

Before you begin

4) Select Role based or feature-based installation. As we are installing role directly on a particular server and not on any env. remotely.

Installation Type

5)  Current server will come by default. Select the server and click next.

Destination server

6) On the Server Role page select the Active Directory Domain Services. A list of additional things which are required with this will appear, select Add Features.

Add features

7) Select the features like .Net and Group policy Management. Scrolling down you will see the Remote server Administration tool is already selected as it is required with Active directory installation.



8) Read the information given in AD DS page and click Next


9) Read the DNS  information and click next.

DNS Server

10) Select the restart the destination server check box and click Install.

Add Roles and Features

11) You are also export the Configuration settings which has been defined for future use.


12) Once AD DS is installed you can start configuration directly from result page “ Promote this server to domain controller”. It can also be done through Server Manager page.


14) Close the wizard , once installation completes.



b) How to Configure AD.


1) After AD DS role is installed it will be directly displayed on the ‘Server Manager’ page. For completing the configuration open the Notifications Pane by clicking on Notifications icon on the top of the Server Manager. click Promote this server to a domain controller.

Domain Controller

2) As we are creating a new forest . Select the option “Add New Forest” and provide the name of root domain. i.e in my case it is learning.com

Deployment Configuration

3) Select Forest functional level and Domain Functional Level. Here I am considering that all my servers are server 2012 . If there are server less than window server 2012. We should consider for backend Compatibility and level should be considered accordingly.


a) As it is the first Domain controller there is no option to check or uncheck . But for future ADC we need to check or uncheck these option as per need.


b) Kindly provide the DSRM password. It commonly known as passphrase earlier. Which is used while adding or removing any additional domain controller to have administrator authentication.

Note: Kindly note the password for future perspective.

Domain controller Option

4) Read the below Warning and click Next. This warning is basically because of the Authoritative Zones which need to be created in DNS explicitly.

DNS Option

5) Provide the Netbios name of your domain in the field required. i.e Learning for our case.

Netbios name

6) Specify the location of below NTDS and Sysvol file. By Default it is C: Drive.

ADDS path

7) Read and acknowledge the below information before clicking Next.

ADDS Review

8) You can also view the script as what will be done during installation. Same can be done with power shell also.

Script ADDS

9) After the prerequisite check. Click on Install.


10) After the installation is completed Successfully. Server will be Restarted and your Active Directory Domain Services is installed and configured on Windows Server 2012.


Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at :https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful

Hope this help

Posted in SharePoint 2013, SQLServerPedia, Window Server | Tagged , , , , , | Leave a comment