Reserve licenses

You can reserve licenses to specific devices in the License Manager. Reserving a license to a particular device ensures that the license cannot be acquired by another InTouch application and interrupt or prevent your application from running.

User-based License Reservation

In the AVEVA Enterprise License Manager license reservation page, it is possible to mark a license to be reserved to a specific user. While the reservation page allows this particular configuration, it's important to know that neither InTouch OMI nor InTouch HMI ViewApps support user-based license reservations. The end-result will be the inability for the software to acquire the license reserved. Therefore, only use device-based reservations for Supervisory Client licenses.

Device-based License Reservation

When reserving a Supervisory Client license for a specific device, the Device Name needs to be the name of the computer running the InTouch HMI/OMI ViewApp. In the case where the ViewApp is running inside of an RDS or Terminal Server, the Device Name needs to follow this naming pattern:

<RDSHostName>-<RDPClientName>-<index>

where RDSHostName is the name of the RDS or Terminal Server, and RDPClientName is the name of the PC running the RDP client software, and "index" is 1, unless there will be multiple RDP sessions from a single client machine, in which case the index should be incremented (starting at 1) for each reservation for that specific RDP client, up to the total number of RDP sessions from that specific RDP client.

Example 1: A computer with a hostname of "ControlRoomA" runs InTouch OMI

Device Name: "ControlRoomA"

Example 2: A computer with a hostname of "ControlRoomB" running a single Remote Desktop Client (RDP), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"

Device Name: "PrimaryRDS-ControlRoomB-1"

Example 3: Two computers with hostnames "SupervisorPC1" and "LineMgrA", respectively, each running a single Remote Desktop Client (RDP) connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"

Device Names:

License Reservation 1: "PrimaryRDS-SupervisorPC1-1"

License Reservation 2: "PrimaryRDS-LineMgrA-1"

Example 4: A computer with a hostname of "ExecutiveDesktop" running four (4) Remote Desktop Clients (RDPs), connecting to the Remote Desktop Server (aka: Terminal Server) with a hostname of "PrimaryRDS"

Device Names:

License Reservation 1: "PrimaryRDS-ExecutiveDesktop-1"

License Reservation 2: "PrimaryRDS-ExecutiveDesktop-2"

License Reservation 3: "PrimaryRDS-ExecutiveDesktop-3"

License Reservation 4: "PrimaryRDS-ExecutiveDesktop-4"

For RDS load balancing support, all RDS licenses can be activated on a single License Server that multiple RDS client sessions can point to. The licenses on the server must be of the same capability so that the licenses can be shared amongst each RDS client session. Licenses are considered to be of the same capability if their internal parameters have the same value. No reservations are needed in this scenario. If different license types for different RDS client sessions are required, then a License Server must be installed on each RDS server.

Refer to the AVEVA Enterprise Licensing Guide for detailed license reservation procedures.