Join the K2 v4.6 production environment to a different domain

@AbdulRahman Here is the KB article copied and pasted as requested by you per private message.

Summary

This article describes a few scenarios for installing or upgrading K2 when a database and/or a server move needs to take place at the same time. Choose your scenario and follow the steps below.

Details

When installing or upgrading K2 blackpearl, there are several scenarios that must be match to your environment before proceeding with the installation. Find the one below that corresponds with your installation path and follow the instructions.

• Scenario #1: New K2 Server installation with existing database (same version of K2)
• Scenario #2: New K2 Server installation with existing database (newer version of K2)
• Scenario #3: New K2 Server installation with moved database
• Scenario #4: Existing (in-place) K2 server configuration with moved database
• Scenario #5: Existing (in-place) K2 server upgrade with existing database
• Scenario #6: Existing (in-place) K2 server upgrade with moved database

Scenario #1: New K2 Server installation with existing database (same version of K2)

1. Run the K2 blackpearl Setup Manager on the new K2 Server machine
2. On the Installation Type panel, select the Custom Installation option
3. On the Select Components panel (tree view) select the desired K2 component to be installed on the new K2 Server machine
4. On the License Configuration panel, specify a valid K2 license
5. On the K2 Server Configuration panel, select the configuration for the new K2 Server
   • To replace a previous K2 Server with a new one, select the Standalone K2 Server option
   • To create a new K2 Server Farm, select the K2 Server Farm option and specify the K2 Server Farm Name
   • To add a server to an existing K2 Server Farm, ensure that the farm is already set up by making sure the previous step has been successfully configured on the existing K2 Server. Once this has been confirmed, select the K2 Server Farm and Add K2 Server to existing Farm option. Note: The remainder of the steps are unnecessary when adding an additional server to the K2 Server Farm.
6. On the K2 Pass-Through Authentication panel, select either Windows or Kerberos
7. On the K2 Server Configuration panel, specify the ports for Host Server and Workflow Services, SPN and start options, outgoing SMTP e-mail and From address.
8. On the K2 Workspace Web Site Configuration panel, specify the URL used for the K2 Workspace (the URL previously used within the environment)
9. On the CRM Configuration panel, specify the desired settings
10. On the Database Configurations panel, follow these steps:
    • Click the Change link in the Connection column
    • Specify the correct server and database names. Typically this is K2HostServer when you have mulitple databases, or simply K2 if you have a single database
    • Click Test to test the connection. Note: You must have db_owner and securityadmin membership and access to all databases for the account used for the installation
    • Click OK. This will validate the required SQL and database permissions and navigate you back to the Database Configuration panel. The Status column on this panel should now show Up to date as the action that will take place.
11. On the Service Accounts Configuration panel, specify the user names and passwords used for the environment
12. Continue through the rest of the K2 blackpearl Setup Manager and complete the installation
13. Install the same version of Cumulative Updates and Fix Packs as on the previous environment

In distributed environments, all other components must be reconfigured to ensure that all K2 Server connection strings are updated to reference the new K2 Server.

Scenario #2: New K2 Server installation with existing database (newer version of K2)

This scenario follows the previous scenario. Ensure that the version you are upgrading from is supported by 4.6.3 or later.

In distributed environments, all other components must be upgraded to ensure that all K2 Server connection strings are updated to reference the new K2 Server.

Scenario #3: New K2 Server installation with moved database

This section assumes that you have already moved your databases from the original SQL server to the new SQL server.

1. Run the K2 blackpearl Setup Manager on the new K2 Server machine
2. On the Installation Type panel, select the Custom Installation option
3. On the Select Components panel (tree view) select the desired K2 component to be installed on the new K2 Server machine
4. On the License Configuration panel, specify a valid K2 license
   • If you are installing a single server, select the Standalone K2 Server option
   • To create a new K2 Server Farm, select the K2 Server Farm option and specify the K2 Server Farm Name
   • To add a server to an existing K2 Server Farm, ensure that the farm is already set up by making sure the previous step has been successfully configured on the existing K2 Server. Once this has been confirmed, select the K2 Server Farm and Add K2 Server to existing Farm option. Note: The remainder of the steps are unnecessary when adding an additional server to the K2 Server Farm.
