Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Enterprise Licensing

Workgroup back-end applications

  • Last UpdatedFeb 05, 2025
  • 1 minute read

Work with back-end applications in a workgroup environment

Back-end applications must access a local or remote License Server node to acquire licenses. When a workgroup topology is implemented and the License Server is installed on a remote node, special configuration arrangements are required.

The possible scenarios and applicable authentication processes are described below.

Scenario 1 (Recommended): License Manager, License Server and Installed Products on Single Node

Use of a workgroup configuration may not be as secure as an Active Directory domain controller. For security reasons, the recommended configuration is to have License Manager and License Server installed on each node that will have installed products that need to be licensed. Each node must belong to either the SELicMgr or Administrator Security Identity group.

Licenses should then be activated and administered only for the products installed on each node.

Scenario 2: Back-End or Clients Running on a Separate Node than the License Server

In this scenario, the License Server is installed on one node, and the products that need to acquire licenses are installed on another node and are running as User accounts. User accounts present their local identity to the remote node. The remote node will then examine the local user repository for the exact same user name and password from the requesting account.

If a match is found, the account that the back-end or client application is running as is authenticated. Otherwise it is not authenticated. This means that the account that the back-end or client application is running as must be replicated on the License Server node.

TitleResults for “How to create a CRG?”Also Available in