RSCD agent licenses


The BLCLI commands described here have been optimized in version 8.7 of BMC Server Automation. For earlier versions of BMC Server Automation, BMC recommends using a script provided by BMC; obtain this script from BMC Communities.

In previous releases, RSCD agents required licenses. Since version 8.2, you no longer need to explicitly license agents. Instead BMC Server Automation users report agent usage. The following BLCLI commands can help you obtain current agent utilization:

Utility agentLicenseUsageReportByAbsoluteDateRange
blcli Utility agentLicenseUsageReportByAbsoluteDateRange /mydir/report.xml "2013/01/15 01:02:04-0500" ""
Utility agentLicenseUsageReportByRelativeDateRange
blcli Utility agentLicenseUsageReportByRelativeDateRange /mydir/report.xml 2 years

The following sample report demonstrates what data such commands provide.

Configuration Manager Agent Activity License Report


3/3/2010 12:49

Selected Date Range:

2/8/2001 12:51 -  2/8/2020 12:51

BladeLogic Environment (Database URL):


Currently Active Agent Count:


BladeLogic Manager Suite Type

Minimum BBSA Licenses
Required to Enable
Currently Used Functionality

Configuration Manager


Compliance Manager


Provisioning Manager


Configuration Manager + Compliance Manager or Server Automation Suite


Compliance Manager + Provisioning Manager or Server Automation Suite


Configuration Manager + Provisioning Manager or Server Automation Suite


Compliance Manager + Provisioning Manager + Configuration Manager or Server Automation Suite


BladeLogic Suite types

The following product suite types are available for licensing:

  • Compliance Manager—BladeLogic product used to perform compliance, snapshot, audit, and discovery jobs on the target agents
  • Configuration Manager—BladeLogic product used to perform Deploy operations on the target agents
  • Provisioning Manager—BladeLogic product used to perform provisioning activities.

How agent licenses are counted

The Minimum BBSA Licenses Required to Enable Currently Used Functionality column in the report lists the number of agents used exclusively for each suite type, that is, to perform operations of only the specific suite type. The following rules are applied to the counting of agent licenses:

  • No target agent is counted twice.
  • If a target agent participated in both a Compliance operation and a Provisioning operation, then the target agent is counted only towards the Compliance+Provisiong entry in the table.
    It is not counted towards the Compliance Manager entry or the Provisioning Manager entry.
  • The sum of all these column values should add up to the number of active servers at that point in the date range.



During a specific date range, 20 servers were active. They were used for the following suite types:

  • 6 target agents were used for Compliance activities. Of these, 2 of the target agents were also used to perform Provisioning activities.
    Hence, only 4 were used to perform Compliance activities exclusively.
  • 8 target servers were used for Configuration activities. Of these, 6 were also used for Compliance activities.
    Hence, only 2 target agents were used exclusively for Configuration activity.
  • 6 servers were used for Provisioning. Of these, 4 were also used for Configuration.
    Hence, only 2 were used exclusively for Provisioning.

The final counts are:

  • Configuration – 2
  • Compliance – 4
  • Provisioning – 2
  • Compliance+Provisioning – 2
  • Compliance+Configuration – 6
  • Configuration+Provisioning – 4

 The total number of target agents adds up to 20.

Agents running earlier releases

If you are using earlier versions of RSCD agents, you must still license them. Refer to documentation for those earlier releases for details on licensing. If you upgrade an agent from a pre-8.2 release, the agent becomes fully licensed.

Utility agentLicenseUsageReportByRelativeDateRange

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