Your browser does not allow storing cookies. We recommend enabling them.


Adding Distribution Groups

Once you have defined one or more existing hosts to act as Distribution Servers, you need to create distribution groups and populate them with hosts that will connect to the specified Distribution Servers.

To add distribution groups, follow the steps below:

  1. In the main menu, select Hosts → Manage Server Hierarchy.

  2. To add a distribution group, click Create new group. Give the group a descriptive name and click OK. The group is added under the Management Server in the tree view.

    Adding distribution groups

    Figure 7.5. Adding distribution groups

  3. To define a Distribution Server for the new distribution group, select the group name in the tree, and proceed to select a suitable Distribution Server in the Set Distribution Server 1 for this group drop-down list, and click Set. Hosts which have previously been converted into Distribution Servers, and are not in use by any other group, are available for selection in the drop-down list.

    Each distribution group can have one or two Distribution Servers that will act as back-up for each other.

  4. To populate the group with hosts, click Management Server in the tree view. From the host list that opens, select the hosts that you want to move to the new distribution group. Then select the group name from the Move selected hosts to distribution group drop-down list, and click Move now.

  5. When you have defined the Distribution Servers and distribution groups, proceed to deploying the distribution hierarchy to the hosts, see Deploying Distribution Server Hierarchy.

    In summary, the deployment is done like this: Select Hosts → Host Connectivity on the main menu. In the Deploy Hierarchy tab, verify the pending changes and click Deploy now.

Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps