Documentation Index

Fetch the complete documentation index at: https://help.board.com/llms.txt

Use this file to discover all available pages before exploring further.

Board On-premises multi-node installation

  • Updated on Jul 1, 2026
  • Published on Jul 1, 2026
  • 8 minute(s) read
Prev Next

This article explains how to install Board in a multi-node on-premises environment.

This article covers:

A multi-node setup separates the Web layer from the application layer. Board Web runs on the Web Node. Board Engine runs on the Board Engine Node.

ActiveX control

This diagram shows the Web Node and the Board Engine Node on separate Windows Server machines:

  • The Web Node hosts IIS and Board Web.

  • The Board Engine Node hosts Board Engine.

  • The diagram also shows separate volumes for Board Web files, Board data, and logs.

Users connect to Board Web through HTTPS. Board Web then communicates with Board Engine over an encrypted connection.

This separation gives each node a clear role and can simplify operations, maintenance, and resource management.

Publishing Board Web under IIS can help when you need to:

  • Secure access to Board Web with HTTPS.  

  • Publish the same Board Engine through multiple sites with different configurations.  

  • Allow IT teams to maintain and support the website in a standard Windows Server environment.  

  • Configure scheduled application pool recycles.  

Prerequisites

Before you install Board, prepare prepare both nodes.

  1. Infrastructure sizing. Infrastructure sizing depends mainly on these factors:

    The Board Engine Node is the most important node for sizing because it manages data and processing.

    Size

    Board Engine Node resources

    Small

    8 to 16 vCPU and 64 GB to 128 GB RAM

    Medium

    16 to 64 vCPU and 128 GB to 512 GB RAM

    Large

    More than 64 vCPU and more than 512 GB RAM

    For all sizes, use a vCPU clock frequency of 3.0 GHz or higher.

    The Web Node usually needs fewer resources than the Board Engine Node. Size the Web Node based on expected concurrent web sessions and total web traffic.

    These values are guidelines. Validate the final sizing based on the project, Data Model size, application complexity, and expected workload.

  2. Install Microsoft IIS on the Web Node. Make sure IIS is installed and configured correctly before you install Board Web.

  3. Install Microsoft .NET Framework 4.8. Board requires the .NET Framework 4.8 runtime environment to function correctly.

  4. On the Web None, enable these IIS role services under "Application Development":

    1. ASP.NET 4.8

    2. WebSocket Protocol

  5. Enable required Windows features. Enable all necessary Windows features as shown in the tables below to ensure compatibility and full functionality of the Board platform.

    1. Open Server Manager and click on “Add roles and features”
      Instructions for configuring a local server, highlighting the step to add roles and features.

    2. In the “Add Roles and Features Wizard”, make sure the following role services and features are enabled:

      Roles for the Web Server (IIS)

      Category

      Role Service

      Common HTTP Features

      Default Document

      Common HTTP Features

      Directory Browsing

      Common HTTP Features

      HTTP Errors

      Common HTTP Features

      Static Content

      Health and Diagnostics

      HTTP Logging

      Performance

      Static Content Compression

      Security

      Request Filtering

      Security

      Windows Authentication

      Application Development

      .NET Extensibility 4.8

      Application Development

      ASP.NET 4.8

      Application Development

      ISAPI Extensions

      Application Development

      ISAPI Filters

      Application Development

      WebSocket Protocol

      Management Tools

      IIS Management Console

      If your environment uses Windows Authentication, make sure "Windows Authentication" is enabled under "Security".

      Windows Features

      Category

      Feature

      .NET Framework 4.8 Features

      .NET Framework 4.8

      .NET Framework 4.8 Features

      ASP.NET 4.8

      Windows PowerShell

      Windows PowerShell 5.1

Install Board on the Board Engine Node

Step 1: Run the Board setup file

  1. Download the Board server installation package from the official Board downloads page in Community.

  2. Extract the installation package.

  3. Right-click the setup executable.

  4. Select "Run as administrator".

Run the setup as administrator to make sure all components and services are installed correctly.

File explorer showing setup application with options to run as administrator.

Step 2: Complete the installation Wizard

  1. Follow the setup wizard.

  2. Accept the license agreement.

  3. Keep the default installation path unless your infrastructure requires a custom path.

  4. Select "Install".

  5. When the setup completes, select "Finish".

Board 15 Server Setup Wizard with installation steps and options displayed on screen.

Step 3: Verify the installation

After the installation completes, verify that Board Engine and the related services are installed by opening the Board Server Configuration app.

Board Server Configuration app interface displaying essential setup options and features.

Configuration settings for the Board Server, including security and application parameters.

Step 4 (Optional): Customize Board path on the Board Engine Node

Use this procedure when Board data must be stored on a dedicated drive.

  1. Stop Board service. Stop the service before you change the Board path. This prevents conflicts during the path change.

    1. Open "Board Server Configuration".

    2. Select "Stop Service".

  2. Change Board path.

    1. In "Board Server Configuration", go to the "General Settings" tab.

    2. In "Board path", click on “Browse” and select the drive and folder where you would like Board to store its data.

    3. Use a path such as X:\Board.

  3. Move existing data.

    1. Copy all folders from the current Board data path to the new path.

    2. Keep the same folder structure in the new path.

    3. Verify that all folders exist in the new path.

      For example, move the folders from C:\Board to X:\Board.
      File explorer showing folders in Windows with highlighted navigation paths and options.

  4. Apply changes.

    1. In "Board Server Configuration", select "Apply Changes".

    2. Select "Start Service".

Install Board Web on the Web Node

Board Web runs under IIS on the Web Node.

Step 1: Download the Board Web package

  1. Download the WebHTML5_IIS package from the official Board downloads page in Community.

  2. Extract the package.

Step 2: Check for blocked files

  1. Right-click the downloaded ZIP file.

  2. Select "Properties".

  3. If Windows shows "This file came from another computer and might be blocked to help protect this computer", select "Unblock".
    Security warning about a file from another computer with an unblock option.

  4. Make sure the attribute “Read-only (Only applies to files in folder)” is unchecked
    Properties window displaying details of the BWEB file folder including size and attributes.

  5. Click "Apply".

  6. To confirm the changes made in the last step, choose “Apply changes to this folder, subfolders and files“.

    Confirmation dialog for changing folder attributes, including read-only settings and options.

Step 3: Create IIS folder

  1. On the Web Node, create a new folder for Board Web under the IIS web root.

  2. Use a path such as C:\inetpub\wwwroot\BWEB.

Step 4: Copy the Board Web files

  1. Copy the contents of the extracted ZIP file to the IIS folder.

  2. Verify that the folder contains the expected Board Web files and folders.

Step 5: Set folder permissions

  1. Right-click C:\inetpub\wwwroot\BWEB.

  2. Select "Properties".

  3. Select the "Security" tab.

  4. Select "Edit".

  5. Grant "Full control" to the IIS_IUSRS group.

  6. Select "Apply".

  7. Select "OK".

Step 6: Configure the certificate between Board Web and Board Engine

Board Web and Board Engine use a certificate to support secure communication between the Web Node and the Board Engine Node.

Use a certificate that meets your company security requirements. For production environments, use a trusted Certificate Authority when required by your security policy.

  1. Create the certificate.
    Create a certificate on one server, then export it with the private key in PFX format.

    You can create a local certificate with Windows PowerShell.

    cd cert:

$cert = New-SelfSignedCertificate `
  -DnsName company.com `
  -FriendlyName MyCert `
  -CertStoreLocation Cert:\LocalMachine\My

$rootStore = New-Object System.Security.Cryptography.X509Certificates.X509Store `
  -ArgumentList Root, LocalMachine

$rootStore.Open("MaxAllowed")
$rootStore.Add($cert)
$rootStore.Close()

    Replace “company.com” with the host name for your environment.

  2. Export the certificate.
    Run these commands in an elevated Windows PowerShell session.

    $mypwd = ConvertTo-SecureString -String "YourPassword" -Force -AsPlainText

cd .\LocalMachine\My\
dir

Get-ChildItem -Path Cert:\LocalMachine\My\<certificate_thumbprint> |
  Export-PfxCertificate `
    -FilePath C:\temp\myBoardPfx.pfx `
    -Password $mypwd

    • Replace “<certificate_thumbprint>” with the certificate thumbprint.

    • Do not use the sample password from the source article in a real environment.

  3. Import the certificate on both nodes.

    Import the PFX certificate on both servers: Web Node and Board Engine Node.

    Use this certificate store:Local Machine\Personal\Certificates

    Context menu showing options for the file 'myBoardPfx' in Windows Explorer.
    Certificate Import Wizard interface showing steps for importing a certificate securely.

  4. Configure certificate permissions.

    1. Open "Certificate Manager" by running certlm.msc.

    2. Go to "Personal".

    3. Go to "Certificates".

    4. Right-click the certificate.

    5. Select "All Tasks".

    6. Select "Manage Private Keys".
      Certificate management interface showing options for managing private keys and certificates.

    7. Select "Add".

    8. Enter IIS_IUSRS and click “OK”.

    9. Grant "Read" permission.

    10. Select "Apply".

    11. Select "OK".

  5. Add the certificate configuration to Board Web.

    1. Open this file on the Web Node:

      C:\inetpub\wwwroot\BWEB\App_Data\config\appSettings.conf

    2. Add or update these parameters in the configuration section of the file above:

      <add key="certificateStoreName" value="My" />
<add key="certificateStoreLocation" value="LocalMachine" />
<add key="certificateThumbprint" value="<certificate_thumbprint>" />

      Replace “<certificate_thumbprint>” with the certificate thumbprint.

  6. Add the certificate configuration to Board Engine.

    1. Open this file on the Board Engine Node:

      C:\Program Files\Board\Board Server\server_config_v2.xml

    2. Add or update these parameters in the configuration section of the file above

      WebSigningCertificateStoreName="My"
WebSigningCertificateStoreLocation="LocalMachine"
WebSigningCertificateThumbprint="<certificate_thumbprint>"

      Replace “<certificate_thumbprint>” with the certificate thumbprint.

