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

Recommended solutions (all facilities)

The recommended solutions in connecting management consoles are hierarchical structure (Master/Slave).

In this situation all follow features will be enabled:

  1. Receiving updates: The slave server will receive its anti-virus update from its Master server. You can change this option in the settings section of the program.
  2. Distributing license: The master server can dedicate its license or a part of it to the slave server. Doing this will be the authority of a master server admin.
  3. Receive a comprehensive report: The master server will be able to make the custom and statistical reports from its slave servers.
  4. Complete control of slave servers: viewing the client status, changing settings and policies, and all matters that can be done by the console, will be possible on slave servers by the master server.
  5. Meanwhile, the master console manager can give limited access to slave servers (for instance accessing reports or settings, etc.). All matters and accesses will be logged. Also, each slave console can have its manager who has full control of its console.

The second solution (remotely)

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

In this situation all follow features are enabled:

  1. Receiving updates: The slave server receives its update file from the Master server. You can change this in the settings sections.
  2. Distribute license: 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.
  3. Receive a comprehensive report: The master server can make the custom and statistical reports from its slave masters.
  4. Complete control of the slave server is not available.

Third solutions (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 as a hierarchical structure (Master/Slave) and you merely adjust the console to receive updates from a sharing folder. Each server can check the update 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 license is not possible
  • Receiving a comprehensive report is not possible
  • There is no complete control over the Slave server.

Solution implementing method

Recommended solution (all features)

To implementing recommended solutions, it is enough that you log in to the server that you choose as a Slave server and introduce the information of the Master server in Changer server settings> Server hierarchy. All features will be enabled for you:

  1. The master server will distribute updates as a default.
  2. In the license management section, the “change distribution” is enabled and allows for license distribution.
  3. Receiving the comprehensive report from Slavemaster in the custom reports section and by editing a report and advanced tab, the generated report for slave servers will be done.
  4. Complete control is possible by opening Slave Servers and choosing the desired console
Note: For the console to work in this mode, both the upstream server and the downstream server must have access to each other’s port 13911.

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 is built a sharing folder named Padvish Update and put 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, follow the safety tips, and close the ability to run the file or service remotely in the Windows server firewall of the destination server.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>