Scenarios For Connecting Padvish Management Consoles To Each Other

Problem

You have multiple Padvish management consoles in your organization and somehow you wish to connect them and you desire to know different possible scenarios for this kind of connection.

Solutions

The second solution (remotely)

The recommended solution allows Master Manager to have complete control of its slave servers. In some organizations and scenarios, giving this type of access control to Master Manager is not proper; but having a method to monitor slave consoles or distribute licenses is needed. In this case, you can choose the second solution.

In this situation, all the following features are enabled:

Receiving updates: The slave server receives its update file from the Master server. You can change this in the settings sections.
Distribute license: The master server can dedicate its license or a part of it to its Slave servers. Doing this is will be the authority of the Master server admin.
Receive a comprehensive report: The master server can make custom and statistical reports from its slave masters.
Complete control of the slave server is not available.

Third solution (merely updating)

This solution is not a communicative solution and in this solution, only Padvish management servers can share antivirus updates. In this solution, there is no concept of a hierarchical structure (Master/Slave) and you merely adjust the console to receive updates from a sharing folder. Each server can check the updated file from each number of other servers and pick up the new files.

In this situation only follow feature is enabled:

Receiving updates: server picks up the update file from a sharing path that is built by another server.
Distribute licenses is not possible
Receiving a comprehensive report is not possible
There is no complete control over the Slave server.

Solution implementing method

Another solution (remote monitor)

If you do not wish to give complete control of the slave server to the master server, it is enough to use the previous method and change servers to master/slave; but the only difference of this solution is closing port 13911 of the Slave server. In this case, the slave server can view the master server port 13911 but the reverse connection is not possible.

So, all features except controlling the slave server are enabled.

The third solution (merely updating)

Padvish management console built a sharing folder named Padvish Update and puts its last update file in it, by default.

So, to set up automatic update receiving among servers (if master/slave does not implement), you only have to go to settings > Change server settings> server update settings and enter the path of the sharing folder in the specified field. So, your server can receive updated files from these sharing folders.

Note: in this solution, you do not need to open port 13911, but port 445 must be open for the receiving server. In this regard, it is appropriate to follow the principle of minimizing access, following the safety tips, and closing the ability to run the file or service remotely in the Windows server firewall of the destination server.