Nintex Workflow 2013 and Nintex Forms 2013 Installation Guide · Nintex Forms Installerfilelocation Licensefilelocation Useraccountfor installationprocess Serverforrunning Nintex

Installation Guide:Nintex Workflow 2013 and

Nintex Forms 2013

Last updated Monday, May 14, 2018

Legal noticesFor the latest information, please see http://en-us.nintex.com/company/legal.

© 2018Nintex Global Ltd. | Privacy Policy | Terms & Conditions | Cookie Preferences | Nintex Support

-i-

Installation Guide: Nintex Workflow 2013 and Nintex Forms 2013

http://en-us.nintex.com/company/legal

https://www.nintex.com/company/legal/privacy-policy

https://www.nintex.com/company/legal


https://www.nintex.com/support

Contents

Introduction: Install Nintex for SharePoint 2013 1Worksheets (optional) 1

Installation checklist 1

Installation worksheet 2Plan your test and production environments 3

System requirements: Nintex for SharePoint 2013 3

Review topology considerations and best practices 4

Set up topology for installation 6

Set up server used for running installers 7Install Nintex products to production environment 8

Obtain account with sufficient permissions 8

Obtain Nintex license files 10

Schedule deployment 11

Run the installer 11

Import the license files 16

Configure databases and other items 17

Connect and enable Nintex Live 23

Enable Nintex Live features for Nintex Workflow 26

Enable form-based authentication for Nintex Mobile 26

Activate features in SharePoint 26

Confirm production installation 28Addendum 31

Nintex Workflow Exchange Connector Service installation 1

Manually export and import Nintex solutions 4

Uninstall Nintex Workflow and Nintex Forms 5Troubleshoot deployment 5

Identify the problem 6

Issues 7


-ii-






Introduction: Install Nintex for SharePoint 2013This document provides guidance for installing the following Nintex products to yourSharePoint environment.

l Nintex Workflow 2013l Nintex Forms 2013l Nintex Live

The installation process involves planning your test and production environments,deploying to a test environment, confirming test deployment, deploying to production,and confirming production deployment.

Note: This guide is intended for brand-new installations of the listed products.For information on installing product updates or upgrading and migratingNintex products, run this search on the Nintex Connect site.

Following are the high-level links useful for installing Nintex products.

Worksheets (optional)Use the following optional worksheets to track your status in the installation and recordthe locations of important information.

Installation checklistUse the following checklist to track your status in the installation process.

1. PlanPlan your test and production environmentsObtain account with sufficient permissionsObtain Nintex license filesSchedule deployment

2. TestDeploy the solutionsImport the license filesConfigure databases and other itemsConnect and enable Nintex LiveActivate features in SharePointConfirm installation

3. InstallDeploy the solutionsImport the license filesConfigure databases and other itemsConnect and enable Nintex LiveActivate features in SharePointConfirm installation


-1-


https://community.nintex.com/search.jspa?q=migration+upgrade+update+%22Nintex+Workflow%22+%22Nintex+Forms%22&type=document





Installation worksheetUse this worksheet to record locations of files and identifiers of servers used ininstallation.

Environment (Production / Test / Other): ______________________________________

Nintex WorkflowFiles, account, and server used for running installer

Installer file location

License file location

User account forinstallation process

Server for runningNintex Workflowinstaller

Web applications

List each web application in the SharePoint farm that is expected to useNintex Workflow.

Databases

Nintex configuration databases:

Nintex configuration database name Failover database name Notes

Content databases:

Nintex content databasename

SharePoint content databasename

Notes

Global settings

Outbound SMTP Server

From Address

Reply to Address


-2-






Nintex Forms

Installer file location

License file location

User account forinstallation process

Server for runningNintex Forms installer

Nintex Forms databasename

Plan your test and production environmentsThis section provides guidance if you are new to setting up SharePoint to run Nintexproducts or require a refresher of the prerequisites.

Planning test and production environments involves meeting system requirements,reviewing topology considerations and best practices, setting up the topology forinstallation, and setting up the server to be used for running installers.

System requirements: Nintex for SharePoint 2013Following are the system requirements for Nintex for SharePoint.

Note: Nintex Forms Enterprise Edition requires Nintex Forms 2.7.0.0 or later,in addition to an Enterprise-enabled license. For more information, see ProductUpdate Process on Nintex Connect.

Type Nintex Workflow 2013 Requirement

Operatingsystem

Microsoft Windows Server 2008 R2 or Microsoft Windows Server 2012(R2 is supported)

Browserclient

To design and run Nintex workflows, use the following browserversions.l Minimum required: Microsoft Internet Explorer 8.xl Recommended: Microsoft Internet Explorer 9 or greater

Software l Microsoft SharePoint Foundation 2013 or Microsoft SharePointServer 2013 (SP1 is supported)

Note: See the following Microsoft article. SharePoint 2013SP1 support in Windows Server 2012 R2.

l SQL Server 2008 R2 SP1, SQL Server 2012, or SQL Server 2014

Hardware Web servers: Nintex Workflow requires the same minimumrequirements that are required when installing SharePoint 2013. Seehttp://technet.microsoft.com/en-au/library/cc262485.aspx.Database servers: Nintex Workflow requires the same minimumrequirements that are required when installing SharePoint 2013. Seehttp://technet.microsoft.com/en-au/library/cc262485.aspx#section3.Hard disk space is dependent on the Nintex database growth rate.This rate is affected by the following:l The number of workflow instances that are executedl The number of actions in a workflow instancel The number of tasks assigned to used


-3-


https://community.nintex.com/docs/DOC-1375


https://support.microsoft.com/en-us/kb/2891274


http://technet.microsoft.com/en-au/library/cc262485.aspx

http://technet.microsoft.com/en-au/library/cc262485.aspx#section3





Type Nintex Forms 2013 Requirement

Operatingsystem

Microsoft Windows Server 2008 R2 or Microsoft Windows Server 2012(R2 is supported)

Browserclient

To design Nintex forms, use the following browser versions.l Minimum required: Microsoft Internet Explorer 8.xl Recommended: Microsoft Internet Explorer 10 or greaterTo run Nintex forms, use the following browser versions.l Minimum required: Microsoft Internet Explorer 8.x or latest versionof Chrome, Firefox, or Safari (Mac/iOS)

l Recommended: Microsoft Internet Explorer 10 or greater, or latestversion of Chrome, Firefox, or Safari (Mac/iOS)

