AVEVA™ Enterprise Licensing version 3.7 Readme

Last revision: 11/19/2020

In This Document

About this Readme

AVEVA Enterprise Licensing Changes and Enhancements

AVEVA Enterprise Licensing Installation

Resolved Issues

Known Issues

Web Help Display and Video Playback

AVEVA Enterprise Licensing Documentation

About this Readme

This document contains important information about AVEVA Enterprise Licensing version 3.7. This Readme documents the system requirements, known issues, resolved issues, and changes, if any, to the AVEVA Enterprise Software documentation included with the AVEVA Enterprise Licensing components.

You can upgrade to version 3.7 directly from versions 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.5.1, and 3.6. Licensing versions earlier than 3.0 require upgrade to version 3.0 before upgrading to version 3.7.

Note: You can find information and procedures for installing and upgrading AVEVA Enterprise Licensing, License Manager, and License Server in the AVEVA Enterprise Licensing Installation online help, available from the installation utility.

AVEVA Enterprise Licensing Changes and Enhancements

The AVEVA Enterprise Licensing system is a common platform that allows you to effectively and efficiently manage AVEVA Enterprise Software product licenses. It is composed of a browser-based License Manager and a License Server that work together to allow you to share and deliver licenses for your installed products with or without an Internet connection.

Version 3.7

This version incorporates the following components and enhancements:

Version 3.6

This version incorporates the following components and enhancements:

Version 3.5.1

This release includes several hotfixes. For more information, refer to the Resolved Issues of Version 3.5.1 section.

Important: AVEVA Enterprise Licensing platform version 3.5.1 is not compatible with versions 2.0 or earlier. Versions 2.0 and earlier were installed with Recipe Manager Plus 2014 R3 and earlier, Alarm Adviser 2014 R2 SP1 and earlier, and Intelligence 2014 R3 and earlier. Upgrading to AVEVA Enterprise Licensing platform version 3.5.1 could interfere with the functionality of those products. To upgrade to version 3.5.1 when you have versions 2.0 and earlier already installed on your system, you need to apply a hotfix. Contact AVEVA Technical Support to obtain the hotfix, and reference change request L00152975.

Version 3.5

This version incorporates the following components and enhancements:

Version 3.4

This version incorporates the following components and enhancements:

Enhanced License Server diagnostics reporting to SMC Log and Grace Period analysis reporting for virtual environments.

Version 3.3

This version incorporates the following components and enhancements:

Version 3.2

This version incorporates the following components and enhancements:

Version 3.1

This version incorporates the following components and enhancements:

Version 3.0

This version incorporates the following components and enhancements:

AVEVA Enterprise Licensing Installation

Introduction

Installation Requirements

Installation

Upgrading AVEVA Enterprise Licensing

Uninstalling AVEVA Enterprise Licensing

Introduction

The AVEVA Enterprise Licensing system is a common platform that allows you to effectively and efficiently manage AVEVA Enterprise Software product licenses. It is composed of a browser-based License Manager and a License Server that together allow you to share and deliver licenses for your installed products.

You can install AVEVA Enterprise Licensing with AVEVA Enterprise products or you can install as a standalone. Different types of installation that you can install as a standalone are:

Installation Requirements

This section describes the operating system, hardware, and software requirements to install AVEVA Enterprise Licensing.

Supported Operating Systems

Below are the Operating System minimum requirements:

AVEVA Enterprise Licensing requires .NET Framework 4.8. The licensing installation process checks if .NET version 4.8 is installed. If not, you are prompted to allow .NET installation.

Note: A system restart is required when .NET installation is complete. If the licensing installation does not automatically resume after the system restart, you can restart it manually.

Hardware Requirements

Below are the basic hardware requirements to install AVEVA Enterprise Licensing:

Software Requirements

Port List

The following ports are used by default:

Installation

This section describes the installation steps of AVEVA Enterprise Licensing.

Installing AVEVA Enterprise Licensing

Note: All installed products should be shut down before upgrading. This will release all the licenses so that when the products are re-started licenses will be acquired correctly.

