• State Verified Answer
  • Replies 2 replies
  • Subscribers 15 subscribers
  • Views 195 views
  • Users 0 members are here
Options
Related

Does each AVEVA Historian app require it's own license when used at the same time?

EJG

Hello all,

We are using an remote desktop server solution to provide the AVEVA Historian Client software to users. We see that a single user is allocating multiple Historian Client licenses, we expect that this appens due to the multiple openend Historian Client apps on a single user session (Trend, Query).


So the question is: Does each AVEVA Historian app require it's own license when used at the same time?

For example: User 1 is using 2x Trend apps and 1x Query app, user 2 is using 1x Trend app and 1x Query app. Both users are connected to the same RDS server and are connected with there own username.

Will this require 5 licenses or should it only require 2 licenses?

Note we are using the following license: AVEVA Historian Client Desktop 2023, Concurrent User 5 Pack

  • +1

    Hi there!

    The Historian Client app license is per session as opposed to per application.  So, if you open trend, the license applied to trend, query, workbook, a trend client open in InTouch, etc. That's all under a single seat. 

    So in your example, you should only need 2 licenses, unless something has changed. 

    What's probably happening, and what I've seen in the past, is that the user is not logging off and logs in on a different session.  This can happen depending on your RDS server settings.  I've had remote users have three stale RDP sessions open on a single server and take up three licenses.  A good way to avoid this is to set disconnected logoff timers in your RDP Collection settings. 

    Hope this helps - 

  • 0 in reply to Phil Wood

    Hi Phil,

    Thanks for your reply.

    Ok that's how we would expect it to work indeed, we did get some different feedback (each app requires a separate license, so in my example 5) so wrote this question to verify that.

    We indeed configured the logoff of disconnected users, this has helped a lot.

    A good reference for people looking this up: Configuring RDP/RDS Sessions Limits (Timeouts) on Windows | Windows OS Hub)