User Synchronization

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.

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.