We're updating some of our product names. K2 Five is now Nintex Automation. You may see both product names in our help pages while we make this change.

Sequence of Component Installation

Depending on which components you intend to install, and what topology you are implementing, you should install the K2 product components in a particular sequence. This topic describes the sequence for installing K2 components in the most common topologies.

Standalone Server Environment

A standalone server environment is where all server components of the K2 Five are hosted on the same server. This is more typical of small-scale deployments or development/test environments.

Farm Environment

A farm environment is where different K2 components are hosted on separate logical servers, where those logical server may consist of a number of load-balanced physical machines.

Install the K2 Server component on the first K2 application server (this includes installing the K2 database on the targeted SQL instance) .
1. Install the K2 Server component on the other K2 application servers, adding them as server to the existing Farm deployment.
Install the K2 Site component on all the IIS Servers (if you are using separate servers to host the K2 Site), pointing the installer to the NLB name of the K2 server farm.
If applicable, run the K2 for SharePoint deployment utility to install the K2 App in your SharePoint environment.