License Configuration
The Setup Manager displays the License Configuration page when licensed components of K2 are being installed. To proceed with the installation from this page, you must get a License key from the Nintex Customer Central , or by using the Request a K2 license link provided on the License Configuration page. Once issued with the key, enter it on this page to continue the installation.
- System Key: The installation generates a system key and you must pair it with a valid license key for the installation to be successful.
- License Key: Request a license using the Nintex Customer Central Portal. Speak with your K2 representative if you have any questions about license types and limitations. Also see the article How to obtain and manage K2 license keys for more information.
What to do on this page
- To get a license:
- Copy the System Key.
- Click on the URL provided on the License page (below the License Key field). This will direct you to the K2 site to request your license key.
- To license your copy of the K2 product:
- If a license key is available, enter the license key.
- Click Next.
- If the license key is valid, the installation will proceed. If the license key is invalid, or a license key is not available the wizard will prevent the installation from proceeding.
Developer License considerations
The following are important considerations that applies to the Developer license:
A K2 Production Server License allows for unlimited installations of K2 Development Servers for non-production use only.
- K2 Development Servers may not run as a Windows Service, and can only operate in console mode.
- K2 Development Servers are limited to Single Server installations.
- Request Development Server licenses on the Nintex Customer Central Portal.
Console Mode has the following limitations and performance implications for all Development Servers:
- Requires Local Login.
- Single-threaded Execution only.
When installing and using K2 with a Developer license, the account used to run the K2 service is always the currently logged-in user. When using a Developer license, the K2 server runs in console mode as the currently logged-in user, and not as a Windows service. K2 uses the currently logged-in user's credentials to connect to the K2 database (when using integrated authentication), and uses the current user’s credentials for certificates, registry keys, and folders required by the K2 service to run. See the topic Accounts used in a K2 Installation for more information.
When updating an expired Developer license, use the information in the article: How to Obtain and Manage K2 License Keys.