BMC License Usage Collection Utility 6.0: Portions of This Document Are BMC Confidential, Bladelogic Confidential

Portions of this document are BMC Confidential, BladeLogic Confidential.
BMC License Usage Collection Utility

6.0
Home
Date: 2023-03-15 4:37

URL: https://docs.bmc.com/docs/x/MXu3Rg
Contents
Release notes and notices...................................................................................................................................................... 7
Known and corrected issues............................................................................................................................................. 23
Technical bulletins ............................................................................................................................................................ 26
BMC License Usage Collection Utility version 4.7.01 ................................................................................................... 26
Change in BNA license report generation mechanism ............................................................................................. 26
6.0.00 enhancements....................................................................................................................................................... 27
New features ................................................................................................................................................................ 27
Other enhancements ................................................................................................................................................... 27
Enhancements to supported BMC products ........................................................................................................................ 28
Supported BMC products ..................................................................................................................................................... 32
Introduction ......................................................................................................................................................................... 36
Introduction to the BMC License Usage Collection Utility ............................................................................................... 36
Downloading the license utility........................................................................................................................................ 37
Videos............................................................................................................................................................................... 37
Getting started ..................................................................................................................................................................... 38
Related topics................................................................................................................................................................... 38
Supported languages and locales......................................................................................................................................... 39
English language considerations ...................................................................................................................................... 40
German language considerations..................................................................................................................................... 40
French language considerations....................................................................................................................................... 40
Spanish language considerations ..................................................................................................................................... 40
System requirements ........................................................................................................................................................... 42
Software requirements .................................................................................................................................................... 42
Operating systems........................................................................................................................................................ 42
PowerShell.................................................................................................................................................................... 42
Hardware requirements ................................................................................................................................................... 43
Installing ............................................................................................................................................................................... 44
Prerequisites for installation ............................................................................................................................................ 44
Downloading the installation file ..................................................................................................................................... 44
Where to go from here................................................................................................................................................. 44
Performing the installation............................................................................................................................................... 45
Before you begin .......................................................................................................................................................... 45
To install or reinstall the BMC License Usage Collection Utility.................................................................................... 45
BMC License Usage Collection Utility 6.0 Page 2

Where to go from here................................................................................................................................................. 47

Uninstalling....................................................................................................................................................................... 47
Upgrading............................................................................................................................................................................. 49
Upgrading to 6.0.00.......................................................................................................................................................... 49
Upgrading from 4.9.00, 5.0.00, 5.5.00 to 6.0.00 .......................................................................................................... 49
Upgrading to 5.5.00.......................................................................................................................................................... 49
Upgrading from 4.8.00, 4.9.00, 5.0.00 to 5.5.00 .......................................................................................................... 49
Upgrading from 4.5.00 to 5.5.00 .................................................................................................................................. 49
Upgrading to 5.0.00.......................................................................................................................................................... 49
Upgrading from 4.7.01, 4.8.00 and 4.9.00 to 5.0.00 .................................................................................................... 49
Upgrading to 4.9.00.......................................................................................................................................................... 50
Upgrading from 4.6.00, 4.7.01, and 4.8.00 to 4.9.00 ................................................................................................... 50
Upgrading to 4.8.00.......................................................................................................................................................... 50
Upgrading from 4.6.00 and 4.7.01 to 4.8.00 ................................................................................................................ 50
Upgrading to 4.7.01.......................................................................................................................................................... 50
Upgrading to 4.7.00.......................................................................................................................................................... 51
Upgrading from version 4.0.01 and 4.5.00 to 4.7.00.................................................................................................... 51
Upgrading to 4.6.00.......................................................................................................................................................... 51
Upgrading from version 3.x and 4.x to 4.6.00 .............................................................................................................. 51
Upgrading to 4.5.00.......................................................................................................................................................... 51
Upgrading from version 3.x .......................................................................................................................................... 51
Upgrading from version 4.0.00..................................................................................................................................... 51
Accessing and navigating the license utility ......................................................................................................................... 52
Configuring product servers ................................................................................................................................................. 54
Configuring user settings.................................................................................................................................................. 54
Windows ...................................................................................................................................................................... 54
(Optional) Create a user account ............................................................................................................................. 54
UNIX ............................................................................................................................................................................. 57
Configuring environment settings .................................................................................................................................... 57
Configuring BMC Digital Workplace Named User Report v18.02 and later (DWPNUR) ............................................... 58

Configuring TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03 ...................................................................... 59

Configuring BMC Digital Workplace Active User Report (DWPAUR) 18.05 to 22.1 ...................................................... 59
Configuring BMC Discovery (Discovery) ....................................................................................................................... 59
Configuring BMC Database Automation (BDA) ............................................................................................................ 59
UNIX ......................................................................................................................................................................... 59
Configuring BMC Server Automation (BSA 8.2 to 8.6) ................................................................................................. 59
Configuring BMC Server Automation (BSA 8.7 to 8.9.02) / TrueSight Server Automation 22.2................................... 59
Windows and UNIX .................................................................................................................................................. 60
Windows .................................................................................................................................................................. 60
UNIX ......................................................................................................................................................................... 60
Configuring BMC Client Management (BCM)............................................................................................................... 60
Configuring BMC Performance Manager Portal (BPM Portal v2.11) ............................................................................ 60
Windows and UNIX .................................................................................................................................................. 60
Windows .................................................................................................................................................................. 61
UNIX ......................................................................................................................................................................... 61
Configuring BMC Release Process Management (RPM)............................................................................................... 61
Configuring Remedy AR System Server (ARS) based products ..................................................................................... 61
Windows .................................................................................................................................................................. 61
UNIX ......................................................................................................................................................................... 61
Configuring TrueSight Operations Management (TSOM) 10.7 to 11.3.06.................................................................... 62
Configuring TrueSight Capacity Optimization (TSCO) 10.7 to 20.02.01........................................................................ 62
Administering deployments ................................................................................................................................................. 63
Adding deployments ........................................................................................................................................................ 63
To add a deployment from the License Report tab ...................................................................................................... 63
To add a deployment from the Manage Deployment tab ............................................................................................ 64
BMC Discovery (Discovery) 8.3.2 to 23.1 ..................................................................................................................... 65
BMC Database Automation (BDA) 8.3 to 20.21.01....................................................................................................... 65
BMC Network Automation (BNA) 8.3 to 8.9.04 / TrueSight Network Automation 22.4 .............................................. 66
BMC Server Automation (BSA) 8.2 to 8.6 ..................................................................................................................... 67
BMC Server Automation (BSA) 8.7 to 8.9.02 / TrueSight Server Automation 22.2 ...................................................... 68
BMC Client Management (BCM)11.6 to 22.4 ............................................................................................................... 69
BMC Performance Manager Portal (BPM Portal) 2.11 ................................................................................................. 70
BMC Release Package and Deployment (RPD) 4.8.00 to 5.0.03 ................................................................................... 71
BMC Release Process Management (RPM) 4.6.00 to 5.0.07 ........................................................................................ 71
Remedy AR System Server (ARS) 7.6.04 to 20.02......................................................................................................... 72

BMC Digital Workplace (MyIT) 3.1 to 3.3 ..................................................................................................................... 73

BMC Digital Workplace (MyIT) 18.05 to 22.1 ............................................................................................................... 74
TrueSight Capacity Optimization (TSCO) 10.5 to 20.02.01 ........................................................................................... 75
TrueSight Operations Management (TSOM) 10.7 to 11.3.06 ....................................................................................... 75
TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03 ......................................................................................... 76
BMC Digital Workplace Named User Report v18.02 and later (DWPNUR) .................................................................. 77
Editing deployments......................................................................................................................................................... 77
To edit a deployment.................................................................................................................................................... 77
Deleting deployments ...................................................................................................................................................... 78
To delete a deployment................................................................................................................................................ 78
BMC Tools Integration ...................................................................................................................................................... 78
Control-M license usage reporting tool........................................................................................................................ 78
To access the reports................................................................................................................................................ 78
Dashboard overview ............................................................................................................................................................ 79
Bar chart example ............................................................................................................................................................ 79
Bar chart contents per product deployment.................................................................................................................... 79
Creating dashboard bar charts ......................................................................................................................................... 81
To create a dashboard bar chart: ................................................................................................................................. 81
To save a bar chart as a PNG file: ................................................................................................................................. 82
To access dashboard CSV reports:................................................................................................................................ 82
Reports overview ................................................................................................................................................................. 83
Running reports................................................................................................................................................................ 89
To run a report.............................................................................................................................................................. 89
Server clustering information in reports .......................................................................................................................... 91
Emailing reports ............................................................................................................................................................... 94
Prerequisites................................................................................................................................................................. 95
To email reports: .......................................................................................................................................................... 95
Viewing reports ................................................................................................................................................................ 96
To view reports............................................................................................................................................................. 96
Scheduling reports ........................................................................................................................................................... 98
To schedule reports ...................................................................................................................................................... 98
To delete a scheduled report........................................................................................................................................ 99
Enabling email notification of reports with SMTP............................................................................................................ 99
Before you begin .......................................................................................................................................................... 99
To configure a connection with the SMTP server......................................................................................................... 99

To send a test email:................................................................................................................................................... 100

Support information........................................................................................................................................................... 101
Contacting Customer Support ........................................................................................................................................ 101
Support status ................................................................................................................................................................ 101

Release notes and notices

Related topics
This section provides information about what is new or
changed in this space, including urgent issues,
Known and corrected issues
documentation updates, service packs, and patches.
Support information
Downloading the installation file

Date Title Summary
15 6.0.00
Mar 2023 enhanc
ements New features
BMC License Usage Collection Utility 6.0.00 provides the following new features:
• Supports Spanish language and locale (ES-XL).
• Supports open source Red Hat JRE:
BMC License Usage Collection Utility now runs on Open Source Red Hat JRE (java-1.8.0-
openjdk-jre-1.8.0.352-2.b08).
The JRE folder is not deleted after the upgrade to version 6.0.00. If you have any security
concerns, you can manually delete the folder from C:\Program Files (x86)\BMC
Software\LicenseUsageCollector.
• Supports an alerting mechanism on exceeding the threshold for BMC Client Management
product:
• For BMC Client Management, LUCU supports email alert mechanism with
Scheduler option.
• If any BMC Client Management license component is overused, then LUCU creates
a new report with title; for example, <SERVER_NAME>_
BCMLicense_overusage_LUCU.csv.
• The report is accessible in the Details of Selected Reports Run (by
Deployment) table, under the Usage Analysis Report column.
• If the BMC Client Management report is in-capacity, then the current product usage
report is opened.
• For BMC Client Management product execution failure or other BMC products, the
report is displayed as Not Applicable
• Integration with the Control-M Usage Reporting Tool:
• You can invoke the Control-M usage reporting tool (version 9.0.00) from BMC
License Usage Collection Utility from the new BMC Tool Integration tab.
• The Control-M Usage Reporting tool is available only in the English locale. For the
French, Spanish, and German locale machines, the tool will appear in English.
• Feedback survey:
• An ongoing survey is launched to enable customers give feedback on their
experience with BMC License Usage Collection Utility.
• You can access the survey from the new Feedback tab.
Other enhancements
• Enhanced BMC Digital Workplace Active User report to fetch monthly high count for
unique users.

Date Title Summary
• BMC License Usage Collection Utility can generate monthly usage reports in
separate files for BMC Digital Workplace Active Users. The utility generates
Summary files for date ranges and an individual license report file for the entire
month.
• BMC License Usage Collection Utility no longer supports BMC Digital Workpalce
versions 3.4 to 18.02.
• From this release, TLS 1.0 and TLS 1.1 are disabled by default.
Support is added for TLS 1.2.

Date Title Summary
06 5.5.00
May enhanc
2022 ements Product support for new versions
BMC product Version supported
TrueSight Network Automation(TSNA) 22.1
BMC Digital Workplace Active User Report 20.08

(DWPAUR)
New features
• Supports date range across all BMC Digital Workplace Active User Report from version 3.5
to version 20.08.
• Supports an alert mechanism on exceeding the threshold for ARS product.
• For Action Request System, LUCU supports email alert mechanism with Scheduler
option.
• If any AR System license component is overused, then LUCU creates a new report
with title; for example, <SERVER_NAME>_ARSLicense_overusage_LUCU.csv.
This report is accessible in the Details of Selected Reports Run (by Deployment)
table, under the Usage Analysis Report column.
• If the AR System report is in capacity, then the current product usage report is
opened.
• For AR System product execution failure or other BMC products, the report is
displayed as Not Applicable.
Other enhancements
• From TSNA 20.02.01, licensing API is changed and LUCU is enabled—Pass token to
endpoint to hit with valid credentials, from v20.02.01 - Starting from version 20.02.01,
the /about endpoint gets authenticated; therefore, a token has been passed to this
endpoint to resolve “Unauthorized: Failed to provide a suitable Authorization header”
error.

