Summary of Configuration Analysis Tool Checks

The Configuration Analysis Tool checks a large number of tasks, with different sets of tasks checked depending in the installation type. The list shown here is not exhaustive but shows typical checks.

For a list of all tasks checked and notes on individual checks, see the "Configuration Analysis tool all tasks.txt" text file. The file shows an example of the output of the tool with task check successes and failures and the duration the check took. There are also notes concerning many of the checks with further instructions.

Definition of variables used in the explanation below:

[USERSNAME] = The user that is used to run the K2HostServer Service.
[K2SITENAME] = The name that you chose for the K2 site during installation (usually the name is just K2)
[WORKSUSER] = The user under which the Workspace Application pool has been configured to run.
[SHAREUSER] = The user under which the SharePoint Deployment Application Pool is running.

Server

File System Permissions

The file permissions task checks if the requested user has the rights that is required on the specified path.

Registry Permissions

Message Queue Enabled

Checks if MSMQ is installed correctly and checks that Directory Integration is installed.
As a test the tool tries to create a temporary queue with a random name and then tries to delete the queue.

MSDTC

MSDTC Network access

MSDTC Server is Running

K2 blackpearl Server Running

Database Rebuild Indexes

Executes the DatabaseCheckIndexes stored procedure to ensure indexes have been rebuilt in the database for the K2Server, K2ServerLog and K2SmartBroker tables.

Visit KB001281 to learn more about Rebuilding Indexes.

Database Symmetric Key checks

Symmetric keys for the K2HostServer, K2SmartBroker, K2SQLUM, K2SmartBox tables in the K2 database need to be detected.

K2 Workspace

Loopback Host Headers

IIS Permissions

  1. [K2SITENAME] – Set Site Negotiation

    This task checks the sites negotiation settings. If a SPN is detected for the Workspace Application Pool User ([WORKSUSER]) then it should be “Negotiate, NTLM”. If a SPN is not detected it should be “NTLM”. If it is on a workgroup machine it should be Anonymous Authentication.

    • Workspace – Set Virtual Directory Negotiation

    This task checks the virtual directories negotiation settings. If a SPN is detected for the Workspace Application Pool User ([WORKSUSER]) then it should be “Negotiate, NTLM”. If a SPN is not detected it should be “NTLM”. If it is on a workgroup machine it should be Anonymous Authentication.

    • RuntimeServices – Set Virtual Directory Negotiation

    This task checks the virtual directories negotiation settings. If a SPN is detected for the Workspace Application Pool User ([WORKSUSER]) then it should be “Negotiate, NTLM”. If a SPN is not detected it should be “NTLM”. If it is on a workgroup machine it should be Anonymous Authentication.

  2. K2 Application Pool Settings

    This task checks that the K2 Application Pool has been created and that the it is running under the [WORKSUSER] account.

  3. K2 Application Pool Account Permissions

Checks that the [WORKSUSER] is in the following group:

  • IIS 6: IIS_WPG
  • IIS 7: IIS_IUSRS

File System Permissions

The file permissions task checks if the requested user has the rights that is required on the path specified.

Web Deployment Projects

Checks if the Visual Studio 2008 Web deployment projects are installed on the machine.

Reporting Indexing

Check the K2ServerLog database to see if the table indexes are created. Also gives you information on how to create the indexes if they are incorrect.

HTTP Activation feature for Windows Server 2012

Checks if the HTTP Activation feature is installed on a Windows 2012 server (specifically with IIS 8). If the feature is not installed, clicking Repair will install it.

K2 Designer for SharePoint

File System Permissions

The file permissions task checks if the requested user has the rights that is required on the specified path.

Database Permissions

The Central Application Pool User account must be one of the Server Roles on the SQL Server Instance:

Web Deployment Projects

Checks if the Microsoft Visual Studio 2008 Web Deployment Project is installed on the machine.

SharePoint

K2 Server Service Account

The K2 Server Service Account must be a member of the Site Collection Administrators Group for all site collections where the K2 features have been deployed.

Loopback Host Headers

This task checks in the registry if loopback host headers are enabled on the machine.

Rights required to run the Analysis Tool on the SharePoint installation

This task checks if the logged on user is a Farm Administrator on SharePoint. The child tasks are dependent on the success of this task.

The file permissions task checks if the requested user has the rights that is required on the specified path.

  1. %SYSTEMROOT%\Temp – Modify – Authenticated Users
  2. %COMMONFILES%\Microsoft Shared\web server extensions\14\Template\Features – FullControl – Authenticated Users
  3. %COMMONFILES32%\Microsoft Shared\web server extensions\14\Template\Features – FullControl – Authenticated Users. (Only on 64-bit systems)
  4. %COMMONFILES%\Microsoft Shared\web server extensions\14\ISAPI – FullControl – Authenticated Users
  5. %COMMONFILES32%\Microsoft Shared\web server extensions\14\ISAPI – FullControl – Authenticated Users. (Only on 64-bit systems)
  6. %COMMONFILES%\Microsoft Shared\web server extensions\14\Template\Layouts – FullControl - Authenticated Users
  7. %COMMONFILES32%\Microsoft Shared\web server extensions\142\Template\Layouts – FullControl - Authenticated Users. (Only on 64-bit systems)

Checks if the Microsoft Visual Studio 2008 Web Deployment Project is installed on the machine.

K2 for Visual Studio and K2 Studio

File System Permissions

The file permissions tasks check if the requested user has the rights that is required on the path specified.

Web Deployment Projects
Checks if the Visual Studio 2008 Web Deployment Project is installed on the machine.

Exchange Integration Permissions

K2 Service Account

PowerShell 3.0 and WinRM Installed

CRM PrivUserGroup Permissions

The INSTALL\k2server account needs to be in the Organization's PrivUserGroup for CRM.

This is a requirement in CRM when using K2 Pass-Through Authentication (ClientWindows) where the K2Service Account needs to impersonate as the Application Pool account when the account is anonymous.

This change needs to be made in Active Directory.