Installing the Server in a Distributed Environment

After you have installed all the prerequisites, created the service accounts, you are ready to install the product Server.

Installation steps

1. Launch the Setup Manager.
2. On the Welcome page, click Next.
3. On the Checking for Latest Version page, the installation will verify the version, click Next.
4. On the End User License Agreement page, read through the EULA. You must select the I agree to the terms and conditions of the license option before you can continue with the installation. You can print out the EULA for your records. Once you have read the EULA, click Next.
5. On the Installation Type page, select the Custom Installation option and type in an Installation Folder, and click Next.
6. On the Select Components page, uncheck everything except the K2 Server and K2 Database, then click Next to continue. You cannot install the K2 Server and K2 Database separately.
7. On the License Configuration page, provide product licensing information.
8. On the Server Configuration page, select the appropriate option for this installation (one of the Farm options if this is a Farm deployment, or the standalone server option if this is a single K2 application server in a distributed environment).
   
9. On the Pass-Through Authentication page, if Kerberos is installed select Kerberos. If not, select Windows and click Next to continue.
10. On the second Server Configuration page (server port configuration), take note of the ports that are used for communication. It is strongly recommended to leave the default ports as is.
    
11. On the Site Configuration page, type in the URL to the product Site (even though we have not configured the product Site yet, enter the URL which you will use to access it). If this is a clustered product Site, be sure to enter the URL used to access the cluster. Using the fully qualified URL to your product Site is preferable.
12. On the Database Configuration page, provide the details for the Database
13. On the Service Accounts Configuration page, enter in the user account details for the Administrator and K2 Service, and click Next to continue.
    
14. Use the Exchange Server Configuration page to configure the Exchange Server if you are using one.
15. If Exchange is being used, integration is configured on the Exchange Integration page.
16. On the SmartActions Configuration page, SmartActions are enabled by default.
    
    The SMTP Settings page is displayed in place of SmartActions setup if the Use Exchange for mail integration option was not selected on the Exchange Server Configuration page.
17. On the Configuration Summary page, validate the settings. You can go back to make any necessary changes, and you can print this page for reference later or copy it to the Clipboard. Once satisfied with your settings, click Next.
18. The Additional Actions page shows if there are additional actions to perform as part of the installation. Click Next to continue.
19. The Setup Manager will update and show you the progress of the component installation on the Components page.
20. Once the installation is done, the Configuration Analysis tool will be available to help troubleshoot any errors detected during the installation.
21. When the installation has completed, you will see a Finished page. There will also be a link to the created configuration log file.

Configuring Kerberos Security

In a distributed environment where components are installed on more than one server and the double-hop issue exists, Kerberos security must be configured. One of the components of Kerberos is the Service Principal Name (SPN). Whenever user credentials must be passed from one system to another, the system that is attempting to pass the credentials must be trusted for delegation. For this step to take place successfully, Kerberos delegation must be configured.

Configuring SPNs is an advanced task and should only be performed by an appropriately trained professional. The steps and configurations given in this help file are to be used as a guide - your system may require additional configuration due to different hardware and software compatibilities. For information on the setspn command, see the Microsoft Command-Line Reference.
Also note that the graphical interface (GUI) to set SPNs is available and started by executing ADSIedit.msc from the Windows > Start > Run menu. How to use ADSIedit is beyond the scope of this document but the simpler command-line method of setting SPNs has been included.

Set SPNs

There are two sets of SPNs that need to be set up for the Service Account:

• K2Server
• K2HostServer

The following placeholders are used in the commands:

• domain\K2 Service Account - The Service Account that runs the product Service.
• MachineName - The name of the computer on which the Service is running.
• MachineName.FQDN - The fully qualified domain name of the computer on which the Service is running.

Be sure to set all the SPNs as listed below. Also, the service account is required so be sure to specify the account properly.
If you have a Server farm running on a cluster, be sure to use the name of the cluster and the fully qualified cluster name instead of a single node's machine name.

Open a command prompt on a server that has the Windows Support Tools installed, and execute the following commands:

• setspn -S K2Server/MachineName:5252domain\K2 Service Account
• setspn -S K2Server/MachineName.FQDN:5252 domain\K2 Service Account
• setspn -S K2HostServer/MachineName:5555domain\K2 Service Account
• setspn -S K2HostServer/MachineName.FQDN:5555 domain\K2 Service Account

If you are installing K2 on an NLB environment, MachineName will change to the LBHostServerName.
The port number may be left out if using default ports.

After the commands have successfully executed, you can verify the SPNs were set by executing the following command:

• setspn -L domain\K2 Service Account

While infrastructure changes are required by the product, each environment is different and has its peculiarities which must be taken into account. Modifying the infrastructure could have unforeseen results if the changes are not appropriately understood or managed. Given the broad spectrum of underlying infrastructure utilized, it is recommended that a page or committee with appropriate skill in each area concerned be assembled to outline the underlying infrastructure changes and gauge the impact of the required changes.

After installing and configuring the Server component, you can easily validate that the Server is functioning properly by running the product Service in console mode. Console mode is a useful troubleshooting tool, as all error and informational messages are sent to the console window so you can watch what is going on. It is important that you run the service as the Service Account in order to accurately troubleshoot permissions and other errors.

To run in console mode, perform the following steps:

1. Open the Services manager (Start > All Programs > Administrative Tools > Services).
2. Scroll down to the K2 Server service, select it and click the Stop Service button.
3. Once the service shows as stopped, you can close the Services manager.
4. Right-click on the K2 Server item in the Start menu (under Start > All Programs > K2 ) and select Run as...
5. Select The following user option, and type in the domain\K2 Service Account as the User Name and password, and click OK.
   The Server will start and initialize. You will see several messages starting the various components.

If you see the following error messages, the SPNs for the Service Account were not set properly:

• Info 7003 SourceCode.SmartObjects.Runtime.SmartObjectClientServer not yet Loaded…
• Error 8060 ProcessPacket Error, Authentication With Server Failed : SEC_E_LOGON_DENIED