Software l SQL Server 2008 R2 SP1, SQL Server 2012, or SQL Server 2014l Nintex Workflow 2013 if using Nintex Forms with Nintex Workflow(for the required version number, see the latest Nintex Forms 2013release notes on NintexConnect: https://community.nintex.com/docs/DOC-1161)

l Microsoft SharePoint Foundation 2013 or Microsoft SharePointServer 2013 (SP1 is supported)

Note: See the following Microsoft article. SharePoint 2013SP1 support in Windows Server 2012 R2.

Note: Publishing forms to Nintex Live may require speciallicensing for external or anonymous users. For moreinformation, reference SharePoint Server 2013 for InternetSites (SharePoint FIS) licensing details, such as thefollowing TechNetarticle: http://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspx.

Hardware No Nintex-specific requirements

Review topology considerations and best practicesThis section provides guidance on preparing your environment for Nintex installation.

High availabilityThis section describes topology considerations and best practices related to highavailability of Nintex databases.

Capacity considerations

Nintex Workflow follows the same scalability and limitations as SharePoint workflows;both Nintex and SharePoint use the workflow engine inside SharePoint.

Storage space

Size your Nintex databases according to the anticipated use of Nintex workflows and thelevel of complexity in those workflows (numbers of actions and tasks).

Content databases and performance

Nintex Workflow installation involves creating Nintex content databases and mappingthem to SharePoint content databases. Nintex content databases store workflow andtask history. For more information about database mapping for Nintex Workflow, seethe following NintexConnect article: Database Design Guide: Nintex Workflow.


-4-





http://blogs.technet.com/b/volume-licensing/archive/2013/08/08/licensing-how-to-sharepoint-server-2013-licensing-changes.aspx








During the planning phase, determine the optimal number of Nintex content databasesfor your workflow traffic. Ensuring a sufficient number of content databases canimprove performance of the workflow engine across all site collections in the farm aswell as facilitating backup, restore, and migration.

For site collections that use workflows, scale each SharePoint content database to oneof the following levels of granularity, depending on the degree of traffic in yourenvironment:

l Multiple web applications per SharePoint content databasel A single web application per SharePoint content databasel Multiple site collections (in a single web application) per SharePoint contentdatabase

l A single site collection (in a single web application) per SharePoint contentdatabase

For environments with high workflow traffic, we recommend using the most granularlevel: a single site collection in a single web application per SharePoint contentdatabase.

Following these guidelines optimizes performance by automatically distributingworkflows to corresponding content databases, thereby helping to avoid workflow time-out issues.

SharePoint and SQL Server

For high availability guidance specific to SharePoint and SQL Server, refer to Microsoftresources at msdn.microsoft.com and technet.microsoft.com, such as the followingarticles:

l Database Mirroring and Log Shipping (SQL Server)l Create a high availability architecture and strategy for SharePoint 2013l Capacity planning for SharePoint Server 2013l Estimate performance and capacity planning for workflow in SharePointServer 2013

l High Availability Solutions (SQL Server)l Workflow Scalability and Performance in Windows SharePoint Services 3.0

SecurityThis section describes topology considerations and best practices related to security ofNintex databases.

Ensuring security for SQL Server and SharePoint addresses the security needs ofNintex.

For security guidance specific to SharePoint and SQL Server, refer to Microsoftresources at msdn.microsoft.com and technet.microsoft.com, such as the followingarticles:

l Security planning for SharePoint 2013 farmsl Security Considerations for a SQL Server Installation

Backup and recoveryThis section describes topology considerations and best practices related to backup andrecovery of Nintex databases.

Databasemapping

Every SharePoint content database that contains site collections using Nintex Workflowshould be mapped to a Nintex Workflow content database. The ideal number ofSharePoint content databases per Nintex Workflow content database varies byenvironment. One-to-one mapping often serves smaller environments while others arebetter served by grouping SharePoint content databases by department or other


-5-


http://msdn.microsoft.com/en-us/library/ms187016.aspx

http://technet.microsoft.com/en-us/library/cc748824(v=office.15).aspx

http://technet.microsoft.com/en-au/library/ff758645.aspx

http://technet.microsoft.com/en-us/library/gg508755.aspx

http://technet.microsoft.com/en-us/library/gg508755.aspx

http://msdn.microsoft.com/en-us/library/ms190202.aspx

http://msdn.microsoft.com/en-au/library/dd441390.aspx

http://technet.microsoft.com/en-us/library/hh377941(v=office.15).aspx

http://msdn.microsoft.com/en-us/library/ms144228(v=sql.110).aspx





function and mapping each set of SharePoint content databases to a singleNintex Workflow content database. For more information, see Database Design Guide:Nintex Workflow.

Simultaneous backups and restores

To retain integrity of data, backup and restore the related databases at the same time.

For detailed instructions on backup and restore practices for Nintex Workflow, seeBackup and restore databases.

SharePoint and SQL Server

For backup and recovery guidance specific to SharePoint and SQL Server, refer toMicrosoft resources at msdn.microsoft.com and technet.microsoft.com, such as thefollowing articles:

l Plan for backup and recovery in SharePoint 2013l Back Up and Restore of SQL Server Databases

Set up topology for installationThis section provides guidance for preparing all servers in the SharePoint farm for theNintex installation process. This task involves ensuring that the required services arerunning and disabling antivirus software—on all servers in the farm.

Ensure services are runningThis section provides instructions for ensuring that the required services are running onall servers in the SharePoint farm.

Nintex Workflow installation requires that the following Microsoft Windows andSharePoint services be running.

Microsoft Windows services required:

l SharePoint Administrationl SharePoint Timer Service

SharePoint services required:

l Microsoft SharePoint Foundation Web Application (for Web Front End (WFE)servers)

l Microsoft SharePoint Foundation Workflow Timer Service

Note: On application servers running Microsoft SharePointFoundation Workflow Timer Service, the Microsoft SharePointFoundation Web Application service can be turned off by followingMicrosoft’s recommended practices. See Microsoft article 2674684.The Windows PowerShell command listed in the "Resolution" sectionmust be run on a Web Front End (WFE) server that has the MicrosoftSharePoint Foundation Web Application service running. In addition,we recommend running the IISRESET command and restarting theSharePoint Timer Service after running the Windows PowerShellcommand.

Nintex Forms installation does not require any services to be running other than thoserequired to run SharePoint.

To ensure that required Microsoft Windows services are running on all servers in the farm

1. On each server, open the Services Microsoft Management Console (MMC)snap-in.


-6-


http://help.nintex.com/en-US/nintex2016/current/Default.htm#cshid=dbdesign

http://help.nintex.com/en-US/nintex2016/current/Default.htm#cshid=dbdesign



http://msdn.microsoft.com/en-us/library/ms187048(v=sql.110).aspx

http://support.microsoft.com/kb/2674684





Note: For instructions on accessing the Services MicrosoftManagement Console (MMC) snap-in, see the Microsoft TechNetLibrary at http://technet.microsoft.com/en-us/library/cc772408.aspx.

2. For any required services that are not running, click Start.

To ensure that required SharePoint services are running on all servers in the farm

1. On the Central Administration Home page, click System Settings.2. Under Servers, click Manage servers in this farm.

Each server on the farm is listed, along with services running on that server.3. If required services are not running on a server, go back to the Central

Administration Home page, click System Settings, and then click Manageservices on this server under Servers.

4. On the Services on Server page, select the server from the Server list todisplay its SharePoint services.

5. For any required services that are not running, click Start.

Disable antivirus softwareThe installation process for Nintex Workflow and Nintex Forms requires antivirussoftware to be disabled.

To disable antivirus software on all servers in the farm

1. On each server, note original settings for antivirus software.You'll need the original settings to revert after installation.

2. On each server, disable all antivirus software.

Set up server used for running installersSetting up the server used for running installers involves temporarily disabling UserAccount Control (UAC), ensuring that the application pools are started, and ensuringthat Windows PowerShell scripts can be run by the installers.

Note: The Nintex Forms installer must be run on a front end server.

Note: The installers need to be run on a single server in the farm only. If youplan to use Nintex Live, choose a server that hosts SharePoint CentralAdministration. Doing so allows you to avoid extra steps when connecting andenabling Nintex Live.

To temporarily disable User Account Control (UAC)

1. On the server that you plan to use for running the installers, from ControlPanel, select Change User Account Control settings.

2. Note the original settings for User Account Control (UAC).You'll need the original settings to revert after installation.

3. Disable User Account Control (UAC).For instructions on disabling UAC, see the followingURL: http://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7


-7-


http://technet.microsoft.com/en-us/library/cc772408.aspx


http://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7

http://windows.microsoft.com/en-us/windows/turn-user-account-control-on-off#1TC=windows-7





To ensure that the application pools are started

1. On a server that can access the application pools, open IIS Manager.For instructions, see http://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspx.

2. Expand the server and then click Application Pools.Status is indicated for each application server, such as SharePoint - 80 andSharePoint Central Administration v4.

To ensure that Windows PowerShell scripts can be run by the installers

1. On the server that you plan to use for running the installers, determine ifWindows PowerShell script execution is set by group policy:

a. Open the Local Group Policy Editor (gpedit.msc); for instructions,see http://technet.microsoft.com/en-us/library/cc731745.aspx.

b. Navigate to Local Computer Policy > Computer Configuration> Administrative Templates > Windows Components > WindowsPowerShell.

c. Click Turn on Script Execution.d. In the Turn on Script Execution dialog box, determine if theEnabled setting is grayed out (unavailable).Unavailability of this setting indicates that group policy is used.

e. Navigate to Local Computer Policy > User Configuration> Administrative Templates > Windows Components > WindowsPowerShell.

f. Click Turn on Script Execution.g. In the Turn on Script Execution dialog box, determine if theEnabled setting is grayed out (unavailable).Unavailability of this setting indicates that group policy is used.

2. If group policy is used for script execution, ask your network administratorto do one of the following:

l Allow script execution policy to be set individually (turn off grouppolicy for that server).

l Set the policy to Unrestricted for the user and server to be usedfor installation.

When the ability to execute Windows PowerShell scripts is available, you cancontinue on to the next step in setting up the topology for installation.

Install Nintex products to production environmentThis section provides guidance for installing Nintex Workflow and Nintex Forms to yourproduction environment. Installation involves running the installers, deploying theprovided Nintex solutions, importing the Nintex license files, configuring databases,connecting and enabling Nintex Live, and activating Nintex features in SharePoint.

Obtain account with sufficient permissionsTo successfully install Nintex products, obtain a user account with sufficientpermissions.

Typical account used for Nintex installationIn most cases, the Farm Installation account (used to install SharePoint) satisfies thepermission requirements for the full installation process.


-8-


http://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspx







To identify the Farm Installation account

Note: By default, the SharePoint Central Administration v4 application pool isconfigured to run using the Farm Installation account.

1. Open IIS Manager.For instructions, see http://msdn.microsoft.com/en-us/library/vstudio/bb763170(v=vs.100).aspx.

2. Under your server, click Application Pools.3. Select SharePoint Central Administration v4.4. Under Edit Application Pool, click Advanced Settings.

The Farm Installation account is indicated in the Identity row under ProcessModel.


-9-








Minimum required permissionsInstallation and deployment of Nintex products requires an account with at least thefollowing permissions.

l SharePoint permissions:l Ability to modify farm properties (required to import the licensefile).Any user account in the Farm Administrators group has the ability tomodify farm properties. To view members of this group, navigate toCentral Administration > Security > Users > Manage the farmadministrators group.

l SharePoint_Shell_Access role membership for the SharePointconfiguration database, Central Administration database, and allSharePoint content databases.For instructions on provisioning this membership using WindowsPowerShell, see http://technet.microsoft.com/en-us/library/ff607596(v=office.15).aspx. For more information aboutaccount permissions and security settings in SharePoint 2013, seehttp://technet.microsoft.com/en-us/library/cc678863(v=office.15).aspx.

l SQL Server permissions:l Ability to create databases as well as modify permissions ondatabases.

l A Microsoft Windows-based login to SQL Server that is a member ofthe following roles:

l securityadmin fixed server rolel dbcreator fixed server rolel db_owner fixed database role for all databases in theserver farm that will be used during installation

l Windows PowerShell permissions:l SharePoint_Shell_Access role membership (required to access partsof SharePoint via Windows PowerShell).

l Ability to run Windows PowerShell scripts if script execution is setby group policy; needed for the server on which the installers arerun only.For more information, see "Set up server used for runninginstallers" on page 7.

l Windows permissions:l Membership of the Administrators group for every server in thefarm.To determine if a user account has local administrator rights on theserver, view the Administrators group: In the Services MicrosoftManagement Console (MMC) snap-in, expand Local Users andGroups, expand Groups, and double-click Administrators. If youraccount is not listed, note original status for reverting afterinstallation is complete, then add the account to the group. Forinformation about Local Users and Groups in the Services MicrosoftManagement Console (MMC) snap-in and instructions on addingaccounts to the Administrators group, seehttp://msdn.microsoft.com/en-us/library/ee250492(v=bts.10).aspx.

Obtain Nintex license filesMake sure your Nintex license file is up to date. Make sure each product license isexplicitly activated for the functionality that you want, such as Enterprise Edition.


-10-


http://technet.microsoft.com/en-us/library/ff607596(v=office.15).aspx




http://msdn.microsoft.com/en-us/library/ee250492(v=bts.10).aspx

http://msdn.microsoft.com/en-us/library/ee250492(v=bts.10).aspx





If you have questions about your license file, contact your Nintex partner or territorymanager.

Schedule deploymentTo minimize interruption of services, determine the best time for deployment toproduction.

Run the installerRun the installer for the products being installed.

In the installer, you have the option to install both Nintex Workflow and Nintex Forms.You also have the option of installing just one product.

You can download the installer file from the product download page of the NintexConnect site at https://community.nintex.com. For more information, contact yourNintex partner or territory manager.

Nintex Workflow installerThis section applies to installation of Nintex Workflow. If you are not installingNintex Workflow, you can skip this section.

To install Nintex Workflow

1. Set up a server for running the installers. See "Set up server used forrunning installers" on page 7.

2. Double-click the installer file to display the installation dialog box.Example installer file: NintexWorkflow2013Int.exe

Note: To run the installer with a user account other than the logged-in user account, press and hold SHIFT, right-click the installer file,select Run as different user, and then enter the credentials forthe desired account.

3. On the Welcome to the Installation Wizard page, click Next.4. On the License Agreement page, review the license, click I Agree, and then

click Next.5. Nintex Live: Choose the desired option.

l To install Nintex Live, select the check box for Install Nintex Liveand then click Next.

Note: Any currently installed version of Nintex Live isautomatically upgraded regardless of the selected option.

Note: For more information on Nintex Live, see "Connectand enable Nintex Live" on page 23. For licensinginformation, see www.nintex.com/licensing.

l To continue without installing Nintex Live, clear the check box forInstall Nintex Live and then click Next.


-11-


https://community.nintex.com/community/installation/product-downloads

https://community.nintex.com/

http://www.nintex.com/licensing





6. Click Yes to initiate adding the solution to SharePoint and then click Next.

Note: You can optionally select No to export the Nintex Workflowsolutions for manual deployment later. For instructions to manuallyexport and import solutions for deployment, see Manually exportand import solutions.

Installation status is indicated by messages and a progress bar.7. When installation is complete, click Close to close the installation dialog box.

The installer installs Nintex-named assemblies and SharePoint featureslocally. For more information, see "Nintex assemblies and features" onpage 29.The solutions are now available for deployment to your SharePoint farm. Forinstructions on deploying solutions, see "Steps for deploying solutions" onpage 16.

Nintex Forms installerThis section applies to installation of Nintex Forms. If you are not installingNintex Forms, you can skip this section.

To install Nintex Forms

Note: The Nintex Forms installer must be run on a front end server.

1. If you plan to use Nintex Forms with Nintex Workflow, make sure that theNintex Workflow solutions are already deployed to the required Webapplications.

2. Set up a server for running the installers. See "Set up server used forrunning installers" on page 7.

3. Double-click the installer file to display the installation dialog box.Example installer file: NintexForms2013Int.exe

Note: To run the installer with a user account other than the logged-in user account, press and hold SHIFT, right-click the installer file,select Run as different user, and then enter the credentials forthe desired account.

4. On the Welcome to the Installation Wizard page, click Next.5. On the License Agreement page, review the license, click I Agree, and then

click Next.The Installing page appears with a description of the Nintex Live installation.


-12-






6. Nintex Live: Choose the desired option.l To install Nintex Live, select the check box for Install Nintex Liveand then click Next.

Note: Any currently installed version of Nintex Live isautomatically upgraded regardless of the selected option.

Note: For more information on Nintex Live, see "Connectand enable Nintex Live" on page 23. For licensinginformation, see www.nintex.com/licensing.

l To continue without installing Nintex Live, clear the check box forInstall Nintex Live and then click Next.

7. On the Confirm Installation page, click Yes to initiate adding the solution toSharePoint and then click Next.Installation status is indicated by messages and a progress bar.

Note: You can optionally select No to export the Nintex Workflowsolutions for manual deployment later. For instructions to manuallyexport and import solutions for deployment, see Manually exportand import solutions.

8. When installation is complete, click Close to close the installation dialog box.The installer installs Nintex-named assemblies and SharePoint featureslocally. For more information, see "Nintex assemblies and features" onpage 29.The solutions are now available for deployment to your SharePoint farm. Forinstructions on deploying solutions, see "Steps for deploying solutions" onpage 16.

Manually export and import Nintex solutionsThe following steps detail how to manually export and import Nintex solutions.

Prerequisites: Windows PowerShell and either SharePoint 2010 Management Shell orSharePoint 2013 Management Shell must be run as administrator to import thesolutions.

To manually export Nintex solutions

1. Run the installation wizard and navigate to:Do you want to add the solution to SharePoint now?

2. Choose No, I wish to export the solution and deploy it manuallylater and then click Export.

3. Select the destination folder.Default value: Desktop.

4. Click OK.Now you can manually import the solutions using Windows PowerShell orSharePoint Management Shell.

To manually import a Nintex solution using Windows PowerShell

1. Add the Windows PowerShell snap-in to the current session by running thefollowing command.Add-PSsnapin Microsoft.SharePoint.PowerShell


-13-


http://www.nintex.com/licensing





2. Add the solution to the farm by running the following command.Add-SPSolution drive:\path\NameofSolution.wsp

where drive is the drive letter, path is the folder path, andNameofSolution.wsp is the name of the solution.Now you can import the license file. See "Import the license files" onpage 16.

To manually import a Nintex solution using SharePoint Management Shell

l Add the solution to the farm by running the following command.Add-SPSolution drive:\path\NameofSolution.wsp

where drive is the drive letter, path is the folder path, andNameofSolution.wsp is the name of the solution.Now you can import the license file. See "Import the license files" on page 16.

Deploy the solutionsThis section provides information about the solutions (.wsp files) included with theinstallers.

Solutions and required deployments

This section describes the solutions (.wsp files) included with the installers and indicatesrequired Web application deployments. For instructions on deploying solutions, see"Steps for deploying solutions" on page 16.

Solution name(ordered alphabetically)

Requireddeployments

All CANintexCommon.wsp Auto AutoNintexForms2013.wspNintex Forms 2013 web application-specific functionality

Auto Auto

NintexForms2013Core.wspNintexForms 2013 farm-wide functionality

Auto Auto

NintexForms2013BackwardsCompatibilityUI.wspNintex Forms 2013 solution for sites that run in 2010 mode(optional)

Note: For more information on running SharePoint2013 sites in 2010 mode, see "True "SharePoint 2010":instead of visual upgrade" in the following Microsoftarticle: What's new in SharePoint 2013 upgrade.

Yes No

NintexLiveCore.wspNintex Live

Auto Auto

NintexWorkflow2013.wspNintex Workflow 2013 web application- specific functionality

Yes Yes

NintexWorkflow2013Core.wspNintexWorkflow 2013 farm-wide functionality for servers withthe role "Application"

Auto Auto


-14-


https://technet.microsoft.com/en-us/library/ee617150.aspx





Solution name(ordered alphabetically)

Requireddeployments

All CANintexWorkflow2013BackwardsCompatibilityUI.wspNintex Workflow 2013 solution for sites that run in 2010 mode(optional)


Yes Yes

NintexWorkflow2013EnterpriseFeatures.wspNintex Workflow 2013 - Enterprise Edition (for Enterprisereporting)

Yes Yes

NintexWorkflow2013EnterpriseFeaturesBackwardsCompat.wspNintex Workflow 2013 - Enterprise Edition solution forrendering Enterprise features on sites that run in 2010 mode(optional)


Yes Yes

NintexWorkflow2013WFECore.wspNintex Workflow 2013 farm-wide functionality for servers withthe role "Web Front End"

Whenrequired

No

Legend:

All: All content Web applications

CA: Central Administration Web application

Auto: Globally deployed automatically via installer

When required: Manual deployment only, for Web Front End servers only.See "Installation error for web front end (WFE) servers: Nintex Workflow"on page 8.

Sequence of solution deployment

Use the following sequence when deploying your Nintex solutions.1. Nintex Workflow

a. NintexCommon.wspb. NintexWorkflow2013core.wspc. NintexWorkflow2013.wspd. Other Nintex Workflow solutions as desired, in any sequence

2. Nintex Forms

Note: If a backwards-compatible user interface solution was provided for theproduct and you decide to use it, deploy it after all other solutions for the givenproduct.


-15-








Steps for deploying solutions

Follow these instructions to deploy Nintex solutions to your SharePoint environment.

This topic assumes that the installers have already been run and the solutions havealready been imported.

If you have an Enterprise license, you need to deploy the Nintex Workflow enterprisefeature.

To deploy a Nintex solution

1. On the Central Administration Home page, click System Settings.2. In the Farm Management section, click Manage farm solutions.

The Solution Management page appears. Solution deployment status isindicated in the Status column; the Web applications to which the solutionsare deployed are indicated in the Deployed To column.If you manually exported the solutions, you must manually import them. Forinstructions, see Manually export and import solutions.

3. To deploy a solution to all content Web applications, do the following:

Note: Make sure you deploy the solution to all content Webapplications first (if required). Make sure you deployNintex Workflow solutions before Nintex Forms solutions (if usingNintex Forms with Nintex Workflow).

a. Display the Deploy Solution page: Click the solution that you wantto deploy and then click Deploy Solution.

b. In the Deploy When? section, select Now.c. In the Deploy To? section, select All content Web applications.d. Click OK.

4. To deploy a solution to the Central Administration Web application, do thefollowing:


b. In the Deploy When? section, select Now.c. In the Deploy To? section, select the URL for the Central

Administration Web application.d. Click OK.

Import the license filesFor full product functionality you must have a license issued by Nintex for each product.Each product license can be either a full production license or an evaluation license. Thelicense file must be imported into SharePoint Central Administration.

Make sure your Nintex license file is up to date. Make sure each product license isexplicitly activated for the functionality that you want, such as Enterprise Edition.

If you have questions about your license file, contact your Nintex partner or territorymanager.

To import each license file

1. On the Central Administration Home page, display the licensing page for yourproduct:


-16-






l For Nintex Workflow, click Nintex Workflow Management andthen click Licensing.

l For Nintex Forms, click Nintex Forms Management and thenclick Licensing.

2. On the selected licensing page, click Import.The page displays a Browse button.

3. Click Browse to locate your license file and then click Import.The licensing information is displayed.

4. Click OK.When all license files have been imported, you can proceed to configuredatabases for Nintex Workflow and Nintex Forms.

Configure databases and other itemsThis section provides the following links.

Nintex product configurationThis section provides guidance on configuration tasks for the Nintex products, includingconfiguring databases, activating web applications, enabling workflow actions,configuring email settings, and setting up LazyApproval.

This section applies to installation of Nintex Workflow. If you are not installingNintex Workflow, you can skip this section.

Configure databases for Nintex Workflow

This section provides instructions for Nintex Workflow database configuration.

Nintex Workflow requires a configuration database. While the configuration databasecan technically serve as the sole content database for Nintex Workflow, we recommendmultiple content databases to ensure high availability. For more information, see"Content databases and performance" on page 4.

To set up configuration and content databases

1. Create a Nintex configuration database:a. On the Central Administration Home page, click NintexWorkflow Management.

b. Click Database setup.c. In the Configuration Database section, click Create.d. On the Create configuration database page, enter the name of

your database server and enter a database name.

Note: The default value for Database Server is thedefault SharePoint database server.

e. Click OK.A database connection string appears in the ConfigurationDatabase section.


-17-






2. Add content databases as needed to store workflow and task history(optional; see "Content databases and performance" on page 4):

a. To redisplay the database setup page, on the CentralAdministration Home page, click Nintex WorkflowManagement and then click Database setup.

b. For each content database to be added, do the following:i. In the Content Databases section, click Add contentdatabase.

ii. In the Add content database page, enter the name ofyour database server and a database name; leave allother settings as default.

iii. Click OK.A database connection string appears in theConfiguration Database section.

c. (Optional.) Update content database parameters using theNWAdmin operation UpdateContentDatabaseParameters.

3. Map Nintex content databases to SharePoint content databases:a. To redisplay the database setup page, on the Central

Administration Home page, click Nintex WorkflowManagement and then click Database setup.

b. Click Manage database mappings.c. For each SharePoint content database corresponding to a site

collection that uses Nintex Workflow, select a Nintex Workflowcontent database under Map to Workflow Content Database.For more information about database mapping forNintex Workflow, see the following Nintex Connect article:Database Design Guide: Nintex Workflow.

d. Click OK.4. Run the IISreset command to implement the changes:

a. Start a command prompt as an administrator.For instructions, see the following TechNetarticle: http://technet.microsoft.com/en-us/library/cc947813(v=WS.10).aspx

b. Enter the following command.IISreset

Activate web applications

Nintex for SharePoint 2016 requires activation of web applications that will use theproduct.

To activate Nintex Workflow on web applications

1. On the Central Administration Home page, click Nintex WorkflowManagement

2. ClickWeb Application activation.The default web application name is automatically selected.

3. To activate all web applications for Nintex Workflow, select the check box forAll content web applications and then click Activate.

4. To activate a subset of web applications for Nintex Workflow, select eachweb application and then click Activate; repeat until all desired webapplications have been activated.


-18-



http://technet.microsoft.com/en-us/library/cc947813(v=WS.10).aspx

http://technet.microsoft.com/en-us/library/cc947813(v=WS.10).aspx





To activate Nintex Forms on a web application

1. On the SharePoint Central Administration Home page, click ApplicationManagement.

2. In the Web Applications section, click Manage web applications.3. In the Name column, select the web application on which you want to

activate Nintex Forms.For example, select SharePoint -80.

4. In the Web Applications ribbon, click Manage Features.The Manage Web Application Features dialog box appears.

5. In the Nintex Forms section, click Activate.After a short delay, the dialog box refreshes and the status is "Active."

6. Click OK.Enable actions for Nintex Workflow

This section provides instructions for enabling Nintex Workflow actions. Only the actionsyou enable are displayed in the Workflow designer.

To enable Nintex Workflow actions

1. On the Central Administration Home page, click Nintex WorkflowManagement.

2. Click Manage allowed actions.By default, for new installations, no actions are selected.

3. Click the check box in the heading row to enable all actions.Alternatively, to enable a subset of the available actions, select the checkbox for each desired action.Enabled actions become available in the Workflow designer.

4. Click OK.The web.config file for each web application is updated to list enabled actionsas safe controls.

Configure SharePoint email prerequisites

This section provides instructions for completing SharePoint email settings that arerequired for using LazyApproval and sending email from Nintex workflows. SharePointemail settings include configuring incoming email, confirming that required services arerunning, and ensuring that incoming emails are sent to the correct servers.

To configure incoming email for the farm

l See the following Microsoft article: Configure incoming email for a SharePoint2013 farm.SharePoint automatically populates the incoming email address for the farmusing the fully qualified domain of the server. To view or edit this address, goto the Central Administration Home page, click System Settings, and thenclick Configure Incoming E-mail Settings.


-19-








To confirm that required services are running

l On each server in your farm that is running the service Microsoft SharePointFoundation Incoming E-Mail, do the following:

For thisservice...

Do this to confirm that the service is running:

MicrosoftSharePointFoundationIncoming E-Mail

On the Central Administration Home page, click Manageservers on this farm (under System Settings).

MicrosoftSharePointFoundation WebApplication

On the Central Administration Home page, click Manageservers on this farm (under System Settings).

SMTP Reference the "Install and configure the SMTPservice" section of the following Microsoftarticle: Configure incoming email for a SharePoint 2013farm.

To ensure that incoming emails are sent to the correct servers (environments with multiplefront-end servers)

l Configure your load balancer to forward incoming emails to servers with theSMTP service enabled. Refer to your organization's SharePoint environmentdocumentation.

Configure Nintex Workflow email settings

This section provides instructions to configure email settings for Nintex Workflow.

To configure email settings for Nintex Workflow

1. Ensure that the SharePoint email prerequisites are met.For more information, see "Configure SharePoint email prerequisites" on theprevious page.

2. On the Central Administration Home page, click Nintex WorkflowManagement and then click Global Settings.

3. Under Email settings, enter the following details.l Outbound SMTP ServerEnter the URL used for outgoing mail in your SharePoint farm.Example: exchange.example.com

l From AddressExample: [email protected]

l Reply To AddressExample: [email protected]

Note: When using LazyApproval, the Reply To Addressmust be identical to the alias specified on the LazyApprovalsettings page. If you would like the workflow-triggeredemails to display an email address other than theconfigured LazyApproval account, then specify the differentemail address in From Address. Make sure that Reply ToAddress is the LazyApproval alias. This way the emailsender can be identified as a portal email address, such [email protected], while replies are sent to theLazyApproval alias, such as [email protected].


-20-


http://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspx#section2

http://technet.microsoft.com/en-us/library/cc262947(v=office.15).aspx#section2







4. Edit other settings on the page as needed for your environment.5. Click OK.

Set up LazyApproval

LazyApproval allows users to respond to requests in real language, even when on the goand without access to the SharePoint portal.

Setting up LazyApproval involves enabling LazyApproval for the server farm,configuring the LazyApproval alias for email, and optionally editing phrases recognizedand ignored by the LazyApproval process.

To set up LazyApproval

1. Ensure that SharePoint email prerequisites and Nintex Workflow emailsettings are configured.For more information, see "Configure SharePoint email prerequisites" onpage 19 and "Configure Nintex Workflow email settings" on the previouspage.

2. Go to the LazyApproval Settings page:a. On the Central Administration Home page, click NintexWorkflow Management.

b. Click LazyApproval settings.c. Click Enable / Disable LazyApproval for the current serverfarm.

Note: The page displays a message if either of thefollowing requirements is missing: email configuration forNintex Workflow and incoming email for the farm. Formore information, see "Configure SharePoint emailprerequisites" on page 19 and "Configure Nintex Workflowemail settings" on the previous page.

3. Under Enable LazyApproval via email, select Yes.4. In the Email alias text box, enter a unique account name.

The alias is the name that will be used as the email address that sends thenotifications and accepts the LazyApproval replies. The domain is determinedby the incoming email address for the farm. To view or edit this address, goto the Central Administration Home page, click System Settings, and thenclick Configure Incoming E-mail Settings.Example: [email protected]

Note: Ensure that the email alias complies with standard SharePointrequirements for email-enabled document libraries and lists. Forexample, the email alias cannot have an inbox in Exchange ashaving one prevents transmission to SMTP.

Note: Contacts in Active Directory are not required. There is noneed for Directory Management Service.


-21-






5. Click OK to save changes.

Note: If the Reply To Address setting under Nintex Workflow> Global settings differs from the Alias setting, then Nintex updatesthe Reply To Address setting to match the Alias setting. These emailsettings must be identical for LazyApproval to function.

The changes propagate to all servers within about 15 minutes.A list of phrases recognized and ignored by the LazyApproval processappears.

6. Add, edit, or remove phrases at your discretion.l To add a recognized phrase, click Create a new LazyApprovalterm for the current server farm and enter the desired phraseand outcome.

l To edit a recognized phrase, click the phrase, then change settingsin the Edit LazyApproval Phrase page.

l To remove a recognized phrase, click the phrase, then click Deletein the Edit LazyApproval Phrase page.

l To add an ignored phrase, click Create a term to ignore andenter the desired phrase.

l To remove an ignored phrase, click the Delete icon next to thephrase.

The changes propagate to all servers within about 15 minutes.7. (Optional) To implement changes immediately, run the IISreset command.

Nintex Forms configurationThis section applies to installation of Nintex Forms. If you are not installingNintex Forms, you can skip this section.

Configuring settings for Nintex Forms involves creating the database and activatingfeatures on the relevant web applications. The Nintex Forms database storesNintex Forms configuration and application settings.

To create the database for Nintex Forms

Note: The Nintex Forms database is required.

1. On the Central Administration Home page, click Nintex FormsManagement.

2. Click Manage database.When Nintex Forms is newly installed, the Manage Database page displaysdefault settings for the Nintex Forms database.

3. If needed, edit the database settings.4. Click OK to create the database.

To activate Nintex Forms on a web application

1. On the Central Administration Home page, click Application Management.2. In the Web Applications section, click Manage web applications.3. In the Name column, select the web application on which you want to

activate Nintex Forms.For example, select SharePoint -80.


-22-






4. In the Web Applications ribbon, click Manage Features.The Manage Web Application Features dialog box appears.

5. In the Nintex Forms section, click Activate.After a short delay, the dialog box refreshes and the status is "Active."

6. Click OK.

Connect and enable Nintex LiveThis section applies to installation of Nintex Live. If you are not installing Nintex Live,you can skip this section.

Connecting and enabling Nintex Live involves establishing a connection to Nintex Live,enabling Nintex Live for Nintex Workflow and Nintex Forms, registering the SharePointfarm, and optionally changing the managed user account that runs the Nintex Liveservices.

Following are the features requiring enabling for Nintex Live:

l Nintex Live for Nintex Workflow: Allows users to add web services from theNintex Live Catalog to the Nintex workflow actions toolbox.

l Also includes ability to enable Nintex Live features DocumentGeneration and External Start. For more information, see "EnableNintex Live features for Nintex Workflow" on page 26.

l Nintex Live Forms: Allows form designers to make designated forms availableto internet users via Nintex Live, with anonymous or secure access via third-party authentication providers.

To connect and enable Nintex Live

1. If Nintex Live was not installed from the installer, manually install anddeploy it. The Nintex Live solution is named nintexlivecore.wsp; you must also importall certificates from the “Certs” folder. This solution and its certificates arelocated in the installation folder for Nintex Workflow and forNintex Formswhen the relevant option is selected from the installer, causingthe solution to be exported for later deployment.

2. If Nintex Live was installed on a machine that does not host SharePointCentral Administration, run the following command:

a. Log on to the server hosting SharePoint Central Administration.b. Open a SharePoint PowerShell command prompt and run the

following command:install-liveservice

3. Make sure the certificates used by Nintex Live are available.a. On the Central Administration Home page, select Security.b. In the General Security section, click Manage trust.c. Review availability of the following certificates; if any are

unavailable, update to make them available.l Baltimore CyberTrust Root.crtl GTE CyberTrust Global Root.cerl Microsoft Internet Authority.cerl Microsoft Secure Server Authority.cerl Thawte Primary Root CA.cerl Thawte SSL CA.cer


-23-






4. Enable Nintex Live for Nintex Workflow.a. On the Central Administration Home page, select NintexWorkflow Management.

b. Click Live settings.c. In the Enable Nintex Live for Nintex Workflow section, clickEnable and then click OK.

5. Enable Nintex Live for Nintex Forms.a. On the Central Administration Home page, select Nintex FormsManagement.

b. Click Live Forms settings.c. In the Enable Nintex Live Forms section, click Enable.d. To allow Live Forms to be submitted by anonymous users over the

Internet, in the Allow anonymous form submissions section, selectYes, and then confirm the action.

Note: Allowing anonymous form submissions mayrequire Microsoft server internet licensing.

6. Establish a connection to Nintex Live.The Nintex Live Framework (installed with Nintex Live) requires a connectionto the internet to communicate with Nintex Live.

a. On the Central Administration Home page, select Nintex LiveManagement.

b. Click Health Checks.If the connection to Nintex Live can be established, a "Success"message is displayed in the status column.

Note: If your network requires a proxy server to accessthe internet, specify the server details in the Proxy serversection. These settings are specific to the Nintex LiveFramework and will be the only application allowedaccess to the internet.

7. Confirm that the server can access the Nintex Live URLs: From the serverrunning the Nintex Live services, navigate to each of the following URLs.

l https://live.nintex.coml https://liveservices.nintex.coml https://nintexlive.blob.core.windows.net/serviceiconl https://nintexrelay.servicebus.windows.netl https://cm.nintex.com (to connect to Connection Manager)l https://run.nintex.io (to connect to the Start Workflow API forExternal Start)

l https://prdswasbuwus01.servicebus.windows.net (to connect toExternal Start)

Nintex Live Relay Service accesses these URLs for both Nintex Workflow andNintex Forms.


-24-






8. Nintex Forms: Register the SharePoint farm for Nintex Live for MobileAccess.

a. If you have a firewall in place, make the following portsaccessible using outbound rules (the ports will be used by NintexLive Relay Service).

l 9351/HTTPl 80/HTTPl 443/HTTP

b. On the Central Administration Home page, click ApplicationManagement.

c. In the Service Applications section, click Manage services onserver.

d. Click Start for Nintex Live Relay Service.e. Click Nintex Forms Management and then click Manage LiveMobile Access.

f. Click Enable.9. Nintex Forms: Change the managed user account that runs the Nintex Live

services (optional).

Note: Nintex Forms 2013: The option to change this user account isavailable in v.3.0.3.1 and greater. Applicable services: Nintex LiveRelay Service.

a. Obtain a managed user account with the following access andgroup memberships:

l Appropriate access to the Nintex Forms and NintexWorkflow databases

l Access to the SharePoint lists and web applications thatmay be used by the Live service

l Membership in the Farm Administration group on theSharePoint farm

b. On the Central Administration Home page, click Security.c. Change the user account for Nintex Live Relay Service:

i. In the General Security section, click Configureservice accounts to display the Service Accountspage.

ii. In the first drop-down menu, selectWindows Service– Nintex Live Relay Service.

iii. From the Select an account for this componentdrop-down menu, select the appropriate user account.

iv. Click OK.


-25-






10. Confirm the ability to register SharePoint accounts with Nintex Live.a. Follow the instructions from Nintex Live registration in the Nintex

Mobile help to register a SharePoint account with Nintex live.If the registration wizard is not displayed, see "Registration error:Nintex Live" on page 11.

b. (Optional.) Confirm that the registered user is listed on the serverhosting SharePoint Central Administration: From the CentralAdministration Home page, click Nintex Forms Managementand then click Manage Live Mobile Users.

c. On a mobile device, sign in to the Nintex Mobile app using theMicrosoft account selected for Nintex Live registration.

Enable Nintex Live features for Nintex WorkflowThis section describes how to enable Nintex Live features for Nintex Workflow. If youare not installing features with this requirement, then you can skip this section.

Enabling Nintex Live features for Nintex Workflow involves configuration in SharePointCentral Administration.

Following are the Nintex Live features for Nintex Workflow.

l Nintex Live actionsl Document Generationl External Start

To enable Nintex Live features for Nintex Workflow

1. Make sure the server can connect to Nintex Live.2. On the Central Administration Home page, click Nintex WorkflowManagement and then click Live and external settings.

3. Enable the prerequisite service and then enable each desired feature.

Enable form-based authentication for Nintex MobileForm-based authentication (FBA) authenticates Nintex Mobile users through a webapplication sign-in page instead of the app sign-in screen. For more information aboutFBA for Nintex Mobile, see the help.

To enable FBA access to Nintex Mobile for the SharePoint farm

1. On the Central Administration Home page, click Nintex FormsManagement.

2. Click Manage FBA Mobile Access.3. Select Enable FBA.4. To change the token expiration period, select the desired value for SetNintex Mobile Token Expiry.

5. Click OK.

Note: If your network infrastructure uses a firewall, ensure that FBA endpointsare externally accessible by Nintex Mobile. FBA endpoints are located at thefollowing URL: <SiteUrl>/_vti_bin/NintexMobile/FBA/

Activate features in SharePointNintex Workflow must be activated on both the site collection and relevant sites;Nintex Forms needs activation on the site collection only.


-26-


http://help.nintex.com/en-US/mobile/Default.htm#cshid=1010

http://help.nintex.com/en-US/mobile/Default.htm#cshid=1010





To activate features on each relevant site collection in your SharePoint environment

1. From your top site level home page, access Site Settings (in SharePoint2013, use the gear icon).

2. In the Site Collection Administration section, click Site collectionfeatures.

3. Nintex Workflow: For each feature listed, in the sequence listed, clickActivate to activate.

a. Activate Nintex Workflow 2013.This feature allows SharePoint lists and libraries in this sitecollection to utilize Nintex Workflow features.After a short delay, the page refreshes and the feature statusbecomes “Active.”

b. Activate each additional feature desired.

Feature (listed inalphabetical order)

Description

Nintex Workflow 2013InfoPath Forms

Allows Nintex Workflow to use startforms and task forms designed withMicrosoft InfoPath.

Nintex Workflow 2013Reporting Web Parts

Note: This feature isonly available for theEnterprise edition ofNintex Workflow.

Allows the Nintex WorkflowEnterprise reporting web parts to beadded to sites in this site collection.

Nintex Workflow 2013Web Parts

Allows the Nintex Workflow webparts to be added to sites in this sitecollection.

c. If using Nintex Live, activate Nintex Workflow - Nintex LiveCatalog.This feature allows Nintex Workflow designers to browse theNintex Live Catalog.

Note: This feature is only available if Nintex Live wasinstalled and deployed.


-27-






4. Nintex Forms: For each feature listed, in the sequence listed, click Activateto activate.

a. Activate Nintex Forms Prerequisites Feature.This feature allows SharePoint lists and libraries in this sitecollection to utilize Nintex Forms features.After a short delay, the page refreshes and the feature statusbecomes “Active.”

b. Activate each additional feature desired.

Feature (listed inalphabetical order)

Description

Nintex Forms for NintexWorkflow

Allows Nintex Workflow in this sitecollection to utilize Nintex Formsfeatures.

Nintex Forms forSharePoint List Forms

Allows SharePoint lists and librariesin this site collection to utilizeNintex Forms features.

Nintex Live Forms Allows Nintex Forms designers topublish forms to Nintex Live

Nintex Forms features are now ready to use on all sites in the sitecollection; Nintex Workflow features require activation in eachrelevant site in the site collection.

To activate features on each relevant site in your SharePoint environment (Nintex Workflowonly)

This section applies to installation of Nintex Workflow. If you are not installingNintex Workflow, you can skip this section.

1. From your top site level home page, access Site Settings (in SharePoint2013, use the gear icon).

2. In the Site Actions section, click Manage site features.3. On the Site Features page, for each desired feature, click Activate.

Feature (listed in alphabeticalorder)

Functionality

Nintex Workflow 2013 Nintex WorkflowNintex Workflow 2013 EnterpriseReporting

Note: This feature is onlyavailable for the Enterpriseedition of Nintex Workflow.

Nintex Workflow Enterprisereporting

After a short delay for each feature activation, the page refreshes and thefeature status becomes “Active.”Nintex Workflow features are now ready to use on the site.

Confirm production installationThis section provides guidance on confirming successful installation of Nintex products.This confirmation involves testing Nintex functionality, confirming the installer andconfiguration tasks were completed, and reinstating original server settings.

Test Nintex functionalityMake sure you test functionality for Nintex on each SharePoint list and library expectedto use Nintex Workflow or Nintex Forms.


-28-






To test functionality for Nintex Workflow (SharePoint document library)

l Select the Library tab from the ribbon, clickWorkflow Settings, and thenselect Nintex Workflow to display the Nintex Workflow designer; addworkflow actions and publish.

To test functionality for Nintex Workflow (SharePoint list)

l Select the List tab from the List Tools ribbon, clickWorkflow Settings, andthen select Nintex Workflow to display the Nintex Workflow designer; addworkflow actions and publish.

To test functionality for Nintex Forms (SharePoint list only)

l Select the List tab from the List Tools ribbon and then click Nintex Forms todisplay configuration options for the default Nintex form.

Confirm installer and configuration tasks (optional)As part of confirming successful installation, you can confirm that expected installer andconfiguration tasks were completed. Following is a summary of these tasks.

l Nintex assemblies and featuresl Solution deploymentsl Licensingl Databasesl Enabled actions (safe controls)

Nintex assemblies and features

As part of confirming installation, you can check for Nintex-named assemblies andSharePoint features. The Nintex installers install assemblies and SharePoint featureslocally.

Assemblies are installed into the Global Assembly Cache (GAC). Both .NET Framework3.5 and .NET Framework 4.0 assemblies are installed.

SharePoint features are installed into the SharePoint 2013 hive.

Solution deployments

During installation, the Nintex solutions need to be deployed to all required Webapplications. For more information, see "Steps for deploying solutions" on page 16.

To view deployment status for solutions in the farm


The Solution Management page appears. Solution deployment status isindicated in the Status column; the Web applications to which the solutionsare deployed are indicated in the Deployed To column.

Licensing

During installation, the license files for installed products need to be imported intoSharePoint Central Administration as indicated in "Import the license files" on page 16.

To view imported license files

l On the Central Administration Home page, click the option for your product(Nintex Workflow Management or Nintex Forms Management) andthen click Licensing.

l For Nintex Live, click Nintex Live Management and then click Healthchecks.


-29-






Databases

Successful installation of Nintex Workflow requires that a configuration database existas well as any additional Nintex content databases needed for your environment; allNintex content databases must be mapped to the corresponding SharePoint contentdatabases. For more information, see "Content databases and performance" on page 4.

For Nintex Forms, confirm that the automatically created database exists. See"Nintex Forms configuration" on page 22.

In addition to ensuring that all required databases are set up, confirm that the webapplication user accounts are members of the custom database role WSS_Content_Application_Pools for all Nintex databases. This membership configuration is completedby the Nintex installers; the WSS_Content_Application_Pools database role has allrequired SELECT and EXECUTE rights to the database required for Nintex functionality.

To confirm database role memberships for web application user accounts

1. Identify the names of all web applications used by Nintex.a. On the Central Administration Home page, click ApplicationManagement.

b. In the Web Applications section, click Manage webapplications.Example name of web application: SharePoint - 80

2. Identify the user account for each web application.a. On the Central Administration Home page, click Security.b. In the General Security section, click Configure serviceaccounts.

c. In the Service Accounts page, select the web application nameidentified in the previous step.

Note: The web application name is prefixed by the phrase"Web Application Pool." Example: Web Application Pool - SharePoint - 80

The user account for the web application is identified under Selectan account for this component.Example user account: NINTEXTEST/PM13-SPWebApp01


-30-






3. View the database role membership for each user account on all Nintexdatabases.

a. View the login user accounts for the database server containingthe Nintex databases: In Microsoft SQL Server ManagementStudio, expand the database server folder, expand the Securityfolder, and then expand the Logins folder.

b. Double-click the user account identified in the previous step todisplay the properties dialog box.

c. Click the User Mapping page to view the databases mapped tothe login user account.

d. For each Nintex database:i. Confirm that the check box for the database isselected.

ii. Select the database to display the database rolememberships, and then confirm that the check box forWSS_Content_Application_Pools is selected.

If the check box for the database is not selected, or if the checkbox forWSS_Content_Application_Pools is not selected, goahead and select it and then click OK.

Enabled actions (safe controls)

When workflow actions are enabled in SharePoint, the web.config files for the webapplications are updated with "safe controls."

To confirm that web.config files were updated with Nintex "safe controls"

l From IIS Manager, right-click the web application, select Explore to view itsfiles in Windows Explorer, and then open the web.config file in a text editor.Example excerpt from web.config file indicating enabled actions: <SafeControl Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral,PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls"TypeName="*" Safe="True" />

Reinstate original server settingsWhen installation is complete, reinstate original server settings across the farm.

On the server used for running the installers, reinstate the following server settings(see "Set up server used for running installers" on page 7):

l User Account Control: reinstate at the original levell User account rights: If you added the Farm Installation account (or other useraccount used for installation) to the Administrators group for the server onwhich you installed Nintex, remove the account from the group. Leaving theaccount in the Administrators group results in report warnings from theSharePoint Health Analyzer.

l Group policy for script execution: reinstate if needed

On all servers in the farm, reinstate the following server settings (see "Disable antivirussoftware" on page 7):

l Antivirus software: re-enable original programs

AddendumThis section contains the following links related to installation of Nintex products.


-31-






Installation Guide:Nintex Workflow 2013 and

Nintex Forms 2013

Last updated Monday, May 14, 2018

Legal noticesFor the latest information, please see http://en-us.nintex.com/company/legal.


-i-


http://en-us.nintex.com/company/legal





Contents

Introduction: Install Nintex for SharePoint 2013 1Worksheets (optional) 1

Installation checklist 1

Installation worksheet 2Plan your test and production environments 3

System requirements: Nintex for SharePoint 2013 3

Review topology considerations and best practices 4

Set up topology for installation 6

Set up server used for running installers 7Install Nintex products to production environment 8

Obtain account with sufficient permissions 8

Obtain Nintex license files 10

Schedule deployment 11

Run the installer 11

Import the license files 16

Configure databases and other items 17

Connect and enable Nintex Live 23

Enable Nintex Live features for Nintex Workflow 26

Enable form-based authentication for Nintex Mobile 26

Activate features in SharePoint 26

Confirm production installation 28Addendum 31

Nintex Workflow Exchange Connector Service installation 1

Manually export and import Nintex solutions 4

Uninstall Nintex Workflow and Nintex Forms 5Troubleshoot deployment 5


Issues 7


-ii-






Nintex Workflow Exchange Connector Service installationThis guide contains the following topics helpful for installing Nintex Workflow ExchangeConnector Service.

IntroductionNintex Workflow Exchange Connector Service is a web service that communicates withMicrosoft Exchange.

System requirementsNintex Workflow Exchange Connector Service has the following system requirements.

Operating System: Microsoft Windows Server 2008 R2, Microsoft Windows Server 2012,or Microsoft Windows Server 2012 R2

Software: Install and correctly configure the following.

l Microsoft Exchange Server 2013, 2010, or 2007l Internet Information Services (IIS) 7.5, 7.0, or 6.0

Install Nintex Workflow Exchange Connector ServiceThis topic describes how to install Nintex Workflow Exchange Connector Service.

If your Microsoft Exchange environment is implemented across multiple machines,install Nintex Workflow Exchange Connector Service on the machine running theExchange Mailbox role.

To install Nintex Workflow Exchange Connector Service

1. Define the following user accounts.l IIS application pool account: Used as the identity under which theweb service IIS application pool runs.Type: Domain userMember of: Exchange Organization, Administrators, LocalAdministrators, Local IIS_WPG

l Web service account: Used as a service user account toauthenticate calls from Nintex Workflow and restrict access to theweb service.Type: Local UserMember of: Local Users

2. Set up an application pool for Nintex Workflow Exchange Connector Service(new application pool recommended) and configure it to use theIIS application pool account defined in the previous step.

Note: For Exchange 2013, configure the application pool to use .NETframework version v4 (under Basic Settings or Advanced Settings,depending on IIS version).

3. Note the following for use in the installer.l Site (for example, Default Web Site selection)l Virtual directory (for example, Nintex.Workflow.ECS)l Application pool (for example, DefaultAppPool selection)

4. Log in to the server using an administrator account with sufficient privilegesto execute Microsoft Installers (.msi files).


-1-






5. Execute the installer file ExchangeConnectorService.msi by either double-clicking it or running it from the command prompt (run as administrator).

Note: The installer file ExchangeConnectorService.msi is located inthe “Supporting” folder created when you choose to export thesolution in the Nintex Workflow installer.

The Nintex Workflow Exchange Connector Service installer wizard appears.6. On the Exchange Connector Service installation wizard page, click Next.7. On the License agreement page, confirm acceptance of the end-user license

agreement and then click Next.8. On the Select site and virtual directory page, edit the following fields as

needed and then click Next.l Site (for example, Default Web Site selection)l Virtual directory (for example, Nintex.Workflow.ECS)l Application pool (for example, DefaultAppPool selection)

9. On the Confirm installation page, click Next.After a short while, the Installation complete page appears.

10. On the Installation complete page, click Close to exit the installer.

Complete post-installation tasksThis topic describes how to complete post-installation tasks.

Post-installation tasks include authorizing the web service user, configuring theapplication pool identity, and setting the authentication method for the virtual directory.

To authorize the web service user

1. Locate the web.config file for the virtual directory specified duringinstallation.The location of the virtual directory folder depends on the site specifiedduring installation. For example, if you selected default web site andspecified Nintex.Workflow.ECS for the virtual directory, then the path to theweb.config file is as follows.C:\Inetpub\wwwroot\Nintex.Workflow.ECS\web.config

2. Right-click the web.config file and select Edit.3. Within the <authorization> section of the web.config file, replace [local

windows account] with the web service account created during installation.Original <authorization> section:<authorization><allow users=”[local windows account]”/><deny users=”*”/></authorization>

Example of revised <authorization> section:<authorization><allow users=”SystemName\WebServiceUser”/><deny users=”*”/></authorization>

4. Save the web.config file, ensuring that no other changes are made.You are now ready to configure the application pool identity.

To configure the application pool identity

Follow the instructions for your version of IIS (Internet Information Services).


-2-






IIS 7 or 7.5 instructions for configuring the application pool identity

1.Open IIS Manager. For instructions, see the Microsoft article "How to:Open IIS Manager."

2.Edit properties for ECSAppPool: In the IIS Manager window, select theApplication Pools folder to list its contents, right-click ECSAppPool,and then select Advanced Settings to display the Advanced Settingsdialog box.

3.Edit the Identity property: Expand the Process Model section, click theellipsis (...) for Identity, and complete the following configuration.

lChoose to use a custom account.lEnter the credentials of the application pool account createdduring installation.lFor Exchange 2013, configure the application pool to use.NET framework version v4 (right-click and select Basic Set-tings).

4. Save changes and close the Advanced Settings dialog box.You are now ready to set the virtual directory authentication method.

IIS 6 instructions for configuring the application pool identity


2.Edit properties for ECSAppPool: In the IIS Manager window, expandthe Application Pools folder, right-click ECSAppPool, and thenselect Properties to display the Properties dialog box.

3.Select the Identity tab and complete the following configuration.lChange the identity to Configurable.lEnter the credentials of the application pool account createdduring installation.lFor Exchange 2013, configure the application pool to use.NET framework version v4 (right-click and select Basic Set-tings).

4.Click OK twice to close the Properties dialog box.5. Ensure that ECSAppPool is started: Right-click ECSAppPool. If not yet

started, click Start.You are now ready to set the virtual directory authentication method.

To set the virtual directory authentication method

Follow the instructions for your version of IIS (Internet Information Services).IIS 7 or 7.5 instructions for configuring the virtual directory authenticationmethod


2.Edit properties for the virtual directory specified duringinstallation: Expand the Web Sites folder, expand the site folder, andselect the virtual directory folder to display available selections in thepane on the right.


-3-


https://msdn.microsoft.com/en-us/library/bb763170.aspx










3.In the pane on the right, within the IIS section, double-clickAuthentication and then complete the following configuration.

lEnsure that “Anonymous Authentication” is set to Disabled(right-click to set).lEnsure that “Basic Authentication” and “Windows Authentic-ation” are set to Enabled (right-click to set).

You have now completed all post-installation tasks and you can nowconnect to Exchange from Nintex workflows. For more information,see "Connect to Exchange from Nintex workflows" below.

IIS 6 instructions for configuring the virtual directory authentication method


2.Edit properties for the virtual directory specified duringinstallation: Expand the Web Sites folder, expand the site folder, right-click the virtual directory folder, and select Properties.

3.In the Properties dialog box, select the Directory Security tab, clickEdit... in the Authentication and access control section, and then com-plete the following configuration.

lEnsure that Enable anonymous access is unchecked.lSelect the check box for either Integrated Windows authen-tication or Basic authentication.

4. Click OK twice to close the Properties dialog box.You have now completed all post-installation tasks and you can nowconnect to Exchange from Nintex workflows. For more information,see "Connect to Exchange from Nintex workflows" below.

Connect to Exchange from Nintex workflowsThis topic describes how to define the web service URL and account credentials for theaction Provision User In Exchange.

The action Provision User In Exchange connects to Microsoft Exchange to provision amailbox for the specified user.

When configuring this action, specify the web service URL as the path to NintexWorkflow Exchange Connector Service (EmailProvisioning.asmx) and specify thecredentials for an authorized web service account. You can confirm authorized webservice accounts by reviewing the web.config file for the virtual directory.

In the following example web service URL, the mycompany.com website contains thevirtual directory "siteECS" that itself contains the web service"EmailProvisioning.asmx"—both created by the Nintex Workflow Exchange ConnectorService installer.

Example: http://www.mycompany.com/siteECS/EmailProvisioning.asmx

Manually export and import Nintex solutionsThe following steps detail how to manually export and import Nintex solutions.

Prerequisites: Windows PowerShell and either SharePoint 2010 Management Shell orSharePoint 2013 Management Shell must be run as administrator to import thesolutions.

To manually export Nintex solutions

1. Run the installation wizard and navigate to:Do you want to add the solution to SharePoint now?

2. Choose No, I wish to export the solution and deploy it manuallylater and then click Export.


-4-








3. Select the destination folder.Default value: Desktop.

4. Click OK.Now you can manually import the solutions using Windows PowerShell orSharePoint Management Shell.

To manually import a Nintex solution using Windows PowerShell

1. Add the Windows PowerShell snap-in to the current session by running thefollowing command.Add-PSsnapin Microsoft.SharePoint.PowerShell

2. Add the solution to the farm by running the following command.Add-SPSolution drive:\path\NameofSolution.wsp

where drive is the drive letter, path is the folder path, andNameofSolution.wsp is the name of the solution.Now you can import the license file. See "Import the license files" onpage 16.

To manually import a Nintex solution using SharePoint Management Shell

l Add the solution to the farm by running the following command.Add-SPSolution drive:\path\NameofSolution.wsp

where drive is the drive letter, path is the folder path, andNameofSolution.wsp is the name of the solution.Now you can import the license file. See "Import the license files" on page 16.

Uninstall Nintex Workflow and Nintex FormsThis section provides guidance for uninstalling Nintex Workflow and Nintex Forms.

To remove for reinstall:

l Run the IISreset command on all servers in the farm to ensure that Nintexassemblies are not write-locked. Make sure you run this command after afailed installation of the installer package.

l Retract and remove Nintex solutions from the farm, first for content webapplications, and then for Central Administration. For retraction and removalinstructions, refer to the following MSDNarticle: http://msdn.microsoft.com/en-us/library/office/aa543958(v=office.14).aspx.

To remove completely (no reinstall intended):

l Remove all Nintex entries from the relevant web.config files. For moreinformation, see "Enabled actions (safe controls)" on page 31.

l Remove all Nintex assemblies. For more information, see "Nintex assembliesand features" on page 29.For more detailed guidance on complete removal of Nintex Workflow andNintex Forms, see the following uninstall documents on Nintex Connect.Uninstall Nintex Workflow 2013Uninstall Nintex Forms 2013

Troubleshoot deploymentThis section describes ways to narrow down deployment problems as well as resolutionsfor deployment issues that may come up.


Issues 7


-5-


http://msdn.microsoft.com/en-us/library/office/aa543958(v=office.14).aspx

http://msdn.microsoft.com/en-us/library/office/aa543958(v=office.14).aspx







Identify the problemThis section describes methods for narrowing down problems with solution deployment.

Deploy test solution packagesDeployment issues with the Nintex Workflow solution package(nintexworkflow2013.wsp) may indicate an issue with the SharePoint environment. Ifyou suspect issues with the SharePoint environment, you can deploy test solutionpackages to determine if the deployment issues persist.

The following test solution packages are available from Nintex:

l TestingSolutionGlobal.zip: This solution deploys globally; no URL needs to bespecified. The solution creates the following file:C:\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\15\TEMPLATE\TestingSolutionGlobal.txt

Note: If you don't see the file in the above location, check the pathfor the SharePoint 2010 hive: C:\Program Files\CommonFiles\Microsoft Shared\Web ServerExtensions\14\TEMPLATE\TestingSolutionGlobal.txt

If Solution 1 does deploy correctly, then please try Solution 2 as well, which isslightly more advanced.

l TestingSolutionForWebApps.zip: This solution requires selection of a webapplication. The solution creates the following file:C:\Program Files\Common Files\Microsoft Shared\Web ServerExtensions\15\TEMPLATE\TestingSolutionForWebApps.txt

Note: If you don't see the file in the above location, check the pathfor the SharePoint 2010 hive: C:\Program Files\CommonFiles\Microsoft Shared\Web ServerExtensions\14\TEMPLATE\TestingSolutionForWebApps.txt

The solution also deploys a file called SimpleSolution.dll to the GAC and addsan entry to the web.config file for the web application as follows:<SafeControl Assembly="SimpleSolution, Version=1.0.0.0, Culture=neutral,PublicKeyToken=a10b52b9b77b11de" Namespace="SimpleSolution" TypeName="*"Safe="True" />

Note: The SimpleSolution.dll contains no code that executes.

To deploy test solution packages

1. Download the test solution packages from the following URLs: http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.ziphttp://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip

2. Run the following command to add the solutions to the solution store:stsadm.exe -o addsolution -filename <path to wsp file>

For a mapping of Stsadm operations and their equivalent WindowsPowerShell cmdlets, see the following Microsoft TechNetarticle: http://technet.microsoft.com/en-us/library/ff621081.aspx


-6-


http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip

http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip

http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip

http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip

http://technet.microsoft.com/en-us/library/ff621081.aspx





3. Deploy the test solution packages from Central Administration. Forinstructions, see "Steps for deploying solutions" on page 16.If deployment does not successfully complete with one or more of the testsolution packages, the SharePoint environment may have an issue. Wesuggest contacting Microsoft for additional support with your SharePointenvironment.If deployment successfully completes with both test solution packages,contact Nintex Support.

Review SharePoint ULS log filesThe SharePoint Unified Logging Service (ULS) log files may contain helpful informationfor troubleshooting issues with deployment of solution packages.

For example, the following error suggests a critical timer job error related to internalSharePoint problems persisting objects to the database. These errors also mention an"update conflict" as experienced when attempting solution deployment. This underlyingissue may be preventing solution deployment and should thus be resolved. ContactMicrosoft for additional support if presented with this error.

“The Execute method of job definitionMicrosoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition(ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) threw an exception. Moreinformation is included below. An update conflict has occurred, and you must re-try this action. The object IndexingScheduleJobDefinition Name=IndexingSchedule Manager on servername Parent=SearchService Name=OSearch isbeing updated by DOMAIN\username, in the OWSTIMER process, on machineSERVERNAME. View the tracing log for more information about the conflict."

By default, ULS logs are located in the SharePoint hive. For example, the defaultlocation for SharePoint 2013 ULS logs is %ProgramFiles%\Common Files\MicrosoftShared\Web Server Extensions\15\Logs.

Note: For more information about ULS logging, see the following MSDNarticle. http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspx.

In your review of the log files, search for logged information during the time range inwhich the solution was scheduled to be deployed.

To aggregate all log files from SharePoint servers

l Use the Merge-SPLogFile cmdlet in a SharePoint Management Shell window.

IssuesThis section provides guidance for resolving common issues related to deployment.

Installation error for "Admin SVC": Nintex Forms 2013Symptom

The installer displays the following error message:

“Admin SVC must be running in order to create deployment timer job.”

Cause

The Microsoft Windows service SharePoint Administration is not running.

Resolution

Make sure that the service is running. For instructions, see "Ensure services arerunning" on page 6.


-7-


http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspx

http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspx






Installation error for "RPC server": Nintex WorkflowSymptom

During installation of Nintex Live and Nintex Workflow on a multi-server farm thefollowing error message appears:

"The RPC server is unavailable"

This message may indicate upgrade or installation issues on one or more servers in thefarm for one or more of the following services:

Nintex Live Workflow Queue Service Recycle

Nintex Workflow Start ServiceCause

Possible causes for this error include firewall and security restrictions for affectedservers.

Resolution

Manually install or upgrade the Nintex LiveWorkflow Queue Service andNintex Workflow Start Service on each server in the farm using the following procedure.

1. In SharePoint Management Shell, run the following script for theNintex Live Workflow Queue Service:$path =

[Microsoft.SharePoint.Utilities.SPUtility]::GetVersionedGenericSetupPath("bin\NintexWorkflow\Nintex.Workflow.Live.QueueService.exe", 15)

$serviceName = "Nintex Live Workflow Queue Service"

New-Service -Name $serviceName -DisplayName $serviceName -BinaryPathName $path

2. In SharePoint Management Shell, run the following script for theNintex Workflow Start Service:$path =

[Microsoft.SharePoint.Utilities.SPUtility]::GetVersionedGenericSetupPath("bin\NintexWorkflowStart\Nintex.Workflow.Start.Service.exe", 15)

$serviceName = "Nintex Workflow Start Service"

New-Service -Name $serviceName -DisplayName $serviceName -BinaryPathName $path

3. Run the IISReset command and restart the SharePoint Timer Service.4. To start the service on the current server, do the following:

a. On the Central Administration Home page, click ApplicationManagement.

b. In the Service Applications section, click Manage services onserver.

c. On the Services on Server page, select the desired server.d. Click Start for Nintex Live Workflow Queue Service.e. Click Start for Nintex Workflow Start Service.

Installation error for web front end (WFE) servers: Nintex WorkflowSymptom

The following message appears when installation is complete for Nintex Workflow.

Found Server(s) with ‘Web Front End’ Server Role:

[server-name]

Manual deployment of NintexWorkflow2013WfeCore.wsp solution on each listed WFEserver is required.


-8-






where [server-name] is a server detected to have the Web Front End server role

Cause

The installer could not deploy the solution to the indicated WFE servers.

Resolution

Manually deploy the version-specific solution on each WFE server using the PowerShellscript InstallWfeCoreLocal.ps1. Instructions follow.

1. Record the names of the WFE servers indicated in the installer message.

Note: You can rerun the installer to view the message again.

2. Export the solutions from the installer by rerunning the installer and selectingthe export option.

a. Double-click the installer file to display the installation dialog box.b. On the Welcome to the Installation Wizard page, click Next.c. On the License Agreement page, review the license, click IAgree, and then click Next.

d. For Nintex Live, choose the desired option.e. On the page “Do you want to add the solution to SharePoint now?,”

select No, I wish to export the solution and deploy itmanually later.

f. Save the exported files to a folder of your choice.3. In the folder containing the exported files, open the "Workflow" folder and

copy the following files.l InstallWfeCoreLocal.ps1l NintexWorkflow2013WfeCore.wsp

4. On each WFE server indicated in the installer message, do the following.a. Paste the copied files.b. Using PowerShell with administrative privileges, run the following

file.InstallWfeCoreLocal.ps1The script deploys the solution locally. You can confirmdeployment using Central Administration.

LazyApproval issues occurFor help troubleshooting LazyApproval issues, see the following Nintex Connectarticle: LazyApproval Guide.

Nintex icons missing from Central AdministrationSymptom

Nintex icons are missing from Central Administration.

Cause

The Central Administration feature is not activated. It's possible that theNintex Workflow or Nintex Forms solution was deployed to the front-end web serversbut not to the server hosting SharePoint Central Administration.

Resolution

To resolve this issue, deploy the Nintex Workflow and Nintex Forms solutions to theCentral Administration Web application; if needed, activate the relevant Nintex featuresmanually using Stsadm commands.


-9-







To deploy the solutions to Central Administration


The Solution Management page appears. Solution deployment status isindicated in the Status column; the Web applications to which the solutionsare deployed are indicated in the Deployed To column.

3. Deploy the Nintex Workflow and Nintex Forms solutions to the CentralAdministration Web application:


b. In the Deploy When? section, select Now.c. In the Deploy To? section, select the URL for the Central

Administration Web application.d. Click OK.

To activate Nintex Workflow features on Central Administration

l Run the following command, where http://centraladminurl:port is replacedwith the URL and port for the Central Administration Web application.stsadm.exe -o activatefeature -name nintexworkflowadmin -url http://centraladminurl:port

To activate Nintex Forms features on Central Administration

l Run the following command, where http://centraladminurl:port is replacedwith the URL and port for the Central Administration Web application.stsadm.exe -o activatefeature -name NintexFormsAdminWeb -url http://centraladminurl:port

Nintex Live Workflow Queue Service failed to startSymptom

The Nintex Live Workflow Queue Service failed to start and the following error messageappears:

"No connection could be made because the target machine actively refused it"

Cause

This message indicates a firewall issue.

Resolution

Confirm accessibility of all required ports and Nintex Live URLs using the followingprocedure.

1. If you have a firewall in place, make the following ports accessible (the portswill be used by NintexLiveWorkflow Queue Service).

l5671/TCPl5672/TCPl443/HTTP

Note: Note: Nintex uses Advanced Message Queuing Protocol(AMQP) over TCP traffic for Service Bus brokered messaging, whichrequires ports 5671 and 5672 to both be open for AMQPcommunication. By default, port 5671 is used by Secure AMQP.


-10-






2. Confirm that the server can access the NintexLive URLs: From the serverrunning the Nintex Live Workflow Queue Service, navigate to each of thefollowing URLs.

lhttps://live.nintex.comlhttps://liveservices.nintex.comlhttps://nintexlive.blob.core.windows.net/serviceiconlhttps://nintexrelay.servicebus.windows.net/

3. To start the service on the current server, do the following:a. On the Central Administration Home page, click ApplicationManagement.


c. Click Start for Nintex Live Workflow Queue Service.

Nintex Live: Multiple Workflow actions run in parallel may take hours to com-pleteSymptom

Processing takes hours to complete when multiple Workflow actions are run in parallelon different servers in a SharePoint farm topology.

Cause

The Nintex Live Workflow Queue Service has been enabled on two or more servers. As aresult, the queue service generates a Live event that slows down processing times.

Resolution

Do not enable the Nintex Live Workflow Queue Service on more than one server in afarm topology.

Registration error: Nintex LiveSymptom

The following message appears when a user attempts to register with Nintex Live byclicking the SharePoint user name, selecting Nintex Mobile Apps, and then selectingRegister with Nintex Live.

"An error occurred during the registration process."

Cause

This error may be caused by an inability to connect to Nintex Live.

Resolution

Make sure that the SharePoint site can connect to Nintex Live.


-11-






l Confirm that Nintex Live is fully connected and enabled. For instructions, see"Connect and enable Nintex Live" on page 23.

l Confirm connectivity to the Nintex Live relay service bus athttp://nintexrelay.servicebus.windows.net.Follow Microsoft best practices for troubleshooting service bus connectivity.For more information, see the Microsoft article athttp://social.technet.microsoft.com/wiki/contents/articles/2055.troubleshooting-connectivity-issues-in-the-azure-appfabric-service-bus.aspx.

l As part of troubleshooting: l Review verbose log files for the Nintex Live relay service.For instructions on enabling verbose logging and reviewing the logfiles, see the related procedure below.If you find any proxy errors in the log, contact your networkinfrastructure team.

l Restart the Nintex Live relay service using the procedure below.l Check for blocked IP addresses using the procedure below.l Check for any proxy or firewall rules that isolate specific IPaddresses.If you find any such rules, contact your network infrastructure team.

l Retry Nintex Live registration: Click the SharePoint user name todisplay the context menu, select Nintex Mobile Apps, and thenselect Register with Nintex Live.

To check for blocked IP addresses

1. With the help of the network administrator, trace the connections by openingthe proxy and firewall servers.

2. Compare the traced connections to the known reserved addresses.See http://blogs.msdn.com/b/narahari/archive/2011/08/01/ip-range-for-windows-azure-platform-identifying-connectivity-issues.aspx; refer toMicrosoft sites for the latest information on identifying connectivity issueswith Windows Azure.

3. If any IP addresses used by the service bus are blocked, then contact yournetwork infrastructure team to resolve the situation.

To enable verbose logging for the Nintex Live Relay Service and review log files

1. In a text editor, open the relay service configuration file.By default, the file is located in the SharePoint hive, under /BIN/NintexLive.For example, the default location is %ProgramFiles%\Common Files\MicrosoftShared\Web Server Extensions\15\BIN\NintexLive\Nintex.Live.RelayService.exe.config.


-12-


http://social.technet.microsoft.com/wiki/contents/articles/2055.troubleshooting-connectivity-issues-in-the-azure-appfabric-service-bus.aspx

http://social.technet.microsoft.com/wiki/contents/articles/2055.troubleshooting-connectivity-issues-in-the-azure-appfabric-service-bus.aspx

http://blogs.msdn.com/b/narahari/archive/2011/08/01/ip-range-for-windows-azure-platform-identifying-connectivity-issues.aspx

http://blogs.msdn.com/b/narahari/archive/2011/08/01/ip-range-for-windows-azure-platform-identifying-connectivity-issues.aspx





2. Edit the file to include the following lines, indicated by bold type.<?xml version="1.0" encoding="utf-8"?><configuration><appSettings><add key="MaximumRetryInterval" value="60" /><add key="RetryIntervalCoefficient" value="2.5" /><add key="KeepLogsForMonths" value="2" /><add key="VerboseFileLogging" value="true" /></appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup><system.net><defaultProxy useDefaultCredentials="true"><proxy bypassonlocal="True" usesystemdefault="True"/></defaultProxy></system.net></configuration>

3. Save your changes and close the file.4. To start verbose logging, restart the Nintex Live Relay Service.

For instructions, see the related procedure below.5. Retry Nintex Live registration: Click the SharePoint user name to display the

context menu, select Nintex Mobile Apps, and then select Register withNintex Live.

6. To review the log files, open the folder /BIN/NintexLive/LOGS in theSharePoint hive.The default location for the Nintex Live Relay Service log files is as follows.%ProgramFiles%\Common Files\Microsoft Shared\Web ServerExtensions\15\BIN\NintexLive\Logs

To restart the Nintex Live Relay Service

1. On the Central Administration Home page, click System Settings and thenclick Manage services on this server under Servers.

2. Click Start for Nintex Live Relay Service.

Service stuck on "starting": Nintex Live Workflow Queue Service RecycleSymptom

The Nintex Live Workflow Queue Service Recycle is in a “starting” status (with nostart/stop link) for a prolonged period.

Cause

Nintex assemblies have not been refreshed by existing processes.

Resolution

Manually refresh Nintex assemblies using the following procedure.1. Delete the provisioning job as follows:

a. On the Central Administration Home page, click Monitoring.b. Click Review job definitions.c. Click the job “Nintex Live Workflow Queue Service Recycle on

[SERVERNAME]” and then delete the job.2. Restart the SharePoint Administration Service.3. Restart the SharePoint Timer Service.4. Run the IISRESET command.


-13-






5. To start the service on the current server, do the following:a. On the Central Administration Home page, click ApplicationManagement.


c. Click Start for Nintex Live Workflow Queue ServiceRecycle.

Solution package is listed as error: Nintex WorkflowSymptom

The Nintex Workflow solution package (nintexworkflow2013.wsp) is listed as error.

Cause

The solution may not have been deployed correctly.

Resolution

1. Confirm that the SharePoint Administration service is running. See "Ensureservices are running" on page 6.

2. Run the following stsadm command:stsadm.exe -o execadmsvcjobs


3. Redeploy the solution by doing one of the following:l Click Deploy Solution button in the toolbar. For completeinstructions, see "Steps for deploying solutions" on page 16.

l Run the following stsadm command:stsadm.exe -o deploysolution -n nintexworkflow2013.wsp -allcontenturls -immediate -allowgacdeployment

If the solution package is still in error, check the solution information pagefor potential information about error causes. To view the solution informationpage, go to the Central Administration Home page, select System Settings,click Manage farm solutions, and click the link for the solution of interest.You can also analyze the SharePoint ULS log files to determine what iscausing the failure. For more information, see "Review SharePoint ULS logfiles" on page 7.

Solution package is stuck in deployment: Nintex WorkflowSymptom

The Nintex Workflow solution package (nintexworkflow2013.wsp) is stuck indeployment.

Cause

The solution may not have been deployed correctly.

Resolution

Cancel and restart the deployment.1. Run the following stsadm command to list the job identifiers for all

deployments in progress.stsadm -o enumdeployments


-14-








2. Note the job identifier for the stuck Nintex Workflow deployment job.3. Cancel the deployment, using the following stsadm command:

stsadm -o canceldeployment -id "your job id string here"

The solution management page in Central Administration updates the statusof the solution to "not deployed." You can now deploy the solution again.

4. Redeploy the solution by doing one of the following:l Click the Deploy Solution button in the toolbar. For completeinstructions, see "Steps for deploying solutions" on page 16.

l Run the following stsadm command:stsadm.exe -o deploysolution -n nintexworkflow2013.wsp -allcontenturls -immediate -allowgacdeployment

If the deployment is stuck again, analyze the SharePoint ULS log files todetermine what is causing the failure. For more information, see "ReviewSharePoint ULS log files" on page 7.


-15-







Documents

Nintex Workflow 2013 and Nintex Forms 2013 Installation Guide · Nintex Forms Installerfilelocation Licensefilelocation Useraccountfor installationprocess Serverforrunning Nintex