Configure NLB
- Last UpdatedApr 01, 2026
- 2 minute read
Overview
Microsoft Network Load Balancing (NLB) can be used to configure multiple web servers for high availability and load distribution in AVEVA Work Tasks Enterprise Console deployments.
In this setup, multiple web servers are grouped into an NLB cluster and exposed through a single virtual IP address or URL. Incoming requests are distributed across the available servers.
For redundancy, NLB (or ARR) can be used as a recommended approach.
Logical architecture (Example configuration)
In a typical deployment, AVEVA Work Tasks can be configured with multiple web servers for redundancy using Network Load Balancing (NLB).
A common setup includes:
-
Two engine servers
-
Two web servers configured in an NLB cluster
-
One database server
This architecture can be extended to include additional components such as SMS Server or License Server, based on deployment requirements.
Prerequisites
Before configuring NLB:
-
Each web server must have: Static IP addresses
-
Two network adapters (NICs) configured (as required by the environment)
-
Windows Network Load Balancing feature must be installed
-
Servers must be reachable within the same network
Install and configure NLB
For detailed steps on configuring Windows Network Load Balancing, refer to Achieving High Availability and Scalability - ARR and NLB.
Important: Configuring NLB requires knowledge of Microsoft NLB architecture, including network configuration, port management, and cluster setup. It is recommended that NLB configuration be performed by personnel familiar with these concepts.
Limitations
Web API calls initiated from the user interface may not complete successfully if a server becomes unavailable
Certificate requirements for NLB
Use certificates provided by IT
If your IT department provides the certificates, ensure that the certificates are installed in the appropriate certificate stores on the local machine.
-
Import the root certificate into the Local Computer Trusted Root Certification Authorities store
-
Import the intermediate certificate into the Local Computer Intermediate Certification Authorities store
-
Import the SSL certificate into the Local Computer Personal store
Certificates storage requirements
|
Certificate |
Store |
Private Key Access Permissions |
|
Root certificate |
Local Computer Trusted Root Certification Authorities store |
Not applicable |
|
Intermediate certificate |
Local Computer Intermediate Certification Authorities store |
Not applicable |
|
SSL certificate |
Local Computer Personal store |
Ensure appropriate read access is configured for the application pool identity |
SSL certificate requirements
|
Field |
Value |
Comment |
|
Key Usage |
Digital Signature, Key Encipherment, Data Encipherment (b0) |
Required |
|
Enhanced Key Usage |
Server Authentication (1.3.6.1.5.5.7.3.1) |
Required |
|
Subject Alternative Name |
DNS Name = <nlb-cluster-url> |
Must include the common NLB URL used to access the application |
|
DNS Name = <machine-name> |
Required |
|
|
DNS Name = <fully-qualified-domain-name> |
Required when wildcard is not used |
|
|
DNS Name = <wildcard-domain> |
Optional |
Note: If you are using certificates provided by your IT team, ensure that Microsoft guidelines for certificate creation and installation are followed. The certificate must include the common NLB URL as part of the certificate request.