To install the AVEVA Enterprise Licensing standalone

  1. Right-click the setup.exe file and select Run as administrator.

    The License Agreement screen appears.

  2. Accept the End User License Agreement and then click Next.
  3. Select the components that you want to install:
  4. Click Next.

    The Ready to Install the Application screen appears.

  5. Click Install to start the installation.

    Once the installation is complete, the installation successful dialog box appears.

  6. Click Finish.
  7. Configure the License Server as needed:

Installing AVEVA Enterprise Licensing Silently

If you are installing AVEVA Enterprise Licensing to multiple computers, you can run the installation "silently" (command line mode).

Installing AVEVA Enterprise Licensing Silently from the Command Line

  1. Open the command prompt (cmd.exe) as Administrator.
  2. Change the working directory to the folder where you downloaded AVEVA Enterprise Licensing Setup.exe.
  3. Run one of the following commands, depending on whether or not you want the computer to reboot automatically:

Upgrading AVEVA Enterprise Licensing

You can verify the version of License Manager by navigating to Control Panel and selecting Programs and Features. The installed AVEVA Enterprise License Manager, AVEVA Enterprise License Server, or AVEVA Enterprise Licensing (licensing platform components) version displays in the Version column.

Note:

- Licensing platform components are installed with every product, whether or not a License Manager or a License server are installed on that node. These components display in Programs and Features as "AVEVA Enterprise Licensing" for both 32- and 64-bit systems.

- To be able to checkout licenses, the Server node, Manager node and the relevant Client node should be upgraded to version 3.6 or higher.

The following table describes different upgrade scenarios of AVEVA Enterprise Licensing to version 3.7. In some upgrade scenarios, licenses will enter the grace period. You can resume normal licensing functionality when the grace period ends. Refer to the AVEVA Enterprise Licensing Help, "Working with the Grace Period" topic for more information.

Product Node Upgrade Scenarios

Description

Upgrade a product on the same node as an installed version of License Manager earlier than 3.7.

License Manager and the AVEVA Enterprise Licensing components will upgrade to version 3.7 automatically.

Upgrade a product on the same node as an installed version of License Server earlier than 3.7.

License Server and the AVEVA Enterprise Licensing Components will upgrade to version 3.7 automatically.

Upgrade a product on the same node as installed versions of both License Manager and License Server earlier than 3.7.

License Manager, License Server, and the AVEVA Enterprise Licensing Components will upgrade to version 3.7 automatically.

Upgrade a product on a node that has no License Manager or License Server installed.

The AVEVA Enterprise Licensing components will upgrade to version 3.7 automatically.

Will not result in an automatic upgrade of License Manager and License Server installed on remote nodes. You must upgrade your License Manager and License Server separately on the node where each is installed.

Upgrade to version 3.7 in Hyper-V and Azure virtual machines

The license server will enter the Grace Period upon upgrade. End this grace period by syncing the licenses in the License Server. See the AVEVA Enterprise Licensing Guide for the procedure of syncing licenses.

Important Note: To avoid entering the Grace Period, deactivate all licenses on the license server prior to upgrade in this scenario.

Licensing Version Upgrade Scenarios

Description

Upgrade from version 3.0 to 3.7

The license server will enter the Grace Period upon upgrade. End this grace period by syncing the licenses in the License Server. See the AVEVA Enterprise Licensing Guide for the procedure of syncing licenses.

Important Note: To avoid entering the Grace Period, deactivate all licenses on the license server prior to upgrade in this scenario.

Upgrade - from all versions to all versions

If the license server is in a Grace Period prior to upgrade, it will remain in Grace Period following upgrade. To end the Grace Period after upgrading, you will need to contact Technical Support to obtain a Grace Period exit code.

To avoid this scenario, end the Grace Period before upgrading to a newer License Server version.

Upgrade from version 3.1 to 3.7

The license server will not enter a Grace Period upon upgrade.

Upgrade from version 3.2 to 3.7

The license server will not enter a Grace Period upon upgrade.

Upgrade from version 3.3 to 3.7

The license server will not enter a Grace Period upon upgrade.

Upgrade from version 3.4 to 3.7

The license server will not enter a Grace Period upon upgrade.

Upgrade from version 3.5 to 3.7

The license server will not enter a Grace Period upon upgrade.

Upgrade from version 3.5.1 to 3.7

