Managing agent configuration

The Agent Configuration node enables the administrator to view or modify configurations remotely and directly for the selected device.

When you try to access a managed device's Agent Configuration (Device Groups > (Your Managed Device) > Agent Configuration), you will be asked to provide the login and password to the remote computer to verify you have access permissions.

You can provide the login as one of the following options:

  • as the simple login name of a local user of the remote computer, such as Administrator
  • as \\domain\logon for a domain login of the administrator, such as \\LAB\TEST. The domain part can be set to . to indicate the local computer.

If you are not sure that your local Administrator login has the same passwords for all targets, use the domain login. For domain logins to work correctly, the necessary domain trust relationships must already be set up between the different domain controllers.

This topic includes:

Modifying agent configurations

To modify the settings of any aspect of the agent configuration, proceed as follows:

  1. Select Device Groups> Your Managed Device> Agent Configuration in the left window pane.
  2. Select any line in the table in the right window pane of the respective subnode.
  3. Select Edit> Properties .
    The Properties window appears.
  4. Make the desired modifications to the individual values.

    Configuration TypeDescription
    SecurityThe parameters in this node define the options for secure agent communication. This includes the way the agents communicate between each other and the certificates being used for secure communication. For Windows devices, the access to the MyApps can also be defined.
    CommunicationThe parameters under this node define the basic access settings for the communication between the agents and agent and console, such as the different ports of communication, the timeouts for different types of communication and the frame and connection queue sizes.
    User InterfaceThese parameters define the settings for the application kiosk MyApps. If packages are advertised to a device, they will appear in the system tray. If not, a message will be displayed on the local device.
    Reboot ManagementThe parameters defined in this section define the default reboot settings which are used by the BMC Client Management - Patch Management .

    The Logging node provides access to the log files of the agent via its Parameters tab. The parameters in this view define the basic settings for log files of the software, that is, the values specify the contents of granularity of the log files and their output location for example. This also includes the log file sizes and numbers, which types of entries are to be logged, the time format, if alerts are to be sent in case of logged errors, etc.

    Module Configuration

    See the Configuring modules section below.

  5. Click OK to confirm the modifications and close the window.

Configuring modules

This node provides access to all BMC Client Management modules that are currently loaded on the selected device. Here you can modify configuration parameters and access local information about the respective module. Modules in CM are responsible for a certain functionality in the product. Their settings are defined through individual configuration files, one per module which are stored in the config directory. The modules themselves are stored in themodules/agent directory in the form of one .dll file for computers with a Windows operating system, for Linux systems you can see there one .so file per module.

From the Module Configuration section, you can perform the following actions:

Viewing agent modules

The Configuration tab displays the modules currently loaded on the selected device. This Console view provides an overview over all modules which are currently loaded. You cannot execute any modifications on any of the modules listed in this view, these are carried out directly in their configuration files or via the Agent Configuration nodes.




The name of the loaded module.


The complete version information of the respective module, that is, the version number with the build number and the date and time the version was compiled at.


The full installation path of the respective module.

Action Count

The number of actions contained in this module which may be called by other modules.


This box can contain a description of the module.

Configuring agent modules

  1. Select Device Groups > Your Managed Device > Agent Configuration > Module Configuration in the left window pane.
  2. Select the desired module in the left window pane.
  3. Select Edit > Properties .
    The Properties window appears.
  4. Make the desired changes in the boxes.
  5. Click OK to confirm.

The configuration of the selected agent module is updated.

Loading agent modules

Depending on the usage of the individual client, further modules might have to be loaded to those which are loaded by default or defined through the rollout installation.

  1. Select Device Groups > Your Managed Device > Agent Configuration > Module Configuration in the left window pane.
  2. Select Edit > Load Modules .
    The Select Agent Modules window appears.
  3. To add modules to the list of loaded modules mark them in this list box.

    The check box Persistent defines if the agent module now being selected is to be loaded from now on at every agent startup. By default this box is checked.

    In the following list box all modules are listed which are currently not loaded and available for the operating system of the selected device.

  4. Click OK to confirm.

The selected modules are added to the list of loaded modules.

Unloading agent modules

Not all modules need to be loaded on all clients. You can unload modules that are not required on a specific device.

  1. Select Device Groups > Your Managed Device > Agent Configuration > Module Configuration in the left window pane.
  2. Select the module to be unloaded in the right window pane.
  3. Select Edit > Unload Modules .
    Confirmation dialog box appears on the screen.
  4. Click either:
    • Yes , if the module is not to be loaded at every agent startup from now on
    • No , if the module is only to be unloaded this one time

The selected module is unloaded.

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