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 single-node installation

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

This article explains how to install Board server on a single-node Windows server environment.

This article covers:

A single-node setup runs Board Engine and Board Web on the same Windows server. The diagram bellow shows this setup with IIS Web, Board Engine, and separate volumes for Board data, logs, and web files.

Before you begin

Before you begin, have in mind:

  • The steps in this article assume that Board Engine and Board Web are installed on the same Windows Server.

  • Make sure the Windows server meets the required software and security prerequisites before you install Board server. You need administrator permissions on the server.

  • 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 server, complete:

  1. Install Microsoft IIS Role. Make sure Internet Information Services (IIS) is installed and properly configured on the Windows Server.

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

  3. In IIS, enable these role services under Application Development:

    1. ASP.NET 4.8

    2. WebSocket Protocol

  4. 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 server

Step 1: Run the Board server 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, highlighting security risks and application paths.

Step 4 (Optional): Customize Board path

Follow these steps if you need Board to store data on a different 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 and BoardData locations with options menu.

  4. Apply changes.

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

    2. Select "Start Service".

Install Board Web under IIS

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 of the BWEB folder, including size, location, and attributes settings.  

  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. 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.

    Directory listing showing folders and a config file in a web server structure.

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 (Optional): Configure a local certificate

This section is optional. Use it only when you need a local certificate for the Board Web setup.

For production environments, use a certificate that meets your company security requirements.

  1. Create a certificate.
    Run these commands in an elevated Windows PowerShell session

    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. 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".

  4. Add the certificate configuration to Board Web.

    1. Open this file:

      C:\inetput\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.

  5. Add the certificate configuration to Board Server.

    1. Open this file:

      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, configure IIS to host the site. Then update the Board Web configuration files 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 server.

Step 1: Create and configure the IIS website

  1. Open the IIS Manager.

  2. Add a new website and set its physical path to the BWEB folder.

    Configuration settings for adding a new website in IIS, including site name and bindings.

  3. Then, add a binding that associates the site with the external name or IP address of the server you intend to use.

    Configuration settings for SSL site binding, including hostname and certificate options.

  4. In "SSL certificate", select the certificate that you created or installed earlier.

  5. Select "OK".

Step 2: Configure the Application Pool settings

  1. Open the Application Pool of the IIS Board website.

  2. Click on “Advanced Settings”.

  3. Set Load User Profile to True.

  4. Click “OK”.
    Advanced settings for application pools in IIS, highlighting 'Load User Profile' option.

Step 3: Configure the public origin

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

    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://company.com/" />
<add key="publicOrigin" value="https://company.com/" />
<add key="boardEngine" value="https://company.com/" />
<add key="port" value="443" />

    • 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.

Step 4: Configure the Board Mailer service

  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://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://company.com/” with the 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”.

  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):

mklink /J "X:\Board\Dataset\Log" "K:\Board\Log"
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 the Board service is running.

  2. Verify that the Board Mailer Service is running.

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

  4. Verify that the HTTPS certificate is valid.

  5. Verify that users can access the Board Web site.

  6. Verify that Board Web can connect to Board Engine.

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