Space banner

   

This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

Rolling out relay agents in a cloud environment

A typical BMC Helix Client Management architecture has a smaller number of relays directly under the master and a larger number of clients under each relay. The following topic guides you through the process of a relay rollout with one of the master relays as the direct parent of the targets.

Note:

This rollout uses device groups, specifically those that were synchronized with a directory server (see the Defining the rollout targets via a directory server topic). If you have not yet created a group, do so before starting this example procedure. It is also possible to find your rollout targets via other lists, such as the Microsoft Network option or autodiscovered devices. You can find information on these options in the Rollout alternatives section.

Before you begin

Before you continue with the following procedure, ensure that you have installed first-level master relay. For instructions, see Installing the first-level master relay.

To roll out relay agents in a cloud environment

  1. Select Wizards > Agent Rollout .
    The Core Setup Configuration window appears.
  2. Check the box for Enable agent as a relay for the other agents.

    If you want to schedule the rollout at a specific date and time check the box for second last question.

  3. Click Next.
    The General Parameters appears.
  4. Enter the name of the new rollout (for example, Linux Relay Agents ) in the Name box.
  5. Enter the name for the rollout package executable in the Auto-extractable Name box (for example, linux64relayagent12.sh for a Linux rollout, or win7relayagent12.exe for a Windows 7 installation).
  6. Select the operating system group to which the agent is to be rolled out from the Operating System list, for example, Linux 64 bit.
  7. Click Next.
    The Rollout Server window appears. It provides the list of all defined rollout servers.
  8. Select the rollout server you want to use. If none of the exising rollout servers fits your requirements you can also add a new rollout server in this window. For this proceed as follows:
    1. Click Add Device  on top of the table.
      The Add a new rollout server pop-up window displays displaying the list of all devices, that can be a server due to their operating system.
    2. Select the device to be added from one of the list boxes.
    3. Click OK to confirm and close the window.
      The device is added to the table of available servers and selected.
  9. Click Next.
    The Targets & Accounts window appears.
  10. Click Select a device .
  11. Select the desired group that contains the relay rollout targets of the defined operating system type in the Available Objects box.
  12. To select individual devices instead of a group click All  on the left bar and select your devices from the list that appears.
  13. Click OK to add the group and close the window.
  14. Click Add Administrator .
  15. Enter the required data for the account login in the respective text boxes.
  16. To add a new account, click Add Administrator .
    The Properties dialog box appears on the screen.
  17. Enter the following data for a new account login in the respective text boxes:
    1. Enter the name of the domain to which the rollout is going in the Administrator Domain box. If the rollout is going to all domains, you can use an asterisk (*).
    2. Enter the login name of the admin (for when the agent deployment tries to log on to the remote target to install the agent) in the Administrator Login box.

      • For Windows XP Professional rollouts, you must enter a valid login and password, and it must be the same for all devices, that is, the rollout server (the master) and targets.
      • If you are not sure if your local administrator login has the same passwords for all targets, use the domain logon. For domain logons to work correctly, the necessary domain trust relationships must already were set up between the different domain controllers.
    3. Enter the password of the above-entered admin in the Password box. For security reasons the passwords is only displayed in the form of asterisks (*).
    4. Confirm the above-entered the password in the next text box.
    5. Click OK to confirm the new account and add it.
      It is now shown in the list above.
  18. Click Verify Rollout at the bottom to ensure that the credentials are correct.
  19. Click Finish .
  20. In the Confirmation dialog box, select the Go to Rollout radio button to change the focus of the console window to the new rollout.
  21. Click Yes to confirm the immediate activation.
    The focus of the console is now switched to the the Assigned Schedule tab of the newly created rollout. Here you can follow the general progress of the relay rollout assignment. If you did not check the Go to Rollout box at the end of the wizard select the newly created rollout in the left tree hierarchy and then its Servers subnode.
  22. When the status value displays Executing , select the Targets tab to follow progress of each individual target through the Status column (initial status is Initial and the final status should be Installed).

Your first group of relays is now installed. If you need to have another level of relays below these, repeat this procedure for all other relays.

Note:

When you are rolling out agents on MAC OS X devices and you want to remotely control these devices you must reboot them after the installation.

Where to go from here

To continue installing your architecture with clients below the relays continue with the Rolling out client agents in a cloud environment topic.

Was this page helpful? Yes No Submitting... Thank you

Comments