Windows PowerShell for SharePoint Command Builder

https://www.microsoft.com/resources/TechNet/en-us/Office/media/WindowsPowerShell/WindowsPowerShellCommandBuilder.html

Create a cloud Search service application in SharePoint Server 2013

The cloud SSA lets you crawl and add metadata from on-premises content to the search index in Office 365. Each search farm can have only one cloud SSA, but can have multiple SSAs in combination with the cloud SSA. You can’t convert an existing SSA to a cloud SSA.

You can create a cloud SSA in the SharePoint Central Administration website, just like an SSA. Here we describe how to create a cloud SSA by running the CreateCloudSSA.ps1 Windows PowerShell script from the Microsoft Download Center. This script installs the cloud SSA and the default search architecture for cloud hybrid search.

A cloud Search service application (SSA) cannot be created using the central admin SSA creation user interface. The reason being that the cloud SSA requires a property setting that is not applied by the UI based creation process. This property is called CloudIndex and must be set to true for a cloud SSA. CloudIndex is a read-only property of any deployed SSA and as such cannot be set post creation. this also implies that an existing regular SSA cannot be converted to a cloud SSA.

The property value for a SSA can be checked by executing
(get-spenterprisesearchserviceapplication).cloudindex       

 

On the search server in SharePoint Server 2013, follow these steps:

1. Run the CreateCloudSSA.ps1 PowerShell script.
2. When prompted, type:
1. The host name of the search server in SharePoint Server 2013.
2. The Search service account in this format: domain\username.
3. A name of your choice for the cloud SSA.
4. The name of the database server in SharePoint Server 2013
3. Verify that you see the message that the cloud SSA was successfully created.

Copy this to .ps1 to SharePoint app server from where cloud search service will run.

Now open windows power shell as an administrator and execute the above PS file.

Now it will ask you all the parameters one by one, you must supply all the values.

After that it will first start checking whether service account is already registered or not, then it will create an application pool and search service application. All the components for search service will be configured. After that it will activate search topology for this search service application and it will create search service proxy.

Now you validate it part by part. First you validate the status of this newly created cloud search service, verify the account.

Install hybrid onboarding prerequisites

To successfully execute the on-boarding script, the following prerequisites must be installed on the SharePoint Server where the script is executed.

Download the two prerequisites and save in the same folder where the Install-HybridSearchConfigPrerequisites.ps1 . The two prerequisites can be downloaded from:

Microsoft online sign in assistant – http://www.microsoft.com/en-us/download/details.aspx?id=39267

Microsoft Azure AD PowerShell – http://go.microsoft.com/fwlink/p/?linkid=236297

Execute the Install-HybridSearchConfigPrerequisites.ps1 to install prerequisites. 

To confirm the Microsoft Online Single Sign On Assistant is successfully installed

(get-service msoidsvc).Status

A response of Running is a report of success

To confirm the Windows Azure AAD PowerShell is successfully installed import the msonline modules

import-module msonline

import-module msonlineextended       

A successful import results in no error message    

If you wish to double check the import then use the –verbose switch to show the cmdlets being successfully loaded

import-module msonline -verbose     

import-module msonlineextended -verbose      

Both Office Single sign-on assistant and AAD PowerShell MUST succeed before continuing with the onboarding process.

Note: If you try to proceed onboarding without these components installed the onboarding script will recognize this state and exit gracefully.    

Enable Server-to-Server Authentication

The next step in the process is to enable server-to-server auth­entication. By doing so, the local SharePoint farm and the cloud-based SharePoint Servers can request and access resources on one another's behalf. Once again, Microsoft has provided a script that automates the configuration process.

Therefore, mentioned CreateCloudSSA.ps1 script included within a .ZIP file is called CloudHybridSearchPreview.zip. The documentation for setting up Hybrid Search also contains the Windows PowerShell script (OnBoard-HybridSearch.ps1) required for enabling server-to-server authentication.

.\OnBoard-CloudHybridSearch.ps1 -PortalUrl <SPOTenantPortalUrl> -CloudSsaId <CloudSSANameCreatd>

SPOTenantPortalUrl is the URL of your company's or organization’s UNRESOLVED_TOKEN_VAL(SharePoint Online) portal, and CloudSsaIDis the name of the cloud SSA that you created earlier. If connection is successful, the script will proceed and you should be presented with an output matching the following print screen