Date Title Summary
• Improved PDF Report Generation—PDF reports with high number of records are
supported.
• Support for special English characters—In TrueSight Server Automation (version 8.7 and
higher), in Product Password field, the following characters are supported:
• @
• %
• !
• #
• *
• (
• /
• ?
• .
• [
• ]
• {
• }
• \
• -
• _
• +
• `
• ~
• :
• '
• Enhanced error logging of all web-based products
• The log4j library is upgraded to version 2.17.1
• BMC Digital Workplace named user report has the following improvements:
• Record fetching is possible in batch of 2000 records
• Print the Login Id, First Name, Last Name, Email Id fields in the report
• Report file prints scrambled values rather than actual values for the UserId, First
Name, Last Name, Email
• In the Duration dropdown, the Last Month option is included
• For TSCO product LUR, the Read time out is increased to 150 seconds
• UI changes—For easy readability of links, rows appear in gray during selection
• Added support information for Control-M on Help tab—Added new support redirection
statement for Control-M under the Help tab

Date Title Summary
5.0.0
10 enhanc
Jul 2020 ements Product support for new versions
Support has been added for the following products/versions:
BMC product Added support for version #
TrueSight App Visibility Manager(TSAVM) 11.0 to 11.3.03
New features
BMC License Usage Collection Utility 5.0 provides the following new features:
• BMC License Usage Collection Utility now supports French language and locales (fr_FR, fr).
• BMC License Usage Collection Utility now provides supports for DWP Named User Report
by consuming AR REST API.
Other enhancements
Anonymized DWP and MyIT active user reports:
BMC License Usage Collection Utility now generates the anonymized reports for Digital
Workplace 3.1. to 20.02 . The UserId, First Name, Last Name, and Email columns in the reports
now contain anonymized data.

Date Title Summary
4.9.00
10 enhanc
Oct 2019 ements Product support for new versions
BMC Digital Workplace (MyIT) 19.05
 Note
Instructions for manually pulling the named user count in MyIT/DWP license usage
report is available in the below link.
To measure the license usage of BMC Digital Workplace (MyIT), see Measure BMC
Helix Digital Workplace Usage.
New features
• BMC License Usage Collection Utility now provides enhancements in the TrueSight
Operations Management (TSOM) reports.
The TSOM reports now consists of detailed reports for each TSIM component. In addition
to the summarized report, each TSIM report consists of current account and high count
details in separate files.
• BMC License Usage Collection Utility scheduler enhancements
The deployment status notification emails now contain the deployment ID, product name,
and deployment status in the email subject. You do not need view the report ZIP files or
logs to know the deployment status of a product.
• BMC License Usage Collection Utility now provides a UI tip for just in time product support.
You can click this tip and navigate to the documentation that provides information about
the latest additions to supported versions.
• The Windows batch file for BMC Server Automation (BSA) 8.7 and later versions is now
updated to work with the blcred utility.

Date Title Summary
10 4.8.00
Apr 2019 enhanc
ements Product support for new versions
BMC Client Management (BCM) 12.8
BMC Truesight Server Automation (BNA) 8.9.04
BMC Truesight Capacity Optimzation (TSCO) 11.5
BMC TrueSight Server Automation (BSA) 8.9.04
BMC Digital Workplace (MyIT) 18.11.00 and 19.02
BMC Truesight Operations Management 11.3.02
New features
• BMC License Usage Collection Utility now generates the anonymized reports for Discovery
versions prior to 11.2. The Server name and Discovered OS columns in the reports now
contain anonymized data.
• Product Usage Charts are now available via manual execution and automated execution.
You can now view Product Usage Charts in JPEG format for the following products:
• BMC Client Management(BCM)
• BMC Database Automation (BDA)
• BMC Digital Workplace (MyIT)
• BMC Discovery (Discovery) up to 11.1
• BMC Network Automation (BNA) / TrueSight Network Automation

Date Title Summary
• BMC Release Package and Deployment (RPD)

• BMC Release Process Management (RPM)
• BMC Server Automation (BSA) / TrueSight Server Automation
• Remedy AR System Server (ARS)
• TrueSight Capacity Optimization (TSCO)
• TrueSight Operations Management (TSOM)
YouTube video playlist on Help tab

The link to the YouTube video playlist on the Help tab is updated, where you can view the
latest videos for the license utility.
26 4.7.01 • BMC License Usage Collection Utility version 4.7.01: Change in BNA license report
Nov 2018 Technic generation mechanism
al
bulleti
n
10 4.7.00 Support has been added for the following products/versions:

Oct 2018 enhanc
ements • BMC Database Automation (BDA) 8.9.03
• BMC Digital Workplace (Digital Workplace) 18.08
• Remedy AR System Server (ARS) 18.05 and 18.08
• TrueSight Capacity Optimization (TSCO) 11.3.01
• TrueSight Operations Management (TSOM) 11.3.01
BMC License Usage Collection Utility 4.7 provides the following new feature:
The dashboard feature has been added to provide a quick view of BMC product license usage
per product deployment in the form of bar charts.

Date Title Summary
18 4.6.00
Jun 2018 enhanc Enhanced support for the following products
ements
• BMC Client Management
• Added support for version 12.7
• BMC Digital Workplace (formerly MyIT)
• Added support for versions 18.02 and 18.05
• REST API support has been added for versions 3.4 to 18.05
• BMC Discovery
• Added support for version 11.3
• TrueSight Network Automation (formerly BMC Network Automation)
• Added support for version 8.9.03
• TrueSight Server Automation (formerly BMC Server Automation)
• Added support for version 8.9.03
Other enhancements
• The BMC License Usage Collection Utility is now a single (Java) platform product. The Perl
platform has been removed, closing security bridges.
• The product has been enriched with higher security
• For an enhanced user experience, the position of the "License Utility" stamp has been
changed to the header of each report.
• See the screenshot on the Introduction page

Date Title Summary
28 4.5.00
Feb 2018 enhanc Existing product support enhancements for new releases
ements
• Added support for 8.9.02
• BMC Network Automation (BNA)
• BMC Server Automation (BSA)
• Added support for 8.9.01 and 8.9.02
• Added support for 3.4 and 3.5
• BMC Discovery (Discovery)
• Added support for 11.2
• Added support for 9.1.03 and 9.1.04
Other enhancements
• The German language and locale are now supported (de_DE, de). See Supported languages
and locales.
• The following text appears on all reports generated from the license utility: "Report
Generated Using BMC License Utility". See Introduction.
• You can now view a license report in PDF for the following products:
• BMC Client Management (BCM)
• BMC Discovery (Discovery) version 11.1 or earlier

Date Title Summary
Other changes
The PDF version of the product documentation has been removed from the Help tab. You can
access the up-to-date PDF from the Online Documentation link on the Help tab.
06 4.0.01 • Version 4.0.01 is a minor release delivered only for additional security.
Oct 2017 enhanc • The product has been upgraded to the Java 1.8 platform enabling usage of JavaKeyStore
ements for securing deployment details.
• It has enhanced encryption algorithm and communication between Java and Perl
platforms.

Date Title Summary
31 4.0.00
Jul 2017 enhanc New product support
ements
• Truesight Operations Management (TSOM): LUCU now supports the TSOM product
starting with version 10.7
Existing product support enhancements for new releases

• BCM Client Management (BCM) 12.5 and 12.6
• BMC Database Automation (BDA) 8.8, 8.9 and 8.9.01
• BMC Network Automation (BNA) 8.8 and 8.9
• BMC Network Automation (BNA) 8.9.01
• Changed with Rest API mechanism for efficient and faster execution
• BMC Release Package and Deployment (RPD) 5.0.01 and 5.0.02
• BMC Server Automation (BSA) 8.2 to 8.6
• Redeveloped to use the JDBC approach for improved customer experience
• BMC Release Process Management (RPM) 5.0.01 and 5.0.02
• BMC Discovery (Discovery) 11.0 and 11.1
• Changed with licensing count calculation to exclude client and desktop devices
Enhancements
• The Help tab now provides the following information:
• Links to documentation (online and PDF)
• Email addresses in order to contact Support and the License Compliance team
• The Manage Deployment tab now provides the supported version numbers for each
product in the "Select Product" list.
• For example: Remedy AR System Server v7.6.04 to v9.1.02 (ARS).
• The Reports folder name has been changed to remove the weekday
• Support for a non-default port for Unix based product configuration has been added

Date Title Summary
10 3.6.00
Apr 2017 enhanc
ements • Support has been added for:
• MyIT 3.1 to 3.3
Current product upgrade support has been added for:
• BMC Discovery (ADDM) 11.1
• Remedy AR System Server (ARS) 9.1.02
• German input characters and numerals are allowed in server username and password
fields for:
• BMC BladeLogic Network Automation (BNA) report enhancement to show "Total Device
Count" in order to provide clarity on license usage
• For BSA 8.2 to 8.6 and Remedy AR System Server (ARS):
• The license utility is shipped with two additional shell scripts in order to set the
home variable, located in the following directory:
• \Program Files (x86)\BMC
Software\LicenseUsageCollector\licenseusagecollector\ENvVariableScripts
January 3.5.00 • Support is now available for:

13, 2017 enhanc • German OS and system locale
ements
• Windows 10
• Two new products have been added:
• Release Process Management (RPM) – 4.6.00 to 5.0.00
• BMC Release Package and Deployment (RPD) – 4.8.00 to 5.0.00
• Current product upgrade support has been added for:

• BladeLogic Server Automation - BSA 8.8 and 8.9
• TrueSight Capacity Optimization – TSCO 10.7
• User Interface (UI) changes for improved customer experience
• A tooltip has been added to the Email Reports button (License Report tab) to notify
users to select the record(s) from the Select All column
• The “Current License Report Run” label (License Report tab) has been changed to
"License Report Run Notes"
• The following note has been added to the Manage Deployment tab: “LU supports:
English input language characters, numerals and special characters”
• BSA 8.7 has been changed to 8.7 to 8.9

Date Title Summary
October 3.0.00
24, 2016 enhanc Product enhancements
ements
• The UI has been updated to enhance usability, including button and drop-down colors. See
the Getting started topic.
• The BNA report has been updated to correspond to the report in the BNA product.
Documentation enhancements and changes

• Version 3.0.00 wiki docs and PDF have been added
• The following topics have been added:
• 3.0.00 enhancements
• The screenshots in the Getting started topic have been updated.
July 21, 2.5.00 • Support has been added for BMC Performance Manager Portal 2.11
2016 enhanc • You can now enable email notification of reports with SMTP. See Enabling email
ements notification of reports with SMTP.
• For BSA, ARS, and BPM Portal, you can now install the license utility and the BMC product
on the same Windows computer. See Adding deployments
• Documentation enhancements and changes
• Version 2.5.00 wiki docs and PDF have been added
(Version 2.0.00 and 1.6.00 wiki docs have been maintained as separate spaces.)
• Enabling email notification of reports with SMTP
• The screenshots in the Getting started topic have been updated with the following:
• The SMTP Configuration tab has been added

Date Title Summary
April 11, 2.0.00 • Support has been added for BMC TrueSight Capacity Optimization 10.5 (TSCO)
2016 enhanc • Corrections for BSA 8.2 to 8.6 reporting has been added. See the following topics:
ements
• Upgrading
• Configuring environment settings
• Adding deployments
• You can now schedule license reports. See Scheduling reports
• Version 2.0.00 wiki docs and PDF has been added
(Version 1.6.00 wiki docs have been maintained as a separate space.)
• Upgrading
• Server clustering information in reports
• Scheduling reports
• The screenshots in the Getting started topic have been updated with the following:
• The License Report tab has been updated to show the Execution Method
column (Manual or Auto)
• The Schedule reports tab has been added
Decembe 1.6.00 • The Report File Prefix field has been added to the Manage Deployments form where you
r 15, 2015 enhanc can enter the server name. This will be automatically appended to the report file name.
ements See Adding deployments.
• The Email Attachment File Prefix text box has been added to the License Report tab. This
enables you to append a prefix to the file name, such as your organization's name, so that
you can easily find the file in your default email client mailbox. See Emailing reports.
• When reports are generated by the License Utility, a CSV file is created from the BMC
product's native file. The License Utility internally converts the native file format (for
example, XML or HTML) to the CSV format. See Running reports.
• The Release notes and notices and Known and corrected issues topics have been
updated
• A table listing the supported BMC products for the BMC License Usage Collection
Utility 1.6.00 has been added to the Integrating topic
• The Language information topic has been added
• The screenshots in the Getting started topic have been updated

Date Title Summary
May 19, 1.0.00 • Installation

2015 enhanc • The installer includes a license for easier installation
ements
• The Java Runtime Environment (JRE) is included with the utility, eliminating the
need to install/upgrade the existing JRE installed on user computers
• As part of the initial setup and prerequisites, an automated copy process was
added for BMC product-specific script files
• A new feature was added to encrypt/decrypt credentials
• New user interface
• See the Quick tour of the new UI with screenshots in the Getting
started topic.
• New robust and feature-rich user interface
• License Report and Management Deployment tabs
• New Help tab to provide user documentation
• Deployments
• Add, edit and delete deployments with real-time connectivity test and validation
for a given user session
• Test existing deployments to ensure data validity at any point of time
• Reports
• You can run license usage reports on: ADDM, ARS, BDA, BNA, and BSA
• You can run reports for deployments hosted on both Unix/Linux and Windows
platforms
• When running license usage reports, you can:
• Select single, multiple, or all deployments
• Select various duration times (start and end dates for the report
time frame)
• View real-time status messages while the report is running
BMC Confidential. BladeLogic Confidential. The following information is intended only for registered users of docs.bmc.com.
The following issues pertain to this release of the BMC License Usage Collection
Related topics
Utility and its service packs and patches.


Known and corrected product issues
Componen Description Correcte Affected Defect

t d in versions ID
License In the Windows 4.9.00 4.8.00 DRLUC-

Gathering server username or 258
password, if you
specify a character
string such as
passw$RD123, the
server connection
fails.
Installation A "Failed to find any 2.0.00 1.5.00 LU-57

suitable JVM"
message appears
while installing the
License Utility using
setup.exe when Java
has not been
installed on the
computer.
All BMC License 2.5.00 1.0.00,

Collection Utility 1.6.00, and
installed using non- 2.0.00
English language.
Manage If the BNA and ADDM 1.5.00 1.0.00 DE9366

Deploymen default ports are 1
ts changed, the license
usage will not be
collected.
License LUCU to handle error 2.5.00 2.0.00 DRZJZ-5

Gathering 302 and HTTP URL 11
output as ADDM web
API response.


t d in versions ID
License Change in ADDM 2.5.01 2.5.00 DRZJZ-5

Gathering query from License 36
Utility similar to built-
in query in ADDM.
UI High CPU 2.5.01 2.5.00 DRZJZ-5

consumption on 35
launch of License
Utility.
Manage RPD connection fails 4.0.00 3.5.00 DRZJZ-1

Deploymen when there are zero 038
ts or one server
configured under RPD
server.
Manage RPM connection fails 4.0.00 3.5.00 DRZJZ-1

Deploymen when there are zero 039
ts or one server
configured under
RPM server
Manage LUCU 3.6.00 failed to 4.0.00 3.6.00 DRZJZ-1

Deploymen run ADDM 11.1 for 016
ts HTTPs protocol.
Reports TSCO shows 4.0.00 3.6.00 DRZJZ-1

successful status 139
even when report is
not generated.
Manage Issue with 4.0.00 2.5.00 DRZJZ-7

Deploymen deployment ID 78
ts creation for same
server name.


t d in versions ID
Manage Application hangs 4.6.00 DRZJZ-1

Deploymen while saving a 901
ts deployment after
attempting to add
multiple manual
deployments (
irrespective of the
product).
BMC Confidential. BladeLogic Confidential. The preceding information is intended only for registered users of docs.bmc.com.
Technical bulletins
Review this section for information updates to the BMC License Usage Collection
Related topics
Utility product and documentation that are not related to flashes, service packs, or
patches.
• BMC License Usage Collection Utility version 4.7.01
BMC License Usage Collection Utility version 4.7.01
Change in BNA license report generation mechanism
 Note
The following applies to BMC Network Automation (BNA) version 8.9.x and higher.
For BMC License Usage Collection Utility version 4.7.01, there is a change in the mechanism of reading the Consumption
field for REST API of BMC Network Automation version 8.9.x and higher. This change has no impact to the license utility
users; there is no change in the UI, nor in any functionality.

For customers using BMC License Usage Collection Utility version 4.7.00 and BNA 8.9.x and higher, we recommend
upgrading to the license utility version 4.7.01.
For more information on upgrading, see Upgrading .
6.0.00 enhancements
New features
• Support for the Spanish language and locale (ES-XL).

• Support for open source Red Hat JRE.
The JRE folder is not deleted after the upgrade to version 6.0.00. If you have any security concerns, you can
manually delete the folder from C:\Program Files (x86)\BMC Software\LicenseUsageCollector.
• Support for an alert mechanism on exceeding the threshold for BMC Client Management product.
• Integration with the Control-M Usage Reporting Tool.
• Continuous Feedback survey option.
Other enhancements
• Enhanced BMC Helix Digital Workplace Active User report to fetch the monthly count for unique users.
• Disablement of TLS 1.0 and TLS 1.1.
• Support added for TLS 1.2.

Enhancements to supported BMC products

The following are the just in time updates:
BMC product Latest supported version Support added on
BMC Discovery (Discovery) 23.1 20 Jan 2023
TrueSight Network Automation (TSNA) 22.4 20 Dec 2022
TrueSight Operations Management (TSOM) 11.3.06 06 Dec 2022
BMC Client Management (BCM) 22.4.00 06 Dec 2022
BMC Digital Workplace (MyIT) 21.05, 21.3, 22.1 28 Jul 2022
TrueSight Server Automation(TSSA) 22.2 24 Jun 2022
BMC Release Process Management (RPM) 5.0.07 25 May 2022
BMC Digital Workplace (MyIT) 20.08 06 May 2022
TrueSight Network Automation (TSNA) 22.1 06 May 2022
TrueSight Network Automation (TSNA) 20.02.01 06 May 2022
BMC Discovery (Discovery) 22.1 07 Feb 2022
BMC Release Process Management (RPM) 5.0.06 25 Jan 2022
BMC Client Management (BCM) 21.02.02 18 Nov 2021

TrueSight Operations Management (TSOM) 11.3.05 31 Oct 2021
TrueSight Server Automation(TSSA) 21.03 21 Oct 2021
BMC Database Automation (BDA) 20.21.01 31 Aug 2021
BMC Discovery (Discovery) 21.05 28 May 2021
BMC Release Process Management (RPM) 5.0.05 26 May 2021
TrueSight Server Automation(TSSA) 21.02 15 Mar 2021
BMC Client Management (BCM) 21.02 22 Feb 2021
BMC Release Process Management (RPM) 5.0.04 18 Dec 2020
BMC Database Automation (BDA) 20.20.02 21 Oct 2020
TrueSight Operations Management (TSOM) 11.3.04

15 Sep 2020
BMC Discovery (Discovery) 20.08

15 Sep 2020
TrueSight Capacity Optimization (TSCO) 20.02.01

21 Aug 2020

21 Aug 2020
BMC Database Automation (BDA) 20.20.01

18 May 2020

BMC Digital Workplace (MyIT) 19.08, 19.11, 20.02

04 May 2020
TrueSight Network Automation(TSNA) 20.02

24 Feb 2020
BMC Discovery (Discovery) 12.0

24 Apr 2020
Remedy AR System Server (ARS) 20.02

24 Feb 2020
TrueSight Capacity Optimization (TSCO) 20.02

24 Feb 2020
TrueSight Server Automation(TSSA) 20.02

24 Feb 2020
TrueSight Operations Management (TSOM) 11.3.03

23 Dec 2019
BMC Database Automation (BDA) 20.19.03

23 Dec 2019

29 Aug 2019
Remedy AR System Server (ARS) 19.08

27 Aug 2019
19.02.01
Remedy AR System Server (ARS) 31 May 2019

TrueSight Capacity Optimization (TSCO) 11.5.01

02 Aug 2019

Supported BMC products

The BMC License Usage Collection Utility supports the following BMC products to
run license usage reports:
Related topic
Note

BMC License Usage Collection Utility supports the latest BMC product
versions to run license usage reports. However, BMC License Usage Adding deployments
Collection Utility displays the product versions based on your updated
version of the utility. You might see the older BMC product versions on
the BMC License Usage Collection Utility UI.
BMC product Supported versions
BMC Digital Workplace Named 18.02 and later

User Report v18.02 and later
(DWPNUR)
TrueSight App Visibility 11.0 to 11.3.03

Manager (TSAVM)
BMC Discovery (Discovery) 8.3.2 to 23.1
BMC Database Automation 8.3 to 20.21.01

(BDA)
BMC Network Automation 8.3 to 8.9.02

(BNA)
(see also TrueSight Network

Automation 8.9.03)

BMC Server Automation (BSA) 8.2 to 8.6*
(see also TrueSight Server 8.7 to 8.9.02

Automation 8.9.03)
*See separate instructions in
.Upgrading v5.0, .Configuring environment
settings v5.0, and Adding deployments
BMC Client Management 11.6 to 22.4

(BCM)
BMC Performance Manager 2.11

Portal (BPM Portal)
BMC Release Package and 4.8.00 to 5.0.03

Deployment (RPD)
BMC Release Process 4.6.00 to 5.0.07

Management (RPM)
BMC Digital Workplace (MyIT) 3.1 to 3.3 and 18.05 to 22.1
Note:
• DWP Active user reports are available for

all versions (3.1 to 3.3 and 18.05 to 22.1)
of DWP.
• Named user reports are available from
version 18.02 and later.

Remedy AR System Server 7.6.04 to 20.02

(ARS)
If you are running the Remedy AR System
Server 19.02.01 on UNIX platform and you
need to generate a license compliance report,
perform the steps specified in the
workaround of the defect SW00558482 to
make the produse.exe utility work.
Notes:
• BMC License Usage Collection Utility does

not supports Remedy AR System Server
19.02.00. Issue occurs while running the
produse.exe file.
• If you are running the Remedy AR System
Server 19.02.00 and you need to generate
a license compliance report, see
BMC Communities .
Or
You can send the LicenseReport.txt file
located at <Drive where ARS is installed>:
\Program Files\BMC
Software\ARSystem\Arserver\Db to the
BMC License Compliance team.
TrueSight Capacity 10.5 to 20.02.01

Optimization (TSCO)
TrueSight Network Automation 8.9.03 to 22.4
(formerly BMC Network

Automation - BNA)
TrueSight Operations 10.7 to 11.3.06

Management (TSOM)
TrueSight Server Automation 8.9.03 to 22.2
(formerly BMC Server

Automation - BSA)


Introduction
Introduction to the BMC License Usage Collection Related topics

Utility
The BMC License Usage Collection Utility is a free application that enables you to run Getting started
license compliance reports on the BMC products your organization owns. This
information can help you determine whether you're under-utilizing or over-utilizing PDFs and videos
licenses. Although you can run license reports from individual BMC products, the
license utility enables you to run reports all at once across many BMC products (See Downloading the installation
Supported BMC products). The license utility provides specific license report file
information for each BMC product, so the report contents and formatting vary
(see Reports overview for details on each product's report). You can also view BMC
product license usage per product deployment in the form of bar charts
(see Dashboard overview).
Configuration is quick and easy. You configure the license utility only once for each
BMC product by connecting to the servers that host the BMC products. (See
Configuring product servers.) When you're ready to run the reports, the license
utility automatically connects to the server and produces a report, like the following
CSV example. (See Running reports.) Each time reports are run, they are stored in
the user\Reports folder where the License Utility is installed
($LicenseUsageCollectorHome\licenseusagecollector\user\Reports\timestamp
folder).
You can schedule the license reports to run automatically on a daily, weekly, or
monthly basis, or on a customized schedule. (See Scheduling reports.) You can also
configure the license utility to automatically email scheduled reports to a specified
email address (See Enabling email notification of reports with SMTP.)

After you review the reports and email them to the BMC License Compliance team,
you can also talk to your BMC sales representative about managing your under-
utilized or over-utilized licenses.
Downloading the license utility

You can download the free license utility either from the BMC Communities page or
from the BMC Electronic Product Distribution (EPD) site (see Performing the
installation).
Videos
For a brief overview and demo, see our videos on YouTube.

Getting started
The following diagram provides a walk-through of the license utility process flow.
Related topics
Introduction
PDFs and videos

Supported languages and locales

Related topics
The BMC License Collection Utility supports the following languages and locales:
• English (en_US, en) Performing the installation

• German (de_DE, de)
• French (fr_FR, fr)
• Spanish (es_XL, es)
The product documentation is available in English, German, French and Spanish.
 Note
Currently you can only install the license utility for one language at a time.
If you need to switch languages, you will need to uninstall, then reinstall in
the preferred language. See .Uninstalling v4.5 and .Performing the
installation v4.5.
English language considerations

Special characters are allowed only in server username and password fields.
German language considerations

German input characters and numerals are only allowed in server username and
password fields for:

French language considerations

French input characters and numerals are only allowed in server username and

Spanish language considerations

Spanish input characters and numerals are only allowed in server username and


 Note
In Microsoft Windows operating systems, some of the French characters
and special characters are not supported. Therefore, you may not be able
to use such characters for the Remedy AR System Server (ARS) username.
BMC License Collection Utility support French characters in the password
except the blank 'space' and ` (backtick) characters.
For BCM, all French character combinations work well.

System requirements
The License Utility can run on a server or desktop environment that has connectivity to the computers where the BMC
products are installed. The following hardware and software requirements must be met before installing the BMC License
Usage Collection Utility.
Software requirements
Operating systems
The following operating systems are supported for the ControllerHost:
Operating system Version
Windows • Windows 10 (64-bit)

• Windows 2012 Enterprise Server
PowerShell
The BMC License Usage Collection Utility version 4.6.00 requires PowerShell 2.0 and later.
PowerShell Version #
PowerShell 2.0
PowerShell 3.0
PowerShell 4.0
PowerShell 5.0
Email client
The following email clients are supported for the license report email attachment feature (not required for installation):

Operating system / version Email client / version
Windows 10 (64-bit) • Microsoft Office Outlook 2016 (32-bit)

• DreamMail
• eM client
• Postbox
• SeaMonkey
• Thunderbird
Windows 2012 (64-bit) • Microsoft Office Outlook 2016 (32-bit)

• Microsoft Office Outlook 2013 (64-bit and 32-bit)
• DreamMail
• eM client
• Postbox
• SeaMonkey
• Thunderbird
Hardware requirements
Computer Recommended specifications
Controller Host Installation folder size: 186 MB
Windows Installer size: 83.0 MB

Installing
This section provides information about installing the BMC License Usage Collection
Related topics
Utility.
You can install the BMC License Usage Collection Utility on Windows systems. For
more information, see the System requirements and Prerequisites for installation. • Prerequisites for
installation
• Downloading the
 Important installation file
• After installing the license utility, we recommend that you maintain
• Performing the
the User folder securely in its installed path, as it contains your
installation
server deployment information, for example: C:\Program Files
(x86)\BMC • Uninstalling
Software\LicenseUsageCollector\licenseusagecollector\user.
Installing on Windows 10
To install the BMC License Usage Collection Utility in the default path (C:
\Program Files\BMC Software\LicenseUsageCollector), you should launch
the installation setup.exe of the utility using the “Run as Administrator”
option.
Prerequisites for installation

• Make sure that your system meets the minimal requirements for Hardware and Software. For more information,
see the System Requirements.
• The ControllerHost must be able to connect remote servers where BMC products are installed through WMI for
Windows servers and through SSH for Unix servers.
Downloading the installation file

You obtain the free product installation file by downloading it either from 1) the
BMC Electronic Product Distribution (EPD) website , or 2) the BMC Community page .
Access to the EPD website requires that you provide your BMC Support credentials. You might also be prompted to
complete the Export Compliance Form.
Where to go from here

