Identifying disconnected computers as running on public clouds (disconnected scenario)
Available from 9.2.23.
Computers that run on public clouds must additionally be identified as such. It ensures that proper subcapacity counting rules are applied by License Metric Tool. You can identify a computer as running on a public cloud from the License Metric Tool user interface or by using the disconnected scanner configuration file.
Before you begin
- Closed appliances that do not allow for using the disconnected scanner configuration file.
- When you did not identify an x86 computer as running on the public cloud from the very beginning as it applies the proper counting rules for the past. In case of other architectures, the computer is considered as running on a public cloud from the day when it was marked as such.
About this task
- License Metric Tool supports selected operating systems that run on selected public clouds. For more information, see: Licensing on public clouds.
- Computers that are not identified as public clouds can have the No VM Manager Data or No Scan Data status on the Capacity Scan Health widget on the Dashboard.
- Marking computers from the License Metric Tool user interface overrides values that you specify in the configuration file.
Identifying computers from the user interface
You can identify the computer as running on a public cloud from the Hardware Inventory report in License Metric Tool. The disconnected scanner must be in version 9.2.28 or later for this method to work.
Identifying computers by using the configuration file
You can identify the computer as running on a public cloud by setting the value of the PUBLIC_CLOUD_TYPE parameter in the setup_config.ini file.
- Log in to the computer that runs on the public cloud.
- Go to the directory in which the disconnected scanner is installed, and open the setup_config.ini file.
- Set the value of the PUBLIC_CLOUD_TYPE parameter. For the list of
available values, see: Configuration parameters of the disconnected scanner (disconnected scenario). Note: Ensure the name of the public cloud is enclosed in quotation marks.
- For the changes to take effect, run the following script.