StarQuest Technical Documents
StarLicense: Using starlic-remote-admin
Last Update: 20 Feburary 2020
Product: StarLicense
Version: 1.2 or later
Article ID: SQV00SL009
Abstract
StarLicense for Windows includes a command line application starlic-remote-admin that provides a subset of the status information and configuration functions provided by the StarLicense Manager GUI application.
For instance, the command starlic-remote-admin localhost active-checkout-count could be run periodically to monitor whether a license count is close to its maximum.
Solution
The starlic-remote-admin command is in the installation directory of StarLicense Server (default C:\Program Files\StarQuest\StarLicense).
Some of the useful options for monitoring are:
starlic-remote-admin localhost active-license-show
starlic-remote-admin localhost active-checkout-show
starlic-remote-admin localhost active-checkout-count
starlic-remote-admin localhost active-checkout-countq
(this displays the checkout count without a label)
The command should be run elevated.
To use the command from a remote machine, perform a custom installation of StarLicense Server and select only the Management feature. You may encounter authorization & firewall issues, but these are similar to running the StarLicense Manager GUI application remotely.
Invoking the command without any parameters displays the possible options:
C> starlic-remote-admin
usage: starlic-remote-admin MACHINE options...
options:
show commands:
show
service-show
key-show
primary-show
listener-show
active-license-show
active-checkout-show
active-checkout-count
active-checkout-countq
loglevel-show
journallevel-show
journalretain-show
config commands:
key-add <key> [grace period]
primary-add <hostname | IP>
key-remove <key>
primary-remove <hostname | IP>
listener-add <IP> <port>
listener-remove <IP> <port>
loglevel-set <hex>
journallevel-set <hex>
journalretain-set <# days>
control commands:
service-start
service-stop
license-revoke <token>
"?" after any option provides detailed help
DISCLAIMER
The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization. The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.