Boring Server Complete Installation Fails on Non-English Windows Systems using 'Network Service'

Issue

The Boring Server Complete installer may fail on Windows systems configured to use a language other than English.

This can occur when the Milestone IIS application pool is configured to run as Network Service. On non-English Windows installations, the Network Service account name may be localized. As a result, the installer may be unable to find or resolve the account correctly.

Resolution

Temporarily configure the Milestone IIS application pool to use a Windows service account, run the Boring Server Complete installer and database migration, and then restore the IIS application pools and Boring Windows services to Network Service.

Step 1: Change the Milestone Application Pool Identity

1. Open Internet Information Services (IIS) Manager.
2. In the Connections pane, select Application Pools.

3. Select:

   VideoOS Management Server AppPool

4. In the Actions pane on the right, click Advanced Settings.
5. Expand the Process Model section.
6. Select the Identity property, and then click the … button.
7. Select Custom account.
8. Click Set.

9. Enter the username and password for a Windows service account with sufficient permissions.

   The username may need to be entered in one of the following formats:

   DOMAIN\Username

   or:

   COMPUTERNAME\Username

10. Click OK to save the credentials.
11. Click OK again to close the Application Pool Identity window.
12. Click OK to close Advanced Settings.

Step 2: Run the Boring Server Complete Installer

Run the Boring Server Complete installer again.

Allow the installation to complete before restoring the application pool identity to Network Service.

Step 3: Run the Boring Database Migration

After the installer completes, manually run the Boring database migration using the same service account or another Windows account that has permission to make changes to the Boring database.

For an existing installation, the account must have db_owner permissions on the BoringBase database.

For a new installation, the account must also have permission to create a database on the SQL Server instance.

Follow the instructions in:

Running the Boring Database Migration Manually

Run the migration from the following installation directory (default below):

cd "C:\Program Files\The Boring Lab\Boring Migration\"
.\BoringLab.Data.Migrations.exe

Step 4: Restore the IIS Application Pool Identities

After the installation and database migration complete successfully, restore the IIS application pools to Network Service.

Repeat the following steps for each application pool:

• VideoOS Management Server AppPool
• BoringLabService AppPool
• BoringToolboxWeb AppPool

For each application pool:

1. Open IIS Manager.
2. Select Application Pools.
3. Select the application pool.
4. Click Advanced Settings in the right-side Actions pane.
5. Expand Process Model.
6. Select the Identity property, and then click the … button.
7. Select Built-in account.
8. Select NetworkService from the drop-down menu.
9. Click OK to save the change.
10. Click OK to close Advanced Settings.
11. Recycle or restart the application pool.

Step 5: Restore the Boring Windows Services

The Boring Windows services should also be configured to run as Network Service after installation.

1. Press Windows + R.

2. Enter:

   services.msc

3. Click OK.
4. Locate each installed Boring Windows service, including:
   • Boring Live Monitoring
   • Boring Milestone Proxy
   • Boring Service Host
5. Right-click the service and select Properties.
6. Open the Log On tab.
7. Select This account.

8. Find and select the built-in Network Service account. The account name may be localized and displayed differently depending on the Windows language.

9. Leave the password and password confirmation fields blank.
10. Click Apply, and then click OK.
11. Restart the service.

Repeat these steps for each installed Boring Windows service.

Verification

After restoring the IIS application pools and Windows services:

1. Confirm that the following application pools show a Started status in IIS:
   • VideoOS Management Server AppPool
   • BoringLabService AppPool
   • BoringToolboxWeb AppPool
2. Confirm that all installed Boring Windows services are running.
3. Open Boring Toolbox and verify that the application loads successfully.
4. Confirm that Boring Toolbox can communicate with the Milestone Management Server.
   https://management-server-address/BoringToolbox 
   (replace management-server-address with the address of the management server)