• Replies 6 replies
  • Subscribers 586 subscribers
  • Views 243 views
  • Users 0 members are here
Options
Related

Start as administrator

Daniele Cerri

Hi,

I have a problem on my system: citect always want to run as administrator of the PC, but I don't want to leave the psw to the customer.

How can I solve this problem?

Parents

  • By default, Citect should be launched under the current Windows logon user unless you specify (run as different user). However, if you configure Runtime Manager as service, all Citect processes should run under the predefined virtual service account [Citect Runtime Manager]. For visualization, you will have to launch a /x client on that machine. Of course, you can also configure which Windows users are allowed to run Citect. For more information, please refer to another discussion thread or Security topic on Citect Help.

     Limit Citect SCADA to one user 

    Hope this would help.

    Regards,

    Jacky

Reply

  • By default, Citect should be launched under the current Windows logon user unless you specify (run as different user). However, if you configure Runtime Manager as service, all Citect processes should run under the predefined virtual service account [Citect Runtime Manager]. For visualization, you will have to launch a /x client on that machine. Of course, you can also configure which Windows users are allowed to run Citect. For more information, please refer to another discussion thread or Security topic on Citect Help.

     Limit Citect SCADA to one user 

    Hope this would help.

    Regards,

    Jacky

Children
  • in reply to Jacky Lang

    Thanks Jacky but i'm not able to perform what you say; I'm using a PC with domain administrator and a rule delete all the admin that I create.

    I've created a new user, inserted it in the rule of "runtime user" (citect.localusers see the jpg) but every time I execute the Runtime plant scada, the system ask to me the admin psw.

    It drive me creazy..........

  • in reply to Daniele Cerri

    Hi  ,

    It appears that you are using Citect SCADA 2018 R2. Below is the table of user groups that you could use to configure the limit access to operations. If a machine is set up to run server processes, you need to have the windows logon user in ServerUsers group. 

    Windows User Group Name

    Description

    Citect.Engineers

    Users in this group can read and write the server to server password. This user corresponds to a user who would run the Setup Wizard activities (either in Citect Studio or the Configurator).

    Users in group have all privileges available to users in the other two groups.

    Citect.ServerUsers

    Controls which users can run Citect SCADA as a server process. This group is used to limit access to the server password which is used in server to server communications.

    If you are not running Citect SCADA as a service, any Windows user who needs to run a Citect SCADA server (including a display client with [CtAPI]Remote enabled needs to be added to this group.

    Note: If you are running Citect SCADA as a service, it is recommended that you do not add users to this group.

    Citect.LocalUsers

    Users in this group have access to the CtAPI interface exposed by Citect SCADA client processes. This group can be used to restrict CtAPI access to pre-determined users or services

    Regards,

    Jacky

  • in reply to Daniele Cerri

    Hi Jacky,

    I solved the problem as Your advice!

    Thanks a lot

    Now I have another problem on a client laptop: it works fine, there is communication between it and the server, but I have the System service offline as you can see below.

    I repeat, it works but why this alarm?

  • in reply to Daniele Cerri

    I am not sure why you are running Runtime Manager in service mode unless this note is a terminal (RDS) server where you can run multiple x/ clients in different RDS (remote desktop) sessions.

    In general, the "offline" means this node lost the connections to its intended servers either because the servers are not reachable or no license acquired. Check the syslog in Logs folder that should log some info for this error.

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