Contents
To configure an on-premises SharePoint Server content farm to return results from its search index to a separate on-premises SharePoint Server farm, you must perform the following two main procedures: Configure a server-to-server trust relationship by using the Open Authorization 2.0 (OAuth 2.0) web authorization protocol.
How does receivingfarm work with a SharePoint Server?
An on-premises SharePoint Server farm that has a search service that sends search queries to ReceivingFarm. An on-premises SharePoint Server content farm that has a search index that receives search queries from SendingFarm. In this article, it is assumed that ReceivingFarm has at least one web application that hosts content.
We’ve estimated that this search architecture can crawl 50 documents per second, and serve in the order of 10 queries per second. If you have up to 20 million items in a SharePoint Server 2016 farm, the small search farm will probably be the most suitable farm for you.
How to share search results in SharePoint Server?
For more information, see Configure result sources for search in SharePoint Server. After you create the result source, you expose the search results that it provides by using it in a Web Part or a query-rule action. In this way, users of the farm that is sending search queries can see results from the farm that is receiving the queries.
How to get search results from sendingfarm search index?
In order for SendingFarm to be able to get search results from the search index in ReceivingFarm, the farms must have the following characteristics: Each farm is a SharePoint Server on-premises deployment. User profiles in the two farms are synchronized.
Can a SharePoint account reside in a two way domain?
SharePoint can’t reside in a domain that’s part of a two-way domain trust where users who have active accounts in both domains share SID history. Each account must be unique. To make sure that this is the case, you need to do one of the following in Active Directory: Disable the source account.
Users are migrated to Domain B together with the SID history from Domain A, and the users are still active in Domain A. In a SharePoint farm that resides in one of the domains, you may experience the following issues: Users from one of the domains can’t be found in the people picker.