Hi,

Welcome to the community 

When you have a redundant OS server, you have to confgure only one OS project, because both OS projects must be equal. The same OS project is downloaded to both servers. There are however some local settings that must be done, like setting the redundancy options.

You won't have to compile the OS server project, because you did not change the CFC logic right? You only changed the User Administrator settings. Normally this change can be done by an OS download change, were both servers are downloaded, first standby then master server.

If you have made a lot of changes (a lot of tags), you may end up that download change cannot be done, in this case you need to full download one server, wait for the server to be in runtime and synchronization is complete, and then you full download the other server. In this way, the operator won't loose visualization.

For the clients, you can download them one by on from the ES. 

Hi,

See the following manual for more information about downloading. You can also find which changes can be downloaded with a change and which not. SIMATIC PCS 7 Operator Station (V10.0). See chapter 19 and 20.

The OS download change is executed automatically by the system. Both servers will remain in runtime. You won't have to configure anything. If in any case, the downloading fails, you need to execute a full downloiad instead.

Synchronization is still active, but when you download full a server, then that server is missing alarms and tags in the period runtime is not active. Therefore, after the server is back in runtime, synchronization occurs so that the returned server is up to date again.

You can however stop the second server immediately when the first server is back in runtime when a full download is executed, but this can cause a gap in the alarms and taglogging.

Changed in User Administrator are not taken from the server. A change must be done in the client project and then downloaded to the client. PS: You can also import/export the configuration of the User Administrator, so it's easier to use. 

Also think about using SIMATIC Logon. This allows you to only configure authorization for groups instead of doing this for each person. New users can be added to groups in Windows and they automatically receive the group authorization when logged on to WinCC.

its_Suhas

Hello Orcea, 

Thank you for the clarification. Does loading changes close the project in the server, in that case:

“first standby then master server”: If I first download to server B (standby), wait for synchronization and then download to server A (master), server A becomes the standby server, right? If I want server A to become the master again, I have to restart server B.

Is downloading first to ServerB and later to ServerA the wrong procedure? 

For the clients: Should I manually create a new authorization and use it in the .pdl, or are the changes fetched from the OS server project automatically (e.g., generate server package), so that I can simply load them one by one?

Thank you