Performing the installation

Performing the installation

The following instructions describe how to install or reinstall the BMC License Usage
Collection Utility. If you are upgrading, please see Upgrading.
Related topics
Before you begin
• Download the installation file
Configuring product servers
 Note Uninstalling
The License Usage Collection Utility supports two models for deployment:
Supported languages and
1) The license utility installed on one computer and the BMC product
locales
installed on another and accessed remotely, or 2) The license utility
installed on the same computer as the BMC product. For more information,
see Adding deployments.
To install or reinstall the BMC License Usage Collection Utility
 Important
• After installing the license utility, we recommend that you maintain
the User folder securely in its installed path, as it contains your
server deployment information, for example: C:\Program Files
(x86)\BMC
Software\LicenseUsageCollector\licenseusagecollector\user.
Installing on Windows 10
To install the BMC License Usage Collection Utility in the default path (C:
\Program Files\BMC Software\LicenseUsageCollector), you should launch
the installation setup.exe of the utility using the “Run as Administrator”
option.
1. Log in as an Administrator on the computer where you want to install the

BMC License Usage Collection Utility.
 This computer must be able to connect to all servers/systems that

host BMC products, and will be referred to as the “ControllerHost”.
2. Extract the installer file contents in any directory on the ControllerHost. This
will create a directory named Disk1.
3. Run the setup.exe located in the Disk1 directory.
4. On the License Usage Collector screen, select a language: US English,
Deutsch (German), French or Spanish then click OK.

 Note
After you select a language and install the license utility, the UI will
appear in your selected language. The language cannot be changed
after installing. If you wish to change the language, you will need to
uninstall, then reinstall the license utility. See Uninstalling.
5. On the Welcome screen, click Next.