Some following commands to add or remove service instance

·         $srvc = Get-SPServiceInstance -Server INDR-SPAS02 | where-object {$_.TypeName -eq "SharePoint Server Search"}

·         $srvc.provision()

·         Get-SPServiceInstance -Server INDR-SPAS02 | where-object {$_.TypeName -eq "SharePoint Server Search"} | Stop-SPServiceInstance -confirm:$false > $null

·         Get-SPServiceApplicationPool | Select Id, Name

·         Get-SPServiceApplicationPool -Identity "CloudSearchServiceApplication_AppPool" | Remove-SPServiceApplicationPool

·         Start-SPServiceInstance -Identity 716cfc86-b69a-4b54-939c-cd5be43cf7d9

·         Get-SPServiceInstance | Where-Object {$_.TypeName -eq "CloudSearchServiceApplication"} | select Status, Id

Configure content sources on-premises

Content sources in the Cloud SSA are no different to Content Sources in a regular Enterprise SSA.

Follow the steps in https://technet.microsoft.com/en-us/library/jj219808.aspx?f=255&MSPPError=-2147217396 to create and manage content sources in the cloud SSA.

Start the full Crawl on Cloud search service application Content Source

Crawl completed successfully.

Verify that cloud hybrid search works

After the full crawl completes, verify that your on-premises content shows up in the search results in your validation Search Center in Office 365.

1.     Log in to Office 365 with your work or school account. Make sure that:

o    You have access to the validation Search Center.

o    You have access to the content in the content source that you have crawled.

o    Your organization hasn’t assigned user access rights to the on-premises content by using one of the default security groups in Windows Server Active Directory (AD), for example the Domain Users security group, learn more in Plan cloud hybrid search for SharePoint.

2.     Search for IsExternalContent:1 in the validation Search Center.

3.     Verify that your on-premises content shows up in the search results.

Set up Search of OneDrive for Business in Office 365 from SharePoint Server

Link: https://technet.microsoft.com/en-us/library/dn627526(v=office.16).aspx

Creating and configuring 2 Search Service Application in same SharePoint 2013 farm

Description: This is for specific need of having 2 different Search Indexes in the same farm and make use of both in a same Search center site. You can have different search topologies on different search service applications in the same farm.

Steps

• Create 2 Search service application namely “Search Service Application 1(Consuming)” and “Search Service Application 2(Publishing)”

• Create 2 web application “SSA1” and “SSA2” for 2 search center sites

SSA1 http://sp:5001/  

SSA2 http://sp:5002/

• Create 2 Enterprise search center site collection on these web applications

SSA1 site: http://sp:5001/sites/Search5001   (Consuming)

SSA1 site: http://sp:5002/sites/Search5002   (Publishing)

• Added 2 different content sources to each Search Service application as below

For Search service application 1:

1. 1. Local SharePoint resource : http://sp:5001

For Search service application 2:

1. 1. Local SharePoint resource : http://sp:5002
   2. Websites: http://onlinehelp.microsoft.com/en-in/bing/ff808487.aspx

• Perform full crawl on all the content sources in both the Search service applications
• Change the proxy associations of the 2 web applications as given below, deselect the other search service application proxy

SSA1 web application - Search Service Application 1  [default]

SSA2 web application - Search Service Application 2  [default]

• Verify if you can search and get the results on both the search center sites according to the content source added to it

http://sp:5001/sites/Search5001/Pages/results.aspx?k=site

http://sp:5002/sites/Search5002/Pages/results.aspx?k=site

• Now open Search service application 1, go to Result sources
• Add new result source with name “SSA2”

• Configure this “SSA2” result source as below

Protocol: Remote SharePoint

Remote service URL: http://sp:5002/sites/Search5002/

• Go to consuming search center site -> pages library -> Create a page  with name “SSA2”

• Now go to site setting and then Search settings -> Configure Search Navigation
• Add link -> Select the new created page “SSA2” with title “SSA2”

• Edit the existing “Everything” link as “SSA1”

• Click Ok to save and apply
• Now consuming Search center site should look like below

• Edit the search center site and edit the search result web-part query to display the results from result source created “SSA2”

• Save the webpart and then the page.
• Clicking the Search vertical links namely “SSA1” and “SSA2” will display results from corresponding search service application

       

Note:- You can modify the result source or the search result web part query to display the results differently for both the Search service applications in the consuming search center site