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.

Ex:
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

SearchQueryAndSiteSettingsService
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:
$Spclone.Activate()

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
Ashi

Advertisements
Posted in SharePoint 2013, SQLServerPedia | Tagged , , , , , | 10 Comments

Wishing You a Very Happy Diwali

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

KAHI TIMTIMAHAT HAIN DIYO KI, KAHI SHOR HAAN ATHISBAZI KA

CHAMAK HAAN DIL MAIN, UMEEDO KI KHANAK HAAN

MITHAIYO KA ANAND HAAN, PATHAKO KI JHADI HAAN

YE JEET HAAN SACH KI, YE JASAN HAAN DIWALI KA

Happy Diwali- Ashish Banga

 

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

 

Ashi

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
Ashi

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.

dcpromo

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

 Steps:

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.

Features

 

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

ADDS

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.

Results

14) Close the wizard , once installation completes.

 

Steps:

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.

Prerequisite

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
Ashi

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

How to Configure Form Base Authentication(FBA) in SharePoint Server 2010 Claim based using LDAP

Hello Friends,

It’s been months I haven’t written anything as I was busy with lot of stuff. There are many things to write but starting with topic for which I got many mails from lot of friends through blogs and linked in.

As we all are aware with Claim based in SharePoint 2010 and different option/ways of Authentication( Ldap, Sql, Federation). Claim is the technology of today, In SharePoint 13 Microsoft even removed the Classic  Mode and made it the days of past. Today we will discuss with the form based with LDAP Authentication.

 I will try to provide and exact way to configure Form based authentication in Claim Based Authentication in SharePoint. To enable a form based , web application should be created in Claim based mode only.

Steps:

Creating a Claims based web application using GUI

  • Go to Application Management in Central admin
  • Go to Manage Web Applications and create a new web application
  • In the option select Claims Based Authentication mode

web app creation1-Ashish Banga

  • In claim authentication types select Enable Windows Authentication and select NTLM
  • In authentication type section for  form based configuring select Enable ASP.NET Membership provider name.

    Note: Membership provider and Role manager name which you provide in this section will be used in everywhere for web config and enabling it. So give it properly and note it for reference.

  • Click on “OK” button to create the web application.
    web app creation2-Ashish Banga
  • web app creation3-Ashish Banga web app creation4-Ashish Banga
  • Now everybody knows web application is nothing until and unless there is at least a single site collection in it. So first create a site collection for it.
  • Go to CA, Application Management, Create site collections
  • Select the appropriate web application
  • Create a site collection with adding appropriate entries .
  • Now the task remain is to modify different web config files and adding user policy for the web application.
Modifying Web.Config files for the FBA web application , Central Administration and Secure Token Service

Note: All the web config entries for copying are provided at end of blog:

In the below web configs (for all ) 3 entries need to be added as per your entry:
1) one for Membership provider and Role manager name
2) Server name
3) Group Container. If you have access to AD you can find the container easily. Go to the AD . Select a user or a group in the container

AD1-Ashish Banga

AD2-Ashish Banga

Modifying web.config of the web application

  • Open the web.config file  of claim based web application’s
  • Find the <membership> entry. There should be only one membership entry and modification should be done in that only. Duplicity will give error.
  • Put the below XML directly under <Providers> entry
    webconfig-WP1-Ashishbanga
  • Find the <roleManager> entry.
  • Put the below XML directly under <Providers> entry.
    webconfig-WP2-Ashishbanga
  • Put the below entry in the People Picker Wildcards entry
    people picker-Ashishbanga

Modifying web.config of the Central Administration site

  • Open web.config file of  Central Administration site
  • Find the <system.web> entry
  • Put the following XML directly below it
    webconfig-CA-Ashishbanga
  • Put the below entry in the People Picker Wildcards entry
    people picker-Ashishbanga                            

 

Modifying web.config of the Security Token Service (STS) in 14 Hive

  • Open the web.config file  of Security Token Service (STS)
  • Find the </system.net> entry
  • Below full entry need to be added directly below </system.net> entry
    webconfig-secure store-Ashishbanga

Note: If you more than one SharePoint servers hosting Central Administration or the claims based web application then all web config entries need to be changed in all SharePoint servers.