The license server will not enter a Grace Period upon upgrade.

Upgrade from version 3.6 to 3.7

The license server will not enter a Grace Period upon upgrade.

Note: You can resume normal licensing functionality once the Grace Period is ended. See the AVEVA Enterprise Licensing Guide for the detailed procedure. Since all licenses should be removed from the server prior to ending the Grace Period, no licenses will be lost due to this action.

To upgrade AVEVA Enterprise Licensing

Note: All products should be shut down before upgrading. This will release all the licenses so that when the products are started licenses will be acquired correctly.

  1. Right-click the setup.exe file and select Run as administrator.

    An alert message with the list of products that will be upgraded appears.

  2. Click OK.

    The License Agreement screen appears.

    Follow the steps from step 2, in the Installing AVEVA Enterprise Licensing section.

Uninstalling AVEVA Enterprise Licensing

Note: You cannot uninstall the product licensing if there is a product currently installed or when other products are currently using it.

To uninstall an AVEVA Enterprise Licensing Component

  1. Click the Uninstall or Change a Program option in Windows Control Panel. The list of software installed on your computer appears.
  2. Select the AVEVA Enterprise Licensing component that you want to uninstall, and then click the Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.
  3. Click the Remove option, and then click Next. The confirmation dialog box appears.
  4. Click Uninstall. The component is uninstalled, and the complete uninstallation dialog box appears.
  5. Click Finish.

Modifying AVEVA Enterprise Licensing

You can change the AVEVA Enterprise Licensing components installed on your computer. You can add new components or remove the existing ones. You can modify any component of AVEVA Enterprise Licensing.

Note: You must have the installation media ready before you can modify a program.

To modify an installation

  1. Select the Modify option from the AVEVA Enterprise Licensing Modify, Repair or Remove Installation dialog box. You can open the dialog by doing either of the following:

    Note: The name of the Uninstall/Change option may vary depending on which Windows operating system is installed on your computer.

  2. Click the Modify option, and then click Next. The list of AVEVA Enterprise Licensing components appears.
  3. Select or clear the components that you want to add or remove, and then click Next. The verify change dialog box appears.
  4. Click Modify. The selected components are added or removed and the complete modification dialog box appears.
  5. Click Finish.

    Note: The system may not prompt you to restart the system after Modify is successful. However, if you have added a new product or feature, a system restart is recommended.

Repairing AVEVA Enterprise Licensing

You can repair the installation of any component of the AVEVA Enterprise Licensing. You can repair missing or corrupt files, registry keys or shortcuts. You can also reset the registry key to the default value.

Note: You must have the installation media ready before you repair a program.

To repair an installation

  1. Click the Uninstall or Change a Program option in Windows Control Panel. The list of software installed on your computer appears.
  2. Select the AVEVA Enterprise Licensing component that you want to repair, and then click the Uninstall/Change button. The Modify Repair or Remove Installation dialog box appears.

    Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.

  3. Click the Repair option, and then click Next. The Confirm Repair dialog box appears.
  4. Click Repair. The complete repair dialog box appears.
  5. Click Finish.

Resolved Issues

This section describes resolved issues in AVEVA Enterprise Licensing.

Resolved Issues of Version 3.7

CR/Defect Number

Service Request ID

Description

L00156638

-

Multi-instances of ABCIP Communication Drivers got deactivated and displayed the red status icon.

L00156722

-

The MOM client license could not be released after closing InTouch application on Terminal server.

L00157891

-

The Batch client on Terminal got disconnected from the Batch server.

L00158417

SR 103168922

Licenses were not released by the WindowViewer when the RDP sessions were logged off.

L00158773

SR 103172663

Could not establish connection to the remote License Server after the installation of Communication Drivers Pack 2020.

L00159099

SR 103172244

The remote server returned an error: (407) Proxy Authentication Required.

L00159129

SR 73610236

Could not check-out licenses on ACP thin client RDS Server.

L00159391

SR 48710641

The Historian Client worksheet could not recognize the license. The log messaged displayed as 'tamper detected'.

L00159478

-

When Offline-Activated for the first time, could not activate or deactivate the subsequent line entries.

L00159639

 

Historian acquired two licenses from the pool even though the Device Reservation had been done using the 5K tag license.

