It is possible to change the search index location to a dedicated volume after the installation using PowerShell.
You can find a great artivle about it here, the following is an abstract from that post:
Managing the search topology in SharePoint 2013 can be done only via PowerShell.
Here is an article about the procedure:
I think it should be:
I have tested it at my end and it only shows the data from the subsite.
If you need more help on search using REST, I found the link below to be useful
This is a well identified issue which was fixed with the Oct 2013 CU update to SP 2013.
This happens because the managed property ‘Title’ is mapped to crawled property ‘MetadataExtractorTitle’ by default as first priority and there was no way to change the order of this crawled property unless October 2013 Cumulative Update was applied.
However, this issue ...
Nothing is stupid here.
When you create a custom column in a list do a full crawl and you will see a crawled property available with the name ows_ColumnName.
You can't map a column to a Managed Property. You always map Crawled Properties to Managed Properties. So you will have crawled properties from site columns and the YES you can map as many crawled ...
Yes, it is normal. The Enterprise Search Center template will create a site, which is configured to not be indexed by the search crawler.
You should be able to re-activate the indexing of the search center by going into the "Site Settings" and select "Search and Offline Availability". There you see the Option "Allow this site to appear in search results" ...
Two things, the start address for Profiles should be sps3://mysitehost. The permissions on the User Profile Service for the default crawl account has to be allowed to "Retrieve People Data for Search Crawlers". Go to Central Administration | Application Management | Manage Service Applications. Select the User Profile Service Application (don't click the ...
Once I ran into the same problem long ago. The command
stsadm -o deleteconfigurationobject -id “your search service application ID”
helped. I was told that the PowerShell command
Remove-SPServiceApplication -id “your search service application ID” -RemoveData
would not always do the trick because it's weaker than the stsadm command.
Without development you can try add a static query to the content search result webpart: tags:"Keyword X" or tags:"Keyword Y" or tags:"Keyword Z" - tags should be the managed property for the Enterprise Keyword column.
With development you have to use the KeywordQueryClass, see: http://msdn.microsoft.com/en-us/library/ms544561%28office.12%29.aspx
The list is quite extensive when you look at it flat foundation vs enterprise. And not knowing what your customers needs are I would, personally, tell these things to my customer;
Custom site definitions and site provisioning are not available.
InfoPath forms service
And ALL of ...
You cannot set the crawl in O365. It is set to do a continuous crawl, and should take ~15 minutes for results to show in search results. However, in times of heavy use, that can increase to hours. This link provides more information: http://www.sharepointnutsandbolts.com/2013/10/waiting-for-search-crawl-in-office-365.html
You can specify a search center for all My Sites in the User Profiles Service Application > Setup My Sites > Preferred Search Center. Are the OOTB search box not working out?
Be sure to add "/pages/" after the URL to your search-center. As the example under the text box states.
There is currently a bug in SP2013, that by my understandings won't let you ...
that is expected behavior, but it does not mean that incremental crawl runs every 4 hours. you have to select between continuous vs incremental.
When you click on Continuous Crawl it disable the Incremental crawl. Continuous crawl automatically run every 15 min( by default).
Continuous crawls crawl SharePoint sites frequently to help keep
I have the same problem, and found solution - Here
Corrupted node.ini file in AdminComponent1 folder - size 2kb, but empty when open with notepad.
Solution - browse to:
C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Nodes\
For each node, open the folder and browse to \Configuration\Local\ and check the node.ini file ...
SharePoint 2013 places the Search index in the C: by default. There are many reasons why you would want to move the index to a different places.
This script will take three parameters, the Search Service Name, the Server Name and Index Location. There is an example on the bottom of the script.
Move-SPEnterpriseSearchIndex -SearchServiceName "Search ...
Yes it is.
Please see this TechNet documentation for when a full crawl is needed.
A Search service application administrator or site collection administrator added or changed a managed property. A full crawl of all affected content sources is required for the new or changed managed property to take effect.
We had this exact same problem. This post is what worked for us, without having to recreate components like some will tell you to do.
Hope it works for you!
Yes the site template Enterprise Search Center is available in the SharePoint Server 2013 standard edition.
The features of search NOT available in standard version is:
Content Search Web Part
Custom entity extraction
Extensible content processing
Query rules—advanced actions
Search vertical: “Video”
Reference: SharePoint 2013 feature ...
The process is:
Clone the existing topology
Add the components to the new Search Server
Activate the topology
More or less, it'll look something like this:
$si = Get-SPEnterpriseSearchServiceInstance -Local
$clone = $sa.ActiveTopology.Clone()
New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $si
We finally figured out the problem with this one.
We had given Full Read permissions to NT AUTHORITY\Authenticated Users for All zones in User Policy of the web applications in question. I am not sure of the reason for giving this. We removed it. Then, a full crawl fixed the issue.
You need to setup the site collection's search settings (Site Actions -> Site Settings -> Search Settings). Enable custom scopes by pointing the site to your search center, and set the dropdown mode to enable those scopes to be used. Additionally, you should also point it to the applicable search results for your search center, so that when users perform a ...
With regards to that particular error code it is linked to Performance Monitor. You could try Make sure the Search Service account is added in the Performance Log Users and afterwards check that you find a search related trace with status Running in "Event Trace Sessions" of the Performance Monitor.
Here is what you are looking for. I have used this when I had to recreate my search center and it worked like a charm:
All you basically do is save your new search center url in a variable and use that variable to set the url to all sites within a web app by ...
This is NOT possible with Managed Property keyword queries. The only wildcard capability that Sharepoint Search Server 2010 supports is "Stemming". Stemming expects the characters to be matched by the characters at the start of a string in the index.
e.g. Item contains Title string "TestMe"
You're query can be : Title:"Tes" and that would pick up the ...
The issue seemed to be down to the size of the Index Partition. We reduced the number of items in the index using crawl rules and were able to get it down to about 8 million items from 12 million.
We were able to then make changes to the search topology.
What was interesting was the SharePoint Search Service on the rogue Crawl server would take about 90 ...
When was the last time you ran a full crawl since this issue? I'll be clear, I don't think that's the issue but managed properties (the refiners) are very unique and a full crawl is needed before you can even search against them. I wouldn't be half-surprised, as unbelievable as it sounds, that you would need to do a full crawl for the refiners to show the ...
Increasing the context weight for the property title, a search word hit in a title will receive a higher rank score than a hit in the body. This causes the item with a search word hit in the title to appear higher up on the search results list. The different managed properties, such as title and body, are mapped into different important levels. The context ...