Article How do I install Telligent Community?

Looking for the upgrade instructions?

Are you using the Free version? Please refer to this page to see the restrictions: https://www.telligent.com/licensing-and-pricing/

Before proceeding with the installation, you should ensure you meet the system and hardware requirements as well as determine the following:

    • Service Accounts:
      Are you using domain accounts or local accounts?  If using a domain account, you'll need to know the credentials for that accountt
    • Filestorage Path:
      The path you're using for filestorage.  For a local install use a local directory (e.g. D:\Community\Filestorage).  With Multiple Servers, this will be a UNC share or a DFS Replicated folder.
    • Database Authentication Method:
      Are you going to use SQL authentication or Integrated authentication
    • Have the Community Installation package:
      Contact Support to obtain this. After downloading, make sure to unblock the package by right-clicking on it and choosing properties.  At the bottom of the window may be an option to unblock the file - Click the button or check the box (depending on your version of windows) then click OK.  If you don't see an option to unblock the file, then you're good to go.

    Install Database

    SQL Server 2016 or higher is recommended. Amazon RDS and Azure SQL are also supported.

    1. Create a new database.
    2. Run Install.sql:
      This can be found in the SqlScripts directory of the installation package.  If you encounter any errors, make sure to look at the earliest errors first - later errors are usually side effects of the earlier errors.  This should be run using an account with the default schema set to dbo.
      • Run cs_system_CreateCommunity:
        Run the following script against your database, replacing AdminPassword with a temporary password.
        EXECUTE[dbo].[cs_system_CreateCommunity]
            @ApplicationName = N'telligent',
            @AdminEmail = N'notset@localhost.com',
            @AdminUserName = N'temporary-admin',
            @AdminPassword = N'[PUT A TEMPORARY PASSWORD HERE]',
            @PasswordFormat = 0
      • Create logins and grant permissions:
        It is recommended to use separate accounts for accessing the community database and the reporting database.  If using integrated authentication, create logins for service accounts, otherwise create a new SQL login for the community.  (If using local service accounts, you will have to come back to this step later).

        Grant the community database login the following roles in the community's database:
        • aspnet_Membership_FullAccess
        • aspnet_Profile_FullAccess
        • db_datareader
        • db_datawriter
        • db_ddladmin

        Grant the reporting database login the following roles in the reporting database:
        • db_datareader
        • db_datawriter
        • db_ddladmin

      Install Search

      Search requires that Java 8 Update 121 64 bit or higher is installed on the search server.

      1. Install Search Files:
        Locate the Search directory in the installation package.  Copy this to a location on disk where you wish to install search (e.g. d:\Community\Search\ ). Do not place this folder in your Web directory.
      2. Install Search Service:
        To install search, open up PowerShell with administrator rights and execute .\bin\ServiceInstall.ps1. If you encounter any errors, refer to Troubleshooting PowerShell at the end of this article. When complete, the script will output the message "Solr has been successfully installed to http://localhost:8983/solr/". Open this URL in your web browser to verify installation completed successfully.
      3. Secure & Expose Search:
        If your website or job services are installed on other machines, you may need to configure your network so those servers can access search.  You MUST NOT expose search over the public internet, instead use firewalls and network isolation technologies to ensure that the TCP Port 8983 can only be accessed from the web or job servers.
      4. For advanced Solr topics see Advanced Solr Configuration.

      Install Website

      .Net 4.7.2 (or newer) is required on web servers.  If you have multiple web servers, repeat steps 1-5 on each server

      1. Install the web files:
        Locate the Web directory in the installation package.  Copy this to a location on disk where you wish to install the site files (e.g. d:\Community\Web\ )
      2. Configure connection strings:
        Open the connectionstrings.config file, and update the connection strings to match your environment
        • SiteSqlServer- the connection string to your database.  This will typically look something like the following
          • Integrated Authentication: server=SQLSERVER;Trusted_Connection=yes;database=TELLIGENT-COMMUNITY
          • SQL Authentication: server=SQLSERVER;Trusted_Connection=no;database=TELLIGENT-COMMUNITY;uid=USERNAME;pwd=PASSWORD
        • Reporting - the connection string to your reporting database (configured later).  This will typically look something like the following
          • Integrated Authentication: server=SQLSERVER;Trusted_Connection=yes;database=TELLIGENT-REPORTING
          • SQL Authentication: server=SQLSERVER;Trusted_Connection=no;database=TELLIGENT-REPORTING;uid=USERNAME;pwd=PASSWORD
        • FileStorage: The path to the folder or UNC share used for filestorage (e.g. d:\Telligent\Filestorage or \\FileServer\TelligentFilestorage )
        • SearchContentUrl: The URL to the Solr core containing the main content index.  Typically this will be http://YOUR-SEARCH-SERVER:8983/solr/telligent-content/
        • SearchConversationsUrl: The URL to the Solr core containing the conversation index.  Typically this will be http://YOUR-SEARCH-SERVER:8983/solr/telligent-conversations/
        •  SiteUrl: The fully qualified url of your community, including the proper protocol(http/https) (e.g. https://yourcommunity.com).
      3. Create a new website:
        Open up IIS Manager.  In the tree on the left, right click on Sites, select "Add Website" and follow the wizard.  Point the physical path to the folder created in step 1, and ensure that a new application pool is created with the website.
      4. Configure the Application Pool:
        In the tree view in IIS Manager, go to Application Pools.  Right-click the application pool created in step 3 and select Advanced Options.  Ensure the following settings are configured:
        • General:
          • .Net CLR Version: 4.0
          • Managed pipeline mode: Integrated
        • Process Model:
          • Identity: If using a domain account to authenticate with SQL or a UNC share for filestorage, set this to your service account, otherwise set it to the built-in account ApplicationPoolIdentity.
          • Idle Time-out (minutes): 0
          • Shutdown Time Limit: 150
        • Recycling
          • Private Memory Limit: 1572864KB (1.5GB)
          • Regular Time Interval (minutes): 0
          • Generate Recycle Event Log Entry: Set all values to true
      5. Grant Permissions
        Grant the website account "Read and execute", "List Folder Contents" and "Read" permissions on the directory you installed the website to in step 1.
        If using ApplicationPoolIdentity, grant permissions to IIS APPPOOL\<AppPoolName> (where <AppPoolName> is the name of your application pool). You'll also need to go back and set permissions on the Database and Filestorage now the local accounts have been created.

      At this point, you should be able to browse to your community in your web browser. Navigate to it and open your community - this first access may take several minutes while it finishes the installation.  Once completed, you should see a screen like the following.

      Install Job Server

      .Net 4.7.2 (or newer) is required on job server.

      1. Install the Job Server files:
        Copy the JobServer folder form the installation package to a location on the server hosting the job server  (e.g. D:\Community\Jobs\ ). Do not place this folder within your Web directory
      2. Configure the Job Server:
        Copy the connectionstrings.config file from the web server to the job server
      3. Install the Job Server service:
        Open up PowerShell as an administrator. The command to use depends on whether you are using local or domain accounts.  (If you encounter any errors running these scripts, refer to the "Troubleshoting Powershell" section at the end of this article)
        • Local account:
          Run the following command:
          .\Install.ps1

        • Domain Account:
          Run the following command.  It will first prompt your for the credentials of your service account before installing the job server using those credentials.
          .\Install.ps1 -Credential (Get-Credential)

      4. Grant Database Permissions if using local accounts with SQL Integrated Authentication
        If using local accounts with SQL integrated authentication, grant NT SERVICE\TelligentCommunityJobService the required database rights (see Install Database step 4).  After this is done, start the job service
        Start-Service TelligentCommunityJobService
      5. Ensure the job service account belongs to the Performance Log Users Group
        The Document Preview feature utilizes server performance resources to monitor memory consumption and process timing, the account that your Job Service is running under needs to be a member of the Windows security group "Performance Log Users". If you see the error "access to the registry key 'global' is denied", this is more than likely the cause.

      Install Community Reporting

      Install Reporting Database

      SQL Server 2016 or higher is recommended.  

      1. Create new database; e.g. CommunityReporting
        We recommend turning the Recovery Model (located Properties -> Options) to "Simple".  We recommend the Reporting Database be on a separate database server as the Community Database to avoid any performance issues with your community.
      2. Run Install.sql:
        This can be found in the ReportingETL\SqlScripts directory of the installation package.  If you encounter any errors, make sure to look at the earliest errors first - later errors are usually side effects of the earlier errors.
        • Create login and grant permissions:
          The ETL process will read from the community database and write to the reporting database. It is recommended to use a separate login but not required. If using integrated authentication, create a login for the reporting service account, otherwise, create a new SQL login for the reporting. (If using local service accounts, you will have to come back to this step later).  This should not be the same account as in the Web\connectionstrings.config
          Grant this login the following roles in the community database.
          • db_datareader

          Grant this login the following roles in the reporting database.
          • db_owner

        Install ETL Service

        .Net 4.7.2 (or newer) is required on ETL service server.

        1. Install the ETL service files:
          Copy the ETL folder from the \ReportingETL folder in the installation package to a location on the server hosting the service  (e.g. D:\Community\ETL\). Do not place this folder within your Web directory.
        2. Configure connection strings:
          Open the connectionstrings.config file and update the connection strings to match your environment
          • SiteSqlServer- the connection string to your Community database.  This will typically look something like the following
            • Integrated Authentication: server=SQLSERVER;Trusted_Connection=yes;database=TELLIGENT-COMMUNITY
            • SQL Authentication: server=SQLSERVER;Trusted_Connection=no;database=TELLIGENT-COMMUNITY;uid=USERNAME;pwd=PASSWORD
          • Reporting: the connection string to your Reporting database.
            • Integrated Authentication: server=SQLSERVER;Trusted_Connection=yes;database=TELLIGENT-REPORTING
            • SQL Authentication: server=SQLSERVER;Trusted_Connection=no;database=TELLIGENT-REPORTING;uid=USERNAME;pwd=PASSWORD

        3. Setup recurring ETL scheduled task:
          Open Windows Task Scheduler and create a new Task using the 'Create Task' option. Ensure the following settings are configured:
          • General:
            • Name: Community Reporting ETL (or whatever you prefer)
            • User Account: [Choose proper service account according to your setup. If using integrated SQL authentication this account must have read access to the Community database and read/write/ddladmin access to the reporting database]
            • Security Options: Run whether user is logged in or out
          • Triggers:
            Create 'New' trigger with the following settings:
            • Settings: Daily, Starting at 12:00AM, recurring every day
            • Advanced Settings: 
              • Repeat task every: X hours (Note: This can be more or less frequent based on your community)
              • Synchronize across time zones: Checked
              • Enabled: Checked
            • Example


          • Actions:
            Create a new action with the following settings:
            • Program: [folder location of ETL service]\ReportingETL.exe
            • Example

        Turn on Reporting in the Community 

        1. Enable the Reporting Plugin
          Log into your site as an administrator and navigate to Administration->Extensions, locate the Reporting plugin.

          Set the timezone offset preferred and enable the plugin by checking the "Enabled" checkbox and clicking Save button. After refreshing your page you should see the Reporting administration section in the left-hand navigation. 
          Note: Data will show up after the next ETL run.
      3. Install Video Transcoder

        The HTML5 Video Transcoder enables videos of any format to be uploaded to Community and to be made playable directly within the browser without using plugins. 

        1. Download installation package from here.
          Unblock the zip package by right-clicking it and going to Properties. If there is an Unblock button at the bottom of the Properties window, click it to unblock the zip package. If not, the zip package is already unblocked.
        2. Confirm Prerequisites
          Ensure the database user for the Community Server instance has proper ddladmin permissions on the database, because the Video Transcoder plugin installs a new table.
        3. Install file web files:
          Copy Telligent.Evolution.VideoTranscoding.dll from the [download package]\Web\bin folder into the Web\bin directory of the website.
        4. Install the Job Service Files:
          Stop the Job Service. In the installation package, locate the Tasks folder and copy the contents of the Tasks folder to the root of your Job Service installation. For example, if your Job Service root was c:/JobServer, it would end up containing c:/JobServer/ffmpeg folder and c:/JobServer/Telligent.Evolution.VideoTranscoding.dll.
        5. Restart the Job Service
        6. Enable the Video Transcoder Plugin
          Log into your site as an administrator and navigate to Administration->File Viewers, locate the Video Transcoder plugin and enable it by checking the "Enabled" checkbox and clicking Save button.
          By default, the job will run every 2 minutes. If you wish to change this, click the Configure button next to Video Transcoder Job plugin.

        Install Socket Bus

        Socket Bus is required. Note: .Net 4.7.2 (or newer) is required on the socket bus server.

        1. Install the Socket Bus files:
          Locate the SocketMessageBus directory in the installation package.  Copy this to a location on disk where you wish to install socket bus (e.g. d:\Telligent\SocketBus\ )
        2. Install Socket Bus Service:
          Open up PowerShell as an administrator, then run .\install.bat
        3. Start the Service:
          From PowerShell, run the following command
          Start-Service 'Telligent Socket Message Bus'

        4. Secure and Expose Socket Bus:
          You MUST NOT expose socket bus over the public internet, instead use firewalls and network isolation technologies to ensure that TCP Port 9623 can only be accessed from the web and job servers.
        5. Configure socket bus in the website
          Open up your community in a web browser.  Login as "temporary-admin" with the password you used when executing the cs_system_createcommunity stored procedure.  In the top left of the screen is a pencil icon - click on this to open the management panel then go to Administration. In administration, use the search pane at the top right of the screen to search for "Socket Message Bus Service Connector".  Set the Service Host Name to be the host name of the server running the socket bus service.

        What's Next

        Congratulations, you have now set up Verint Community.  You can login with the username "temporary-admin" using the password you used when creating the database.

        The first thing you should do is create a new admin user, log in as that new user and delete the temporary admin account.  Then you can get started with the "Set up your community" wizard on the homepage.

        Troubleshooting PowerShell 

        If you get the following error, the installation package was not unblocked before you extracted it.  To fix this, either unblock the zip file then re-extract the files, or run the following command

        Get-ChildItem d:\Telligent\Search -Recurse | Unblock-File

        .\ServiceInstall.ps1 : File d:\Community\Search\bin\ServiceInstall.ps1 cannot be loaded. The file
        d:\Telligent\Search\bin\ServiceInstall.ps1 is not digitally signed. You cannot run this script on the current system.
        For more information about running scripts and setting execution policy, see about_Execution_Policies at
        http://go.microsoft.com/fwlink/?LinkID=135170.
        At line:1 char:1
        + .\ServiceUninstall.ps1
        + ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : SecurityError: (:) [], PSSecurityException
        + FullyQualifiedErrorId : UnauthorizedAccess

        If you get the following error when running, ensure your execution policy is set to at RemoteSigned by running the following command.  (This is the default value for Server 2012 R2, but may need to be configured manually on older versions)

        Set-ExecutionPolicy RemoteSigned

        .\ServiceInstall.ps1 : File d:\Commuity\Search\bin\ServiceInstall.ps1 cannot be loaded because running scripts is
        disabled on this system. For more information, see about_Execution_Policies at
        http://go.microsoft.com/fwlink/?LinkID=135170.
        At line:1 char:1
        + .\ServiceInstall.ps1
        + ~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : SecurityError: (:) [], PSSecurityException
        + FullyQualifiedErrorId : UnauthorizedAccess

      Microsoft Azure

      See How Do I Deploy my Site to Microsoft Azure?  (New Installations Only)