L00159640

SR 103174543

Error messages were displayed in the logger when reserving and deactivating licenses.

Resolved Issues of Version 3.6

CR/Defect Number

Service Request ID

Description

L00154325

-

The remote server returned an error: (503) Server unavailable

L00153969/

L00155897/

L00156554

-

Adding a domain group to the SELicMgr did not work.

L00154320

-

The primary License Server Core Service was stopping and starting. Eventually, it consumed 2GB of RAM and did not work.

L00155069

SR 103162536

The License Server ran into grace period.

L00153235

-

Unable to see the Usage Details in the paired redundant License Server.

L00153698

-

OI Server Professional was acquiring license from the Backup Server instead of the Primary Server.

L00154362

-

Trend could not see the license. Trend was not running on the Historian Server even when everything was local and Historian was running fine.

L00156722

SR 103166266

The MOM client license cannot be released after closing the InTouch application on the Terminal server.

Resolved Issues of Version 3.5.1

CR/Defect Number

Service Request ID

Description

L00151754

SR59210165

OEM bin license files were not working with terminal services.

L00151825

SR103156510

.bin license file was not detected by the License Manager.

L00151755

SR37613245

.bin license file was not detected by the License Manager after hard shut down.

-

-

Failover was not happening back from Backup Server to Primary Server when Primary Server came up.

-

-

Deployment of LicAPIConnection.dll and LicAPILoader.dll to GAC so that all products use the latest dlls.

 

-

It was unable to break redundant pair when exit grace period code is activated on the pair.

-

-

Redundant Server Upgrade to 3.5 was breaking the pair.

L00151982

SR 103156929

It was unable to clear grace period expired on redundant license servers.

-

-

Monitor thread in License Server agent to monitor License Server memory consumption and restart.

-

-

Changes related to environment ID calculation for machines where hardware parameters cannot be retrieved.

Resolved Issues of Version 3.5

CR/Defect Number

Service Request ID

Description

CR L00150317

SR 103153019 and SR 103153041

After adding domain groups to SELicMgr group, users did not get permissions to access License Manager.

Resolved Issues of Version 3.4

CR/Defect Number

Service Request ID

Description

L00148154 / 985368

SR 12614248

SR 38710447

The Historian could not acquire a license due to a corrupted ServerConfig.xml file.

1023561

 

Licenses were not getting released during deactivation when the License Server is not running on the default port.

1018005

 

Was not able to reserve licenses using IP address.

L00149110

SR 48912110

Was not able to access the SELicenseManager portal even though the user was in the domain user group, which was a member of "SELicMgr" group.

L00149014

SR103150510

When changing the demo license with a new license, the Historian client was not able to see the new one.

L00148723

SR10918122

SR59010207

SR59010232

Redundant License pair got unpaired by itself. Backup server was unable to provide licenses.

L00149098

SR 12614357

The backup license server in a redundant configuration failed after three days when the primary license server did not become active during that period.

Resolved Issues of Version 3.3

CR/Defect Number

Service Request ID

Description

L00147842

SR 103148987 SR 103149093

The License Server ID changed while the server was running, with licenses active on the server. This caused issues with the active licenses.

985890

 

Paired License servers were not able to communicate with each other after renaming a license server machine and launching License Manager in a new machine.

Resolved Issues of Version 3.2

Defect Number

Service Request ID

Description

777401

 

If Wonderware Intelligence 2014 R3 is installed on the same node as Schneider Electric Licensing 3.1, Intelligence will fail to acquire a license.

If Wonderware Intelligence 2014 R3 is installed on the same node as Schneider Electric Licensing 3.1 and Alarm Adviser 2014 R2 SP1 or Recipe Manager Plus 2014 R3, then each product will fail to acquire a license.

Please contact Global Customer Support for assistance.

Resolved Issues of Version 3.1

Defect Number

Service Request ID

Description

L00140352

103139020

License Manager documentation has been updated to specify that both ports 55555 and 59000 must be open when validating server configuration.

TFS 698291

 

When a License Server containing activated licenses was upgraded from earlier versions to version 3.0, offline license activation would fail while offline deactivation would succeed. In both cases, the Pending Activation Request notification would remain in the Activation Grid.

