• Replies 4 replies
  • Subscribers 586 subscribers
  • Views 266 views
  • Users 0 members are here
Options
Related

Limit Citect SCADA to one user

Brian

Hi All,

Citect 2016 R2 Update 21.


We have a Client only PC that auto logs in with Operator Privileges and Citect Client will auto start.
Recently someone logged in as Administrator which took the License and the Operator instance could not run.

Is is possible to disallow an instance of Citect to run under a user, is another instance is already running under another logged in user?

Citect cannot be run in Service mode as the customer is making use of SCADAPhone which requires a Citect Runtime opened on Startup.

Cheers

  • Hi  ,

    What Operating System are you using?

    It was my assumption that only one instance of "Citect Runtime Manager" can run on any machine at once. Any second instance will be blocked.

    When the Administator logged onto the machine, is there any startup command to run Citect SCADA?

    With the release of Plant SCADA 2023 and AVEVA Enterprise Licensing, it is now possible to use Device Reservation and Checkout to assign a license to a specific machine.

    Just curious why SCADAPhone requires Citect Runtime? I would have assumed it is getting data via CtAPI or OPC DA, which can both be accessed when running as a Windows Service.

    Kind regards

    Olivier

  • in reply to Olivier

    Thanks Oliver,

    Running Windows Server version 2016 64bit.

    I have realised that Citect was being called to start from: win + R > msconfig > startup
    I do recall Citect Client running without the runtime manager running..
    Doing some research I have realised there are 2 different startup locations! One per user, and one for the whole system..

    USER:     C:\Users\myusername\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    COMPUTER: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

    Ill give that ago next time on site aswell.

    Investigating this particular site, i have realized it is running as service mode..

    I came across the issue at a different site and looking back through my notes I came across this article:
    https://honeywellprocess-community.force.com/opcsupport/s/article/What-does-Failed-to-connect-to-Citect-Error-code-2-mean
    Running Citect as standalone instantly fixed my issue, it was 10pm so i didn't investigate it further at the time :P

  • It is possible. Check if a Windows user group of Citect.RuntimeUsers or SCADA.RuntimeUsers was created on that machine. If a Windows logon user is not in this group, Citect runtime cannot be launched even for the local administrator. I am sure Plant SCADA 2020R2 (v8.3) and 2023 (v8.4) can restrict users from launching Citect runtime. I am not sure your version. If either of these group doesn't exist, you could create your own group and use this group to apply ACL to citect.ini file (remove all other access users). If citect.ini file is not accessible to a logon user, the citect runtime cannot be launched. Hope this would help.

    The prompt message for the user who is not in RuntimeUsers group.

  • in reply to Jacky Lang

    Thanks Jacky, that's a great option.
    Currently they are Running 2016 so we will have to follow the second method until they upgrade later this year.

© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.