Non-AD workgroup installation

This section describes the installation of K2 blackpearl on a machine in workgroup mode, with all server and client components included. This installation might be used when installing on a VM hosted in Azure and not joined to an AD domain, for example.

Prerequisites

A non-AD installation has similar requirements to a standard installation on a domain joined machine except for the following:

• No domain service accounts need to be created; the installation will be done using a local machine account with administrator permissions on the virtual machine, and the K2 service accounts will be local machine accounts with administrator permissions on the local machine.
• You will not need a domain DNS Host (A) record since this installation assumes that there is no domain. However, you will need a resolvable hostname to be able to access the K2 server from other machines. For example if you are installing K2 on a cloud-hosted VM, you will need to make a note of the DNS name of the VM to be able to connect to it.
• You do need to set up MSDTC, but the settings are slightly different for a non-AD installation. Follow the instructions in the Distributed Transaction Controller (DTC) topic and also mark the following check boxes when configuring DTC:
  
  • Allow Remote Administration
  • Enable XA Transactions
• IIS needs to be set up as described in the topic Required IIS settings for K2 blackpearl.
• Microsoft Message Queuing (MSMQ) with private queues must be set up as described in the Message Queuing topic, with the following exception:
  • Directory Service Integration is not needed as there is no directory.
• Read the topic Certificate and Internet Requirements in K2 for important information on the security certificate for your VM.
• If you are setting up a VM hosted in Azure and/or the K2 database will be hosted in a SQL Azure database, you must set up the K2 database in an Azure SQL Database server using the K2 DACPAC as described in the topic Install K2 blackpearl with SQL Azure.

K2 blackpearl Installation steps

When the installation is started, the Setup Manager runs through the following steps:

