Configuring a super master installation

If you are installing a super master architecture, you must execute the installation procedure described in section Installing BMC Client Management on-premises at least twice: once for the super master on its device and once for each regular (nonsuper) master server that is installed on your different locations. When all masters including the super master are installed, you need to make the following modifications on the regular masters.

To configure the Vision64Database.ini file

In the Vision64Database.ini configuration file (the BMC Client Management database configuration file), you define the parameters on which data is uploaded to the super master and its database. To do so, proceed as follows:

1. Go to the [InstallDir]/master/config directory and open the file Vision64Database.ini in a text editor.

2. Find the section [AdministeredRelayUpload] in the file.

   This section defines all parameters dealing with the relationship between regular master and super master. It provides the parameters, which, by default, are all set to true indicating all different types of inventory upload options are activated.
3. If one or the other type of inventory does not need to be uploaded (for example, because you have not acquired the respective license, such as for patch management), modify the value to false .
4. Save the modifications and close the file.

After you have made all these modifications, you can launch the BMC Client Management agent for all different master servers, starting with the super master, and you can continue with the regular installation procedure of the BMC Client Management agent for all other devices in your network.

To configure the relay.ini file

In the relay.ini configuration file for each regular master ( not the super master), you must indicate that even though the device is of type master server, it still has a parent - the super master. To do this, make the following modifications:

1. Go to the [InstallDir]/master/config directory and open the file relay.ini in a text editor.
2. Go to ParentName and enter the name or IP address of the super master device.
3. (Optional) If you did not use the standard installation parameters and assigned a different port to the super master, modify the entry ParentPort .
4. Save the modifications and close the file.

Connecting to a super master console

Connecting with a console to a super master works in exactly the same way as connecting to a site master server. After the console opens on the screen, however the objects displayed will be limited to those you are used to see, because the super master is restricted in its license and thus functionalities.

The dashboard displays only those elements required by the super master, that is, no scanned devices in the Device Distribution, no wizards, and the license box of course includes the license for the super master.

The following top nodes are displayed which again will only display a reduced number of their regular subnodes:

• Search
• Global Settings
• Device Topology
  • Inventories
  • Agent configuration
  • Direct Access
  • Remote Control
  • Financial Asset Management
  • Alert and events
• Device Groups
• Patch Management
• Queries
• Reports
• Events
• Assigned objects: Patch, only to view status

Super Master Agent Interface

The agent interface is available with its basic tabs apart from the maintenance and MyApps functionalities and the task creation page. Neither is the rollout page accessible however the report portal can be called.