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.

Configuring rollout servers

A Rollout Server is a BMC Client Management agent used to deploy other agents. By default, the first relay that is installed in your environment is defined as the rollout server. If you want to use this predefined rollout server for your rollouts you can skip this topic and continue immediately with the next topic, Defining the Rollout Targets .


  • To remotely deploy agents to Windows targets, the rollout server must also have a Windows operating system.
  • Any rollout server can remotely deploy BMC Client Management agents to other operating systems, that is, Linux and MAC OS.
  • If you have a very heterogeneous or distributed environment, you might want to define specific rollout servers for subnets or the different operating system platforms.

The following topics are provided:

Defining rollout server page

The agent running on the rollout server has an additional page, the Rollout Server page. This page cannot be accessed through the regular agent interface. To log on to this page you must either have an admin logon, the system login of the master computer, or a login specifically defined by the admin. This page is only accessible via a browser through the following address: http://<rollout server name> :<rollout server port number>/rollout , for example scotty:1611/rollout.


You can enter the host name either as its short or full network name such as scotty or , or in the form of its IP address. Be aware that when you use IPv6 you need to put square brackets around the IP address, for example, [2001:db8:85a3:8d3:1319:8a2e:370:7348]:1611.

For our first test this is the master and you can use the predefined login admin with no password.

The rollout server page provides the following information about all existing rollouts that are defined as being available on the respective rollout server:



Rollout Name

The name of the rollout as defined at its configuration in the console.

Rollout Type

The installation operation executed by the rollout (that is, if it is an agent installation, reinstallation, or uninstall).

Operating System

The operating system type and version of the target devices.

Auto-extractable Name

This is the name of the rollout package – the actual installation package of the agent as defined in the console. This entry is a direct link to the location of the package from which you can download it or launch it through the use of your mouse buttons.

Publication Date

This date box appears the date and time at which the package was made available on this page for download.

Adding a rollout server

  1. Go to the Global Settings > Rollouts > Servers node.
  2. Click Add Rollout Server .
    The Add a new rollout server window appears.
  3. Click the All tab in the left window part.
    The Add a new rollout server window appears, listing all master relays that you installed in your environment.
  4. Select the device which is to be Your Rollout Server .
  5. Click OK to add it and close the window.

The selected device is added the role of rollout server and is now ready to deploy CM agents to the devices in your environment.

User Accounts

From the User Accounts page, you cannot create a new administrator account to roll out agents. You can only add existing administrator account to a rollout.

To add user accounts that can be associated with rollouts, you need to create an account under the Account Credentials node.

  1. In the User Accounts page, right-click to view the menu options.
  2. Click Add Account
    The Add an account credentials window displays available account credentials.
  3. Select the accounts you want to add to the User Accounts page.
  4. Click OK.

Related topics

Managing administrator credentials centrally for rolling out BCM agents

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