Migrating from License Metric Tool 7.2.2 and 7.5
IBM License Metric Tool Version 9 Migrating from License Metric Tool 7.2.2 and 7.5 ii Contents Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 . . . . . . . . . . . . . 1 Overview and requirements . . . Migrating in parts . . . . . . Step 1: Preparing for migration . . Step 2: Mapping the agents . . . Step 3: Scanning your environment . Optional: Optimizing the software Step 4: Migrating your environment © Copyright IBM Corp. 2002, 2014 . . . . . . . . . . scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 3 3 5 6 7 Verifying the migration . . . . . . Verifying the export to csv files . . . Export reports . . . . . . . Verifying the simulation and migration Migration reports . . . . . . Statuses in migration reports . . Verifying the environment . . . . Verifying the items in V7.2.2 . . . Verifying the items in V7.5 . . . . . . . . . . . . reports . . . . . . . . . . . . . . . . 10 . 10 . 11 13 . 14 . 17 . 20 . 20 . 23 iii iv Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 You can migrate from License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2 or 7.5, and all subsequent fix packs and interim fixes, to License Metric Tool 9.2. Items that can be migrated are software bundlings, software exclusions, directories excluded from scanning, scan groups, and VM Managers. Overview and requirements The migration is intended to move your software inventory from License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2 or 7.5 to a completely new infrastructure that is based on IBM® Endpoint Manager and License Metric Tool 9.2. As opposed to a simple upgrade which changes the version of an application automatically, the migration requires that you install the new environment separately, mostly due to differences between the source and the target infrastructure. New infrastructure Although the environment to which you are going to migrate resembles the same concepts and follows similar patterns, it has some differences when compared to 7.x. It should be seen as a combination of License Metric Tool and the IBM Endpoint Manager platform that provides the infrastructure elements, such as clients. The platform is responsible for the flow of data between endpoints and License Metric Tool. It is also a terminal used for configuration. A number of tasks included in the following scenarios depend on IBM Endpoint Manager and are completed through the platform console. Scope of migration The migration does not transfer raw data or scan results but information that is specific to your environment. The data about software and hardware that is collected from your endpoints does not need to be migrated. While preparing the new environment, you install new clients that must reside side by side with the existing 7.x agents, at least until you complete the migration. It allows the new software and capacity (hardware) scans to scan the endpoints and discover inventory in the same way as it would be discovered in a new installation of 7.x. What would still be missing is all decisions regarding software classification that were made after installing the 7.x environment and that, in fact, made your software inventory the way it is now. Those decisions include software bundlings that you created and confirmed by assigning software instances to certain products, software exclusions, which represent software instances that are excluded from pricing calculations, and directories that are excluded from scanning. During the migration, those decisions are recognized and extracted from version 7.x along with the definitions of VM Managers, which are necessary to discover complete capacity of your computers. If your computers are divided among various scan groups, you can also migrate those scan groups and their scan schedule. After all this information is migrated, it is applied to the raw inventory that is discovered by the new scans. It allows for recreating your specific software inventory in the new environment. As a result, the same software inventory is managed with a new infrastructure. Requirements Version of the source application v License Metric Tool 7.2.2 and 7.5, and all subsequent fix packs and interim fixes. v Tivoli Asset Discovery for Distributed 7.2.2 and 7.5, and all subsequent fix packs and interim fixes. © Copyright IBM Corp. 2002, 2014 1 The applications might be furthered referred to as 7.x. Operating system License Metric Tool or Tivoli Asset Discovery for Distributed 7.x can be migrated from all operating systems that are supported for this application. User permissions The user whose authentication token is used to access the License Metric Tool 9.2 server must have the Manage IBM Software Classification and Manage VM Managers and Servers permissions. Software catalog To avoid problems that might occur due to differences in discovered software, ensure that the version of the software catalog used in versions 7.5 and 9.2 is the same. The software catalog for License Metric Tool and Tivoli Asset Discovery for Distributed 7.5, and for License Metric Tool 9.2 is released in the same time, so you can update the catalogs to the latest versions. For more information about downloading the latest software catalog in both applications, see Importing software catalogs to License Metric Tool 7.5, Importing software catalogs to Tivoli Asset Discovery for Distributed 7.5, and Working with software catalogs in Managing the software inventory. Migrating in parts You can break the migration into smaller parts either by installing the IBM Endpoint Manager clients only on a group of endpoints or limiting the number of endpoints that are subscribed to the fixlet site. Migration of each endpoint produces a significant amount of information that must be verified to be sure that the migration succeeded. If you want to migrate a large number of endpoints, divide them into groups, especially if you want to migrate a production environment. Such an approach makes the verification easier and less time-consuming, and does not block your entire environment until the whole migration is completed. The size of a group depends on the number of software instances that are installed on endpoints. To break the migration into parts, choose one of the following approaches: v Installing the IBM Endpoint Manager clients on a group of endpoints While preparing the new environment, as described in Step 1: Preparing for migration, install the IBM Endpoint Manager clients only on a group of endpoints. Items can be migrated only from endpoints that have both the 7.x agent and the IBM Endpoint Manager client installed. The remaining items are listed as skipped and not migrated to License Metric Tool 9.2. After you migrate the first group of endpoints, install the clients on the next group and repeat the migration. v Subscribing a group of endpoints to the fixlet site While mapping the agents, as described in Step 2: Mapping the agents, activate the required analysis only for a group of endpoints. Since the analysis is activated globally, which means that it gathers information from all endpoints in the fixlet site, subscribe the endpoints to the fixlet site in groups. When you do so, the analysis gathers information only from a group of endpoints that is currently subscribed to the fixlet site. Items can be migrated only from endpoints whose IDs and versions were retrieved by the analysis. The remaining items are listed as skipped and not migrated to License Metric Tool 9.2. After you migrate the first group of endpoints, subscribe the next group to the fixlet site and repeat the migration. For more information about limiting the number of subscribed endpoints, see Restricting computers. Important: In either approach, all items from the source application are included in the csv files that are created during migration. This is to be expected, because the files list all items that are eligible for migration, not only those that were actually migrated. Items that were not migrated are listed as skipped with an explanation saying that the IBM Endpoint Manager client is not installed. Filter the files by host names to limit the view only to items from a particular group of endpoints. Despite being listed in the csv files, the items are not saved in the target environment. 2 Step 1: Preparing for migration Before you start the migration, prepare your target environment by installing IBM Endpoint Manager and License Metric Tool 9.2. Procedure v Install License Metric Tool and all required components on one server using the combined installer: 1. Complete the All-in-One installation. 2. Install an IBM Endpoint Manager client on each endpoint that you want to include in your migrated environment. The clients must be installed side by side with your License Metric Tool agents. v Install License Metric Tool and all required components separately: 1. Install IBM Endpoint Manager. 2. Install an IBM Endpoint Manager client on each endpoint that you want to include in your migrated environment. The clients must be installed side by side with your License Metric Tool agents. 3. Install the IBM Endpoint Manager console. 4. Enable the IBM License Reporting (ILMT) v9 fixlet site. 5. Install License Metric Tool. 6. When the installation is complete, click Import Now to start the initial import. What to do next Step 2: Map the agents. Step 2: Mapping the agents Map the License Metric Tool or Tivoli Asset Discovery for Distributed 7.x agents to recognize their IDs and versions, which is necessary to migrate your specific software inventory. About this task Decisions regarding software classification link software instances to the agents that they are installed on. License Metric Tool and Tivoli Asset Discovery for Distributed 7.x save the ID and version of an agent to be able to recognize software instances that are the targets of classification. Before you migrate, you must activate an analysis that recognizes those IDs and versions, which is key for recreating your software inventory in the migrated environment. Activating the analysis is enough to complete the migration, however if you plan to remove the 7.x agents, you must also run a task that maps the agents and copies their IDs and versions to the new IBM Endpoint Manager clients. You can map the agents right after activating the analysis, or at any time before you remove them. Procedure 1. Log in to the IBM Endpoint Manager console. 2. In the navigation tree, click Sites > External Sites > IBM License Reporting (ILMT) v9. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 3 3. Click Analyses and then complete the following steps: a. Select the LMT/TAD4D 7.x Agent Mapping analysis, right-click on it, and then click Activate. b. To check the progress of retrieving the IDs and versions, click the Results tab. 4. Map the License Metric Tool or Tivoli Asset Discovery for Distributed 7.x agents to copy their IDs and versions to the IBM Endpoint Manager clients. Note: This step is optional for the migration, however it must be completed before you remove the 7.x agents. After removing the agents, their IDs and versions cannot be retrieved by the analysis, which is why they must be copied to the new clients. a. Click Fixlets and Tasks. b. Select the Map LMT/TAD4D 7.x Agents task, and then click Take Action. From the list of applicable endpoints, select all that have both agents installed, and then click OK. The mapping is started. c. You can check the progress of mapping in the LMT/TAD4D 7.x Agent Mapping analysis that you activated before. The progress can be viewed under the Results tab. 4 The mapping is complete when the Mapped LMT/TAD4D 7.x Agent ID and Mapped LMT/TAD4D 7.x Agent Version columns are filled in with IDs and versions. What to do next Step 3: Scan your environment. Step 3: Scanning your environment Scan your environment to discover your hardware and software inventory through the new infrastructure. Before you begin v After you complete this step, software scans from both applications might run simultaneously, which can impact your processor usage. To avoid this problem, see Optimizing the software scan. Procedure 1. Log in to the IBM Endpoint Manager console. 2. In the navigation tree, click Sites > External Sites > IBM License Reporting (ILMT) v9. 3. Go to Analyses, and select all analyses. Right-click on them to view the list of options, and then click Activate. Important: If you excluded any directories from scanning in version 7.x, ensure that the Excluded Directories analysis is activated. This analysis allows you to migrate those directories. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 5 4. Go to Fixlets and Tasks, and run the License Metric Tool software and capacity scans on all your endpoints to discover your hardware and software inventory through the new infrastructure. Tip: To run a particular fixlet, select it, and then click Take Action. From the list of applicable endpoints, you can select all endpoints at once instead of targeting each of them separately. a. Run Install Scanner. b. Run Initiate Software Scan. This fixlet becomes accessible only when the scanner is installed. c. Run Upload Software Scan Results. This fixlet becomes accessible only when the software scan finishes collecting the results. d. Run Run Capacity Scan and Upload Results. 5. Go to Fixlets and Tasks, and run the following fixlets against your IBM Endpoint Manager server to install the VM Manager Tool: Note: If the following fixlets cannot be run against your IBM Endpoint Manager server, it means that they were initiated automatically during the installation and you can omit this step. a. Run Install VM Manager Tool and wait until the action completes. b. Run Upload VM Manager Tool Scan Results. 6. To initiate the VM Manager Tool, log in to License Metric Tool, and click Management > VM Managers. It is enough to access the panel to initiate the tool. 7. To run a data import, which is required to process the scan results, click Management > Data Imports, and then click Import Now. Results Data about your software and hardware inventory was collected and uploaded to License Metric Tool. The capacity data from your virtual machines is not complete, which is to be expected. The lacking results will be uploaded in the next step after you migrate the VM Managers. What to do next Step 4: Migrate your environment. Optional: Optimizing the software scan You can change the schedule of software scan either from the IBM Endpoint Manager console, or from the License Metric Tool user interface. About this task Until you complete the migration, your License Metric Tool or Tivoli Asset Discovery for Distributed 7.x agents and IBM Endpoint Manager clients must be installed side by side on your endpoints. It might happen that the scans from both applications are running in the same time, which might impact your processor usage. You can change the scan schedule so that the scans do not run simultaneously. Note: The schedule of the capacity scan cannot be changed, however it has minimal impact on your processor usage. Procedure v To change the software scan schedule from the IBM Endpoint Manager console, complete the following steps: 1. Log in to the IBM Endpoint Manager console. 2. In the navigation tree, click Sites > External Sites > IBM License Reporting (ILMT) v9 > Fixlets and Tasks. 6 3. Select Initiate Software Scan and click Take Action. 4. Click the Execution tab. 5. Select the Run only on check box, and choose a day that does not conflict with the 7.x scans. Click OK. v To change the schedule from the License Metric Tool user interface, complete the following steps: 1. Log in to License Metric Tool. 2. Click Management > Scan Configurations. 3. Select the data source that you want to change scan settings for. 4. Select a new schedule from the Frequency list and specify the start date. Click Save. Step 4: Migrating your environment Migration is performed through the migration tool that can either export your information to csv files, migrate it directly to version 9.2, or run a simulation that allows you to see the expected result without saving the information in the target. Before you begin v Some of the items, such as software instances installed on shared disks, cannot be migrated. To understand which items are omitted during migration, see Migrated items. v The migration tool must be run on the same endpoint as the License Metric Tool 9.2 server. v During migration, the following must be running: License Metric Tool or Tivoli Asset Discovery for Distributed 7.x database, IBM Endpoint Manager server, and License Metric Tool 9.2 server. v You can run the migration tool repeatedly if you want to break the migration into parts. The items that were already migrated are then skipped. v If you want to migrate to multiple IBM Endpoint Manager servers, treat each of them as a separate migration. First specify the access details to one of the servers and start the migration. When it is completed, change the access details to another server and repeat the migration. v If you encounter any problems during migration, see Migration problems in Troubleshooting to learn how to solve them. About this task Migration includes your custom software bundlings, software instances excluded from pricing calculations, directories excluded from scanning, and definitions of VM Managers. You can also expand it with the migration of scan groups and the scan schedule. Data about your software and hardware inventory is not migrated because it was already gathered by the License Metric Tool 9.2 scans. The migration completes this data with information about your choices regarding software classification to recreate your specific software inventory. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 7 Procedure 1. From the License Metric Tool 9.2 installation directory, go to migration/product. 2. Edit the migration.properties file and specify all parameters that are listed in it. The migration.properties file is a configuration file in which you specify details of the License Metric Tool or Tivoli Asset Discovery for Distributed 7.x, IBM Endpoint Manager, and License Metric Tool 9.2 servers. It also provides customizable settings that can be used to migrate scan groups and the scan schedule. 3. Before you start the migration, export the information to csv files to know which items are eligible for migration. Items that are not included in the export are not migrated. a. To export the information to csv files, run the following command: Linux Windows ./migration.sh -export [-dir directory] ./migration.bat -export [-dir directory] [-dir directory] Specifies a directory to save your csv files to. If you omit this parameter, the csv files are created in the main directory of the migration tool. b. Check the summary of export that is displayed after the export is completed. c. Verify the exported information in seven csv files that were created. The files list all items that are eligible for migration. You can later compare those files with reports that are created after the migration to verify if all of the eligible items were migrated. To properly recognize the created files and information included in them, see Verifying the export to csv files. 4. Simulate the migration to check which items are migrated without saving them in the target environment. Items that are not included in the simulation are not migrated. a. To simulate the migration, run the following command: Linux Windows ./migration.sh -migrate [-dir directory] -simulate ./migration.bat -migrate [-dir directory] -simulate [-dir directory] Specifies a directory to save your csv files to. If you omit this parameter, the csv files are created in the main directory of the migration tool. b. Check the summary of simulation that is displayed after the simulation is completed. 8 Tip: Items are first exported from the source and then imported to the target application. If the number of exported and imported items is the same, the items were successfully migrated. Some items might be skipped if, for example, an Endpoint Manager client is not installed on an endpoint. The reason for skipping such items is provided in the csv reports. c. Verify the outcome of simulation in five csv reports that were created. The verification is the same as in the case of complete migration, however only the csv reports can be checked, because the information is not saved in the target environment. To properly recognize the created reports and information included in them, see Verifying the simulation and migration reports. 5. Migrate the information directly from the source to the target application. a. To start the migration, run the following command: Linux Windows ./migration.sh -migrate [-dir directory] ./migration.bat -migrate [-dir directory] [-dir directory] Specifies a directory to save your csv files to. If you omit this parameter, the csv files are created in the main directory of the migration tool. b. Check the summary of migration that is displayed after the migration is completed. The summary is the same as the summary of simulation. c. Verify the outcome of migration in five csv reports that were created. Next, compare the source and the target environment to ensure that all items were successfully migrated. For more information, see Verifying the simulation and migration reports. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 9 Results Your custom software bundlings, software instances excluded from pricing calculations, and directories excluded from scanning were migrated. Scan groups and scan schedules were also migrated. Definitions of VM Managers were sent to the VM Manager Tool that will use them to connect to those computers and gather data about their capacity, which is required to properly calculate the PVU consumption. Depending on the number of your VM Managers, it might take time to connect to all of them and gather the capacity data. What to do next After the capacity data is gathered by the VM Manager Tool, it is uploaded to your IBM Endpoint Manager server every 12 hours, but you can trigger the upload by running the Upload VM Manager Tool Scan Results fixlet from the IBM License Reporting (ILMT) v9 fixlet site. The data is then transferred from IBM Endpoint Manager to License Metric Tool with each data import. To verify if all capacity data was collected and uploaded to the server, run a data import in License Metric Tool, and then check the IBM Capacity Data Completeness widget on the dashboard. If all your computers are in the OK status, your data is accurate and complete. Otherwise, repeat the upload and data import until all your computers achieve this status. Next step: Verify the migration Verifying the migration Start the verification by checking the items that were exported to csv files to recognize those that are eligible for migration. When the migration is complete, check the reports that were created, and then compare your source and target environments to verify if the migration succeeded. Verifying the export to csv files When you export your information from License Metric Tool or Tivoli Asset Discovery for Distributed 7.x, it is saved in seven csv files, each devoted to a particular type of migrated items. Open the csv files and verify if the migrated items correspond with those that are present in your existing 7.x environment. Before you begin Some of the items, such as software instances installed on shared disks, cannot be migrated. To understand which items are omitted during migration, see Migrated items. Procedure 1. Open the agentsmap.csv file. This file lists the agent mappings that were created after activating the LMT/TAD4D 7.x Agent Mapping analysis before the migration. The most important information included in this file are the IDs of your 7.x agents and IBM Endpoint Manager clients. If any of the agents is not included in the list or is missing one of the IDs, the software bundlings and exclusions from this agent are not exported. 2. Open the vmmanagers.csv file. This file contains the list of exported VM Managers. Verify if the number of VM Managers and their access details correspond with VM Managers that are defined in the source environment. 3. Open the bundles.csv file. This file contains the list of exported software bundlings. Verify if the number of products and their names correspond with software bundlings that are defined in the source environment. 4. Open the excludedsoftware.csv file. 10 This file contains the list of exported software exclusions. Verify if the number of products and their names correspond with software exclusions that are defined in the source environment. 5. Optional: Open the excludedirectories.csv file. The file contains the list of all directories excluded from scanning that were exported from the source environment. To verify if all directories were exported, use the listexclusions command in version 7.x. 6. Optional: Open the agents.csv file. The file contains the list of all your 7.x agents. You can compare them with agents in the agentsmap.csv file to recognize how many of them were already mapped and included in the migration. 7. Optional: Open the scangroups.csv file. The file contains the list of scan groups and scan schedules that are defined in 7.x. Verify if the number of scan groups and their schedules correspond with the ones that are defined in the source environment. Export reports When you export information from License Metric Tool or Tivoli Asset Discovery for Distributed 7.x, it is saved in seven csv files, each devoted to a particular type of migrated items. Agent mappings Agent mappings are exported to the agentsmap.csv file. Table 1. Description of columns that are in the agentsmap.csv file. Column Description IEM Client ID ID of an IBM Endpoint Manager client. LMT/TAD4D 7.x Agent ID ID of a 7.x agent. LMT/TAD4D 7.x Agent Version Version of a 7.x agent. Host Name Host name of the endpoint where the agent is installed. Operating System Operating system of the endpoint where the agent is installed. VM Managers Definitions of VM Managers are exported to the vmmanagers.csv file. Table 2. Description of columns that are in the vmmanagers.csv file. Column Description IP Address IP address of a VM Manager. User Name Credentials used to log in to a VM Manager. The password is encrypted. Password URL Web address of a VM Manager. Type Type of a VM Manager. It can assume the following values: 1 - Microsoft Hyper-V 2 - VMWare ESX, ESXi, or vCenter 3 - KVM RHEV-M Shared Credentials Specifies whether a VM Manager shares credentials with hosts in the same cluster. This function is available only for Microsoft Hyper-V. Software bundlings Software bundlings are exported to the bundles.csv file. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 11 Table 3. Description of columns that are in the bundles.csv file. Column Description LMT/TAD4D 7.x Agent ID ID of a License Metric Tool or Tivoli Asset Discovery for Distributed 7.x agent. Component GUID GUID of the exported component. Product GUID GUID of a product that the exported component is assigned to. Component Path Installation path of the exported component. In License Metric Tool 7.x, the path is empty. Component Name Name of the exported component. Component Version Version of the exported component. Product Name Name of a product that the exported component is assigned to. Release Version Version of a product release that the exported component is assigned to. LMT/TAD4D 7.x Agent IP Address IP address of a 7.x agent. Host Name Host name of a 7.x agent. Operating System Operating system of the endpoint where the agent is installed. Report Group ID ID of a report group. Items that are not in the default report group are not migrated. Software exclusions Software exclusions are exported to the excludedsoftware.csv file. Table 4. Description of columns that are in the excludedsoftware.csv file. Column Description LMT/TAD4D 7.x Agent ID ID of a 7.x agent. Product GUID GUID of a product that the excluded release is assigned to. Reason for Exclusion Reason that you specified while excluding a release. Comment Comment that you attached to the excluded release. Product Name Name of a product that the excluded release is assigned to. Release Version Version of the excluded release. Report Group ID ID of a report group. Items that are not in the default report group are not migrated. Host Name Host name of a 7.x agent. IP Address IP address of a 7.x agent. Agents The list of all 7.x agents is exported to the agents.csv file. You can compare agents listed in this file with those that are in the agentsmap.csv file to recognize how many of them were already mapped and used in the migration. Table 5. Description of columns that are in the agents.csv file. Column Description ID Agent ID. Version Agent version. Host Name Host name of the endpoint where the agent is installed. IP Address IP address of the endpoint where the agent is installed. Operating System Operating system of the endpoint where the agent is installed. 12 Table 5. Description of columns that are in the agents.csv file. (continued) Column Scan Group ID Description ID of the scan group to which the agent is assigned. Directories excluded from scanning The list of all directories that are excluded from scanning in 7.x is exported to the excludedirectories.csv file. Table 6. Description of columns that are in the excludedirectories.csv file. Column Description Excluded Directory Directories that are excluded from scanning in 7.x. Platform Operating system with the excluded directory. A directory can be excluded either on a certain type of operating system, for example on all Windows systems in your environment, or on a particular agent. If this column contains a value, then the following columns are empty. LMT/TAD4D 7.x Agent ID ID of an agent with the excluded directory. IP Address IP address of an agent with the excluded directory. Host Name Host name of an agent with the excluded directory. Operating System Operating system of an agent with the excluded directory. A directory can be excluded either on a certain type of operating system, for example on all Windows systems in your environment, or on a particular agent. If this column contains a value, then the preceding column is empty. Scan groups and scan schedules The list of scan groups and scan schedules that are defined in 7.x are exported to the scangroups.csv file. Table 7. Description of columns that are in the scangroups.csv file. Column Description Scan Group ID ID of the scan group from 7.x. Scan Group Name Name of the scan group from 7.x. Scan Start Date The date and time when the specified scan schedule starts. Frequency Frequency with which the scan runs. Calendar Unit The type of calendar unit to which the frequency applies. Possible values are days, weeks, and months. Number of Agents Number of 7.x agents that belong to the scan group. Verifying the simulation and migration reports When you migrate your information directly from License Metric Tool or Tivoli Asset Discovery for Distributed 7.x to License Metric Tool 9.2, you can view the summary of migration in five csv reports. The reports describe the details of migrating your software bundlings, software exclusions, directories excluded from scanning, VM Managers as well as scan groups and scan schedules. If the information in those reports is accurate and complete, you can log in to the target application to verify if your software inventory corresponds with the one in your existing 7.x environment. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 13 Before you begin Some of the items, such as software instances installed on shared disks, cannot be migrated. To understand which items are omitted during migration, see Migrated items. Procedure 1. Open the vmmanagers_report.csv file. This file shows the summary of migrating your VM Managers. Verify if the number of VM Managers and their access details correspond with VM Managers that are defined in version 7.x . For more information about statuses displayed in this report, see Statuses. 2. Open the software_report.csv file. This file shows the summary of migrating your software bundlings and exclusions. Verify if the number and details of the migrated items correspond with the software that is available in version 7.x. For more information about statuses displayed in this report, see Statuses. 3. Open the excluded_directories_report.csv file. This file shows the summary of migrating directories that are excluded from scanning. Verify if the migrated directories correspond with the ones that are available in version 7.x. For more information about statuses displayed in this report, see Statuses. 4. Optional: Open the scan_groups_report.csv file. This file shows the summary of migrating scan groups and scan schedules. Verify if the number of scan groups and their schedules correspond with the ones that are defined in 7.x. For more information about statuses displayed in this report, see Statuses. 5. Optional: Open the matched_agents_report.csv This file shows information about whether migrated 7.x agents were assigned to Endpoint Manager scan groups. Results If some items were not migrated, check the explanation in the csv reports and correct the problems. The migration can be repeated as many times as you want. In such case, the items that were already migrated will be skipped. What to do next Checking the migration reports is sufficient to verify that the migration succeeded. However, to ensure that the new environment resembles the one from which you are migrating, you can log in to both applications and verify the migrated items in the user interface. For more information, see Verifying the items in V7.5 or Verifying the items in V7.2.2. Migration reports When you migrate information directly from License Metric Tool or Tivoli Asset Discovery for Distributed 7.x to License Metric Tool 9.2, the summary of migration is saved in five csv reports. The reports are created in the main directory of the migration tool. Reports Migrated VM Managers The summary of migrating the VM Managers is saved to the vmmanagers_report.csv file. Table 8. Description of columns that are in the vmmanagers_report.csv file. Column Item 14 Description An item that was migrated. In this report, it always assumes the VMMANAGER value. Table 8. Description of columns that are in the vmmanagers_report.csv file. (continued) Column Description Status Status of a migrated item. It can assume the following values: succeeded, skipped, or failed. Description Explanation of the status. For more information, see Statuses. URL Web address of a VM Manager. User Name User name that is used to log in to a VM Manager. Type Type of a VM Manager. It can assume the following values: 1 - Microsoft Hyper-V 2 - VMWare ESX, ESXi, or vCenter 3 - KVM RHEV-M Migrated software bundlings and exclusions The summary of migrating the software bundlings and exclusions is saved to the software_report.csv file. Table 9. Description of columns that are in the software_report.csv file. Column Item Description An item that was migrated. In this report, it can assume the following values: BUNDLING - software bundling EXCLUSION - software exclusion Status Status of a migrated item. It can assume the following values: succeeded, skipped, or failed. Description Explanation of the status. For more information, see Statuses. IEM Client ID ID of an IBM Endpoint Manager client. LMT/TAD4D 7.x Agent ID ID of a 7.x agent. Product Name Name of the product that the component is assigned to. Release Version Version of the product release that the component is assigned to. LMT/SUA Release GUID GUID of the product release that the component is assigned to. LMT/SUA Component Name Name of the component in the target environment. LMT/SUA Component Version Version of the component in the target environment. LMT/SUA Component GUID GUID of the component in the target environment. LMT/TAD4D 7.x Component Path Installation path of the migrated component that was discovered by the software scan in 7.x. LMT/SUA Component Path Installation path of the migrated component that was discovered by the software scan in License Metric Tool 9.2. Host Name Host name of the endpoint where the agent is installed. IP Address IP address of the endpoint where the agent is installed. Operating System Operating system of the endpoint where the agent is installed. Directories excluded from scanning The summary of migrating directories that are excluded from scanning is saved to the excluded_directories_report.csv file. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 15 Table 10. Description of columns that are in the excluded_directories_report.csv file. Column Description Status Status of a migrated item. It can assume the following values: updated, skipped, or failed. Description Explanation of the status. For more information, see Statuses. Platform Operating system with the excluded directory. A directory can be excluded either on a certain type of operating system, for example on all Windows systems in your environment, or on a particular agent. If this column contains a value, then the columns with agent information are empty. IEM Client ID IDs of an IBM Endpoint Manager client and a 7.x agent. LMT/TAD4D 7.x Agent ID A directory can be excluded either on a certain type of operating system, for example on all Windows systems in your environment, or on a particular agent. If these columns contain a value, then the Platform column is empty. LMT/SUA Directories Directories that are excluded from scanning in License Metric Tool 9.2. LMT/TAD4D Directories Directories that are excluded from scanning in 7.x. Migrated Directories Directories that were migrated. If the same directories are specified both in version 7.x and 9.2, they are not migrated. Operating System Operating system of an agent with the excluded directory. Host Name Host name of an agent with the excluded directory. IP Address IP address of an agent with the excluded directory. Scan groups and scan schedules The summary of migrating scan groups and scan schedules is saved to the scan_groups_report.csv file. Table 11. Description of columns that are in the scan_groups_report.csv file. Column Description Status Status of a migrated scan group and scan schedule. It can assume the following values: succeeded, updated, skipped, or failed. Description Explanation of the status. For more information, see Statuses. LMT/TAD4D 7.x Scan Group Name Name of the scan group in 7.x. IEM Computer Group Name Name of the migrated computer group in Endpoint Manager. LMT/TAD4D 7.x Scan Schedule Scan schedule that is specified in 7.x. IEM Scan Schedule Scan schedule that is specified in Endpoint Manager after migration. Because scheduling options that are available in 7.x and Endpoint Manager differ, only scan schedules that can be re-created are migrated. If the schedule cannot be re-created, this field is empty. Scan Start Date The date and time when the specified scan schedule starts. Schedule Created in IEM Information whether the scan schedule was re-created in Endpoint Manager. Information about whether migrated 7.x agents were assigned to Endpoint Manager scan groups is saved to the matched_agents_report.csv file. 16 Table 12. Description of columns that are in the matched_agents_report.csv file. Column Description IEM Client ID ID of the Endpoint Manager client. LMT/TAD4D 7.x Agent ID ID of the 7.x agent. LMT/TAD4D 7.x Agent Version Version of the 7.x agent. Host Name Host name of the endpoint where the agent is installed. Operating System Operating system of the endpoint where the agent is installed. Scan Group Name Name of the 7.x scan group to which the agent is assigned. Assigned to IEM Computer Group Information whether the endpoint is assigned to an Endpoint Manager computer group. Statuses in migration reports Each migrated item is described with a status and an explanation that summarizes the result of the migration. VM Managers Succeeded Items were successfully migrated and no additional action is required. Skipped Items were not migrated. The only reason why they can be skipped is because they are already defined in License Metric Tool 9.2. Such a status might occur if you repeat the migration, in which case the VM Managers were migrated during the first run. Failed This status is not related to problems with items that you want to migrate, but rather to errors that are returned from the License Metric Tool 9.2 or IBM Endpoint Manager server. Such a status might be the result of connection problems. Each of the server errors is saved in the tema.log file that is in the following directory on your License Metric Tool server: Linux /opt/ibm/LMT/wlp/usr/servers/server1/logs/ Excluded directories Updated Directories were successfully updated on the IBM Endpoint Manager server, which then delivers them to your endpoints. Skipped Items were not migrated. They were skipped for one of the following reasons: The IEM client is not installed. You can migrate the items only from computers that have both the 7.x agent and the IBM Endpoint Manager client installed. Action: Install an IBM Endpoint Manager client and subscribe it to the IBM License Reporting (ILMT) v9 fixlet site so that its ID and version can be retrieved. Directories are already excluded Directories are already excluded in License Metric Tool 9.2 and do not need to be migrated. Action: No action required. The item exists in the target environment. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 17 Unsupported platform Directories cannot be migrated because they are excluded on i5 systems, which are not supported in License Metric Tool 9.2. Failed The items were not migrated. They failed for one of the following reasons: The Add Excluded Directories task cannot be found in the LMT/SUA fixlet site. The Add Excluded Directories task must be present in the IBM License Reporting (ILMT) v9 fixlet site. Your fixlet site might not be updated to the latest version. Action: Update the fixlet site to download the latest content. For more information, see Updating the fixlet site in Configuring. The Add Excluded Directories task in the LMT/SUA fixlet site cannot be initiated. The task cannot be initiated because the connection to the IBM Endpoint Manager server failed. Action: Check the migration.log file that describes details about this problem. Software bundlings and exclusions Succeeded Items were successfully migrated and no additional action is required. Skipped Items were not migrated. They were skipped for one of the following reasons: The IEM client is not installed. You can migrate the items only from computers that have both the 7.x agent and the IBM Endpoint Manager client installed. Action: Install an IBM Endpoint Manager client and subscribe it to the IBM License Reporting (ILMT) v9 fixlet site so that its ID and version can be retrieved. The software exclusion already exists in the target instance. The software exclusion was already migrated or the same one was created in the target instance. Action: No action required. The item exists in the target environment. The software bundling already exists in the target instance. The software bundling was already migrated or the same one was created and confirmed in the target instance. Action: No action required. The item exists in the target environment. The report group ID is incorrect. Only software that belongs to the default report group can be migrated. Action: Reassign the software instance to the default report group. The software was not discovered in the target instance. The component that is included in the bundling was not discovered by the License Metric Tool 9.2 software scan. The software exclusion could not be migrated because the related software does not exist in the target instance. The excluded release was not discovered by the License Metric Tool 9.2 software scan. The component is assigned to a different product in the target instance. The component in the target instance was assigned to a different product and you confirmed this assignment. This confirmation created a custom bundling that cannot be overwritten by the migration. 18 Action: Log in to License Metric Tool 9.2, and click Management > IBM Software Classification. Locate the software, and manually reassign it to the right product. Shared components cannot be migrated. Components that are shared between multiple products cannot be migrated. Failed This status is not related to problems with items that you want to migrate, but rather to errors that are returned from the License Metric Tool 9.2 or IBM Endpoint Manager server. Such a status might be the result of connection problems. Each of the server errors is saved in the tema.log file that is in the following directory on your License Metric Tool server: Linux /opt/ibm/LMT/wlp/usr/servers/server1/logs/ Scan groups and scan schedules Succeeded The scan group and schedule were successfully migrated. The scan group and scan schedule were successfully migrated and no additional action is required. The scan group was successfully migrated. The scan schedule was not migrated because this option was not specified in the migration.properties file. The scan group was migrated. The scan schedule was not re-created in Endpoint Manager because the MIGRATE_SCAN_SCHEDULE parameter is set to false in the migration.properties file. The scan group was successfully migrated. The scan schedule was not migrated because IEM does not provide a direct equivalent of the scan frequency. The scan group was migrated. The scan schedule was not re-created in Endpoint Manager because there is no direct equivalent of the scan frequency. You can define a new scan frequency in Endpoint Manager. The scan group was successfully migrated. The scan schedule was not migrated because no agents are assigned to the scan group. The scan group was migrated. The scan schedule was not re-created in Endpoint Manager because no agents are assigned to the scan group in 7.x. Updated The scan group already exists in IEM but its scan schedule was updated. The scan group was not migrated because it already exists in Endpoint Manager. However, its scan schedule was updated. If you run the migration multiple times, the existence of a particular computer group is verified during every run. However, the existence of a migrated scan schedule is not verified. It means that the scan schedule is re-created every time you run the migration even if the schedule did not change. Skipped The scan group already exists in IEM. The scan schedule was not migrated because this option was not specified in the migration.properties file. The scan group was not migrated because it already exists in Endpoint Manager. The scan schedule was not re-created in Endpoint Manager because the MIGRATE_SCAN_SCHEDULE parameter is set to false in the migration.properties file. The scan group already exists in IEM. The scan schedule was not migrated because IEM does not provide a direct equivalent of the scan frequency. The scan group was not migrated because it already exists in Endpoint Manager. The scan schedule was not re-created in Endpoint Manager because there is no direct equivalent of the scan frequency. You can define a new scan frequency in Endpoint Manager. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 19 The scan group already exists in IEM. The scan schedule was not migrated because no agents are assigned to the scan group. The scan group was not migrated because it already exists in Endpoint Manager. The scan schedule was not re-created in Endpoint Manager because no agents are assigned to the scan group in 7.x. Failed The scan group was not migrated because an error occurred. The scan group was not migrated. Try rerunning the migration. The scan schedule was not migrated because an error occurred. The scan schedule was not migrated. Try rerunning the migration. The scan group was successfully migrated but one or more computers were not assigned. The scan group was migrated. However, one or more computers that were assigned to the scan group in 7.x were not assigned to the computer group in Endpoint Manager. Try rerunning the migration or assign the computer manually in Endpoint Manager. Verifying the environment After verifying the migration reports, ensure that the scan groups were created in IBM Endpoint Manager, and then log in to the source and target applications to verify that all items were successfully migrated. Verifying the items in V7.2.2 Open the user interface of the source and target applications, and verify that all items were successfully migrated. Items that can be verified on the user interface are VM Managers, software bundlings, software instances excluded from pricing calculations as well as scan groups and scan schedules. About this task The software inventory is displayed differently between the source and the target applications. In V7.2.2, the software inventory panel shows a list of products that must be clicked to view the associated components. In V9.2, a software product can be expanded to show the associated components on the same panel, which facilitates the verification. Procedure 1. Compare VM Managers. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2, click Infrastructure > VM Managers. b. In License Metric Tool 9.2, click Management > VM Managers. 2. Compare custom software bundlings. 20 a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2, click Software > Software Products. The panel lists all software products in your environment. b. Click on a software product to drill down to components that are associated with it. c. In License Metric Tool 9.2, click Management > IBM Software Classifications. Verify that the product and its components were migrated. 3. Compare software exclusions. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2, click IBM Audit Reports > PVU Current Capacity. Each product that is excluded from pricing calculations has no PVU consumption and a comment saying that its instances are excluded. b. In License Metric Tool 9.2, click Management > IBM Software Classifications. You can recognize the excluded product by the exclusion icon next to the product name. 4. Optional: Compare scan groups. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2, click Infrastructure > Scan Groups. b. In Endpoint Manager, click Computer Groups. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 21 Important: Stand-alone scan groups are not migrated. 5. Optional: Compare scan schedules. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.2.2, click Infrastructure > Scan Groups, and then the name of the scan group. b. In Endpoint Manager, click Actions, and then select the Initiate Software Scan for group group name. Important: In Endpoint Manager, you can schedule scans to run every 1, 2, 3, 5, 7, 15, or 30 days. Because the options differ from the options that are available in version 7.x, only scan schedules that can be re-created in Endpoint Manager are migrated. Scan schedules that are defined to run once are not migrated. 22 If you want to change the schedule for a particular group, stop the Initiate Software Scan for group group name action, run the Initiate Software Scan fixlet, specify the new schedule, and choose the relevant computer group. What to do next If you are satisfied with the result of migration, you can start removing the 7.2.2 agents from your environment. Before you do so, remember to run the Map LMT/TAD4D 7.x Agents task from the IBM Endpoint Manager console to save their IDs and versions. Verifying the items in V7.5 Open the user interface of the source and target applications, and verify that all items were successfully migrated. Items that can be verified on the user interface are VM Managers, software bundlings, and software instances excluded from pricing calculations. Procedure 1. Compare VM Managers. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.5, click Infrastructure > VM Managers. b. In License Metric Tool 9.2, click Management > VM Managers. 2. Compare custom software bundlings. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.5, click Software > Manage Software Inventory. b. In License Metric Tool 9.2, click Management > IBM Software Classification. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 23 3. Compare software exclusions. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.5, click Software > Manage Software Inventory. b. In License Metric Tool 9.2, click Management > IBM Software Classification. 4. Optional: Compare scan groups. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.5, click Infrastructure > Scan Groups. b. In Endpoint Manager, click Computer Groups. Important: Stand-alone scan groups are not migrated. 5. Optional: Compare scan schedules. a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.5, click Infrastructure > Scan Groups, and then the name of the scan group. 24 b. In Endpoint Manager, click Actions, and then select the Initiate Software Scan for group group name. Important: In Endpoint Manager, you can schedule scans to run every 1, 2, 3, 5, 7, 15, or 30 days. Because the options differ from the options that are available in version 7.x, only scan schedules that can be re-created in Endpoint Manager are migrated. Scan schedules that are defined to run once as well as hardware scans are not migrated. If you want to change the schedule for a particular group, stop the Initiate Software Scan for group group name action, run the Initiate Software Scan fixlet, specify the new schedule, and choose the relevant computer group. What to do next If you are satisfied with the result of migration, you can start removing the 7.5 agents from your environment. Before you do so, remember to run the Map LMT/TAD4D 7.x Agents task from the IBM Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 25 Endpoint Manager console to save their IDs and versions. 26 Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.2.2 and 7.5 27
© Copyright 2026