6. Review the End User License Agreement, then select I agree to the terms of
license agreement, and then click Next.
7. If you are installing the application for the first time:
 Note
Go to Step 10 if you are reinstalling in order to change the language
from English to German, English to French or English to Spanish or
vice versa.
8. On the Directory Selection screen, accept the default location (C:\Program

Files\BMC Software\LicenseUsageCollector), or click Browse to select an
installation folder, then click Next.
 Note
The Directory Selection screen appears when you are installing the
license utility for the first time. For reinstallations, see step 10,
below.
9. On the Installation Preview screen, click Install.

The progress bar appears while the application is installed.
10. If you are reinstalling or upgrading the application:
a. On the Installation Preview screen, the location where the product is
installed appears, along with the features to be installed. Click Install.
The progress bar appears while the application is reinstalled.
b. A message displays asking if you want to overwrite the existing
directory. Click Yes to All to overwrite all files.
 Note
When installing in German, French or Spanish make sure to
select the "Yes to All" option.
If you select only Yes or No, you will need to confirm the directory
location for each file.
If you select Yes or Yes to All, all of the deployment details history will
be removed.
If you select No to All, all of the deployment details history will be

retained.
11. Accept the default "Create and Start Scheduler Service" and "Create Shortcut
on Desktop",or deselect the check boxes, then click Next.
The LUCService (License Usage Collector Service) will appear in Windows
Services with the status "Started". You can manually start and stop the
LUCService.
12. On the next screen, in the One-time Install Key field, enter a password of
your choice (minimum: eight characters), then click Next.
If you are upgrading from version 4.6.00, this step is not required.
13. (Optional) On the Installation Summary screen, click View Log to see the
installation log.
The licenseuagecollector_install_log.text window appears. You can click each
item in the list to view additional details.
14. On the Installation Summary screen, click Done.
To access the BMC License Usage Collection Utility user interface,
see Accessing and navigating the license utility.
Where to go from here

Uninstalling
You can either specify to uninstall the License Usage Collector Utility application and usage data at once, or you can
specify to uninstall only the application and preserve the usage data. You cannot uninstall only the usage data.

Uninstalling in order to reinstall in either English, German, French or Spanish
• Make sure to select option 4b to only uninstall the application and preserve the usage data files.
Uninstalling on Microsoft Windows 10

If the BMC License Usage Collection Utility was installed in the default path (C:\Program Files\BMC
Software\LicenseUsageCollector), you should:
1. Launch the uninstallation of the utility using the “Run as Administrator” option.
2. Restart your computer to complete the uninstallation process.
To uninstall the BMC License Usage Collection Utility

