Upgrade Nintex K2 4.7 or Nintex K2 Five 5.x to Nintex Automation 5.7

Use the Setup Manager to upgrade your Nintex K2 4.7 or Nintex K2 Five environment to Nintex Automation (5.7). The Setup Manager installs and upgrades the tools you need to design, deploy, and use the product features. You use the same installer to configure, modify, remove and update Nintex Automation.

Please note the following important considerations before running Setup Manager:

• When upgrading, the /Identity realm is automatically created and configured to use the same issuers as the primary/default SmartForms runtime site. If you have multiple runtime sites which makes use of different issuers, you need to make sure that the /identity realm has all the relevant issuers selected based on the combination of all runtime sites.
• The Setup Manager detects your installation and identifies the components installed on the machine. It then upgrades each supported component while maintaining your configuration.
• If you have Nintex K2 for SharePoint 2013 in SharePoint 2010 mode, Nintex K2 for Visual Studio 2012, or Nintex K2 for Reporting Services installed, you must first uninstall these components before upgrading to Nintex Automation (5.7). See Removing legacy components for more information on how to do this.
• Nintex K2 4.7 used the C:\Program Files (x86)\ folder by default and this installation location is maintained during an upgrade. A clean installation of the product uses the C:\Program Files\ folder by default.

• Site Configuration: In Nintex Automation (5.7), all web properties and services, Management, Designer, SmartForms runtime, Identity) are installed in an IIS site called Sites. When upgrading your Nintex K2 4.7 environment, the installer preserves your existing IIS configuration of your sites. When reconfiguring the environment after upgrade, the existing configuration is also preserved. If you would rather have a single Site, select the new site option in the installer or create a new site in IIS and select it when installing.

• You need a new Nintex Automation (5.7) license key to install, which you can get on the Nintex Customer Central Portal.
• After the Setup Manager is finished, AppDeployment.exe runs to add the new version of the Nintex K2 for SharePoint app to your app catalog.
• You cannot deploy packages you created with K2 Package and Deployment on previous versions of K2 to your upgraded Nintex Automation (5.7) environment. You must recreate the packages after upgrading to Nintex Automation (5.7).

If there are any Database Triggers defined for the product tables in the K2 database, ensure that the triggers are dropped when performing upgrades. If they are not dropped (or only disabled) during the upgrade process, errors occur. For example, you can use the following command:
DROP TRIGGER [Identity].[TG_Identity_PreventDeletion] GO

You can query triggers in the database with the following script:

SELECT 
     sysobjects.name AS trigger_name 
    ,USER_NAME(sysobjects.uid) AS trigger_owner 
    ,s.name AS table_schema 
    ,OBJECT_NAME(parent_obj) AS table_name 
    ,OBJECTPROPERTY( id, 'ExecIsUpdateTrigger') AS isupdate 
    ,OBJECTPROPERTY( id, 'ExecIsDeleteTrigger') AS isdelete 
    ,OBJECTPROPERTY( id, 'ExecIsInsertTrigger') AS isinsert 
    ,OBJECTPROPERTY( id, 'ExecIsAfterTrigger') AS isafter 
    ,OBJECTPROPERTY( id, 'ExecIsInsteadOfTrigger') AS isinsteadof 
    ,OBJECTPROPERTY(id, 'ExecIsTriggerDisabled') AS [disabled] 
FROM sysobjects 

INNER JOIN sysusers 
    ON sysobjects.uid = sysusers.uid 

INNER JOIN sys.tables t 
    ON sysobjects.parent_obj = t.object_id 

INNER JOIN sys.schemas s 
    ON t.schema_id = s.schema_id 

WHERE sysobjects.type = 'TR' 

Upgrade Path

Using the Setup Manager to upgrade

1. The Setup Manager displays the version check page.
   If there is a discrepancy between the latest version available and the version of the Setup Manager, the following text is shown:
   This may not be the latest version available. Please make sure you have downloaded the latest version to ensure that you are up to date with the latest updates.
   Click Next to continue.
   
2. The Setup Manager detects the components installed on the machine and displays them.
   
   If there are missing requirements, a page which contains details is displayed. Fulfill the requirement and click Refresh to confirm each requirement is satisfied, then Next to continue.
   
3. As the service account registers a new service as part of the update, the Additional Input Required page requires you to enter the service account password.
   
4. The update begins and progress is displayed.
   
5. After the update, the Configuration Analysis tool runs.
   
6. When the components are updated and the analysis tool is done, the Finished page is shown with a link to the update log file. There is also a check box to start the Nintex K2 for SharePoint App Deployment. Click Finish to close the Update Manager. Once the Setup Manager is complete, the Nintex K2 Five for SharePoint App Deployment Wizard will start if you checked the box. If you are using Nintex K2 for SharePoint on a different machine, you must run the Setup Manager on that machine too.

Removing legacy components

If the Setup Manager detects legacy components that are not allowed in Nintex Automation (5.7), like Nintex K2 for SharePoint 2013 in SharePoint 2010 mode, Nintex K2 for Visual Studio 2012, or Nintex K2 for Reporting Services, you see a red icon with this information.

When you click the Cancel button, you will see an Info screen that asks if you want to launch the Setup Manager to allow you to uninstall the unsupported components. To remove the unsupported components, select the Modify option, then remove them from the component selection. Finish the wizard, then restart the Setup Manager to update your environment.

Modifying an Updated Environment

To modify a system updated to the latest version of the product, take the following steps:

1. Run the Setup Manager and choose the Modify option.
2. In the tree view, select the components that need to be modified.
3. Follow the pages and complete the installation.
4. After all the above steps have been completed successfully, run the Setup Manager to update the newly-added components to the latest version.