AnsweredAssumed Answered

Nintex issues while configuring Hybrid Search

Question asked by gona.dakshayani on Oct 3, 2017
Latest reply on Oct 3, 2017 by Clavin Fernandes

We are currently using Nintex in our on-premises SharePoint 2013 farm. We are also currently configuring our Office 365 and SharePoint Online implementation.

As part of that effort, we are working on configuring hybrid search between on-prem and the cloud following these steps: https://technet.microsoft.com/en-us/library/dn720906.aspx

 

According to this article<https://support.office.com/en-us/article/Hybrid-picker-in-the-SharePoint-Online-admin-center-efce8417-c9bc-4a2c-ac9d-cce6c4e84a9c> there is some risk that the configuration will break the Workflow Manager, and there are some remediation scripts<https://support.microsoft.com/en-us/help/4010011/provider-hosted-add-ins-stop-working-and-http-401-error> that involve deleting and recreating the workflow manager proxy (additional information here<https://blogs.technet.microsoft.com/beyondsharepoint/2016/09/15/considerations-when-deploying-sharepoint-office365-hybrid-workloads-in-a-farm-utilizing-provider-hosted-add-ins-or-workflow-manager/>).

 

We would like to know if Nintex has configured hybrid search in a SharePoint farm running Nintex on-prem, and whether these configurations steps will cause any service disruption in the Nintex workflows. Does Nintex rely on SharePoint Workflow Manager or does it use its own workflow manager? Would deleting and recreating this proxy break any running workflows?

Outcomes