K2 Service Startup

If the K2 Service takes a while to startup, the time taken may be from 2 - 3 minutes which is a noticeable delay in startup. See the possible options below to improve the K2 Server startup time:

Certify Authority

If a trust relationship exists between machines which uses authenticode signing then the recommended way forward is to download and install the root Certificate Authority. Although acceptable, disabling i.e. bypassing the CA effectively breaks the trust relationship between the machines.

The K2 administrator has two options:

  1. Download and install the Root Certificate Authority.
  2. Disable or bypass the Root Certificate Authority.

Implementing the following configuration change is at the discretion of the K2 system administrator.

The K2 Server Machine Configuration file must be updated using the following code snippet:

Copy

K2 Server Machine Configuration file update

<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration
Certificate Authority Description
True

The K2 Server boots using the Root Certificate Authority.

Warning: Unless the Root Certificate Authority has been downloaded and installed, the K2 Service Account may experience delays of up to 3 minutes before starting.
False

When set to False the K2 Server boots without using the Root Certificate Authority.

Warning: When set to False, the trust between machines is broken.