The supplied certificate is used with a master key on the K2 Server to encrypt the data. SQL on-line does not support this method so the user is asked for a certificate. Installs with on-premises SQL servers use SCSSO Key encryption, K2 basically tells SQL to make a certificate and a master key for that certificate and then uses that to encrypt the data in the SQL server. Do so by clicking the Browse button and selecting the certificate to use. If connecting to an Azure SQL Database, this page will require you to select an Azure Encryption Certificate. If you do not configure the SPNs properly in a distributed environment, the Server will not function properly. If the account you are logged in as while installing the Server does not have domain administrator rights to configure the SPNs, you will need to configure the SPNs manually after installing the product(unless you've determined that PTA will work in your environment, i.e that you do not need Kerberos). Resolve database related issues in a timely manner.

Adhere to database change control procedures and policies. The Discovery Service port is used in legacy versions of K2, but is not used in Nintex Automation. By default, non-NLB environments use port 49599, and NLB environments use port 49600.

This port is only displayed if you are installing a K2 Server Farm. It is important to verify that the specified ports are not blocked in your environment to ensure that the product runs successfully. Duties and Responsibilities: Maintain database security and integrity at all the times. The K2 management tools use it to identify the clustered K2 servers in your environment.

SQL Backup Master 6.3.628.0 instaling