1. Launch the K2 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 User Manager Settings page, select SQL User Manager in the User Manager drop-down and change the installation folder if you want to, then click Next.
6. On the Select Components page, check all the components you want to install (select everything for full install).
7. On the Database Configurations page, you will see the name of the K2 Database that will be created as well as the SQL Server it will be created on. You can change the installation location for the database by clicking on the change link, or the Change All button. You must use SQL Authentication and enter the SQL user details. You can also change the Database Name by clicking on the change link and editing the Database Name field, but the default K2 is recommended. When you have completed your database configuration, click Next to continue.
8. On the Database Configuration page, provide the details for the K2 Database
9. On the License Configuration page, provide K2 licensing information.
10. On the K2 Server Configuration page, select the Standalone K2 option.
11. On the second K2 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.
    It is important to verify that the specified ports are not blocked in your environment to ensure that K2 runs successfully. If the account you are logged in as while installing the K2 Server does not have domain administrator rights to configure the SPNs, you will need to configure the SPNs manually after installing K2 (unless you've determined that K2PTA will work in your environment, i.e that you do not need Kerberos). If you do not configure the SPNs properly in a distributed environment, the K2 Server will not function properly.
12. Next, configure the K2 Workspace web site
13. On the K2 Workspace Application Pool Configuration page, select an existing application pool to use or update / create a new application pool. Selecting the Set K2 Workspace SPN allows the Setup Manager to set the SPN for you, leaving the checkbox clear means you need to set the SPN manually after the install (unless using K2PTA).
14. The SQL Reporting Services Configuration page allows you to integrate with SQL Server Reporting Services, which provides import / export capabilities between K2 reports and SSRS. This integration is not required for viewing or creating K2 reports. If you selected the SSRS Server Component in the Select Components page, you must select the SSRS instance here. If you did not select the SSRS component at the start, select the box here to enable integration and enter the web service URL. The default URL is: http://{your server:80}/ReportServer
15. On the Service Accounts Configuration page, enter the local admin account details that you are installing with for the Administrator and K2 Service, and click Next to continue.
16. The Exchange Server Configuration page is used to configure the Exchange Server if one is being used in the environment that K2 is being installed to.
17. If Exchange is being used, integration is configured on the Exchange Integration page.
18. The SMTP Settings page is displayed if the Use Exchange for mail integration option was not selected on the Exchange Server Configuration page.
19. 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 you are satisfied with your settings, click Next.
20. The Additional Actions page shows you actions the Setup Manager will perform as part of the installation. Click Next to continue.
21. The Setup Manager will update and show you the progress of the components on the Installing Components page as it installs the software, followed by the Configuration Status page which shows the progress of the configuration of installed components.
22. Once the installation is done, the Configuration Analysis tool will be available to help troubleshoot any errors detected during the installation.
23. When the installation has completed, you will see a Finished page. There will also be a link to the created configuration log file.

K2 smartforms Installation Steps

The steps below describe how to install this component, and the wizard pages that will be displayed in the order in which they occur.

1. Launch the K2 smartforms Setup Manager.
2. On the Welcome page, click Next.
3. The Setup Manager will check for the latest version of K2 smartforms.
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 Select Components page, select the relevant components that should be installed (the default is all components). For a standalone installation leave all the components selected.
6. On the Host Server Database Configurations page, the SQL Server text box should automatically populated with the SQL server name where the K2 database is installed. If required you can enter the database information manually. Select the Authentication mode to be used to authenticate the connection to the SQL Server. When you have verified your database configuration, click Next to continue.
7. License Configuration page: you must enter the license corresponding to the system key displayed. This can be obtained using the key request link on the page.
8. K2 Designer Web Site page, enter or select the web site details.
9. Designer Web Site Application Pool: the next step is to configure the Application Pool account. It's Managed Pipeline mode must be set to Integrated.
10. SmartForms Runtime Site: the site is configured here.
11. SmartForms Runtime Site Application Pool: the selected Application Pool account's Managed Pipeline mode must be set to Integrated.
12. On the Configuration Summary page, validate the settings. You can go back to make any necessary changes, and you can print this Form for reference later. Once you are satisfied with your settings, click Install. Once the Setup Manager starts the installation, the Workflow cannot be stopped.
13. On the Additional Actions page the additional, required actions that need to be performed will be displayed, for example IISRESET, by clicking Next these actions will be performed by the K2 smartforms Setup Manager before starting the installation process. You can manually perform these actions and then click Refresh. Click Next to initiate the installation.
14. The Installing page displays the progress of the installation as the installation occurs, reflecting the components you selected. If a component fails to install, a red cross will display next to the failed component.
15. The Configuration Status page shows the configuration status of the selected components. Just wait for this screen to complete and click Next
16. Once the components are installed and configured, the Configuration Analysis tool runs to verify settings. The tool will display a warning or error icon If issues are discovered. You can attempt to repair all reported issues by clicking Repair All , or select individual issues by selecting the issue and clicking Repair
17. Finished: page appears when the K2 Setup Manager is complete. If available, you can select to deploy the SmartForms components for SharePoint on this page.

Considerations

• Before the installation is started, you must decide if the trace logging feature should be enabled. See the topic Installer Trace Logging Feature for more information.
• If the K2 application server or K2 SQL Database is hosted in a cloud service, it is highly recommended that the K2 database is installed in a SQL server where there is high bandwidth and low latency between the K2 application server(s) and the database server. (For example, in Microsoft Azure the Application Server Virtual Machine and the SQL Database should be in the same subscription and geographical location.) Alternatively, when installing the K2 database in an Azure SQL database but the K2 application server is in a different location, ensure that the network latency between the application server and the SQL server is as low as possible (for example by configuring Azure ExpressRoute or a dedicated network circuit). Excessive network latency between the application server and SQL server will negatively impact performance of your K2 environment.
• If SharePoint 2010 is detected by the Setup Manager, the Finished page of the Setup Manager provides the option of starting the SharePoint 2010 Configuration, see the topic SharePoint Configuration in the installation Post common tasks section of this help file.