Resolved Issues of Version 3.0

Defect Number

Service Request ID

Description

L00140352

103139020

License Manager documentation has been updated to specify that both ports 55555 and 59000 must be open when validating server configuration.

TFS 698291

 

When a License Server containing activated licenses was upgraded from earlier versions to version 3.0, offline license activation would fail while offline deactivation would succeed. In both cases, the Pending Activation Request notification would remain in the Activation Grid.

Known Issues

This section describes known issues in AVEVA Enterprise Licensing.

Known Issues of Version 3.7

Defect Number

Description

614163

Checkout fails when the same feature from two different versions are checked out from license manager to the same device.

Workaround: Checking out the feature from both the versions at the same time works. That is, checkout the feature from one version and simultaneously, checkout the feature from the other version too.

NA

If Intelligence 2017 Update 1 plugin and the License Server plugin are installed on the same node, the License server configuration fails.

Workaround:

For issue resolution, contact Technical Support.

Known Issues of Version 3.6

Defect Number

Description

1249922

When the communication between the client machines and the primary server failed, the licenses were acquired from the backup server (3.3), even though the primary server was online. In this scenario, when the License Server was upgraded from version 3.3 to version 3.6, the Backup License Server failed to start.

 

Workaround:

  1. Re-create the FNEServer folder in the Backup Server in the path C:\ProgramData\FNEServer.
  2. From the License Manager, start the Backup License Server.
  3. From the License Manager, perform a ‘Sync’ operation to get the licenses on to the Backup Server. For more information about syncing licenses, see the AVEVA Enterprise Licensing Guide.

1251403

Errors and Warnings were observed in the Logger when License Manager was upgraded from an earlier version to version 3.6 without closing the client.

 

Workaround: All the errors and warnings display additional information and get automatically resolved once the upgrade is complete. We recommend that you close the browser in the License Manager before the upgrade.

L00156638

Multi-instances of OI ABCIP start showing the red icon of (screenshot attached), and then shortly become deactivated. This keeps propagating through the system causing communications loss.

L00156181

Multi-instance ABCIP OI Server is not getting license and is disconnected randomly.

1282154

When the computer name is changed in both the primary and secondary license servers in a paired scenario, the backup license server does not get detected, and the server enters a grace period.

1268190

During the upgrade of Remote System Platform Development Client from WSP 2017 on Simplified Chinese Windows 8.1 Pro OS, a message is displayed from the License Server notifying that the License Server is in upgrade grace period.

1251206

License Manager gets an “Access denied” error if the trust relationship between the domain and the machine is broken.

Known Issues of Version 3.5.1

Test Setup

Description

L00152975

AVEVA Enterprise Licensing platform version 3.5.1 is not compatible with versions 2.0 or earlier, which were installed with Recipe Manager Plus 2014 R3 and earlier, Alarm Adviser 2014 R2 SP1 and earlier, and Intelligence 2014 R3 and earlier. Upgrading to AVEVA Enterprise Licensing version 3.5.1 could interfere with the functionality of those products. To upgrade to version 3.5.1 when you have versions 2.0 and earlier already installed on your system, you need to apply a hotfix. Contact AVEVA Customer Support to obtain the hotfix, and reference this change request.

License Manager 3.5, License Server 3.5.1

When License Server is in an upgrade grace period, License Manager did not remove grade period by preserving licenses. License Server ID is changed. So licenses are lost. Also, upgrade grace period flag was not reset.

License Manager 3.5.1, License Server 3.5

When tried to reset License Server ID from UI, the License Server ID is not reset.

License Manager 3.5.1, License Server 3.5

When License Server is in an upgrade grace period, License Manager did not remove grace period by preserving licenses.

License Manager 3.5.1, License Server 3.5

After renaming License Server machine and deactivating licenses, License Server ID has not changed.

License Manager 3.5.1, License Server 3.5

After License Servers are unpaired, Server IDs are not changed.

Note: If License Manager or License Server is in version 3.5, then the License Manager should be upgraded before the License Server.

Known Issues of Version 3.5

There are no known issues in version 3.5 of the AVEVA Enterprise Licensing.

Known Issues of version 3.4