Add a user policy to the web application

  • Go to CA, Application Management, Manage Web Applications
  • Highlight the claims based web application
  • Click on User Policy and select Add Users link
  • Click the Address Book icon. Type the login name to search. There will be two entries for same name one of AD and other for LDAP
  • Select the account from form authentication one in the User section and click the Add button
  • Give the Full Control access by checking that box. then click the Finish button
    LDAP1-Ashish Banga
    LDAP2-Ashish Banga

Now is the time for testing:

Open your web application in the browser. If all things are done fine. It will open like this:

Claim Based application1-Ashish Banga

Now click on sign in:

Claim Based application2-Ashish Banga

Now Your form based authenticated site will open for you:

Claim Based application3-Ashish Banga

Web config entries


Membership entry:
         <add name=”LdapMember” type=”Microsoft.Office.Server.Security.LdapMembershipProvider, Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” server=”server2008.ashish.com” port=”389″ useSSL=”false” userDNAttribute=”distinguishedName” userNameAttribute=”sAMAccountName” userContainer=”OU=CLAIM,DC=ASHISH,DC=COM” userObjectClass=”person” userFilter=”(ObjectClass=person)” scope=”Subtree” otherRequiredUserAttributes=”sn,givenname,cn” />

Role provider entry:
<add name=”LdapRole” type=”Microsoft.Office.Server.Security.LdapRoleProvider,  Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” server=”server2008.ashish.com” port=”389″ useSSL=”false” groupContainer=”OU=CLAIM,DC=ASHISH,DC=COM” groupNameAttribute=”cn” groupNameAlternateSearchAttribute=”samAccountName” groupMemberAttribute=”member” userNameAttribute=”sAMAccountName” dnAttribute=”distinguishedName” groupFilter=”(ObjectClass=group)” userFilter=”(ObjectClass=person)” scope=”Subtree” />

People picker entry:
<PeoplePickerWildcards>
<clear />
<add key=”AspNetSqlMembershipProvider” value=”%” />
<add key=”LdapMember” value=”*”/>
<add key=”LdapRole” value=”*”/>
</PeoplePickerWildcards>

Role Manager key for CA:
<roleManager enabled=”true” defaultProvider=”AspNetWindowsTokenRoleProvider” >

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
Ashi

Posted in SharePoint2010, SQLServerPedia | Tagged , , , , , , , , , , , , , , , , | 8 Comments

SQL Database connectivity|| SharePoint Configuration || Named Pipes Error In MOSS 2007

Hello Friends,

MOSS2007 is still live and sometime we need to check certain features and that can give learning too. Recently one of my friend was installing MOSS 2007 on his Virtual machine and during the configuration of the “SharePoint Configuration Wizard” he encountered an error while creating a new farm.

Ashish-Sql connec

Error is reflecting that SQL Server cannot be connected to the network, To diagnose it further we check lot of stuff:

  • VMware network settings.
  • IP addresses Provided to the servers were in the same subnet mask.
  • Any specific DNS issue.
  • able to ping IP address from both ends.
  • Non blockage of SQL port 1433 by firewalls.

It was my mistake and didn’t check PS config Diagnostic configuration error log at first in the 12 Hive. After spending some time and checking the log thoroughly. We got a log entry that “Named Pipes” might not be enabled on the SQL Server.

I check the Microsoft sites and there was no need for Named pipes as the connection are made through TCP socket but still I enabled Named Pipes on Sql server.

I tried the things again and this time it run without any error. It was success.

“Named Pipes” can be enabled as:

  1. Go to “SQL Server Configuration Manager”
  2. Go to “SQL Server 2005 Network Configuration”
  3. Go to “Protocols for MSSQLSERVER”
  4. Right-click the “Named Pipes” and “Enable” it.

If you uninstall and install sharepoint again or disable named pipes on same server configuration you will never get the error again. But if you create a new server VM and all configuration it will give same error. I have checked it but not sure why it gives error on new servers. Might be on fresh it needs named pipes to be enabled for a single time.

But nevertheless problem got resolved.

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
Ashi

Posted in MOSS 2007, SQLServerPedia | Tagged , , , , , , , , , , , , | 11 Comments