You have a claims-based web application (let’s call it https://mywebapp.com) running on SharePoint Server 2010. You’ve set up the Search Service application and it’s crawling your content without issues. Your shared search scopes are working great (search All Sites, search All People), but the contextual search scopes (search This Site or search This List) are returning no results. How do we fix this?
Step 1. Extend web app to an NTLM auth site. (If you’ve already extended your web app to NTLM, skip to Step 2.)
As you probably already know, SharePoint 2010 cannot crawl claims-based web applications directly. So the first thing to do is to extend https://mywebapp.com application to another IIS site which uses only NTLM authentication.
Navigate to Central Administration > Application Management > Manage web applications
Select your web application > click on Extend button in the ribbon. Fill out the “Extend web application” form and make sure that for Claims Authentication Types you only select “Enable Windows Authentication” and check “Integrated Windows Authentication” NTLM checkbox.
All other fields can be left with their default values. Make sure to take note of the Public URL, it will look something like this:
Step 2. Modify Search Service app content sources to crawl the NTLM site.
In Central Admin, open Application Management > Manage service applications > click on your Search Service application. Click on Content Sources and edit your content source to crawl the NTLM site you just created (http://myservername:43374).
Step 3. Add Server mapping (This is important!)
Within your Search Service Application, click on “Server Name Mappings” and creating a mapping between your NTLM site and the public URL.
Address in index: http://myservername:43374
Address in search results: https://mywebapp.com
Note: Some blog posts online will skip the server name mapping step and instead tell you to change your Default Alternate Access Mapping to point to http://myservername:43374. While it may work in some cases, there are times when you cannot (or should not) change your Default AAM. The server name mapping in SSA helps you avoid changing the AAM.
Step 4. Indexing.
Finally, in your Search Service Application, reset the index and perform a full crawl. Review the crawl log and make sure that there are no top level errors.