Defect Number

Description

1052505

A warning message appears in the Configurator when Schneider Electric Licensing (licensing components other than License Manager and License Server) is upgraded from version 3.2 to version 3.4 where the computer has version 2.0 or older installed before version 3.2 was installed.

Note: Because you can upgrade to version 3.4 only from version 3.0 or later, it might be necessary to first upgrade from 2.0 to 3.0. The warning message subsequently displays in the Configurator as described.

The displayed warning message: ServerConfig file is not in proper format. Please check with administrator.

Workaround:

The message can safely be ignored. The message does not appear if Schneider Electric Licensing 2.0 or earlier were not installed on the computer.

Known Issues of Version 3.3

There are no known issues in version 3.3 of the Schneider Electric Licensing.

Known Issues of version 3.2

Defect Number

Description

647506

In a workgroup environment, the addition of an available license server on another node to a License Manager will fail.

We recommend using a domain environment rather than a workgroup environment if adding more than one license server.

Browser Cache Issue

When upgrading from version 3.1 to 3.2, the browser cache will not automatically update.

If the License Manager page renders incorrectly after the initial upgrade, we recommend manually clearing the cache and refreshing the License Manager page within the browser.

To manually clear the cache for all supported Windows-based browsers, press CTRL and the F5 key simultaneously. For the list of supported browsers, please see the License Manager Help Guide.

Known Issues of Version 3.1

Defect Number

Description

647506

In a workgroup environment, the addition of an available license server on another node to a License Manager will fail.

As a workaround, the License Manager user can be added to the administrators users group in the license server.

777401

If Wonderware Intelligence 2014 R3 is installed on the same node as Schneider Electric Licensing 3.1, Intelligence will fail to acquire a license.

If Wonderware Intelligence 2014 R3 is installed on the same node as Schneider Electric Licensing 3.1 and Alarm Adviser 2014 R2 SP1 or Recipe Manager Plus 2014 R3, then each product will fail to acquire a license.

Please contact Global Customer Support for assistance.

Known Issues of Version 3.0

Defect Number

Description

647506

In a workgroup environment, the addition of an available license server on another node to a License Manager will fail.

As a workaround, the License Manager user can be added to the administrators users group in the license server.

System Requirements

The system requirements for AVEVA Enterprise Licensing components are the same as those for the products you have purchased and installed. See the Readme file and the installation guide associated with your specific product for more information.

Browser Settings- Security

AVEVA Enterprise License Manager is accessed through the browser installed on any computer on your network. License Manager is compatible with the major browsers including Microsoft Internet Explorer, Firefox, and Chrome. Each browser has its own security features and configuration.

For example, using Internet Explorer to access License Manager requires setting the following options:

See the Internet Explorer documentation for information about how to configure trusted sites.

For additional information on browser-based web help and active content, see Web Help Display and Video Playback.

Browser Settings- Animation Display

Browser-specific settings need to be configured to enable animation display within AVEVA Enterprise License Manager. Setting details for each browser are described below.

Internet Explorer

Animation display is not enabled by default for Internet Explorer. To enable animation, do the following:

  1. From the browser, select Internet Options.

    The Internet Options dialog box appears.

  2. Scroll to the Multimedia options and select Play animations in webpages.

Firefox

Animation display is enabled by default in Firefox. If animated content such as progress meters is not displaying, do the following:

  1. Enter about:config into the browser address bar.

    Acknowledge the warning to proceed.

  2. Enter image.animation into the search bar.

    The image.animation_mode setting will appear.

  3. Set the setting to normal.

Web Help Display and Video Playback

Web Help - Browser-based User Assistance

Web help components have been delivered in this release. Web help displays in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.

Typically, help content is installed on your local machine as part of the documentation library, and displays in your default browser without requiring an Internet connection. You can invoke the help by right-clicking a context menu item, a symbol, or another UI element, or otherwise invoking help using elements contained in your specific UI.

Browser Permissions for Displaying Web Help

Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.

You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your specific browser.

Playback of Tutorial Videos

The web help may contain a number of brief tutorial videos. To play these videos:

AVEVA Enterprise Licensing Documentation

The AVEVA Enterprise Licensing documentation includes the following:

© 2020 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us