5. On the K2 Pass-Through Authentication panel, select either Windows or Kerberos
6. On the K2 Server Configuration panel, specify the ports for Host Server and Workflow Services, SPN and start options, outgoing SMTP e-mail and From address
7. On the K2 Workspace Web Site Configuration panel, specify the URL used for the K2Workspace (the URL previously used within the environment)
8. On the CRM Configuration panel, specify the desired settings
9. On the Database Configurations panel, follow these steps:
   • Click the Change link in the Connection column
   • Specify the correct server and database names. Typically this is K2HostServer when you have mulitple databases, or simply K2 if you have a single database
   • Click Test to test the connection. Note: You must have db_owner and securityadmin membership and access to all databases for the account used for the installation
   • Click OK. This will validate the required SQL and database permissions and navigate you back to the Database Configuration panel. The Status column on this panel should now show Up to date as the action that will take place.
10. On the Service Accounts Configuration panel, specify the user names and passwords used for theenvironment
11. Continue through the rest of the K2 blackpearl Setup Manager and complete the installation
12. Install the same version of Cumulative Updates and Fix Packs as on the previous environment

Scenario #4: Existing (in-place) K2 server configuration with moved database

For best results, take the old databases offline or turn off the old SQL server before following these steps.

1. 1. Run the K2 blackpearl Setup Manager on the existing K2 Server machine
   2. On the Maintenance panel, select the Configure K2 blackpearl option and click Next
   3. On the License Configuration panel, specify a valid K2 license
   4. On the K2 Server Configuration panel, select the correct option for the current environment
   5. On the K2 Pass-Through Authentication panel, select either Windows or Kerberos
   6. On the K2 Server Configuration panel, specify the ports for Host Server and Workflow Services, SPN and start options, outgoing SMTP e-mail and From address
   7. On the K2 Workspace Web Site Configuration panel, specify the URL used for the K2 Workspace (the URL previously used within the environment)
   8. On the SQL Reporting Service Configuration panel, specify the Web Service URL
   9. On the CRM Configuration panel, specify the desired settings
   10. On the Database Configurations panel, follow these steps:

       

       • Click the Change link in the Connection column
       • Specify the correct server and database names. Typically this is K2HostServer when you have mulitple databases, or simply K2 if you have a single database
       • Click Test to test the connection. Note: You must have db_owner and securityadmin membership and access to all databases for the account used for the installation
       • Click OK. This will validate the required SQL and database permissions and navigate you back to the Database Configuration panel. The Status column on this panel should now show Up to date as the action that will take place.
   11. On the Service Accounts Configuration panel, specify the user names and passwords used for the environment
   12. Continue through the rest of the K2 blackpearl Setup Manager and complete the installation
   13. Install the same version of Cumulative Updates and Fix Packs as on the previous environment

   In distributed environments, all other components must be reconfigured to ensure that all K2 Server connection strings are updated to reference the new K2 Server.

   Scenario #5: Existing (in-place) K2 server upgrade with existing database

   1. Run the K2 blackpearl Setup Manager on the existing K2 Server machine
   2. On the Maintenance panel, select the Upgrade option, and then click Next
   3. On the Upgrade Summary Panel, confirm the components that will be upgraded, and then click Next
   4. On the K2 Database Connection Panel, confirm that the correct (and previously used) SQL Server is populated in the SQL Server textbox. Test the connection and continue through the UI with all of the current values. Note: The installation account requires the db_owner and securityadmin membership, and permissions to access all K2 databases

   Scenario #6: Existing (in-place) K2 server upgrade with moved database

   1. Run the K2 blackpearl Setup Manager on the machine that you want to upgrade the K2 Server component
   2. Continue through the upgrade until you reach the K2 Database panel
      • Specify the correct server and database names. Typically this is K2HostServer when you have mulitple databases, or simply K2 if you have a single database
      • Click Test to test the connection. Note: You must have db_owner and securityadmin membership and access to all databases for the account used for the installation
      • Click Next. The K2 blackpearl Setup Manager will attempt to update all existing connection strings from the old SQL server to the new SQL server. You can verify this by looking at the K2 trace logs which state that the connection string has changed from the connection string using the old SQL instance to the connection string using the new SQL instance.
   3. Continue through the rest of the K2 blackpearl Setup Manager and complete the installation

   Considerations

   If you have in-flight processes, keep the old server running until those processes complete, using a Hosts file on the old server to point to localhost so that they can complete using the old server