1. From the Start menu, select All Programs > BMC Software > LicenseUsageCollector > Uninstall
LicenseUsageCollector.
2. On the License Usage Collector screen, select English, Deutsch (German), French or Spanish then click OK.
3. On the License Usage Collector Uninstaller screen, click Next.
4. Select one of the following for the features you would like to uninstall:
a. License Usage Collector (version #) Uninstallation
(This will uninstall both the application and the usage data files.)
or
b. Uninstall License Usage Collection (version #), then deselect the Uninstall License Usage Data (version #)
check box.
This will only uninstall the application and will preserve the usage data files. If you are uninstalling in order
to switch languages (English, German, French or Spanish), select this option.
 Warning
If you select Uninstall License Usage Data, all of the usage data will be deleted. By default, these
files are located in
C:\Program Files\BMC Software\LicenseUsageCollector\licenseusagecollector\user.
If you attempt to only uninstall the usage data, a warning message appears directing you to go
back and select one of the two options above in step 3.
5. After you have made your selection, click Next.

6. The Uninstallation Preview screen displays the selected features to be uninstalled. Click Uninstall.
The progress bar appears while the application is uninstalled.
7. (Optional) On the Uninstallation Summary screen, click View Log to see the log.
The licenseuagecollector_uninstall_log.text window appears. You can click each item in the list to view additional
details.
8. On the Uninstallation Summary screen, click Done.
The LUCService (License Usage Collector Service) will be removed from Windows Services.
9. Restart your computer to complete the uninstallation process.
To reinstall the license utility, see Performing the installation.

Upgrading
This section provides information about upgrading the BMC License Usage Collection Utility.
Upgrading to 6.0.00
Upgrading from 4.9.00, 5.0.00, 5.5.00 to 6.0.00

• Before upgrading to version 6.0.00, you do not need to manually uninstall the previous version of BMC License
Usage Collection Utility. The installation process automatically upgrades to the new version.
• You must run the installer as an administrator.
• During the installation process, you have an option No to All to maintain the deployment settings from the
previous version, or overwrite the deployment settings in the new version.
• The JRE folder is not deleted. If you have any security concerns, you can manually delete the folder from C:
\Program Files (x86)\BMC Software\LicenseUsageCollector.
Upgrading to 5.5.00
Upgrading from 4.8.00, 4.9.00, 5.0.00 to 5.5.00

• Before upgrading from 4.8.00 version to 5.5.00 version, you do not need to manually uninstall the previous version
of BMC License Usage Collection Utility. The installation process automatically upgrades to the new version.
• You must run the installer as an administrator.
• During the installation process, you have the No to All option to maintain the deployment settings from the
Upgrading from 4.5.00 to 5.5.00

Before upgrading to 5.5.00 version from 4.5.00 version, uninstall the current 4.5.00 version on your system and then install
the 5.5.00 version.
Upgrading to 5.0.00
Upgrading from 4.7.01, 4.8.00 and 4.9.00 to 5.0.00

• Before upgrading from version 4.7.01 to version 5.0.00, you do not need to manually uninstall the previous version
• You must run the installer as an administrator user.

• Upgrading to version 5.0.00 is not supported from 4.5.00 versions of the BMC License Usage Collection Utility.

• Before upgrading to version 5.0.00, you must uninstall the previous version of BMC License Usage Collection Utility.
Upgrading to 4.9.00
Upgrading from 4.6.00, 4.7.01, and 4.8.00 to 4.9.00
Upgrading to 4.8.00
Upgrading from 4.6.00 and 4.7.01 to 4.8.00


Upgrading to 4.7.01
• For customers using BMC License Usage Collection Utility version 4.7.00 and BNA 8.9.x and higher, we recommend
upgrading to the license utility version 4.7.01. For more information, see Technical bulletins.

Upgrading to 4.7.00

• You do not have to manually uninstall a previous version of the license utility before upgrading from version 4.6.00
to version 4.7.00. The installation process will automatically upgrade to the new version.
• When upgrading, run the installer as an administrator user. During the installation process, you will have the
option ("No to All") to maintain the deployment settings from the previous version, or overwrite them in the new
version. See Installing.
• When upgrading, you will not need to enter a password in the One-time Install Key field (it will automatically
update from version 4.6.00).
Upgrading from version 4.0.01 and 4.5.00 to 4.7.00

• Upgrading to version 4.7.00 is not supported from 4.0.01 and 4.5.00 versions of the BMC License Usage Collection
Utility.
• You will need to uninstall previous versions before installing version 4.7.00. See Installing.
Upgrading to 4.6.00
Upgrading from version 3.x and 4.x to 4.6.00

• Upgrading to version 4.6.00 is not supported from any previous versions of the BMC License Usage Collection
Utility.
• You will need to uninstall previous versions before installing version 4.6.00. See Installing.
Upgrading to 4.5.00
Upgrading from version 3.x

A new installation is required in order to access the user\logs and user\Reports directories.
Upgrading from version 4.0.00

When installing, make sure to select the "Yes to all" option. This will remove all of the deployment details history and
create a clean install copy. (For details, see #7 in Performing the installation.)

You do not have to manually uninstall a previous version of the license utility before upgrading from version 4.0.01 to
version 4.5.00. The installation process will automatically upgrade to the new version.
When upgrading, run the installer as an administrator user. During the installation process, you will have the option ("No
to All") to maintain the deployment settings from the previous version, or overwrite them in the new version.

Accessing and navigating the license utility

This topic describes how to access the BMC License Usage Collection Utility user
Related topics
interface.
1. From the Start menu, select All Programs > BMC Software >
LicenseUsageCollector > Start LicenseUsageCollector. Getting started
You can also navigate to C:\Program Files\BMC
Software\LicenseUsageCollector\licenseusagecollector\startUI.bat. Dashboard overview
2. Select a tab to access features. The default tab appears depending on the
Creating dashboard bar
following conditions:
charts
• If no deployments have been added, the Manage Deployment tab is
selected by default.
• If a deployment has been added, the License Report tab is selected by
default. Running the license utility
as an administrator
• If the dashboard has been configured, the Dashboard tab is selected
by default.
If the BMC License Usage
Collection Utility was
installed in the default path
(C:\Program Files\BMC
Software\LicenseUsageColle
ctor), you should launch the
utility using the Run as
Administrator option:
1. From the Start menu,

select All
Programs > BMC
Software >
LicenseUsageCollect
or.
2. Right-click Start
LicenseUsageCollect
or, then select Run as
Administrator.
For more information on this example, see Dashboard overview
Automatically running the

license utility as an
administrator
Local administrators can

configure the utility shortcut
to automatically run as an

administrator. (The following

does not apply to non-local
administrators.)
To configure the shortcut:
1. From the Start menu

or the desktop, right-
click the Start
LicenseUsageCollect
or shortcut, select
Properties.
2. On the Shortcut tab
of the Start
LicenseUsageCollect
or Properties dialog
box, click Advanced.
3. On the Advanced
Properties dialog
box, select the Run
as Administrator
check box, then click
OK.
4. Click OK to close the
Start
LicenseUsageCollect
or Properties dialog
box.


After you install the BMC License Usage Collection Utility, it must be able to connect
Related topics
to remote servers that host BMC products to successfully complete the license usage
collection process.
The utility secures a WMI connection to connect Windows based servers and an SSH • Configuring user
connection to connect UNIX/Linux based servers. In both the cases it uses the settings
deployment details, such as server name, user credentials, etc. to connect the
• Configuring
remote servers that the you have entered into the utility on the Add Deployment
environment settings
screen.
The utility does not require you to have administrator privileges on the servers.
However, as a one-time setup activity, you must complete the following tasks:
1. With the assistance of the your server administrator, ensure that the
PowerShell exists and is up and running. See System requirements.
2. Verify that the environment settings are in place. See Configuring
environment settings.
 Note
To configure user settings to enable non-administrative users to run the
license utility, see Configuring user settings.
Configuring user settings

Follow the steps below in each section for your operating system.
 Note
Please contact your local administrators who are responsible for configuring the servers for BMC products if you
encounter any issues while creating or setting up the environment variables.
Windows
Configure the Windows environment for non-administrator users
(Optional) Create a user account

1. Click Start, and in the Search programs and files box, type mmc compmgmt.msc, then press Enter.
2. In the left pane of Microsoft Computer Management Console, expand Local Users and Groups.
3. Right click the Users folder, then click New User.
4. Type the appropriate information in the dialog box, and then click Create.
5. Ensure that the User must change password at next logon checkbox is not selected.
This will ensure that the BMC License Usage Collection Utility will not prompt the user to change their password.
6. When you finish creating user accounts, click Close.

Windows Server 2003
 Note
The following steps are required only for Windows Server 2003.
1. In Windows Explorer, right click the executable C:\WINDOWS\system32\cmd.exe.

2. Select the Security tab.
3. On the cmd.exe Properties dialog, and add the following permissions to it:
• Read
• Read and Execute
Add the required groups to the new user
1. In the left pane of Microsoft Management Console, expand the Users folder.
2. Right click the user name, then click Properties.
3. Select the Member Of tab.
4. Click Add, then add the following groups:
• Distributed COM Users
• Performance Log Users
• Users

5. Click OK.
Verify password settings for non-administrator users
1. In the left pane of Microsoft Management Console, expand the Users folder.
2. Right click the user name, then click Properties.
3. Ensure that the User must change password at next logon checkbox is not selected.
This will ensure that the BMC License Usage Collection Utility will not prompt the user to change their password.
Configure WMI user access permissions for non-administrator users
1. Select Start, then enter wmimgmt.msc and press Enter.

This opens the Windows Management Instrumentation (WMI) console (wmimgmt).
2. In the console tree, right-click WMI Control, and then click Properties.
3. On the WMI Control Properties dialog, Click the Security tab, then click the Security button.
4. On the Security for Root dialog, select the License user, then select the Allow check boxes for each of the following
permissions:

• Execute Methods
• Enable Account
• Remote Enable
• Read Security
5. Click the Advanced button.
6. On the Advanced Security Settings for Root dialog, select the License user, then click the Edit button.
7. On the Permission Entry for Root dialog, from the Apply to list, select "This namespace and subnamespaces", then
click OK.
UNIX
(Optional) Create a new user
 Note
The user should be authorized to connect remotely using SSH.
If you want to add a new user, create the new user with the useradd command on the UNIX operating system.
Configuring environment settings

The following instructions describe how to configure BMC product servers to prepare for adding deployments to connect
to the license utility.
 Note
Configuration is not required for:
• BMC Digital Workplace (MyIT) 3.1 to 3.3

Configuring BMC Digital Workplace Named User Report v18.02 and later (DWPNUR)
Detailed instructions...
1. REST API should be accessible on AR server for HTTP and HTTPS.

2. For HTTPS, there are two scenarios : Only AR server HTTPS configuration or AR server HTTPS configuration with
RSSO.
3. The AR user should have following permissions for fetching the user records from REST API + CTM:People Form:
a. As an administrator, log in to the AR Server.
b. On the Home page, select Administrator Console > Application Administration Console.
c. To open the CTM:People form, on the Application Administration Console page, click the View link
corresponding to the People option.
The CTM:People form opens with user records.
d. From the user records table, select a single user whose permissions you want to update.
e. Click the Login/Access Details tab.
f. Navigate to Access restriction tab.
g. Select the Unrestricted Access check box.
h. Click Save.
4. If AR server is connected to the load balancer, which is in turn configured with HTTPS protocol and RSSO server,
then the JWT access should be enabled is the prerequisites for AR server REST API consumption.
For more information, see Everything that you need to know about accessing new CMDB UI.
For an RSSO enabled server, the entry is must be: /api/jwt/login*
Frequently asked question
Customer’s REST APIs stopped working after SP4 in RSSO environment. What do I do?
When you enable RSSO for AR, Jetty also gets enabled with RSSO (as Jetty is embedded in AR and the REST API
runs on Jetty), which results in failed REST API calls due to redirection to RSSO.
In such case, the exclude url in the server’s rsso-agent.properties file must contain /api/jwt/login* so that the
existing REST APIs are not redirected to RSSO.
Given below is a sample patter of the exclude url:
excluded-url-pattern=.*\\.xml|.*\\.gif|.*\\.css|.*\\.ico|/shared/config/.*|/WSDL/.*|/shared/error.jsp|/
shared/timer/.*|/shared/login_commn.jsp|/shared/view_form.jsp|/shared/ar_url_encoder.jsp|/
ThirdPartyJars/.*|/shared/logout.jsp|/shared/doc/.*|/shared/images/.*|/shared/login.jsp|/services/.*|/
shared/file_not_found.jsp|/plugins/.*|/shared/wait.jsp|/servlet/GoatConfigServlet|/servlet/
ConfigServlet|/shared/HTTPPost.class|/shared/FileUpload.jar|/BackChannel.*|/servlet/
LicenseReleaseServlet.* |/api/jwt/login*
5. The REST API generally runs on 8008 port for HTTP and 8443 port for HTTPS. You must confirm these ports on the
Jetty server entry and make sure that these ports are free.
You can configure the servername:8008 AR server so that it has both HTTP and HTTPs protocols enabled.
Example for AR REST API access:

http://servername:8008/api/jwt/login
https://servername:8443/api/jwt/login
Example for accessing CTM:People form

http://servername:8080/arsys/forms/servername/CTM%3APeople/Default+User+View

Configuring TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03

• Ensure that you have installed TrueSight App Visibility Manager server components, version 11.0 or later.
• Your role must be of a Solution Administrator to access the License Usage report.
Configuring BMC Digital Workplace Active User Report (DWPAUR) 18.05 to 22.1
• Specify the user for the BMC Digital Workplace application with the administrator / super administrator role.
Configuring BMC Discovery (Discovery)

• Ensure that the BMC Discovery environment is configured with HTTPS.

• Ensure that the BMC Discovery credentials have administrative rights to collect the BMC Discovery license
information.
• For BMC Discovery version 11.1, users need to have API access permission to query and get data.
• For BMC Discovery version 11.2.x and later, enter the user with Rest API and license data permission over
HTTPS. Do not use the system user.
• User should be part of the api-access group.
• User needs the api/license_data permission.
For example, select Administration > Groups > Action > Edit, on the api-access group, add the api/
license_data permission.
Configuring BMC Database Automation (BDA)

UNIX
1. Ensure that the SSHD process is running on the respective port.
 Note
BDA license gathering is supported only for the root user.
Configuring BMC Server Automation (BSA 8.2 to 8.6)

• Beginning with BMC License Usage Collection Utility 4.0.00, we are using the JDBC approach.
• The database user should be the normal user with Read/Write permissions to the Database schema.
Configuring BMC Server Automation (BSA 8.7 to 8.9.02) / TrueSight Server Automation 22.2
 Note
• For BSA 8.7 Windows and UNIX: The “Profile User” must be assigned to the “BLAdmins” role.

• For version 8.9.03, the product name has been changed to TrueSight Server Automation.
Windows and UNIX

Identify the servers where BMC Server Automation (BSA) Appserver is installed.
Windows
Ensure that the NSH folder is in the system path.
UNIX
Ensure that the SSHD process is running on the respective port.
Configuring BMC Client Management (BCM)

Ensure that the BCM credentials have administrative rights to collect the BCM License information.
Configuring BMC Performance Manager Portal (BPM Portal v2.11)

Windows and UNIX

1. For UNIX, ensure that the SSHD process is running on the respective port.
2. Identify the servers where the BMC Performance Manager Portal database is installed.
3. Ensure that, on the Oracle database server, either the ORACLE_BASE or the DATASTORE_HOME environment
variable is set.
The License Utility will check for these two environment variables.
4. For Windows, ensure that %ORACLE_BASE%\utility\BPM_Datastore_Utility or %DATASTORE_HOME%
\utility\BPM_Datastore_Utility exists and is accessible.
For Unix, ensure that $ORACLE_BASE/utility/BPM_Datastore_Utility or $DATASTORE_HOME/utility/
BPM_Datastore_Utility exists and is accessible.
While configuring the BMC Performance Manager Portal, ensure that the following tasks as complete:
• SQL Plus is invoked and running with the database user that is provided on the BMC License Usage Collection
Utility.
To verify that SQL Plus is invoked, ensure that the tnsnames.ora file is present with correct instance names of the
BMC Performance Manager Portal database configured.
• For UNIX, you have Bash shell installed on the machine where you have the BMC Performance Manager Portal
database.
 Notes
• In Windows the user should belong to the group ora_dba. In Unix it is group dba.
• Ensure that the BPM_Datastore_Utility folder is present on the BMC Performance Manager Portal
database server.
To add the BPM_Datastore_Utility folder to the BMC Performance Manager Portal database server, copy

the folder from the BMC Performance Manager Portal application server to the BMC Performance
Manager Portal database server.
• Ensure that the BMC_PM_Portal_Licensing_Report SQL file is present in the Scripts folder that is
required to generate the BMC Performance Manager Portal license information.
For example, C:\BMCSoftware\Datastore\ora10g\utility\BPM_Datastore_Utility\Scripts
You can download the BMC_PM_Portal_Licensing_Report SQL file from BMC Performance Manager
Portal License Usage Utility 1.0 link on Electronic Product Download.
• If you have your own Oracle license, to use ORACLE_BASE as an equivalent to DATASTORE_HOME perform
the following steps:
a. Create a utility folder with ORACLE_BASE as the parent folder.
b. Copy the BPM_Datastore_Utility folder to ORACLE_BASE\<Utility folder name>.
Windows
Ensure that the "ORACLE_BASE or DATASTORE_HOME " environment variable is set for the logged-in user (Server user
field value) on that server.
UNIX
1. Ensure that the "ORACLE_BASE or DATASTORE_HOME " environment variable is set in the “. profile” file for the
logged-in user (Server user field value) on that server.
2. Make sure one of the following files has the execute permission:
a. $ORACLE_BASE/utility/BPM_Datastore_Utility/DatastoreCliBMCPDS.sh
b. $DATASTORE_HOME/utility/BPM_Datastore_Utility/DatastoreCliBMCPDS.sh
3. If not, assign the permission using the following command: chmod +x DatastoreCliBMCPDS.sh.
Configuring BMC Release Process Management (RPM)

The user must be in the "Root" group to have access to the v1 API.
Configuring Remedy AR System Server (ARS) based products

Windows
1. Identify the server where Remedy AR System Server (ARS) is installed.
2. Ensure that the "BMC_AR_SYSTEM_HOME" environment variable is set on that server.
UNIX
1. Ensure that the SSHD process is running on the respective port.
2. Ensure that the user whose credentials are being used by the License Utility to connect to this server has
BMC_AR_SYSTEM_HOME mapped to the correct directory and exported in the .profile file. For example:
Export BMC_AR_SYSTEM_HOME=/<dir1>/<dir2>/ARSystem
3. Ensure that the non-root user as read access permission for the $BMC_AR_SYSTEM_HOME/db/LicenseReport.txt
file.

4. If the BMC_AR_SYSTEM_HOME variable is not set:

a. Log in to the Unix machine with the user name and credentials used in the "Server User" and "Server
password" fields on the License Utility UI while adding the deployment.
b. Copy the script from location:"<LU_Install_Directory>/licenseusagecollector/EnvVariableScripts" to the
Unix machine.
c. Give execute permission to the script using chmod +x <scriptname>.
d. Execute the script.
Sample run...
Configuring TrueSight Operations Management (TSOM) 10.7 to 11.3.06

Only super and tenant administrator credentials are required to collect the TSOM license information.
Configuring TrueSight Capacity Optimization (TSCO) 10.7 to 20.02.01

1. Log in to the TSCO console.
2. Enter the server name from Administration >COMPONENTS > Backend Services > API Providers - Data service.
a. Alternatively you can obtain your server name from the following path: Administration >COMPONENTS >
Backend Services > API Providers - Data service).
For example: The API is exposed through a REST interface available at the following address:
https://servername:8280/dh-services/data

Administering deployments
In the BMC License Usage Collection Utility, deployments are configurations to connect the license utility with a BMC
product in order to generate license usage reports.
You can add, edit, and delete deployments from the Manage Deployments tab. See the following topics for detailed
instructions.
• Adding deployments
• Editing deployments
• Deleting deployments
• BMC Tools Integration
Adding deployments
The License Usage Collection Utility supports two models for deployment:
1) The license utility installed on one computer and the BMC product installed on another and accessed remotely, or
2) The license utility installed on the same computer as the BMC product.
For BSA, ARS, and BPM Portal, see the note in the respective product's instructions for Windows servers where the
license utility and the BMC product are installed on the same computer.
Note
In order to run license reports, the BMC product name must be listed in the Select Deployments list on the License
Reports tab. If the product is not listed, see the following instructions.
To add a deployment from the License Report tab

The License Report tab provides a link to the Management Deployment tab so you can add deployments.
1. Click the License Report tab, then click Add Deployment.

The Manage Deployment tab opens.
2. Complete the following steps for the respective products, then return to step 4 on this page.
• BMC Discovery (Discovery) 8.3.2 to 23.1
• BMC Database Automation (BDA) 8.3 to 20.21.01
• BMC Network Automation (BNA) 8.3 to 8.9.04 / TrueSight Network Automation 22.4
• BMC Server Automation (BSA) 8.7 to 8.9.02 / TrueSight Server Automation 22.2
• BMC Client Management (BCM)11.6 to 22.4
• BMC Performance Manager Portal (BPM Portal) 2.11
• BMC Release Package and Deployment (RPD) 4.8.00 to 5.0.03
• BMC Release Process Management (RPM) 4.6.00 to 5.0.07

• Remedy AR System Server (ARS) 7.6.04 to 20.02

• TrueSight Capacity Optimization (TSCO) 10.5 to 20.02.01
• TrueSight Operations Management (TSOM) 10.7 to 11.3.06
• TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03
• BMC Digital Workplace Named User Report v18.02 and later (DWPNUR)
To add a deployment from the Manage Deployment tab

1. Click the Manage Deployment tab, then click Add.
 Tip
If you do not see the Add button, you may be viewing the tab in edit mode. Click Cancel and you should
see the Add button.
2. In the Select Product list, select the BMC product, for example: Remedy AR System Server (ARS).
3. Complete the following steps for the respective products, then return to step 4 on this page.
• BMC Discovery (Discovery) 8.3.2 to 23.1
• BMC Database Automation (BDA) 8.3 to 20.21.01
• BMC Network Automation (BNA) 8.3 to 8.9.04 / TrueSight Network Automation 22.4
• BMC Server Automation (BSA) 8.7 to 8.9.02 / TrueSight Server Automation 22.2
• BMC Client Management (BCM)11.6 to 22.4
• BMC Performance Manager Portal (BPM Portal) 2.11
• BMC Release Package and Deployment (RPD) 4.8.00 to 5.0.03
• BMC Release Process Management (RPM) 4.6.00 to 5.0.07
• Remedy AR System Server (ARS) 7.6.04 to 20.02
• TrueSight Capacity Optimization (TSCO) 10.5 to 20.02.01
• TrueSight Operations Management (TSOM) 10.7 to 11.3.06
• TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03
4. A confirmation message appears indicating that the deployment was saved or not.
The Validation Status column displays the outcome of the deployment (Success or Failed).
 Note
If the validation fails, in the Deployments section, select the product name, in the Edit Details section, re-
enter the credentials, then click Save.

The deployments are validated for each user session, so each time the application is launched, the system
validates the deployment details.
In the Deployments grid, the Product Name, Server Name, and Validation Status appears.
BMC Discovery (Discovery) 8.3.2 to 23.1
 Note
• Due to the new Product version field for the 4.5.00 version of the license utility, if you have already added
a deployment for Discovery versions 11.0 or 11.1, you will need to delete it, then add a new deployment.
• Ensure that the BMC Discovery environment is configured with HTTPS.
• Only English characters, numerals and special characters are allowed.
1. In the Enter Details section, in the Environment list, select an option (for example, Production or Pre-production).
2. In the Product Version field, select your Discovery version (applicable only for Discovery versions 11.0, 11.1, 11.2,
11.3, 12.0, 20.08, 21.05 and 23.1).
3. In the Server Name field, enter the server name where the BMC Discovery web service is hosted.
4. In the Server User field, enter the BMC Discovery application user name.
5. In the Server Password field, enter the password for the user specified in step 4.
6. In the Server Confirm Password field, enter the password again.
In the Server Type list, WEBSRV is entered by default.
7. In the Report File Prefix field, the value entered in the Server Name field in step 2 will automatically appear,
appended by "_1", for example: servername_1.
You can edit the field value before saving the Manage Deployment tab.
 Note
Only English characters are allowed in the Report File Prefix field.
After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and cannot
be changed.
8. In the Deployment Protocol list, select an option (HTTPS or HTTP).

9. Click Save.
10. Return to step 4 on Adding deployments.
BMC Database Automation (BDA) 8.3 to 20.21.01
 Note
Only English characters, numerals and special characters are allowed.
2. In the Server Name field, enter the server name where the BDA server is installed.
3. In the Server User field, enter the system user name.

In the Server Type list, UNIX is entered by default.
6. In the SSH Port field, enter the system SSH port (required for non-default) for the UNIX server.
 Note
be changed.
8. Click Save.
BMC Network Automation (BNA) 8.3 to 8.9.04 / TrueSight Network Automation 22.4
 Note
For version 8.9.03, the product name has been changed to TrueSight Network Automation.
2. In the Server Name field, enter the server name where the BNA web service is hosted.
3. In the Server User field, enter the BNA application user name.
 Note
be changed.
7. Click Save.

BMC Server Automation (BSA) 8.2 to 8.6
 Note
• Delete existing and add new BSA deployments for version 2.0.00
• For BSA 8.2 to 8.6, before upgrading to BMC License Usage Collection Utility 2.5.00, BMC
recommends that you delete any existing BSA deployments. Then after upgrading, add a new
deployment for BSA 8.2 to 8.6 with the required information so that the database scripts can
gather the BSA license usage.
• Supported operating systems and database types/versions for BSA 8.2. to 8.6 license generation
Operating System Database type Database Version
Windows SQL Server 2008 R2
Windows Oracle 11g Release 2
Unix Oracle 12c
Unix Oracle 11g Release 2
1. In the Enter Details section, in the Environment list, select an option (for example, or Pre-production ).
2. In the Server Name field, enter the machine name where the BSA database is installed.
3. In the Server Type field, JDBC is entered by default.
 Note
be changed.
4. In the Database Type list, select the server type (Oracle or SQL Server).
5. In the Database Name/Service Name field, enter the SQL Server Database name or the Oracle Service name.
6. In the Database Port field, enter the Database listener port number.
7. In the Database User field, enter the Database user name of the BSA Schema.
8. In the Database Password field, enter the password for the database user specified in step 7.
9. In the Database Confirm Password field, enter the password again.
10. Click Save.

BMC Server Automation (BSA) 8.7 to 8.9.02 / TrueSight Server Automation 22.2
 Note
For version 8.9.03, the product name has been changed to TrueSight Server Automation.
1. In the Enter Details section, in the Environment list, select an option (for example, or Pre-production ).
2. In the Server Name field, enter the server name where BSA Appserver is installed.
 Note
As per Windows PowerShell limitation, you cannot use a forward slash, backward slash, or double quote
characters in a server username and server password field.
 Note
For a Windows server where the License Utility and BSA are installed on the same computer:
Enter one of the following: localhost, computer name, or full computer name (FQDN).
• Connection using an IP address is not supported.
• The following fields are disabled and automatically appear with "NA": Server User, Server
Password, Server Confirm Password, and Server Type (Windows).
• These are not required since the product and license utility are on the same computer.
3. For deployments to a remote server: In the Server User field, enter the system user name.
4. For a Windows server, enter the system user name in the format: Domain name\system username.
 Note
The license utility supports only Secure Remote Password (SRP) authentication.

7. In the Server Type list, enter the server type (Windows or UNIX).
 Notes
• Only English characters are allowed in the Report File Prefix field.
• After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and
cannot be changed.

• Do not use the $ sign in the Product User, Product Password, and Profile Name fields.
The $ sign is used by the Microsoft Windows batch interpreter to understand the parameter
number.
• The Product Password field supports English special characters such as @, %, !, #, *, (, /, ?, ., [, ],
{, }, \, -, _, +, `, ~, :, and '.
10. In the Product User field, enter the BSA profile user name.
The profile user requires access to the BLAdmins Role and login access via SRP Authentication.
11. In the Product Password field, enter the password for the BSA user specified in step 10.
12. In the Product Confirm Password field, enter the password again.
13. In the Profile Name field, enter a name for the profile.This profile name will be used to gather information.
 Note
The profile name for the BSA SRP authentication profile must not contain spaces.
14. Click Save.

BMC Client Management (BCM)11.6 to 22.4
 Note
English Characters, numeral and special characters are allowed for all fields. Additionally German and French
input characters and numerals are allowed only for server username and password fields.
2. In the Server Name field, enter the server name where the BCM web service is hosted.
 Note
BCM accepts only the servername:port format in the Servername field.
3. In the Server User field, enter the BCM application user name.
6. In the Server Type list, WEBSRV is entered by default.
 Note
be changed.


9. Click Save.
BMC Performance Manager Portal (BPM Portal) 2.11
 Note
Supported operating systems and database types/versions for BPM 2.11 license generation
Operating system Database type Database version
Windows Oracle 11.2.0
Unix Oracle 11.2.0
1. In the Enter Details section, in the Environment list, select an option (for example, or Pre-production).
2. In the Server Name field, enter the server name where the BPM Portal database is installed.
 Note
For a Windows server where the License Utility and BPM Portal are installed on the same computer:
Enter one of the following: localhost, computer name, or full computer name (FQDN).
4. For a Windows server, enter the system user name in the format: Domain name\system username.
 Notes
• Only English characters are allowed in the Report File Prefix field.

• After the Manage Deployment tab is saved, the Report File Prefix value becomes read only and
cannot be changed.
• Do not use the $ sign in the Database User and Database Password fields.
The $ sign is used by the Microsoft Windows batch interpreter to understand the parameter
number.
10. In the Database Type list, Oracle appears by default.

12. In the Database User field, enter the Database user name.
13. In the Database Password field, enter the password for the database user specified in step 12.
14. In the Database Confirm Password field, enter the password again.
15. Click Save.
BMC Release Package and Deployment (RPD) 4.8.00 to 5.0.03
 Note
2. In the Server Name field, enter the server name where the RPD web service is hosted.
3. In the RPD User Token field, enter the RPD User token for authentication.
 Note
be changed.

7. Click Save.
BMC Release Process Management (RPM) 4.6.00 to 5.0.07
 Note

2. In the Server Name field, enter the server name where the RPM web service is hosted.
3. In the RPM User Token field, enter the RPM Root Group User token.
 Note
be changed.

7. Click Save.
Remedy AR System Server (ARS) 7.6.04 to 20.02
 Note
English Characters, numeral and special characters are allowed for all fields. Additionally German and French
input characters and numerals are allowed only for server username and password fields.
2. In the Server Name field, enter the server name where the AR server is installed (for example, the machine name
used for the remote desktop connection).
For a Windows server, enter the system user name in the format: Domain name\system username.
 Note
As per Windows PowerShell limitation, you cannot use a forward slash, backward slash, or double quote
characters in a server username and server password field.
3. For a Windows server where the License Utility and ARS are installed on the same computer, enter one of the
following: localhost, computer name, or full computer name (FQDN).
 Note
For a Windows server where the License Utility and ARS are installed on the same computer:

For a Windows server, enter the system user name in the format: Domain name\system username.
 Note
be changed.
10. Click Save.

BMC Digital Workplace (MyIT) 3.1 to 3.3
 Note
• For version 3.3.02, the product name has been changed to BMC Digital Workplace.
• Important: Licensing supported for SQL and Oracle authentication only
• The following operating systems and database types/versions are supported for BMC Digital Workplace
(MyIT) 3.1 to 3.3:
Operating System Database type Database version
Windows SQL Server 2008
Windows SQL Server 2012
Windows Oracle Oracle 11g Release 2
Unix Oracle 12c
2. In the Server Name field, enter the machine name where the BMC Digital Workplace database is installed.
3. In the Server Type list, JDBC is entered by default.

 Note
be changed.
5. In the Database Type list, select the server type (Oracle or SQL Server).
7. In the Database Port field: Enter the Database Listener port number.
8. In the Database User field, enter the Database user name of the BMC Digital Workplace Schema.
9. In the Database Password field, enter the password for the database of the user specified in step 8.
10. Click Save.
BMC Digital Workplace (MyIT) 18.05 to 22.1
 Note
2. In the Product Version field, select your Digital Workplace version.
3. In the Server Name field, enter the server name where the BMC Digital Workspace web service is hosted.
4. In the Server User field, enter the Digital Workspace application username with the administrator / super
administrator role.
You can edit the field value before saving the Manage Deployment tab. Only English characters are allowed in
the Report File Prefix field.
 Note
be changed.

10. Click Save.

TrueSight Capacity Optimization (TSCO) 10.5 to 20.02.01
 Note
2. In the Server Name field, enter the server name where the TSCO web service is hosted.
3. In the Server User field, enter the TSCO application user name.
 Note
be changed.

9. Click Save.
 Important
If the TSCO server has an excessive amount of report data and takes time to respond to the REST client,
the data read time-out is increased to 150 seconds.
TrueSight Operations Management (TSOM) 10.7 to 11.3.06
 Note
Only English characters, numerals, and special characters are allowed.
2. In the Server Name field:
a. For versions prior to 11.0: Enter the server name where the TSOM web service is hosted (TrueSight
Presentation Server).
b. For version 11.0: Enter the server name in FQDN format only where the TSOM web service is hosted
(TrueSight Presentation Server).

 Note
If the TSOM Presentation Server is configured in HA mode, then the Server Name should refer to
the Load balancer (HAProxy) server name and port.
3. In the Server User field, enter the TSOM application user name.
 Note
be changed.
 Best practice
We recommend that you select HTTPS.
9. Click Save.
TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03
 Note
Only English characters, numerals, and special characters are allowed.
2. In the Server Name field, enter the server name where the TSPS web service is hosted.
3. In the Server User field, enter the TSPS application super admin user name.
 Note

7. Click Save.
BMC Digital Workplace Named User Report v18.02 and later (DWPNUR)
2. In the Server Name field, enter the server name where AR web service is hosted. The AR server should have
integration with DWP server, for successful license report generation.
3. In the Server User field, enter the AR server web service admin user having CTM:People Form access, with
administrator role.
 Note
Only English characters are allowed in the Report File Prefix field. After the Manage Deployment tab is
saved, the Report File Prefix value becomes read only and cannot be changed.

9. Click Save.
Editing deployments
To edit a deployment
1. Click the Manage Deployment tab.
2. In the Deployments list, select the BMC product, for example: Remedy AR System Server (ARS).
3. In the Edit Details section, modify the fields using the information in Adding deployments.
4. When you are finished editing the details, click Save.
a. A confirmation message appears indicating that the deployment was saved or not.
b. In the Deployments grid, the Product Name, Server Name, and Validation Status appears.
c. The Validation Status column displays the outcome of the deployment (Success or Failed).
 Note
The deployments are validated for each user session, so each time the application is launched, the system
validates the deployment details.

Deleting deployments
To delete a deployment
1. Click the Manage Deployment tab.
2. In the Deployments list, select the BMC product, for example: Remedy AR System Server (ARS).
3. Click Delete.
4. On the confirmation message, click Yes.
The deployment is removed from the Deployments list.
BMC Tools Integration
Control-M license usage reporting tool

Control-M users no longer need to download and install Control-M reporting tool separately. The tool is integrated with
BMC License Usage Collection Utility tool. Users can access it from the BMC Tools Integration tab.
You can launch the tool by clicking the Launch Control-M License Usage Reporting Tool link. Enter your Control-M
environment details and generate the reports.
To access the reports

Open the Reports folder of the Control-M License Usage Reporting Tool.
You can view the location of the report files.

Dashboard overview
The dashboard displays a quick view of BMC product license usage per product
Related topic
deployment in the form of bar charts. You can configure the dashboard to display
one chart at a time. The bar charts show current license usage, with the exception of
ARS and BSA, where usage within a specific time frame can be displayed.
Creating dashboard bar
charts
You can also save the chart as a .png file. (See the example in the screenshot.)
Bar chart example

In the following example for Remedy AR System Server (ARS), the stacked bar chart displays a license count of 4 licenses
used out of 15 licenses (currently defined limit).
Bar chart contents per product deployment
Product deployment Bar chart Bar chart product usage summary

type
BMC Client Management Layered • Displays Total License Count and Used License Count
(BCM)
BMC Database Automation Standard • Displays Total Server Count

(BDA)

Product deployment Bar chart Bar chart product usage summary

type
BMC Digital Workplace (MyIT) Standard • Displays number of user logged in for iOS client, Android client
and Web client
BMC Discovery (Discovery) up to Standard • Displays Total Server Count

version 11.1
BMC Network Automation Standard • Count for Total Managed Devices

(BNA) / TrueSight Network
Automation
BMC Release Package and Standard • Displays Total RPD Servers

Deployment (RPD)
BMC Release Process Standard • Displays Total RPM Servers

Management (RPM)
BMC Server Automation Stacked • Displays the active count for:

(BSA) / TrueSight Server • Max Managed Servers
Automation
• Servers Running Configuration
• Servers Running Compliance
• Servers Running Patching
• Servers Running Provisioning
• # of Servers Added
• # of Servers Decommissioned based on duration
Remedy AR System Server (ARS) Layered • Displays Currently Defined Limit and Used Count
TrueSight Capacity Optimization Standard • Displays an Audit count for the overall number of categories of
(TSCO) License Description
TrueSight Operations Standard • Displays the number of TSIM components connected

Management (TSOM)

Creating dashboard bar charts

You can create a bar chart to display on the dashboard for the following product
Related topics
deployments:
• TrueSight App Visibility Manager(TSAVM)

Dashboard overview
• BMC Client Management (BCM) Accessing and navigating the
• BMC Database Automation (BDA) license utility
• BMC Server Automation / TrueSight Server Automation (BSA)
To create a dashboard bar chart:

1. Select the Dashboard tab.
2. On a dashboard panel, click the Select Deployment link.
 Note
The Select Deployment link appears if a bar chart has not yet been
created. To replace a bar chart, you will need to delete it, and then
create a new one (See step 5b.)
3. On the Select the Deployment dialog, select a product deployment, then

click OK.
4. On the Duration Selection dialog, select a time frame (for example, Last
Quarter), then click OK.
 Note
The Duration is only applicable for ARS, BSA v8.2 to v8.6, and BSA
8.7 and higher.
While the bar chart is generating, a "please wait" message appears.
 Limitations

Where data exceeds the bar chart panel height, the top and bottom
of the chart may not initially appear. Use your mouse wheel to
zoom out to view the entire chart.
 Note
If an "Error generating dashboard" message appears, please refer to
the log. The path is provided on the message dialog, for example:
C:\Program Files (x86)\BMC
Software\LicenseUsageCollector\licenseusagecollector\user\Dashb
oardlogs\180921_133429_LUCU\vw-aus-rem-
dv1d_dsl_bmc_com_1.txt.
5. After creating a bar chart, the "Select Deployment" link is replaced by

"Refresh" and "Delete".
a. To refresh the data in a bar chart, click the Refresh link.
b. To delete a bar chart, click the Delete link.
The "Refresh" and "Delete" links are replaced by "Select
Deployment" so you can create a new bar chart.
To save a bar chart as a PNG file:

Right click the chart, then select Save as .png.
To access dashboard CSV reports:

Navigate to the following folder: C:\Program Files (x86)\BMC
Software\LicenseUsageCollector\licenseusagecollector\user\DashboardReports.

Reports overview
The BMC License Usage Collection Utility enables you to view and email license
usage reports for your BMC product deployments. Each license report is specific to
each BMC product; therefore, the file format and contents vary depending on the
product. You can also view a report as a PDF. In addition, you can create dashboard Related topics
bar charts to display license usage. (See Dashboard overview.)
Following is a report summary for each product deployment. Running reports
Server clustering information

in reports
Product Report contents summary
deployment Viewing reports
Emailing reports
TrueSight App • Displays information about the number of licenses
Visibility Manager used for TrueSight App Visibility Manager and
(TSAVM) TrueSight Synthetic Monitor.
• For TSAVM 11.0 and later versions, you can view the
following report files for each connected App Visibility
portal component.
• <DeploymentID>_AVM_AVMSeverName_Detai
ls_LUCU.csv
• <DeploymentID>_
TSAVMSummaryLicense_LUCU.csv
You can also view these reports in the PDF
format.
BMC Discovery • Lists the count of discovered servers in the data center.
(Discovery) • For Discovery 11.2 and later: Lists the average number
of discovered cloud resources and servers in the data
center
BMC Database • List of installed BDA agents managed by respective

Automation BDA managers
(BDA)
BMC Network • Lists the Total Device Count

Automation
(BNA)
 Note
TrueSight Network From version 8.9.03, the product name has been
Automation changed to TrueSight Network Automation.


deployment
BMC Server • Information about active agent count and various

Automation manager modules
(BSA) • For BSA version 8.7 and later, two report files are
created:
TrueSight Server
• <DeploymentID>_ BSAv87License_details.csv
Automation
• <DeploymentID>_BSAv87License_summary.csv
 Note
From version 8.9.03, the product name has been
changed to TrueSight Server Automation.
BMC Client • Name—Displays the name of the license

Management • The name can be either BMC Client
(BCM) Management for the basic license of the
software, or the names of individually licensed
modules, such as Remote Control
• Count—Indicates for how many agents the basic
license is valid
• Available—Indicates the number of remaining licenses
• Expiry date—Displays the expiration date if the license
is a limited license, such as an evaluation license
• Status—Displays whether the current License is valid,
invalid, expiring, expired, or exceeded


deployment
BMC Performance The following reports include summarized and detailed

Manager Portal information based on the managed server end points and
(BPM Portal) physical CPU slots count.
Report name Report contents summary
1_Server_Endpoint_Su • The summary of the

mmary_Report.html server endpoint for
each Performance
Manager
(The server endpoint is
a unique host per each
performance manager.)
2_Server_Endpoint_Det • The details of each host

ail_Report.html on which the particular
Performance Manager
is deployed
3_Server_Endpoint_Su • The summary of the

mmary_Report_With_C physical CPU count for
PU_Count_Detected.ht BMC Performance
ml Manager Express for
Microsoft Windows
• If these hosts
have other
Performance
Managers
deployed, those
details are
provided as well


deployment
4_Server_Endpoint_Det • The details of each host

ail_Rep_CPU_Count_De on which BMC
tected.html Performance Manager
Express for Microsoft
Windows is deployed
• If these hosts
have other
Performance
Managers
deployed, those
details are
provided as well


deployment
5_Overall_List_CPU_Can • This report displays the

_not_be_detected.html details of hosts
for which the physical
CPU cannot be
detected.
• Examples
include:
• BMC
Perform
ance
Manage
r
Express
for UNIX
and
Linux
• BMC
Perform
ance
Manage
r
Express
for Log
Manage
ment
Express
solution
s
• The report also
provides an
explanation of why the
CPU was not detected.
BMC Release • Count and List of RPD Servers

Package and
Deployment (RPD)


deployment
BMC Release Name—Unique name for the server

Process DNS/URL—The Domain Name System (DNS) or Uniform
Management Resource Locator (URL) for accessing the server
(RPM) IP address—The Internet Protocol (IP) address of the
server
OS Type—The operating system on which the server runs
Agent Type—The appropriate agent type, if the server uses
an agent NSH or SSH for connection (Agent Type
information gets pulled for RPM 4.8 and 5.0 versions)
BMC Digital • Lists all of the users of the specified tenant name and
Workplace (MyIT) the last login time per device for the month-wise
report
Remedy AR System • Maximum number of licenses that can be used

Server (ARS) concurrently (Currently Defined Limit)
• Peak number of in-use floating licenses or assigned
fixed licenses (Count)
TrueSight Capacity • Audit count for overall number of managed systems

Optimization and number of managed systems imported from
(TSCO) Capacity Agents and average number of server
endpoints
TrueSight • Lists the number of licenses used for each monitoring

Operations solution managed under Infrastructure Management
Management with a high count
(TSOM) • For TSOM 10.7 and later versions, for each connected
TSIM component, you can view current count details
and high count details in the following separate files
along with existing summarized report:
• <DeploymentID>_TSIM_TSIMSeverNam
e_HC_LUCU.csv
• <DeploymentID>_TSIM_TSIMSeverNam
e_CC_LUCU.csv
• <DeploymentID>_TSOMLicense_LUCU.c
sv
You can also view all these report in PDF format.

Running reports
You can run a report in CSV format (or as a PDF for certain products as described in
Related topics
step 6). Each time reports are run, they are stored in the user\Reports folder where
the License Utility is installed
($LicenseUsageCollectorHome\licenseusagecollector\user\Reports\timestamp
Viewing reports
folder).
Adding deployments
To run a report
1. Click the License Report tab.
2. From the Select Deployments list, select a deployment (for example, Remedy
AR System Server (ARS).
To select multiple deployments, use your CTRL and Shift keys while selecting
deployments.
 Tip
To add more deployments to the list, see Adding deployments.
3. From the Duration list, select a time (for example, Last Three Months).
a. To select a custom time, select Custom, then double-click to select the
start date from the "From" Calendar icon and the end date from the
"To" Calendar icon.
 Note
The Duration option is only applicable to: ARS, BSA 8.2 to
8.6, BSA 8.7 to 8.9.02, and TrueSight Server Automation
8.9.03 onwards (formerly BSA), as noted in the tooltip on the
Information icon.
4. Click Run License Report.

The License Report Run Notes box displays the real-time status messages
while the report is running. "Process Finished" will appear once completed.
5. To view the report, in the Details of Selected Reports Run (by
Deployment) section, in the License Report column, click the Click Here link.
 Important
To view the over usage report for AR System or BMC Client
Management, in the Details of Selected Reports Run (by
Deployment) section, in the Usage Analysis Report column, click
the Over-Capacity link.
6. On the Report File/Location Selection dialog, select one of the following

options, then click OK:
• License Report file
The selected report opens in a CSV format for each product.

The following text appears on the bottom of the file for all reports
generated from the license utility: "Report Generated Using BMC
License Utility".
• License Report Chart File
The JPEG format is supported for the following products usage:
• BMC Digital Workplace Named User Report v18.02 and later
(DWPNUR)
• BMC Network Automation (BNA) / TrueSight Network
Automation
• License Report PDF file
• The PDF format is supported for the following products:
• BMC Digital Workplace Named User Report v18.02 and
later (DWPNUR)
• License Report log file
The selected report opens in a TXT format for each product.
 Note
• Each time reports are run, they are stored in
the user\Reports folder where the License Utility is installed

($LicenseUsageCollectorHome\licenseusagecollector\user\Reports\
timestamp folder)
• Folders containing the reports are named with the date and
timestamp when the reports were run. For example, an ARS report
generated on July 1, 2015 at 4:23 PM EDT, would appear in the
following folder:
$LicenseUsageCollectorHome\licenseusagecollector\user\
Reports\150701_162314_LUCU
• For BSA 8.7 to 8.9.02 and TrueSight Server Automation 8.9.03
onwards (formerly BSA) the reports are stored in user\Reports\date
and time stamp\Blade
• For BSA 8.2 to 8.6, the reports are stored in user\Reports\date and
time stamp\BSA
Server clustering information in reports

The following provides details on the availability of server clustering information Related topics
in BMC License Usage Collection Utility reports:
Running reports
Product deployment Notes on license reports containing
Viewing reports
consolidated licensing information for server
clustering
Emailing reports
TrueSight App Visibility TrueSight App Visibility Manager(TSAVM)

Manager (TSAVM) server is similar to TSPS (TrueSight
Presentation Server) as it supports HA. In the
HA setup, the TSAVM server configured in
TSPS should be the load balancer of the
TSAVM server.
(Each tenant would have a TSAVM server,

however, the TSAVM server may not be
installed in HA mode).


clustering
BMC Discovery (Discovery) BMC Discovery supports the notion of a

clustered instance. The license report
generated for a clustered instance of BMC
Discovery returns data for all members of the
cluster. However, this BMC Discovery cluster
presents itself as a single logical instance of
the product, so the licence report generated
from a clustered instance of BMC Discovery
represents all the data in the cluster.
BMC Database Automation BMC Database Automation (BDA) supports

(BDA) server clustering. However, the license report
contains separate licensing information for
each of the servers in the cluster.
BMC Network Automation BMC Network Automation (BNA) / TrueSight

(BNA) Network Automation does not support server
clustering; the license report is for individual
TrueSight Network Automation servers.
 Note
From version 8.9.03, the product
name has been changed to TrueSight
Network Automation.


clustering
BMC Server Automation

(BSA) For BMC Server Automation (BSA) 8.7
and later
TrueSight Server Automation
BMC Server Automation (BSA) / TrueSight
Server Automation has a server group
concept; however, the licenses are extracted
per Device ID. BMC License Usage Collection
Utility generates separate licensing
information for each server.
 Note
From version 8.9.03, the product
name has been changed to TrueSight
Server Automation.
For versions earlier than BSA 8.7

BMC License Usage Collection Utility reports
do not contain consolidated licensing
information for a server group.
BMC Client Management Not applicable – BMC Client

(BCM) Management (BCM) does not support server
clustering.
BMC Performance Manager For BMC Performance Manager Portal (BPM

Portal (BPM Portal) Portal), there will be a single report
irrespective of the nodes in the cluster.
Release Package and Release Package and Deployment (RPD)

Deployment (RPD) supports server clustering; however, the
license is not based on it.


clustering
BMC Release Process BMC Release Process Management (RPM)

Management (RPM) supports server clustering; however, the
license is not based on it.
BMC Digital Workplace (MyIT) BMC Digital Workplace (MyIT) supports server
clustering; however, the license is not based
on it.
Remedy AR System Server Remedy AR System Server (ARS) supports

(ARS) server clustering. The servers in server groups
use a shared database; therefore, license
reports generated from this database contain
consolidated licensing information.
TrueSight Capacity Optimization TrueSight Capacity Optimization (TSCO) does

(TSCO) not support server clustering; the license
report is for individual servers.
TrueSight Operations For TrueSight Operations Management

Management (TSOM) (TSOM), the TSPS (TrueSight Presentation
Server) with the API for the BMC License
Usage Collection Utility does not support
native clustering. However, it does support HA
(High Availability configuration) using a Load
Balancer (HAProxy server) and a Primary and
Secondary TSPS server.
Therefore, in this configuration, the Server

Name needs to be the host name directing to
the LoadBalancer (HAProxy Server).
Emailing reports
After reports are generated, you can email them as attachments from the License Report tab.
You can append a prefix to the zip file name, so that:
• the license compliance team can search for license report zip files received in the BMC mailbox that include the zip
file prefixes provided by customers.

• customers can easily find the license report zip file in their sent mailbox .
Zip file names are formatted as follows: Prefix_TimestampDirName_LUCU.zip. The zip file contains the report in CSV and
the native file format per product, such as XML or HTML. The emailed reports are also stored in the
user\EmailReports folder where the License Utility is installed.
Prerequisites
An email client be configured on computers where the License Utility is installed in order to use this feature. For
supported email clients, see the Email client section in the System requirements topic.
To email reports:
1. On the License Report tab, click the checkbox next to the report you want to email.
You can select multiple reports at once.
2. To append a prefix to the file name, in the Email Attachment File Prefix text box, enter a prefix, for example:
YourOrganizationName.
The prefix can contain up to 15 characters except the following: \ / : * ? " < > | and .
3. Click Email Reports.
Your email client opens with a zip file of the report and log attachment, including the report name you specified
along with a date/time stamp in the following format:
• Report file: Prefix_TimestampDirName_LUCU.zip
• Log file: Prefix_Log_TimestampDirName_LUCU.zip
 Note
• If an email client does not exist on the computer or the email client is not configured, the following
message appears: "Error occurred while launching mail client. One or more unspecified errors occurred."
• When the license utility is running with "Run as administrator" and Outlook is opened by a non-
administrator user, the following error message appears after clicking Email Reports: "Error occurred
while launching mail client. One or more unspecified errors occurred."
• Workaround:
• Close Outlook.
• Click Email Reports.
• After scheduler execution of successful AR System deployment, Over-usage report is received as an
additional independent email for AR System user’s convenience.
• If any AR System license component is overused, then LUCU creates a new Email with subject line
“OVER USAGE REPORT : BMC License Usage Collection Utility report through scheduler”
with an attachment of over usage report file format :
<SERVER_NAME>_ARSLicense_overusage_LUCU.csv
• This report is accessible in the Details of Selected Reports Run (by Deployment) table, under
the Usage Analysis Report column on License Report Tab.
By default, the following appears in the email message:
• To: license_compliance_office@bmc.com
• You can change the email recipient in your email client.

The following can be changed in the email message, but not in the License Utility application:
• Subject: BMC License Utility Reports.

• Message text: Please send this email to BMC Software.
Viewing reports
To view reports
You can view reports from the License Report tab, or from the user\Reports folder where the License Utility is installed.
 Note
• Each time reports are run, they are stored in the user\Reports folder where the License Utility is installed
($LicenseUsageCollectorHome\licenseusagecollector\user\Reports\timestamp folder)
• Folders containing the reports are named with the date and timestamp when the reports were run. For
example, an ARS report generated on July 1, 2015 at 4:23 PM EDT, would appear in the following folder:
$LicenseUsageCollectorHome\licenseusagecollector\user\Reports\150701_162314_LUCU
• For BSA 8.7 to 8.9.02 and TrueSight Server Automation 8.9.03 onwards (formerly BSA) the reports are
stored in user\Reports\date and time stamp\Blade
• For BSA 8.2 to 8.6, the reports are stored in user\Reports\date and time stamp\BSA
• For the Digital Workplace Named User reports, records can be fetched in a batch of 2000 records
1. Click the License Report tab on the BMC License Usage Collector.
The Last 10 License Reports Run section provides the following summary of the last 10 reports that were run,
listed by execution date:
Last 10 License Reports Run section summary information
• Execution Dates
• The date and time the report was run
• Deployments in Run
• The number of deployments included in the run, for example, 1 out of 4
• Successful Run
• The number of reports that successfully ran for the specific date/time
• Failed Run
• The number of reports that failed for the specific date/time
• Execution Method
• Manual (manually run) or Auto (scheduled report)
2. In the Last 10 License Reports Run list, select a report.
The Details of Selected Report Run (By Deployment) section provides the following detailed information for each
deployment in the report:
Last 10 License Reports Run section details

• Product Name
• The product name(s) in the report
• Server
• Status
• Success or Failed
• License Report
• A link to the license report
3. In the Last 10 License Reports Run section, in the License Report column, click the Click Here link.
4. The Report File/Location Selection dialog box appears.
5. On the Report File/Location Selection dialog, select one of the following options, then click OK:
• License Report file
The selected report opens in a CSV format for each product.
The following text appears on the bottom of the file for all reports generated from the license utility:
"Report Generated Using BMC License Utility".
• License Report Chart File
The JPEG format is supported for the following products:
 Note
To view the report chart files, you must have the default JPEG viewer program and the program
must be set to open the chart files.
• License Report PDF file
 Important
From version 5.5.00, in the license reports in the PDF format, high number of records gets
generated without any issue.
• The PDF format is supported for the following products:


• License Report log file
The selected report opens in a TXT format for each product.
 Tip
If the files or report location are not found, verify that the default report folder path has not been
changed. For example:
$LicenseUsageCollectorHome\licenseusagecollector\user\Reports\150701_162314_LUCU)
Scheduling reports
You can schedule license usage reports to run at various intervals, such as daily, weekly, or monthly. The Schedule Reports
tab displays the deployments that have been set up on the Manage Deployment tab. The Last Run/Schedule Details of
Selected Deployment section displays the details for the scheduled reports.
If the scheduler service is running, it will gather license information for the deployments at their scheduled time. When a
new deployment is scheduled for the first time, the following columns in the Last Run/Schedule Details of Selected
Deployment section are blank: Last Run Time, Start Date Used and End Date Used. After the scheduled reports are
executed, this section is updated with the real-time status for all fields. The scheduler.xml file is also updated. (The file is
located in the following directory: C:\Program Files (x86)\BMC
Software\LicenseUsageCollector\licenseusagecollector\user\repository.)
See also Adding deployments
To schedule reports
 Note
• If the LUCService is stopped for any reason, the scheduler will automatically start the service and
continue the report generation.
• Scheduled reports cannot be edited, but you can delete them.
• If you want to schedule reports to run for more than a year, you will need to set up the Duration from the
Custom option on the License Report tab. See Running reports
1. Click the Schedule Reports tab.

2. From the Select Deployments list, select a deployment (for example, Remedy AR System Server (ARS).

3. In the Schedule Information column, click Configure Schedule.

4. In the Configure Schedule for Selected Deployment section, from the Schedule Frequency to Run Reports list,
select the recurrence (for example, Weekly).
5. In the Schedule Starts from Date and Time fields, enter the start date (for example, 03/09/2016).
To use the calendar, click the Calendar icon, then select the start date.
6. In the Time field, type or select the time from the up or down arrows.
7. Click Schedule Report.
The schedule is automatically saved. The details appear in the Last Run/Schedule Details of Selected
Deployment section.
8. To view the over usage report of AR System, in the Details of Selected Reports Run (by Deployment) section, in
the Usage Analysis Report column, click the Over-Capacity link.
To delete a scheduled report

1. From the Last Run/Schedule Details of Selected Deployment list, in the Action column for the deployment, click
Delete Schedule.
2. On the Delete Schedule message, click Yes to delete.
The scheduled report is removed from the list.
Enabling email notification of reports with SMTP

The License Utility can be configured to automatically send license usage reports via email. To use this feature, make sure
you have scheduled the license reports, then configure the connection with the SMTP server, as described in this topic.
 Note
BMC recommends using a professional SMTP service, since using a free email provider does not ensure the
correct delivery of your messages (especially if you want to send to a large number of recipients)..
Before you begin

Before you establish a connection with the SMTP server, you must know the following information:
• Name of the SMTP server that will send emails

• Port that the specified SMTP server will use
• Email addresses that the License Utility will use to send and receive emails
• Security level for the connection
To configure a connection with the SMTP server

1. Select the SMTP Configuration tab.
2. In the Host Name box, enter the SMTP server name.
3. In the Port box, enter the port number that the SMTP server will use.
Port 25 is the SMTP standard TCP port and is also the default port.

 Tip
If the default port does not work, locate the non-default SMTP port on the server that is running your
email application.
4. In the From box, enter the email address of the sender.

This will populate the From field in the License Utility email messages.
5. In the To box, enter the email address of the recipient.
a. To send emails to multiple recipients, separate the email addresses with a semicolon.
This email address will receive emails generated by the License Utility.
6. If your SMTP server is configured to send authentication credentials:
(Generally, non-default ports and free email providers require these authentication details.)
a. Select the Authentication Required check box.
b. Enter the User Name and Password in the boxes.
i. For Yahoo, Hotmail, and Gmail, enter your email address in the User Name box and your email
password in the Password box.
7. If SMTP TLS/SSL is required, enter the following in the Properties section:
a. In the Name box, enter the property name, for example: mail.smtp.ssl.enable.
b. In the Value box, enter the property value, for example: True.
c. To add more properties fields, click Add Property.
8. When you are finished, click Save.
To send a test email:

1. Click Send Test Email.
2. On the Email successfully sent message, click OK.

Support information
Related topics
This topic contains information about how to contact Customer Support, and the
support status for this and other releases.
 Please upgrade to the latest version (BMC License Usage Collection Utility
6.0.00.) (For more information, see Upgrading.)
Contacting Customer Support

To contact the BMC License Usage Collection Utility Support team, send an email to LicenseUtility@bmc.com. For any
help on Control-M License Usage Reporting tool OR queries on BMC product, send an email to
Customer_Support@bmc.com
The team is available until 11:00 AM CDT in the US.
 Note
Since the license utility is a free application, it does not follow the standard support policy as described on this
page: BMC Product Support Policy.
Support status
The following table shows the support status for the BMC License Usage Collection Utility, also available on the BMC A-Z
Supported Product List page:
Version Support Status Release Date Full Support End Date End of Support Date
6.0.00 Full support 15-March-2023
5.5.00 Full support 04-May-2022 04-May-2025 04-May-2027
5.0.00 Full support 10-Jul-2020 10-Jul-2023 10-Jul-2025
4.9.00 Limited support 10-Oct-2019 10-Oct-2022 10-Oct-2024

Version Support Status Release Date Full Support End Date End of Support Date
4.8.00 Limited support 10-Apr-2019 10-Apr-2022 10-Apr-2024
4.7.01 Limited support 21-Nov-2018 21-Nov-2021 21-Nov-2023
4.7.00 Limited support 10-Oct-2018 10-Oct-2021 10-Oct-2023
4.6.00 Limited support 18-Jun-2018 18-Jun-2021 18-Jun-2023
4.5.00 End of support 28-Feb-2018 28-Feb-2021 28-Feb-2023
4.0.01 End of support 06-Oct-2017 10-Oct-2018 27-Feb-2019
4.0.00 End of support 31-Jul-2017 10-Oct-2018 27-Feb-2019
3.6.00 End of support 10-Apr-2017 31-Jul-2017 18-Jun-2018
3.5.00 End of support 13-Jan-2016 10-Apr-2017 01-Apr-2018
3.0.00 End of support 24-Oct-2016 13-Jan-2016 01-Jan-2018
2.5.00 End of support 15-Jul-2016 24-Oct-2016 31-Jul-2017
2.0.00 End of support 11-Apr-2016 15-Jul-2016 10-Apr-2017
1.6.00 End of support 15-Dec-2015 11-Apr-2016 13-Jan-2016
1.5.00 End of support 11-Sep-2015 15-Dec-2015 24-Oct-2016
1.0.00 End of support 2-Jul-2015 11-Sep-2015 15-Jul-2016

Date: 2023-03-15 4:37

URL: https://docs.bmc.com/docs/x/MXu3Rg

A K
Key_concepts 78
Adding_deployments 63
Known_issues 23
Addm 57, 63, 83
Ars 39, 57, 63, 83 L
Language 39, 45
B
Latest_support 28
Bar 79, 81
License_usage_collection_utility 7
Bcm 39, 57, 63, 83
Linux 54
Bda 57, 63, 83
Localization 45
Bmc_restricted 23
Log 96
Bna 57, 63, 83
Bsa 57, 63, 83 N
Notifications 99
C
Chart 79, 81 O
Outlook 42, 94
Concept 78
Configuration 54 P
Password 54, 63
Contributor_unapproved 7, 27, 32, 49, 57, 68, 71, 75, 75, 89, 94,
96, 98, 101 Patch_vv_rr_ss_n 101
Controller_host 42 Pcm 63
Csv 63 Permissions 54
Customer_support 101 Power_shell 42, 54
Prerequisites 44
D
Dashboard 79, 81 R
Defects 23 Reference 23, 26, 101
Deleting_deployments 78 Reinstallation 45
Discovery 83 Release_notes 7, 23, 101
Reports 83
E
Editing_deployments 77 Rpd 63
Email 42, 94, 99 Rpm 63
English 39 S
Environment 54, 57 Security 54
Server_clustering 83
F
Failed 96 Service_pack_1 101
Flash 101 Service_pack_n 101
Fqdn 63 Size 42
Smtp 99
G
German 7, 39, 45 Software 42
Group 54, 63 Specifications 42
Srp_authentication 63
H
Hardware 42 Ssh 44, 54, 54
Home 7 Successful 96
Supported_bmc_products 28
I
Ini 63 System_requirements 42
Installation 42, 44, 45 T
Technical_bulletins 26
Translation 45 V
Truesight 63 Vc 63
Tsco 63 Version_vv_rr_00 101
Virtual_center 63
U
Uninstallation 47 W
Unix 44, 54, 54, 63 Websrv 63
Updates 26 Windows 42, 44, 44, 54, 54, 57, 63
Upgrading 49 Windows_server_2003 54
Usage_data 47 Wmi 44, 54, 54
User_account 54 Workarounds 23

© Copyright 2014-2023 BMC Software, Inc.

© Copyright 2003-2023 BladeLogic, Inc.
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with
the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC
trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other
trademarks or registered trademarks are the property of their respective owners.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Linux® is the registered trademark of Linus Torvalds.
UNIX® is the registered trademark of The Open Group in the US and other countries.
BMC Software Confidential. BladeLogic Confidential.
The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its
affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User
License agreement for the product and to the proprietary and restricted rights notices included in the product
documentation.
Click here for the provisions described in the BMC License Agreement and Order related to third party products or
technologies included in the BMC product.
BMC Software Inc.
2103 CityWest Blvd, Houston TX 77042-2828, USA

713 918 8800
Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

BMC License Usage Collection Utility 6.0: Portions of This Document Are BMC Confidential, Bladelogic Confidential

Uploaded by

Copyright:

Available Formats

You might also like

BMC License Usage Collection Utility 6.0: Portions of This Document Are BMC Confidential, Bladelogic Confidential

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BMC License Usage Collection Utility 6.0: Portions of This Document Are BMC Confidential, Bladelogic Confidential

Uploaded by

Copyright:

Available Formats

Portions of this document are BMC Confidential, BladeLogic Confidential.

BMC License Usage Collection Utility

Date: 2023-03-15 4:37

BMC License Usage Collection Utility 6.0 Page 2

Where to go from here................................................................................................................................................. 47

BMC License Usage Collection Utility 6.0 Page 3

Configuring TrueSight App Visibility Manager (TSAVM) 11.0 to 11.3.03 ...................................................................... 59

BMC License Usage Collection Utility 6.0 Page 4

BMC Digital Workplace (MyIT) 3.1 to 3.3 ..................................................................................................................... 73

BMC License Usage Collection Utility 6.0 Page 5

To send a test email:................................................................................................................................................... 100

BMC License Usage Collection Utility 6.0 Page 6

Release notes and notices

Downloading the installation file

BMC License Usage Collection Utility 6.0 Page 7

Date Title Summary

BMC License Usage Collection Utility 6.0 Page 8

Date Title Summary

BMC License Usage Collection Utility 6.0 Page 9

Date Title Summary

BMC product Version supported

TrueSight Network Automation(TSNA) 22.1

BMC Digital Workplace Active User Report 20.08

BMC License Usage Collection Utility 6.0 Page 10

Date Title Summary

BMC License Usage Collection Utility 6.0 Page 11

Date Title Summary

BMC product Added support for version #

TrueSight App Visibility Manager(TSAVM) 11.0 to 11.3.03

BMC License Usage Collection Utility 6.0 Page 12

Date Title Summary

BMC product Added support for version #

BMC Digital Workplace (MyIT) 19.05

BMC License Usage Collection Utility 6.0 Page 13

Date Title Summary

BMC product Added support for version #

BMC Client Management (BCM) 12.8

BMC Truesight Server Automation (BNA) 8.9.04

BMC Truesight Capacity Optimzation (TSCO) 11.5

BMC TrueSight Server Automation (BSA) 8.9.04

BMC Digital Workplace (MyIT) 18.11.00 and 19.02

BMC Truesight Operations Management 11.3.02

BMC License Usage Collection Utility 6.0 Page 14

Date Title Summary

• BMC Release Package and Deployment (RPD)

YouTube video playlist on Help tab

10 4.7.00 Support has been added for the following products/versions:

BMC License Usage Collection Utility 6.0 Page 15

Date Title Summary

BMC License Usage Collection Utility 6.0 Page 16

Date Title Summary

BMC License Usage Collection Utility 6.0 Page 17

Date Title Summary

• TrueSight Operations Management (TSOM)

BMC License Usage Collection Utility 6.0 Page 18

Date Title Summary

Existing product support enhancements for new releases

BMC License Usage Collection Utility 6.0 Page 19