Configure IIS and Board Web settings

After you copy Board Web files to the IIS folder and configure the certificate, configure IIS to host the site. Then update the Board Web configuration file so Board Web can use the correct public URL and connect to Board Engine.

Before you add the HTTPS binding, make sure the SSL certificate is already installed on the Web Node.

Step 1: Create the IIS website

  1. Open "IIS Manager" on the Web Node.

  2. Create a new website.

  3. Set "Site name" to BWEB, or use the name required by your environment.

  4. Set "Physical path" to C:\inetpub\wwwroot\BWEB.

  5. Add an HTTPS binding.

  6. Set the host name to the external name of the Web Node, such as boardweb.company.com.

  7. Set the port to 443.

  8. Select the SSL certificate that you created or installed earlier.

  9. Select "OK".

    Configuration settings for adding a new website with SSL certificate options.

Step 2: Configure the Application Pool Settings

  1. In "IIS Manager", select "Application Pools".

  2. Select the application pool for the Board Web site.

  3. Select "Advanced Settings".

  4. Set "Load User Profile" to True.

  5. Select "OK".

    Application Pools settings in IIS, highlighting Load User Profile option set to True.

Step 3: Remove the WebDAV module

If WebDAVModule is present, remove it from the IIS modules configuration.

  1. In "IIS Manager", select the Board Web site.

  2. Open "Modules".

  3. Select "WebDAVModule".

  4. Select "Remove".

    Configuration interface displaying various web server modules and their settings options.

Step 4: Configure Board Web connection settings

  1. Find the file located in the Board Web site folder on the Web Node:

    C:\inetpub\wwwroot\BWEB\App_Data\config\appSettings.conf
    Use this file to define the public Board Web URL and the connection to Board Engine.

  2. Add or update these parameters in the configuration section of the file above

    <add key="host" value="https://boardweb.company.com/" />
<add key="publicOrigin" value="https://boardweb.company.com/" />
<add key="boardEngine" value="https://boardengine.company.com/" />

    • Replace “https://company.com/” with the external URL used to access Board Web.

    • The “host” and “publicOrigin” values must match the public URL configured in the IIS binding.

    • The “boardEngine” value must point to the Board Engine Node. Board Web uses this value to communicate with Board Engine.

Step 5: Open ports on the Board Engine Node

Board uses ports 9700 to 9710 for communication between Board Web and Board Engine.

Open this port range in Windows Firewall on the Board Engine Node: 9700-9710

Step 6: Configure the Board Mailer Service

The Board Mailer Service configuration is stored in the Board Web folder on the Web Node.

  1. Edit the Mailer service configuration file.

    1. Open the file C:\inetpub\wwwroot\BWEB\bin\Board.Mailer.Service.exe.config

    2. Update the values for the web URL, watch path, and log folder:

      <add key="WebUrl" value="https://boardweb.company.com" />
<add key="watchPath" value="C:\inetpub\wwwroot\BWEB\App_Data\broadcasting" />
<add key="logFolder" value="C:\inetpub\wwwroot\BWEB\App_Data\broadcasting\Log" />

      • Replace “https://boardweb.company.com/” with the Board Web URL for your environment.

      • The App_Data\broadcasting\Log folder stores broadcasting logs used by the Board Mailer Service.

      • The WebUrl value must match the Board Web host configured in appSettings.conf.

  2. Reconfigure and start the Board Mailer Service.

    1. If needed, restart the server and then run these commands in an elevated Command Prompt (Run cmd as Administrator):

      "C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe" "C:\inetpub\wwwroot\BWEB\Bin\Board.Mailer.Service.exe"

sc config BoardMailerService start=auto

sc start BoardMailerService

Windows Authentication

  1. Open “IIS Manager” on the Web Node.

  2. Select the BWEBsite.

  3. Open “Authentication”.

  4. Enable "Windows Authentication".
    IIS Manager showing Windows Authentication status as enabled in the Authentication section.

Configure a custom Log folder (Optional)

This section is optional. Use it only when you need to store Board logs in a different location.

Run the following  commands in an elevated Command Prompt (Run cmd as Administrator):

  • On the Board Engine Node:

    mklink /J "X:\Board\Dataset\Log" "K:\Board\Log"

  • On the Web Node:

    mklink /J "C:\inetpub\wwwroot\BWEB\App_Data\log" "K:\Board\WebLog"

Replace the paths with the folders used in your environment.

Validate the installation

After the setup is complete, validate the installation.

  1. Verify that Board Engine is running on the Board Engine Node.

  2. Verify that the Board Mailer Service is running on the Web Node.

  3. Open the Board Web URL in a supported browser.

  4. Verify that the HTTPS certificate is valid.

  5. Verify that the Web Node can connect to the Board Engine Node.

  6. Verify that ports 9700 to 9710 are open from the Web Node to the Board Engine Node.

  7. Verify that users can access Board Web.

  8. Verify that logs are written to the expected folders.

  9. Test the main user flows used in your environment.