User Synchronization

hello all,

I am working with Citect Studio 8.1

I have a project wit 2 servers and 4 clients

When i change the password on one of the clients, it does not sync whit the others.

How can i solve this?

Regards

  • Hi ,
    Are you working with native Citect user accounts or Windows user accounts? If you want centralized management of User passwords, you are best to use Windows User accounts for login to Citect, specifically Domain Accounts which are centrally managed via the domain controller.
    Check out the help topic "Integrate Windows™ User Groups" for more information.
  • I am working with Citect User Accounts. With hcitect User accounts it doesnt work?
  • I've used Native Citect accounts in the past and it hasn't worked. I think it is due to my architecture. It is a redundant architecture where the project is deployed to clients from the Primary Server and the both Primary and Secondary servers run the same project. Adding a user from a client doesn't work. I thought I could get it to work using one of the RPC task functions but that means that the project in the secondary server won't be updated with the new credentials. Is this correct? Or is there a way to achieve this without using Windows Active Directory?
  • If you check the help for the user functions, like UserCreateForm, it says "In order to perform user configuration changes online in a system with multiple computers running SCADA nodes using these functions, you will need to use the RUN and COPY parameters to check the updates are distributed throughout the system, and that the functions are called from the computer which uses the COPY path as it's RUN path."

    It is designed to work if you have one master copy of the project on the Citect server and all the clients and other servers use the [CtEdit]Copy parameter to automatically download updates from that shared copy of the project. When you execute the Userxxx command on a client, it should notify the server, which modifies its user.dbf file, recompiles that file (faster if Incremental Compile is enabled), and reloads the runtime database. Then, the alarm server should notify all the clients that they need to reload that runtime database, which will also cause them to re-copy it from the server.

    If you use the deployment feature then this won't work. You may be able to make the changes from the runtime, but you will have to copy the updated user.dbf file from the server to your development PC (if it is a different machine), then deploy the project to all clients and servers, forcing them to restart.