AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status Already exists
Portfolio area Enterprise SCADA Server
Products Control Room Management Security and DMZ
Created by Serge LeBlanc
Created on Aug 25, 2023

RELATED IDEAS

[WWW] Auto-Logon and Logoff - Is there an AVEVA-recommended solution?

Our customer, City of Calgary Water Services, will be upgrading from 7.7 to ES2023 or ES2024. They presently have some batch files in place to automatically log an operator off after a certain length of time and then automatically log in a Read-Only user and start ezXOS. Is there an AVEVA-recommended solution for performing this securely in the latest version of the product?

Thanks,

Clay

Expectation

I expect the answer to be, "this isn't currently supported" but verifying with PrdM to get an official response and/or to see if it could be added to roadmap.
  • Attach files
  • Admin
    Jake Hawkes
    Jul 7, 2025

    Bumping for visibility now that this idea should be visible in the portal.

    Reply
  • Admin
    Jake Hawkes
    Oct 6, 2023

    The TSC's report that both are possible:

    Log off is simple

    I think perhaps using this: https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-force-logoff-when-logon-hours-expire

    To log in securely the following is required.
    The script needs to be run at an administrator level, similar to a Service with a gMSA. This would prevent any human interaction with the script.
    Or
    The password should be encrypted and stored similar to our file processing routines and the recent RTU passwords. The password needs to be encrypted.
    Both of the above can be provided and meet security requirements.
    Reply