Monday, 18 December 2017
Sunday, 17 December 2017
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
(get-spenterprisesearchserviceapplication).cloudindex
On the search server in SharePoint Server 2013, follow these steps:
- Run the CreateCloudSSA.ps1 PowerShell script.
- When prompted, type:
- The host name of the search server in SharePoint Server 2013.
- The Search service account in this format: domain\username.
- A name of your choice for the cloud SSA.
- The name of the database server in SharePoint Server 2013
- 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:
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 authentication. 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.
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:
- Local SharePoint resource : http://sp:5001
For Search service application 2:
- Local SharePoint resource : http://sp:5002
- 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
- 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
Wednesday, 8 November 2017
SharePoint Search 2013
Clone SharePoint 2013 Search components to new Server
Link: https://www.fpweb.net/blog/move-sharepoint-2013-search-components-to-new-server
$ssa = Get-SPEnterpriseSearchServiceApplication
$active = Get-SPEnterpriseSearchTopology -SearchApplication $ssa –Active
$clone = New-SPEnterpriseSearchTopology -SearchApplication $ssa -Clone –SearchTopology $active
$NewServer = Get-SPEnterpriseSearchServiceInstance -Identity "NewServerName"
Start-SPEnterpriseSearchServiceInstance -Identity $NewServer
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $NewServer
Get-SPEnterpriseSearchServiceInstance -Identity $NewServer
New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $NewServer
New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance $NewServer
New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $NewServer
New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance $NewServer
New-SPEnterpriseSearchIndexComponent -SearchTopology $clone -IndexPartition 0 -SearchServiceInstance $NewServer
Set-SPEnterpriseSearchTopology -Identity $clone
Change the default search topology in SharePoint Server 2013
https://technet.microsoft.com/en-us/library/jj862356.aspx
Configuring SharePoint 2013 Search with PowerShell
https://blogs.technet.microsoft.com/ptsblog/2013/09/19/configuring-sharepoint-2013-search-with-powershell/
SharePoint 2013 Search: Moving the Query Component to a Web Front End
http://stevemannspath.blogspot.in/2013/03/sharepoint-2013-search-moving-query.html
Step by Step configuration to Add custom Refiners in the Refinement Panel of Search Results page for SharePoint Online
https://blogs.technet.microsoft.com/sharepoint_made_easy/2013/03/19/step-by-step-configuration-to-add-custom-refiners-in-the-refinement-panel-of-search-results-page-for-sharepoint-online/Sunday, 5 November 2017
Wednesday, 25 October 2017
SharePoint Admin Daily / Weekly / Monthly Activities
SharePoint Admin Daily / Weekly / Monthly Activities
1 Managing and checking the overall server health and functionality
2 Monitoring SharePoint disk space usage through the built-in SharePoint reports for each site collection
3 Managing SharePoint permissions
4 Analyzing and reporting upon SharePoint usage and activity
5 Moving/copying sites
6 Supporting network load balancing needs and ensuring its correct operation (NLB)
7 Regular review of the events and messages reported in Event Viewer and Performance Monitor
8 Regular review, clean-up, management and configuration of SharePoint accounts and sites. This portion of the role will work closely with an Active Directory administrator if they are separated.
9 Regularly analyzing SharePoint content and storage
10 Monitoring SharePoint trends (e.g. site usage and growth, disk space usage and growth)
11 Setting up alerts and enforcing policies
12 Regularly auditing your SharePoint environment
13 Identifying and reporting governance violations
14 Checking for operating system, SQL Server and SharePoint patches and cumulative updates.
One-time / First-time Farm Activities
1. Determine general patch approach for applying patches
2. Windows O/S (Windows Update)
3. SQL Server (Service Packs)
4. Document the overall system architecture
5. Document the disaster recovery plan for data center, server, or document recovery
6. Determine search architecture (What is indexed?, how often?, etc.)
7. Determine design continuity (What templates are used for each area)
8. Determine best practices for creation of Sites, Site Collections, and content databases
9. Determine strategy for business intelligence in SharePoint (upon dashboards, where is
the data stored?, how is it presented?, etc.)
10. Create SharePoint Service Level Agreement
11. Create best practices document for taxonomies
12. Create best practices document on security configuration
13. Create SharePoint roles document
14. Determine who can access the site (internal only? customers?)
15. Determine how partners and users will navigate the sit
16. Determine the process to request a site
17. Determine the process to request access to sites
18. Create best practices document to explain how and when to publish a document to a
global audience (should they be PDFs?)
19. Create feedback and/or suggestion mechanism for site enhancements
20. Determine naming conventions
21. Develop process for FAQ (users and help desk)
22. Develop training process
Daily Activities
1. Review Windows Event Logs for high-priority issues
2. Review the SharePoint Logs for high-priority issues
3. Monitoring Third party tool, Services, web sites, applications
4. Tickets ,XIS Reports, Calls, Think about new PowerShell Script (Such as Automation , Monitoring tools)
5. Workflow task, web site permission issue , make daily To-do list , IIS Logs , UlS Logs, Think about innovation ideas.
6. Search about SharePoint Blogs , Article, Forums and utilizes resolved the issues.
Weekly Activities
1. Review Search Usage reports
2. Attempt searches upon typical end-user searches – verify they work properly
3. Verify Alerts are functioning properly
4. Enhance search through audit of Search patterns (implementation of noise words, best bets,
keywords, thesaurus entry, etc.)
5. Review and maintain current BI cubes and web parts (if applicable)
6. Audit server utilization (disk IO, disk space, CPU, etc.) and update baseline
7. Review past week questions and issues and update FAQ
8. Ensure off-site backup procedure working properly
Monthly Activities
1. Review overall server architecture based on current use
2. Audit individual server design (each server)
3. Review released patch list for Windows Operating System, SQL Server and SharePoint
4. Apply patches per the pre-defined patch approach
5. Review patches or maintenance to third-party controls (web parts, iFilters, etc.)
4. Review overall server architecture diagrams and documentation for updates and revisions
5. Review search architecture for new areas to index, crawl or exclude
6. Report on SharePoint uptime and SLA compliance
7. Review security hierarchy
8. Review new functions or sites deployed. Determine if training needs to be updated
9. Verify backups are valid and contain data
Quarterly Activities
1. Review company disaster recovery plan
Annual Activities
1. Exercise a company disaster recovery plan
2. Plan for upgrade: SQL, Windows, SharePoint 2016, PU, CU, Production end user cleanup task (site, dbs, uls, old user, ups cleanup task)
1 Managing and checking the overall server health and functionality
2 Monitoring SharePoint disk space usage through the built-in SharePoint reports for each site collection
3 Managing SharePoint permissions
4 Analyzing and reporting upon SharePoint usage and activity
5 Moving/copying sites
6 Supporting network load balancing needs and ensuring its correct operation (NLB)
7 Regular review of the events and messages reported in Event Viewer and Performance Monitor
8 Regular review, clean-up, management and configuration of SharePoint accounts and sites. This portion of the role will work closely with an Active Directory administrator if they are separated.
9 Regularly analyzing SharePoint content and storage
10 Monitoring SharePoint trends (e.g. site usage and growth, disk space usage and growth)
11 Setting up alerts and enforcing policies
12 Regularly auditing your SharePoint environment
13 Identifying and reporting governance violations
14 Checking for operating system, SQL Server and SharePoint patches and cumulative updates.
One-time / First-time Farm Activities
1. Determine general patch approach for applying patches
2. Windows O/S (Windows Update)
3. SQL Server (Service Packs)
4. Document the overall system architecture
5. Document the disaster recovery plan for data center, server, or document recovery
6. Determine search architecture (What is indexed?, how often?, etc.)
7. Determine design continuity (What templates are used for each area)
8. Determine best practices for creation of Sites, Site Collections, and content databases
9. Determine strategy for business intelligence in SharePoint (upon dashboards, where is
the data stored?, how is it presented?, etc.)
10. Create SharePoint Service Level Agreement
11. Create best practices document for taxonomies
12. Create best practices document on security configuration
13. Create SharePoint roles document
14. Determine who can access the site (internal only? customers?)
15. Determine how partners and users will navigate the sit
16. Determine the process to request a site
17. Determine the process to request access to sites
18. Create best practices document to explain how and when to publish a document to a
global audience (should they be PDFs?)
19. Create feedback and/or suggestion mechanism for site enhancements
20. Determine naming conventions
21. Develop process for FAQ (users and help desk)
22. Develop training process
Daily Activities
1. Review Windows Event Logs for high-priority issues
2. Review the SharePoint Logs for high-priority issues
3. Monitoring Third party tool, Services, web sites, applications
4. Tickets ,XIS Reports, Calls, Think about new PowerShell Script (Such as Automation , Monitoring tools)
5. Workflow task, web site permission issue , make daily To-do list , IIS Logs , UlS Logs, Think about innovation ideas.
6. Search about SharePoint Blogs , Article, Forums and utilizes resolved the issues.
Weekly Activities
1. Review Search Usage reports
2. Attempt searches upon typical end-user searches – verify they work properly
3. Verify Alerts are functioning properly
4. Enhance search through audit of Search patterns (implementation of noise words, best bets,
keywords, thesaurus entry, etc.)
5. Review and maintain current BI cubes and web parts (if applicable)
6. Audit server utilization (disk IO, disk space, CPU, etc.) and update baseline
7. Review past week questions and issues and update FAQ
8. Ensure off-site backup procedure working properly
Monthly Activities
1. Review overall server architecture based on current use
2. Audit individual server design (each server)
3. Review released patch list for Windows Operating System, SQL Server and SharePoint
4. Apply patches per the pre-defined patch approach
5. Review patches or maintenance to third-party controls (web parts, iFilters, etc.)
4. Review overall server architecture diagrams and documentation for updates and revisions
5. Review search architecture for new areas to index, crawl or exclude
6. Report on SharePoint uptime and SLA compliance
7. Review security hierarchy
8. Review new functions or sites deployed. Determine if training needs to be updated
9. Verify backups are valid and contain data
Quarterly Activities
1. Review company disaster recovery plan
Annual Activities
1. Exercise a company disaster recovery plan
2. Plan for upgrade: SQL, Windows, SharePoint 2016, PU, CU, Production end user cleanup task (site, dbs, uls, old user, ups cleanup task)
Subscribe to:
Comments (Atom)