IBM. Migration Cookbook. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.

Size: px
Start display at page:

Download "IBM. Migration Cookbook. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9."

Transcription

1 IBM License Metric Tool 9.x Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x IBM

2

3 IBM License Metric Tool 9.x Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x IBM

4 ii IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

5 Contents Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and Overview and requirements Migrated items Migrating in parts Step 1: Preparing for migration Step 2: Mapping the agents Step 3: Scanning your environment Optional: Optimizing the software scan Step 4: Migrating your environment Step 5: Verifying the migration Verifying the export to csv files Export reports Verifying the simulation and migration reports 19 Migration reports Statuses in migration reports Verifying the environment Verifying the items in V Verifying the items in V Step 6: Removing the 7.x environment Copyright IBM Corp. 2002, 2016 iii

6 iv IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

7 Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and 7.5 Overview and requirements You can migrate from License Metric Tool or Tivoli Asset Discovery for Distributed or 7.5, and all subsequent fix packs and interim fixes, to License Metric Tool Items that can be migrated are software bundlings, software exclusions, directories excluded from scanning, scan groups, and VM Managers. Important: Audit reports generated in version 7.x are not migrated. Ensure that they are stored in a safe place in case of an audit. The migration moves your software inventory from License Metric Tool or Tivoli Asset Discovery for Distributed or 7.5 to a new infrastructure that is based on IBM BigFix and License Metric Tool As opposed to a simple upgrade, which automatically changes the version of the application, the migration requires that you install the new environment separately, mostly because of differences between the source and the target infrastructure. New infrastructure Although the environment to which you are going to migrate has the same concepts and follows similar patterns, it has some differences when compared to 7.x. It can be seen as a combination of License Metric Tool and the IBM BigFix 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 tool used for configuration. A number of tasks included in the following scenarios depend on IBM BigFix and are completed through the platform console. Scope of migration The migration does not transfer raw data nor scan results. The data is discovered by the software and hardware scans that are set up in the new environment. Audit reports generated in 7.x are also not migrated. Thus, ensure that you store them in a safe place in case of an audit. Items that are migrated include your decisions regarding software classification and include: v Software bundlings that you created and confirmed by assigning software instances to particular products v Software exclusions that represent software instances that are excluded from pricing calculations v Directories that are excluded from scanning During the migration, those decisions are recognized and extracted from version 7.x along with definitions of VM managers that are necessary to discover complete capacity of your computers. If the computers are divided into scan groups, you can also migrate those scan groups and their scan schedule. After this information is migrated, it is applied to the raw data that is discovered by the new scans. It allows for re-creating your specific software inventory in the Copyright IBM Corp. 2002,

8 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 and 7.5 including all subsequent fix packs and interim fixes. v Tivoli Asset Discovery for Distributed and 7.5 including all subsequent fix packs and interim fixes. The applications might from now on be referred to as 7.x. Operating systems and databases License Metric Tool supports a subset of operating systems that are supported by 7.x. You can migrate either to License Metric Tool on Linux with DB2, or on Windows with SQL Server. You can also migrate between different operating systems and databases, for example from AIX to Windows, or from DB2 to SQL Server. User permissions v License Metric Tool user The user whose authentication token is used to access the License Metric Tool server must have the following permissions: Manage Software Classification Manage VM Managers and Servers v BigFix Operator The user must fulfill the following requirements: Has the IBM License Reporting (ILMT) v9 site assigned Can administer computers that are going to be migrated Has the Can use REST API, Can Create Actions, and Custom Content permissions Data import Import of data must be disabled during the migration. To disable the import, log in to in License Metric Tool 9.2.8, and go to Management > Data Imports. Then, clear the Enabled check box, and click Save. Security TLS 1.2. must be disabled in version during the migration. To disable TLS 1.2, log in to License Metric Tool 9.2.8, and go to Management > Server Settings. Then, clear the Use TLS 1.2 check box. You can enable TLS 1.2. after the migration. Clients As one of the first steps of migration, you install the BigFix clients, which are equivalents of the 7.x agents. The client installers are native packages that can be installed using any method. However, BigFix provides several tools to automate this process, for example the Client Deploy Tool. Using BigFix tools for the installation is recommended. However, for large environments you can also use an alternative way and install the clients through the self-update functionality that is available in V7.x. Self-update installs the clients automatically on each computer that already has a 7.x agent. This installation requires the assistance of IBM Support, and is not 2 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

9 Migrated items the most effective method for smaller environments. For more information, download the following PDF guide: Installing BigFix clients through self-update. IBM i Data from IBM i computers is not included in the migration because the BigFix client is not available for IBM i systems. Software discovery on these systems is based on the so-called disconnected scans, a semi-automatic procedure that uses scripts to initiate software and capacity scans. To monitor software that is installed on the IBM i systems, set up disconnected scans after you complete the migration. For more information, see: Discovering software and hardware inventory on IBM i systems. Software catalog Ensure that the version of the catalog that is uploaded to 7.x is not higher than the version that is uploaded to The migration does not transfer raw data or scan results but information that is specific to your environment. This information includes software bundlings and exclusions, VM Managers, and excluded directories. Optionally, you can also migrate scan groups and scan schedules. Software bundlings Each time that a new component is discovered, License Metric Tool associates it with a product based on their relationship in the software catalog. This association is a software bundling. A software bundling must meet the following requirements to be migrated: v Is a confirmed software bundling in the source environment: You confirmed the assignment manually. Default unconfirmed bundlings are not migrated because they are automatically created in the target environment regardless of the migration. You reassigned a component to a different product, which created a confirmed software bundling. The product to which the component is assigned is the only bundling option that is available in the software catalog. v Bundles only IBM products. v Bundles products that are also discovered in the target environment. v Does not bundle components that are shared between multiple products. v Does not bundle components that are confirmed in the target environment. The migration cannot overwrite confirmed bundlings. v Does not bundle components that are assigned to different products in the target environment and whose assignment you confirmed. The migration cannot overwrite confirmed bundlings. If a component is assigned to a different product but is not confirmed, then the migration overwrites this assignment to resemble the source environment. v Bundles products that belong to the default report group. In version 7.5, you can assign software to several report groups, thus having a possibility to create reports that contain software only from a certain group. This function is used to distinguish your software and that of service providers, which might be installed on the same servers. In this case, you can create a Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and 7.5 3

10 separate report group for software that is an obligatory part of a provided service, such as software that is used to manage the provided infrastructure, and a separate one for your software. Software bundlings that do not meet the preceding requirements are skipped. The migration of the software bundlings is enabled by default. If you do not want to migrate the bundlings, set the MIGRATE_SOFTWARE_BUNDLINGS parameter to false in the migration.properties file. Custom bundling options Custom bundling options define custom relations between components and products that are not defined in the IBM software catalog. Custom bundling options are not migrated. To ensure that software that is bundled based on a custom bundling option in version 7.5, remains bundled in the same way in version, you must create the same custom bundling option in version. If the option is not defined in version, the software is bundled according to the rule that is defined in the IBM software catalog and the bundling needs to be confirmed. If the bundling is already confirmed in version, it does not change regardless of whether the custom bundling option is defined in version. Software exclusions Software exclusions are software instances that are excluded from pricing calculations. All software exclusions that do not already exist in the target environment are migrated by default. However, the following exception must be considered: v Migration of a software exclusion confirms the bundling of this software in License Metric Tool 9.2.8, which means that it cannot be changed in the subsequent migration runs. If you later include such an instance in pricing calculations in version 7.x, you must also manually include it in version 9.2.8, because the migration cannot overwrite confirmed bundlings. If you do not want to migrate the software exclusions, set the MIGRATE_SOFTWARE_EXCLUSIONS parameter to false in the migration.properties file. VM managers VM Managers, also known as hypervisors, are used to create and run virtual machines. The access details to VM Managers are necessary to discover the capacity that the virtual machines can use. It is required to accurately calculate the PVU consumption. All VM Managers that are not already defined in the target environment are migrated by default. If you do not want to migrate the VM Managers, set the MIGRATE_VM_MANAGERS parameter to false in the migration.properties file. Excluded directories All directories that are excluded from scanning are migrated by default. If any of them are already excluded in the target environment, they are skipped. 4 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

11 There are two types of excluded directories: v Directories excluded for a platform, for example for all Windows computers. The migration tool extracts them from the 7.x database and passes on to BigFix, which uses the Add Excluded Directories task to deliver them to relevant computers. BigFix recognizes the platforms and distributes the directories appropriately. After migration, all excluded directories from the 7.x agents are added to the BigFix clients. Directories excluded for the i5 platform are not migrated, because this platform is not supported in 9.x. v Directories excluded for an agent, for example for an agent with host name NC Before you run the migration, you activate the Excluded Directories analysis that retrieves directories that are currently excluded for BigFix clients (9.x agents). When the migration tool extracts excluded directories from the 7.x database, it compares them to analysis results to recognize which directories are missing in 9.x. The missing directories are delivered to BigFix clients by using the Add Excluded Directories task. After migration, all excluded directories from the 7.x agents are added to the BigFix clients. Directories excluded for the i5 platform are not migrated, because this platform is not supported in 9.x. Note: Directories can be delivered only to computers that have the BigFix client installed and software scan initiated. Those steps, however, are completed when you prepare the environment for migration. Tip: v The Excluded Directories analysis and the Add Excluded Directories task can be viewed in the BigFix console. v After migration, you can go to the console and click Actions. A set of Add Excluded Directories actions run against your computers to deliver the directories. v The excluded directories can be viewed in excludedirectories.csv (after export) and excluded_directories_report.csv (after simulation and migration). If you do not want to migrate the excluded directories, set the MIGRATE_EXCLUDED_DIRECTORIES parameter to false in the migration.properties file. Scan groups and scan schedules Scan groups in version and 7.5 are used to create separate scan schedules for different groups of computers. This allows the reduction of network traffic that is generated by scans and differentiating scan frequency according to the dynamics with which the software changes on particular computers. The migration of scan groups and scan schedules is optional. If you want to separate the computers in your new infrastructure in a different way, you can skip this part of the migration. Scan groups from 7.x are migrated into computer groups in BigFix. The migration is enabled by default. If you do not want to migrate scan groups, set the MIGRATE_SCAN_GROUPS parameter to false in the migration.properties file. Unlike in 7.x, one computer can belong to multiple groups in BigFix. Stand-alone scan groups are not migrated. Groups that are scheduled to run once are migrated but their schedules are not. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and 7.5 5

12 Migrating in parts After migration, scan groups from 7.x are listed in the BigFix console under Computer Groups. Each migrated computer group is named in the following way: v The prefix Migrated v The name of the scan group from version 7.x v Identifier of the instance of License Metric Tool or Tivoli Asset Discovery for Distributed from which the scan group was migrated. The identifier is the value that you specify as the LMT_TAD4D_DB_HOST parameter in the migration.properties file. This ensures that if you migrate content from multiple instances of License Metric Tool or Tivoli Asset Discovery for Distributed to one BigFix, scan groups with the same name are not skipped. An example of a migrated scan group name is: Migrated_Finance_Department_ You can change it later. Apart from scan groups, you can also migrate scan schedules. In BigFix, 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 BigFix are migrated. Migration of scan schedules is disabled by default. To migrate scan schedules, set the MIGRATE_SCAN_SCHEDULE parameter to true in the migration.properties file. Important: If you migrate scan schedules, both 7.x and scans will run at the same time on your endpoints. You can break the migration down into smaller parts either by installing the IBM BigFix clients only on a group of endpoints or by 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. It also 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 down into parts, choose one of the following approaches: v Scenario 1: Installing the IBM BigFix client on a group of endpoints While preparing the new environment, as described in Step 1: Preparing for migration, install the IBM BigFix clients only on a group of endpoints. Items can be migrated only from endpoints that have both the 7.x agent and the IBM BigFix client installed. The remaining items are listed as skipped and not migrated to License Metric Tool After you migrate the first group of endpoints, install the clients on the next group and repeat the migration. v Scenario 2: 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. Because 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. By doing this, the analysis gathers information only from the endpoints that are currently subscribed to the Fixlet site. 6 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

13 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 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 scenarios 1 and 2, 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 BigFix client is not installed. Filter the files by host names to limit the view only to items from a particular group of endpoints. Although the items are listed in the csv files, they are not saved in the target environment. v Scenario 3: Importing endpoints listed in the agentsmap.csv file Step 1: Preparing for migration Map the agents as described in Step 2: Mapping the agents. Then, run the migration script with the -export command to generate csv files with information about items that are eligible for migration. One of the generated files is agentsmap.csv. Divide the file into a number of smaller files, each containing a group of endpoints that you want to migrate. Ensure that one of the smaller files is called agentsmap.csv as this is the file from which endpoints are migrated. Run the migration with the -csvagentmap command. Only endpoints that are listed in the agentsmap.csv file are migrated. Verify that the first group of endpoints is migrated. Then, rename the second file to agentsmap.csv and migrate the next group of endpoints. Before you start the migration, prepare the target environment by installing all components of License Metric Tool The components include: v BigFix server that coordinates the flow of data to and from the monitored computers, and its database v BigFix console that is used to target computers with specific actions v License Metric Tool server and its database You can install the components on Linux or Windows, except for the console that is available on Windows only. Depending on the environment size, you can also distribute them between one, two, or three computers. For more information about the possible installation scenarios and detailed instructions, see: Installing License Metric Tool. Additionally, install the BigFix client on every computer in your infrastructure that you want to monitor. Tip: For large environments, you can install the clients through the self-update functionality that is available in V7.x. Self-update installs the clients automatically on each computer that already has a 7.x agent. However, this installation requires the assistance of IBM Support, and is not the most effective for smaller environments. For more information, see: Client requirements. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and 7.5 7

14 IBM i The BigFix client is not available for IBM i systems. Software discovery on these systems is based on the so-called disconnected scans, a semi-automatic procedure that uses scripts to initiate software and capacity scans. To monitor software that is installed on the IBM i systems, set up disconnected scans after you complete the migration. For more information, see: Discovering software and hardware inventory on IBM i systems. 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 re-creating 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 BigFix clients. You can map the agents immediately after activating the analysis, or at any time before you remove them. Procedure 1. Log in to the IBM BigFix console. 2. In the navigation tree, click Sites > External Sites > IBM License Reporting (ILMT) v9. 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. 8 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

15 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 BigFix 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 those 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 earlier. The progress can be viewed under the Results tab. 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 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and 7.5 9

16 Procedure 1. Log in to the IBM BigFix 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 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. 4. Go to Fixlets and Tasks, and run the License Metric Tool software and capacity scans on all your endpoints to discover hardware and software inventory through the new infrastructure. Tip: To run a particular task, select it, and then click Take Action. From the list of applicable endpoints, select all endpoints at the same time instead of targeting each of them separately. a. Run the Install or Upgrade Scanner task. b. Run the Initiate Software Scan task. It becomes relevant only when the scanner is installed. When the Fixlet shows 100% completeness, it means that the scans were successfully initiated, not that they finished. c. Run the Upload Software Scan Results task. It becomes relevant only when the software scan finishes collecting the results. d. Run the Run Capacity Scan and Upload Results task. 5. Go to Fixlets and Tasks, and run the following task against the IBM BigFix server to install the VM Manager Tool: Note: If the following tasks cannot be run against the IBM BigFix server, it means that they were initiated automatically during the installation and you can omit this step. a. Run the Install VM Manager Tool task and wait until the action completes. b. Run the Schedule VM Manager Tool Scan Results Upload task. 6. To initiate the VM Manager Tool, log in to License Metric Tool, and click Management > VM Managers. Just 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. 10 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

17 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 missing results will be uploaded in the next step after you migrate the VM Managers. What to do next To verify that the scans completed successfully, log in to License Metric Tool, and go to Reports > Computers. If the report lists all computers in your infrastructure and for each computer has a date in the Latest Scan Import column, the scans were successful and you can proceed to Step 4: Migrate your environment. Otherwise, wait some time and run another import. If it does not help, further troubleshooting might be required. Optional: Optimizing the software scan You can change the schedule of software scan either from the IBM BigFix 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 BigFix clients must be installed side by side on your endpoints. The scans from both applications might run at 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 BigFix console, complete the following steps: 1. Log in to the IBM BigFix console. 2. In the navigation tree, click Sites > External Sites > IBM License Reporting (ILMT) v9 > Fixlets and Tasks. 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 the scan settings for. 4. Select a new schedule from the Frequency list and specify the start date. Click Save. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

18 Step 4: Migrating your environment Migration is performed by using the migration tool that can either export your information to csv files, migrate it directly to version 9.2.8, or run a simulation that allows you to see the expected result without saving the information in the target environment. 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 on page 3. v The migration tool must be run on the same endpoint as the License Metric Tool server. v During migration, the following servers must be running: License Metric Tool or Tivoli Asset Discovery for Distributed 7.x database, IBM BigFix server, and License Metric Tool server. v You can run the migration tool repeatedly if you want to break the migration down into parts. The items that were already migrated are then skipped. v If you want to migrate to multiple IBM BigFix 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 use TLS 1.2, disable it before the migration. v If you encounter any problems during migration, see: Migration problems 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 scans. The migration completes this data with information about your choices regarding software classification to re-create your specific software inventory. Procedure 1. From the License Metric Tool installation directory, go to migration/product. 12 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

19 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 BigFix, and License Metric Tool servers. It also provides customizable settings that can be used to migrate scan groups and the scan schedule. Important: Ensure that the value of the LMT_SUA_SITE property is IBM License Reporting which is the default value. The name of the site that will be displayed in the IBM BigFix console is IBM License Reporting (ILMT) v9 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 the 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./migration.sh -migrate [-dir directory] [-csvagentmap] -simulate Windows./migration.bat -migrate [-dir directory] [-csvagentmap] -simulate [-dir directory] Specifies a directory to save your csv files to. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

20 If you omit this parameter, the csv files are created in the main directory of the migration tool. [-csvagentmap] Migrates only computers that are listed in the agentsmap.csv file. Use this parameter if you want to migrate the environment in parts. If you omit this parameter, the simulation covers all computers that fulfill migration requirements. b. Check the summary of simulation that is displayed after the simulation is completed. 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, a BigFix 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 the 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 on 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] [-csvagentmap]./migration.bat -migrate [-dir directory] [-csvagentmap] [-dir directory] Specifies a directory to save your csv files to. 14 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

21 If you omit this parameter, the csv files are created in the main directory of the migration tool. [-csvagentmap] Migrates only computers that are listed in the agentsmap.csv file. Use this parameter if you want to migrate the environment in parts. If you omit this parameter, all computers that fulfill migration requirements are migrated. 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 the 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. 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 BigFix server every 12 hours. You can trigger the upload by running the Schedule VM Manager Tool Scan Results Upload Fixlet from the IBM License Reporting (ILMT) v9 Fixlet site. The data is then transferred from IBM BigFix to License Metric Tool with each data import. To verify whether 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 the OK status. Next step: Verify the migration Step 5: 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 the 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

22 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 on page 3. 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 BigFix clients. If any of the agents are 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. 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 those 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 the 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 BigFix Client ID ID of an IBM BigFix client. 16 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

23 Table 1. Description of columns that are in the agentsmap.csv file. (continued) Column LMT/TAD4D 7.x Agent ID LMT/TAD4D 7.x Agent Version Host Name Operating System ID of a 7.x agent. Version of a 7.x agent. Description Host name of the endpoint where the agent is installed. 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 IP Address User Name Password URL Type IP address of a VM Manager. Description Credentials used to log in to a VM Manager. The password is encrypted. Web address of a VM Manager. Type of VM Manager. It can assume the following values: Shared Credentials 1 - Microsoft Hyper-V 2 - VMWare ESX, ESXi, or vcenter 3 - KVM RHEV-M 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. Table 3. Description of columns that are in the bundles.csv file. Column LMT/TAD4D 7.x Agent ID Component GUID Product GUID Component Path Component Name Component Version Product Name Description ID of a License Metric Tool or Tivoli Asset Discovery for Distributed 7.x agent. GUID of the exported component. GUID of a product that the exported component is assigned to. Installation path of the exported component. In License Metric Tool 7.x, the path is empty. Name of the exported component. Version of the exported component. 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

24 Table 3. Description of columns that are in the bundles.csv file. (continued) Column Host Name Operating System Report Group ID Host name of a 7.x agent. Description Operating system of the endpoint where the agent is installed. 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 LMT/TAD4D 7.x Agent ID Product GUID Reason for Exclusion Comment Product Name ID of a 7.x agent. Description GUID of a product that the excluded release is assigned to. Reason that you specified for excluding a release. Comment that you attached to the excluded release. Name of a product that the excluded release is assigned to. Release Version Version of the excluded release. Report Group ID Host Name IP Address ID of a report group. Items that are not in the default report group are not migrated. Host name of a 7.x agent. 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. ID Column Version Host Name IP Address Operating System Scan Group ID Agent ID. Agent version. Description Host name of the endpoint where the agent is installed. IP address of the endpoint where the agent is installed. Operating system of the endpoint where the agent is installed. 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. 18 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

25 Table 6. Description of columns that are in the excludedirectories.csv file. Column Excluded Directory Platform Description Directories that are excluded from scanning in 7.x. Operating system with the excluded directory. LMT/TAD4D 7.x Agent ID IP Address Host Name Operating System A directory can be excluded either for a certain type of operating system, for example, for all Windows systems in your environment, or for a particular agent. If this column contains a value, then the following columns are empty. ID of an agent with the excluded directory. A directory can be excluded either for a certain type of operating system, for example, for all Windows systems in your environment, or for a particular agent. If this column contains a value, then the preceding column is empty. IP address of an agent with the excluded directory. Host name of an agent with the excluded directory. Operating system of an agent with the excluded directory. 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 Scan Group ID Scan Group Name Scan Start Date Frequency Calendar Unit Number of Agents Description ID of the scan group from 7.x. Name of the scan group from 7.x. The date and time when the specified scan schedule starts. Frequency with which the scan runs. The type of calendar unit to which the frequency applies. Possible values are days, weeks, and months. 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.8, you can view the summary of migration in the 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 and

26 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 on page 3. 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 those 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 those 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 BigFix 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 this case, the items that were already migrated are 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 V 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.8, the summary of migration is saved in the csv reports. The reports are created in the main directory of the migration tool. 20 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

27 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. Item Status Description URL User Name Type Column Description An item that was migrated. In this report, it always assumes the VMMANAGER value. Status of a migrated item. It can assume the following values: succeeded, skipped, or failed. Explanation of the status. For more information, see Statuses. Web address of a VM Manager. User name that is used to log in to a VM Manager. 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. Item Column Description An item that was migrated. In this report, it can assume the following values: Status Description BigFix Client ID LMT/TAD4D 7.x Agent ID Product Name Release Version LMT/BFI Release GUID LMT/BFI Component Name LMT/BFI Component Version LMT/BFI Component GUID LMT/TAD4D 7.x Component Path LMT/BFI Component Path BUNDLING - software bundling EXCLUSION - software exclusion Status of a migrated item. It can assume the following values: succeeded, skipped, or failed. Explanation of the status. For more information, see Statuses. ID of an IBM BigFix client. ID of a 7.x agent. Name of the product that the component is assigned to. Version of the product release that the component is assigned to. GUID of the product release that the component is assigned to. Name of the component in the target environment. Version of the component in the target environment. GUID of the component in the target environment. Installation path of the migrated component that was discovered by the software scan in 7.x. Installation path of the migrated component that was discovered by the software scan in License Metric Tool Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

28 Table 9. Description of columns that are in the software_report.csv file. (continued) Column Description 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. Table 10. Description of columns that are in the excluded_directories_report.csv file. Status Description Platform Column Description Status of a migrated item. It can assume the following values: updated, skipped, or failed. Explanation of the status. For more information, see Statuses. Operating system with the excluded directory. BigFix Client ID LMT/TAD4D 7.x Agent ID LMT/BFI Directories LMT/TAD4D Directories Migrated Directories Operating System Host Name IP Address A directory can be excluded either for a certain type of operating system, for example, for 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. IDs of a IBM BigFix client and a 7.x agent. A directory can be excluded either for a certain type of operating system, for example, for all Windows systems in your environment, or on a particular agent. If these columns contain a value, then the Platform column is empty. Directories that are excluded from scanning in License Metric Tool Directories that are excluded from scanning in 7.x. Directories that were migrated. If the same directories are specified both in version 7.x and 9.2.8, they are not migrated. Operating system of an agent with the excluded directory. Host name of an agent with the excluded directory. 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 Status Description LMT/TAD4D 7.x Scan Group Name Description Status of a migrated scan group and scan schedule. It can assume the following values: succeeded, updated, skipped, or failed. Explanation of the status. For more information, see Statuses. Name of the scan group in 7.x. 22 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

29 Table 11. Description of columns that are in the scan_groups_report.csv file. (continued) Column BigFix Computer Group Name LMT/TAD4D 7.x Scan Schedule BigFix Scan Schedule Description Name of the migrated computer group in BigFix. Scan schedule that is specified in 7.x. Scan schedule that is specified in BigFix after migration. Scan Start Date Schedule Created in BigFix Because scheduling options that are available in 7.x and BigFix differ, only scan schedules that can be re-created are migrated. If the schedule cannot be re-created, this field is empty. The date and time when the specified scan schedule starts. Information whether the scan schedule was re-created in BigFix. Information about whether migrated 7.x agents were assigned to BigFix scan groups is saved to the matched_agents_report.csv file. Table 12. Description of columns that are in the matched_agents_report.csv file. Column BigFix Client ID LMT/TAD4D 7.x Agent ID LMT/TAD4D 7.x Agent Version Host Name Operating System Scan Group Name Assigned to BigFix Computer Group Description ID of the BigFix client. ID of the 7.x agent. Version of the 7.x agent. Host name of the endpoint where the agent is installed. Operating system of the endpoint where the agent is installed. Name of the 7.x scan group to which the agent is assigned. Information whether the endpoint is assigned to a BigFix 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 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 or IBM BigFix server. Such a status might be the result of connection problems. Each of the server errors is saved in the tema.log file, which is located in the following directory on your License Metric Tool server: Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

30 Linux /opt/ibm/lmt/wlp/usr/servers/server1/logs/ Excluded directories Updated Directories were successfully updated on the IBM BigFix server, which then delivers them to your endpoints. Skipped Items were not migrated. They were skipped for one of the following reasons: Failed The BigFix client is not installed. You can migrate the items only from computers that have both the 7.x agent and the IBM BigFix client installed. Action: Install an IBM BigFix 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 and do not need to be migrated. Action: No action required. The item exists in the target environment. Unsupported platform Directories cannot be migrated because they are excluded on i5 systems, which are not supported in License Metric Tool The items were not migrated. They failed for one of the following reasons: The Add Excluded Directories task cannot be found in the LMT/BFI 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. The Add Excluded Directories task in the LMT/BFI Fixlet site cannot be initiated. The task cannot be initiated because the connection to the IBM BigFix server failed. Action: Check the migration.log file that gives 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 BigFix client is not installed. You can migrate the items only from computers that have both the 7.x agent and the IBM BigFix client installed. 24 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

31 Failed Action: Install an IBM BigFix 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 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 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. Action: Log in to License Metric Tool 9.2.8, and click Reports > Software Classification. Locate the software, and manually reassign it to the correct product. Shared components cannot be migrated. Components that are shared between multiple products cannot be migrated. 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 or IBM BigFix server. Such a status might be the result of connection problems. Each of the server errors is saved in the tema.log file, which is located 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

32 Updated Skipped Failed 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 BigFix 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 BigFix does not provide a direct equivalent of the scan frequency. The scan group was migrated. The scan schedule was not re-created in BigFix because there is no direct equivalent of the scan frequency. You can define a new scan frequency in BigFix. 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 BigFix because no agents are assigned to the scan group in 7.x. The scan group already exists in BigFix but its scan schedule was updated. The scan group was not migrated because it already exists in BigFix. 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. This means that the scan schedule is re-created every time you run the migration even if the schedule did not change. The scan group already exists in BigFix. 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 BigFix. The scan schedule was not re-created in BigFix because the MIGRATE_SCAN_SCHEDULE parameter is set to false in the migration.properties file. The scan group already exists in BigFix. The scan schedule was not migrated because BigFix does not provide a direct equivalent of the scan frequency. The scan group was not migrated because it already exists in BigFix. The scan schedule was not re-created in BigFix because there is no direct equivalent of the scan frequency. You can define a new scan frequency in BigFix. The scan group already exists in BigFix. 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 BigFix. The scan schedule was not re-created in BigFix because no agents are assigned to the scan group in 7.x. The scan group was not migrated because an error occurred. The scan group was not migrated. Try running the migration again. 26 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

33 The scan schedule was not migrated because an error occurred. The scan schedule was not migrated. Try running the migration again. 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 BigFix. Try running the migration again or assign the computer manually in BigFix. Verifying the environment After verifying the migration reports, ensure that the scan groups were created in IBM BigFix, 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.8, 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.8, click Management > VM Managers. 2. Compare custom software bundlings. 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

34 b. Click on a software product to drill down to components that are associated with it. c. In License Metric Tool 9.2.8, 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.8, 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 BigFix, 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.2.2, click Infrastructure > Scan Groups, and then the name of the scan group. 28 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

35 b. In BigFix, click Actions, and then select the Initiate Software Scan for group group name. Important: In BigFix, 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 BigFix are migrated. Scan schedules that are defined to run once 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 agents from your environment. Before you do so, remember to run the Map LMT/TAD4D 7.x Agents task from the IBM BigFix 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

36 a. In License Metric Tool or Tivoli Asset Discovery for Distributed 7.5, click Infrastructure > VM Managers. b. In License Metric Tool 9.2.8, 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.8, click Reports > Software Classification. 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.8, click Reports > 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 BigFix, click Computer Groups. 30 IBM License Metric Tool: Migration Cookbook Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed 7.5 to License Metric Tool 9.x

37 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. b. In BigFix, click Actions, and then select the Initiate Software Scan for group group name. Important: In BigFix, 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 BigFix 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. Migrating from License Metric Tool and Tivoli Asset Discovery for Distributed and

Migration from version 7.5 to 9.0. IBM License Metric Tool & Software Use Analysis Questions and Answers ILMT Central Team

Migration from version 7.5 to 9.0. IBM License Metric Tool & Software Use Analysis Questions and Answers ILMT Central Team Migration from version 7.5 to 9.0 IBM License Metric Tool & Software Use Analysis Questions and Answers ILMT Central Team Agenda Introduction 01 Step 1: Prepare the environment 02 Step 2: Map the agents

More information

Enhancements and new features in ILMT/SUA IBM License Metric Tool & Software Use Analysis Questions and Answers Enablement Team

Enhancements and new features in ILMT/SUA IBM License Metric Tool & Software Use Analysis Questions and Answers Enablement Team Enhancements and new features in ILMT/SUA 9.2.0.2 IBM License Metric Tool & Software Use Analysis Questions and Answers Enablement Team Agenda 01 Introduction 04 Hiding free instances 07 Rebranding 02

More information

Automated Bundling and Other New Features in IBM License Metric Tool 7.5 Questions & Answers

Automated Bundling and Other New Features in IBM License Metric Tool 7.5 Questions & Answers ILMT Central Team Automated Bundling and Other New Features in IBM License Metric Tool 7.5 Questions & Answers Information These slides were just the deck of the ILMT Central Team Questions&Answers session.

More information

ForeScout Extended Module for IBM BigFix

ForeScout Extended Module for IBM BigFix ForeScout Extended Module for IBM BigFix Version 1.0.0 Table of Contents About this Integration... 4 Use Cases... 4 Additional BigFix Documentation... 4 About this Module... 4 Concepts, Components, Considerations...

More information

Installing BigFix clients through self-update IBM

Installing BigFix clients through self-update IBM Installing BigFix clients through self-update IBM ii Installing BigFix clients through self-update Contents Chapter 1. Installing BigFix clients through self-update.......... 1 Step 1: Planning the infrastructure.......

More information

USER GUIDE. Snow Integration Manager. Version 4.7. Release date Document date SNOWSOFTWARE.COM

USER GUIDE. Snow Integration Manager. Version 4.7. Release date Document date SNOWSOFTWARE.COM USER GUIDE Product Snow Integration Manager Version 4.7 Release date 2016-05-16 Document date 2016-08-30 CONTENTS Introduction... 4 Prerequisites... 4 Installation... 5 Configuration... 6 General... 6

More information

ForeScout Extended Module for IBM BigFix

ForeScout Extended Module for IBM BigFix Version 1.1 Table of Contents About BigFix Integration... 4 Use Cases... 4 Additional BigFix Documentation... 4 About this Module... 4 About Support for Dual Stack Environments... 5 Concepts, Components,

More information

vrealize Operations Manager Management Pack for vrealize Hyperic Release Notes

vrealize Operations Manager Management Pack for vrealize Hyperic Release Notes vrealize Operations Manager Management Pack for vrealize Hyperic Release Notes vrealize Operations Manager Management Pack for Hyperic 6.0 Last document update: 04 December 2014. Contents: New Features

More information

IBM BigFix Compliance PCI Add-on Version 9.5. Payment Card Industry Data Security Standard (PCI DSS) User's Guide IBM

IBM BigFix Compliance PCI Add-on Version 9.5. Payment Card Industry Data Security Standard (PCI DSS) User's Guide IBM IBM BigFix Compliance PCI Add-on Version 9.5 Payment Card Industry Data Security Standard (PCI DSS) User's Guide IBM IBM BigFix Compliance PCI Add-on Version 9.5 Payment Card Industry Data Security Standard

More information

USER GUIDE. Snow Integration Manager. Version 5.5. Release date Document date SNOWSOFTWARE.COM

USER GUIDE. Snow Integration Manager. Version 5.5. Release date Document date SNOWSOFTWARE.COM USER GUIDE Product Snow Integration Manager Version 5.5 Release date 2017-09-27 Document date 2017-10-05 CONTENTS 1 Introduction... 4 1.1 Prerequisites... 4 2 Installation... 5 2.1 New installation...

More information

IBM Endpoint Manager. OS Deployment V3.8 User's Guide - DRAFT for Beta V.1.0 (do not distribute)

IBM Endpoint Manager. OS Deployment V3.8 User's Guide - DRAFT for Beta V.1.0 (do not distribute) IBM Endpoint Manager OS Deployment V3.8 User's Guide - DRAFT for Beta V.1.0 (do not distribute) IBM Endpoint Manager OS Deployment V3.8 User's Guide - DRAFT for Beta V.1.0 (do not distribute) Note Before

More information

Forescout. eyeextend for IBM BigFix. Configuration Guide. Version 1.2

Forescout. eyeextend for IBM BigFix. Configuration Guide. Version 1.2 Forescout Version 1.2 Contact Information Forescout Technologies, Inc. 190 West Tasman Drive San Jose, CA 95134 USA https://www.forescout.com/support/ Toll-Free (US): 1.866.377.8771 Tel (Intl): 1.408.213.3191

More information

VMware vrealize Operations for Horizon Installation. VMware vrealize Operations for Horizon 6.5

VMware vrealize Operations for Horizon Installation. VMware vrealize Operations for Horizon 6.5 VMware vrealize Operations for Horizon Installation VMware vrealize Operations for Horizon 6.5 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

VMware vrealize Operations for Horizon Installation

VMware vrealize Operations for Horizon Installation VMware vrealize Operations for Horizon Installation vrealize Operations for Horizon 6.4 Installation vrealize Operations for Horizon 6.4 This document supports the version of each product listed and supports

More information

Contents Upgrading BFInventory iii

Contents Upgrading BFInventory iii Upgrading ii Upgrading Contents Upgrading.............. 1 Upgrading to IBM Tivoli Endpoint Manager for Software Use Analysis version 2.0....... 1 Planning and preparing for the upgrade.... 2 Installing

More information

VMware vrealize Operations for Horizon Installation. VMware vrealize Operations for Horizon 6.3

VMware vrealize Operations for Horizon Installation. VMware vrealize Operations for Horizon 6.3 VMware vrealize Operations for Horizon Installation VMware vrealize Operations for Horizon 6.3 VMware vrealize Operations for Horizon Installation You can find the most up-to-date technical documentation

More information

vrealize Operations Service Discovery Management Pack 2.0

vrealize Operations Service Discovery Management Pack 2.0 vrealize Operations Service Discovery Management Pack 2.0 vrealize Operations Service Discovery Management Pack 2.0 You can find the most up-to-date technical documentation on the ware Web site at: https://docs.vmware.com/

More information

IBM Endpoint Manager. OS Deployment V3.5 User's Guide

IBM Endpoint Manager. OS Deployment V3.5 User's Guide IBM Endpoint Manager OS Deployment V3.5 User's Guide IBM Endpoint Manager OS Deployment V3.5 User's Guide Note Before using this information and the product it supports, read the information in Notices

More information

Let s manage agents. Tom Sightler, Principal Solutions Architect Dmitry Popov, Product Management

Let s manage agents. Tom Sightler, Principal Solutions Architect Dmitry Popov, Product Management Let s manage agents Tom Sightler, Principal Solutions Architect Dmitry Popov, Product Management Agenda Inventory management Job management Managed by backup server jobs Managed by agent jobs Recovery

More information

BigFix 2018 Roadmap. Aram Eblighatian. Product Manager IBM BigFix. 14 May, 2018

BigFix 2018 Roadmap. Aram Eblighatian. Product Manager IBM BigFix. 14 May, 2018 BigFix 2018 Roadmap Aram Eblighatian Product Manager IBM BigFix 14 May, 2018 What's New in BigFix? BigFix Platform BigFix Platform v9.5.7 Released Oct. 2017 Gathering Performance improvements (WebUI and

More information

IBM IBM Tivoli Endpoint Manager V8.1 Implementation.

IBM IBM Tivoli Endpoint Manager V8.1 Implementation. IBM 000-560 IBM Tivoli Endpoint Manager V8.1 Implementation http://killexams.com/exam-detail/000-560 A. It should always be empty in a healthy environment. B. It is used to store downloaded files from

More information

VMware AirWatch Google Sync Integration Guide Securing Your Infrastructure

VMware AirWatch Google Sync Integration Guide Securing Your  Infrastructure VMware AirWatch Google Sync Integration Guide Securing Your Email Infrastructure AirWatch v9.2 Have documentation feedback? Submit a Documentation Feedback support ticket using the Support Wizard on support.air-watch.com.

More information

VMware AirWatch Google Sync Integration Guide Securing Your Infrastructure

VMware AirWatch Google Sync Integration Guide Securing Your  Infrastructure VMware AirWatch Google Sync Integration Guide Securing Your Email Infrastructure Workspace ONE UEM v9.5 Have documentation feedback? Submit a Documentation Feedback support ticket using the Support Wizard

More information

Google Sync Integration Guide. VMware Workspace ONE UEM 1902

Google Sync Integration Guide. VMware Workspace ONE UEM 1902 Google Sync Integration Guide VMware Workspace ONE UEM 1902 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation,

More information

Developing and Deploying vsphere Solutions, vservices, and ESX Agents. 17 APR 2018 vsphere Web Services SDK 6.7 vcenter Server 6.7 VMware ESXi 6.

Developing and Deploying vsphere Solutions, vservices, and ESX Agents. 17 APR 2018 vsphere Web Services SDK 6.7 vcenter Server 6.7 VMware ESXi 6. Developing and Deploying vsphere Solutions, vservices, and ESX Agents 17 APR 2018 vsphere Web Services SDK 6.7 vcenter Server 6.7 VMware ESXi 6.7 You can find the most up-to-date technical documentation

More information

CounterACT VMware vsphere Plugin

CounterACT VMware vsphere Plugin CounterACT VMware vsphere Plugin Configuration Guide Version 2.0.0 Table of Contents About VMware vsphere Integration... 4 Use Cases... 4 Additional VMware Documentation... 4 About this Plugin... 5 What

More information

FlexNet Manager Suite 2015 R2 SP5 FlexNet Manager Suite 2015 Release 2 Service Pack 5

FlexNet Manager Suite 2015 R2 SP5 FlexNet Manager Suite 2015 Release 2 Service Pack 5 FlexNet Manager Suite 2015 R2 SP5 FlexNet Manager Suite 2015 Release 2 Service Pack 5 Release Notes Updated May 31, 2016 The current edition of these Release Notes is published here. FlexNet Manager Suite

More information

Developing and Deploying vsphere Solutions, vservices, and ESX Agents

Developing and Deploying vsphere Solutions, vservices, and ESX Agents Developing and Deploying vsphere Solutions, vservices, and ESX Agents Modified on 27 JUL 2017 vsphere Web Services SDK 6.5 vcenter Server 6.5 VMware ESXi 6.5 Developing and Deploying vsphere Solutions,

More information

IBM Endpoint Manager Version 9.0. Software Distribution User's Guide

IBM Endpoint Manager Version 9.0. Software Distribution User's Guide IBM Endpoint Manager Version 9.0 Software Distribution User's Guide IBM Endpoint Manager Version 9.0 Software Distribution User's Guide Note Before using this information and the product it supports,

More information

IBM Endpoint Manager Version 9.2. Software Use Analysis Installation Guide

IBM Endpoint Manager Version 9.2. Software Use Analysis Installation Guide IBM Endpoint Manager Version 9.2 Software Use Analysis Installation Guide IBM Endpoint Manager Version 9.2 Software Use Analysis Installation Guide Installation Guide This edition applies to IBM Endpoint

More information

PASS4TEST. IT Certification Guaranteed, The Easy Way! We offer free update service for one year

PASS4TEST. IT Certification Guaranteed, The Easy Way!   We offer free update service for one year PASS4TEST \ http://www.pass4test.com We offer free update service for one year Exam : A2010-650 Title : Fundamentals of Applying Tivoli Endpoint Manager Solutions V1 Vendor : IBM Version : DEMO 1 / 5 Get

More information

Developing and Deploying vsphere Solutions, vservices, and ESX Agents

Developing and Deploying vsphere Solutions, vservices, and ESX Agents Developing and Deploying vsphere Solutions, vservices, and ESX Agents vsphere 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

vsphere Update Manager Installation and Administration Guide 17 APR 2018 VMware vsphere 6.7 vsphere Update Manager 6.7

vsphere Update Manager Installation and Administration Guide 17 APR 2018 VMware vsphere 6.7 vsphere Update Manager 6.7 vsphere Update Manager Installation and Administration Guide 17 APR 2018 VMware vsphere 6.7 vsphere Update Manager 6.7 You can find the most up-to-date technical documentation on the VMware website at:

More information

MOVE AntiVirus page-level reference

MOVE AntiVirus page-level reference McAfee MOVE AntiVirus 4.7.0 Interface Reference Guide (McAfee epolicy Orchestrator) MOVE AntiVirus page-level reference General page (Configuration tab) Allows you to configure your McAfee epo details,

More information

Migrating vrealize Automation 6.2 to 7.2

Migrating vrealize Automation 6.2 to 7.2 Migrating vrealize Automation 6.2 to 7.2 vrealize Automation 7.2 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

More information

Inviso SA. Step-by-Step Guide DATE: NOVEMBER 21, 2017

Inviso SA. Step-by-Step Guide DATE: NOVEMBER 21, 2017 Inviso SA Step-by-Step Guide DATE: NOVEMBER 21, 2017 1 Section 1: Introduction Inviso Software Analyzer The Inviso Software Analyzer (InvisoSA.com) is an IT inventory processing service that transforms

More information

vrealize Operations Service Discovery Management Pack 2.1

vrealize Operations Service Discovery Management Pack 2.1 vrealize Operations Service Discovery Management Pack 2.1 You can find the most up-to-date technical documentation on the ware website at: https://docs.vmware.com/ If you have comments about this documentation,

More information

ForeScout Extended Module for Qualys VM

ForeScout Extended Module for Qualys VM ForeScout Extended Module for Qualys VM Version 1.2.1 Table of Contents About the Qualys VM Integration... 3 Additional Qualys VM Documentation... 3 About This Module... 3 Components... 4 Considerations...

More information

Tanium Discover User Guide. Version 2.x.x

Tanium Discover User Guide. Version 2.x.x Tanium Discover User Guide Version 2.x.x June 27, 2017 The information in this document is subject to change without notice. Further, the information provided in this document is provided as is and is

More information

User Guide. Version R95. English

User Guide. Version R95. English Cloud Backup User Guide Version R95 English September 11, 2017 Copyright Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya s Click-Accept EULATOS

More information

Sub-capacity (Virtualization) License Counting Rules. x86 Virtualization Environment. IBM Passport Advantage Software

Sub-capacity (Virtualization) License Counting Rules. x86 Virtualization Environment. IBM Passport Advantage Software IBM Passport Advantage Software Sub-capacity (Virtualization) License Counting Rules x86 Virtualization Environment NOTE: Please use these rules along with the Passport Advantage Agreement.. Index Summary

More information

USER GUIDE. Snow Integration Manager Version 4.3 Release date Installation Configuration Import provider settings Document date

USER GUIDE. Snow Integration Manager Version 4.3 Release date Installation Configuration Import provider settings Document date USER GUIDE Product Snow Integration Manager Version 4.3 Release date 2014-12-18 Content Prerequisites Installation Configuration Import provider settings Document date 2015-01-19 CONTENT ABOUT THIS DOCUMENT...

More information

CloudHealth. AWS and Azure On-Boarding

CloudHealth. AWS and Azure On-Boarding CloudHealth AWS and Azure On-Boarding Contents 1. Enabling AWS Accounts... 3 1.1 Setup Usage & Billing Reports... 3 1.2 Setting Up a Read-Only IAM Role... 3 1.3 CloudTrail Setup... 5 1.4 Cost and Usage

More information

Pure Storage FlashArray Management Pack for VMware vrealize Operations Manager User Guide. (Version with Purity 4.9.

Pure Storage FlashArray Management Pack for VMware vrealize Operations Manager User Guide. (Version with Purity 4.9. Pure Storage FlashArray Management Pack for VMware vrealize Operations Manager User Guide (Version 1.0.139 with Purity 4.9.x or higher) Sunday, November 27, 2016 16:13 Pure Storage FlashArray Management

More information

TECHNICAL DESCRIPTION

TECHNICAL DESCRIPTION TECHNICAL DESCRIPTION Product Snow Inventory Version 5 Release date 2016-09-27 Document date 2017-11-24 CONTENTS 1 Introduction... 3 1.1 What s new?... 3 2 Platform overview... 4 2.1 Architecture... 4

More information

IBM Exam C IBM Tivoli Endpoint Manager V8.1 Implementation Version: 6.0 [ Total Questions: 180 ]

IBM Exam C IBM Tivoli Endpoint Manager V8.1 Implementation Version: 6.0 [ Total Questions: 180 ] s@lm@n IBM Exam C2090-560 IBM Tivoli Endpoint Manager V8.1 Implementation Version: 6.0 [ Total Questions: 180 ] IBM C2090-560 : Practice Test Topic break down Topic No. of Questions Topic 1: Volume A 60

More information

vrealize Operations Management Pack for vrealize Hyperic Release Notes

vrealize Operations Management Pack for vrealize Hyperic Release Notes vrealize Operations Management Pack for vrealize Hyperic Release Notes vrealize Operations Management Pack for Hyperic 6.0.1. Build No. 2470875 Last document update: 23 February 2014. Contents: New Features

More information

Requirements and Milestones Reporting

Requirements and Milestones Reporting IBM BigFix Compliance PCI Add-on Requirements and Milestones Reporting Payment Card Industry Data Security (PCI DSS) 11-17-2016 Table of Contents Introduction...2 Installing the reports manually...3 Updating

More information

IBM BigFix Version 9.5. Patch for Red Hat Enterprise Linux User's Guide IBM

IBM BigFix Version 9.5. Patch for Red Hat Enterprise Linux User's Guide IBM IBM BigFix Version 9.5 Patch for Red Hat Enterprise Linux User's Guide IBM IBM BigFix Version 9.5 Patch for Red Hat Enterprise Linux User's Guide IBM Note Before using this information and the product

More information

Installing and Administering VMware vsphere Update Manager. Update 2 VMware vsphere 5.5 vsphere Update Manager 5.5

Installing and Administering VMware vsphere Update Manager. Update 2 VMware vsphere 5.5 vsphere Update Manager 5.5 Installing and Administering VMware vsphere Update Manager Update 2 VMware vsphere 5.5 vsphere Update Manager 5.5 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/

More information

IBM Tivoli Asset Discovery for Distributed Version 7.2. Installation Guide GI

IBM Tivoli Asset Discovery for Distributed Version 7.2. Installation Guide GI Tivoli IBM Tivoli Asset Discovery for Distributed Version 7.2 Installation Guide GI11-8749-00 Tivoli IBM Tivoli Asset Discovery for Distributed Version 7.2 Installation Guide GI11-8749-00 Installation

More information

IBM Endpoint Manager Version 9.1. Patch Management for AIX User's Guide

IBM Endpoint Manager Version 9.1. Patch Management for AIX User's Guide IBM Endpoint Manager Version 9.1 Patch Management for AIX User's Guide IBM Endpoint Manager Version 9.1 Patch Management for AIX User's Guide Note Before using this information and the product it supports,

More information

Acronis Backup Advanced 11.7 Update 1

Acronis Backup Advanced 11.7 Update 1 Acronis Backup Advanced 11.7 Update 1 APPLIES TO THE FOLLOWING PRODUCTS Advanced for VMware / Hyper-V / RHEV / Citrix XenServer / Oracle VM BACKING UP VIRTUAL MACHINES Copyright Statement Copyright Acronis

More information

USER GUIDE. Snow Integration Manager Version 4.5 Release date Document date

USER GUIDE. Snow Integration Manager Version 4.5 Release date Document date USER GUIDE Product Snow Integration Manager Version 4.5 Release date 2015-10-20 Document date 2015-10-20 CONTENT ABOUT THIS DOCUMENT... 3 PREREQUISITES... 3 INSTALLATION... 4 CONFIGURATION... 7 GENERAL...

More information

Acronis Backup & Recovery 11.5

Acronis Backup & Recovery 11.5 Acronis Backup & Recovery 11.5 Installation Guide Applies to the following editions: Update 2 Advanced Server Server for Windows Virtual Edition Server for Linux Advanced Server SBS Edition Workstation

More information

IaaS Integration for Multi- Machine Services. vrealize Automation 6.2

IaaS Integration for Multi- Machine Services. vrealize Automation 6.2 IaaS Integration for Multi- Machine Services vrealize Automation 6.2 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about

More information

NetWrix VMware Change Reporter Version 3.0 Enterprise Edition Administrator s Guide

NetWrix VMware Change Reporter Version 3.0 Enterprise Edition Administrator s Guide NetWrix VMware Change Reporter Version 3.0 Enterprise Edition Administrator s Guide Table of Contents NetWrix VMware Change Reporter Concepts... 1 Product Editions... 1 How It Works... 2 Deploying Product...

More information

IBM. PDF file of IBM Knowledge Center topics. IBM Operations Analytics for z Systems. Version 2 Release 2

IBM. PDF file of IBM Knowledge Center topics. IBM Operations Analytics for z Systems. Version 2 Release 2 IBM Operations Analytics for z Systems IBM PDF file of IBM Knowledge Center topics Version 2 Release 2 IBM Operations Analytics for z Systems IBM PDF file of IBM Knowledge Center topics Version 2 Release

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.1 Data Protection Guide For VMs and Datastores using the SnapCenter Plug-in for VMware vsphere September 2018 215-13399_B0 doccomments@netapp.com Table of Contents 3 Contents Deciding

More information

User Guide. Version R94. English

User Guide. Version R94. English Cloud Backup User Guide Version R94 English March 30, 2017 Copyright Agreement The purchase and use of all Software and Services is subject to the Agreement as defined in Kaseya s Click-Accept EULATOS

More information

vrealize Operations Management Pack for NSX for vsphere 3.0

vrealize Operations Management Pack for NSX for vsphere 3.0 vrealize Operations Management Pack for NSX for vsphere 3.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

More information

Installing and Configuring vcenter Multi-Hypervisor Manager

Installing and Configuring vcenter Multi-Hypervisor Manager Installing and Configuring vcenter Multi-Hypervisor Manager vcenter Server 5.1 vcenter Multi-Hypervisor Manager 1.1.2 This document supports the version of each product listed and supports all subsequent

More information

vcloud Director Administrator's Guide vcloud Director 8.10

vcloud Director Administrator's Guide vcloud Director 8.10 vcloud Director Administrator's Guide vcloud Director 8.10 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation,

More information

VMware Skyline Collector Installation and Configuration Guide. VMware Skyline Collector 2.0

VMware Skyline Collector Installation and Configuration Guide. VMware Skyline Collector 2.0 VMware Skyline Collector Installation and Configuration Guide VMware Skyline Collector 2.0 You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If

More information

Developing and Deploying vsphere Solutions, vservices, and ESX Agents

Developing and Deploying vsphere Solutions, vservices, and ESX Agents Developing and Deploying vsphere Solutions, vservices, and ESX Agents vsphere 5.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

More information

Citrix SCOM Management Pack 1.4 for ShareFile

Citrix SCOM Management Pack 1.4 for ShareFile Citrix SCOM Management Pack 1.4 for ShareFile Nov 27, 2017 Citrix SCOM Management Pack for ShareFile is an availability and performance management solution that extends end-toend service monitoring capabilities

More information

Citrix SCOM Management Pack for StoreFront

Citrix SCOM Management Pack for StoreFront Citrix SCOM Management Pack for StoreFront Aug 14, 2017 Citrix SCOM Management Pack 1.12 for StoreFront Citrix SCOM Management Pack 1.11 for StoreFront Citrix SCOM Management Pack 1.9 for StoreFront Citrix

More information

Forescout. Controller Plugin. Configuration Guide. Version 1.1

Forescout. Controller Plugin. Configuration Guide. Version 1.1 Forescout Network Module: Centralized Network Controller Plugin Version 1.1 Contact Information Forescout Technologies, Inc. 190 West Tasman Drive San Jose, CA 95134 USA https://www.forescout.com/support/

More information

SnapCenter Software 4.1. Administration Guide. December _C0 Updated for 4.1.1

SnapCenter Software 4.1. Administration Guide. December _C0 Updated for 4.1.1 SnapCenter Software 4.1 Administration Guide December 2018 215-13391_C0 doccomments@netapp.com Updated for 4.1.1 Table of Contents 3 Contents Deciding whether to read the SnapCenter Administration information...

More information

Log & Event Manager UPGRADE GUIDE. Version Last Updated: Thursday, May 25, 2017

Log & Event Manager UPGRADE GUIDE. Version Last Updated: Thursday, May 25, 2017 UPGRADE GUIDE Log & Event Manager Version 6.3.1 Last Updated: Thursday, May 25, 2017 Retrieve the latest version from: https://support.solarwinds.com/success_center/log_event_manager_(lem)/lem_documentation

More information

vrealize Infrastructure Navigator Installation and Configuration Guide

vrealize Infrastructure Navigator Installation and Configuration Guide vrealize Infrastructure Navigator Installation and Configuration Guide vrealize Infrastructure Navigator 5.8.5 This document supports the version of each product listed and supports all subsequent versions

More information

IBM License Metric Tool 9.0 Installation

IBM License Metric Tool 9.0 Installation ILMT Central Team IBM License Metric Tool 9.0 Installation Questions & Answers Welcome This is the twenty second Q&A event prepared by the ILMT Central Team We concentrate on License Metric Tool version

More information

ForeScout Extended Module for Tenable Vulnerability Management

ForeScout Extended Module for Tenable Vulnerability Management ForeScout Extended Module for Tenable Vulnerability Management Version 2.7.1 Table of Contents About Tenable Vulnerability Management Module... 4 Compatible Tenable Vulnerability Products... 4 About Support

More information

Laserfiche Rio 10.3: Deployment Guide. White Paper

Laserfiche Rio 10.3: Deployment Guide. White Paper Laserfiche Rio 10.3: Deployment Guide White Paper January 2018 Table of Contents How Laserfiche Licensing Works... 4 Types of Licenses... 4 Named User Licenses... 4 WebLink Public Portal Licenses... 6

More information

Veeam ONE. Version 8.0. User Guide for VMware vsphere Environments

Veeam ONE. Version 8.0. User Guide for VMware vsphere Environments Veeam ONE Version 8.0 User Guide for VMware vsphere Environments July, 2015 2015 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication

More information

vrealize Operations Manager Customization and Administration Guide vrealize Operations Manager 6.4

vrealize Operations Manager Customization and Administration Guide vrealize Operations Manager 6.4 vrealize Operations Manager Customization and Administration Guide vrealize Operations Manager 6.4 vrealize Operations Manager Customization and Administration Guide You can find the most up-to-date technical

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1.1 Client Installation and User's Guide SC27-2809-04 IBM Tivoli Storage Manager FastBack for Workstations Version 7.1.1 Client Installation

More information

IBM Spectrum Protect Plus Version Installation and User's Guide IBM

IBM Spectrum Protect Plus Version Installation and User's Guide IBM IBM Spectrum Protect Plus Version 10.1.1 Installation and User's Guide IBM Note: Before you use this information and the product it supports, read the information in Notices on page 119. Third edition

More information

VMware vrealize Operations for Horizon Administration

VMware vrealize Operations for Horizon Administration VMware vrealize Operations for Horizon Administration vrealize Operations for Horizon 6.3 This document supports the version of each product listed and supports all subsequent versions until the document

More information

Double-Take Move. Double-Take Move System Center Integration Toolkit User's Guide

Double-Take Move. Double-Take Move System Center Integration Toolkit User's Guide Double-Take Move Double-Take Move System Center Integration Toolkit User's Guide Notices Double-Take Move System Center Integration Toolkit User's Guide Version 7.1, Tuesday, March 03, 2015 Check the Vision

More information

Client Installation and User's Guide

Client Installation and User's Guide IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Client Installation and User's Guide SC27-2809-03 IBM Tivoli Storage Manager FastBack for Workstations Version 7.1 Client Installation

More information

ForeScout CounterACT. Plugin. Configuration Guide. Version 2.1

ForeScout CounterACT. Plugin. Configuration Guide. Version 2.1 ForeScout CounterACT Hybrid Cloud Module: VMware vsphere Plugin Version 2.1 Table of Contents About VMware vsphere Integration... 4 Use Cases... 4 Additional VMware Documentation... 4 About this Plugin...

More information

Qualys Cloud Platform (VM, PC) v8.x Release Notes

Qualys Cloud Platform (VM, PC) v8.x Release Notes Qualys Cloud Platform (VM, PC) v8.x Release Notes Version 8.16 December 14, 2018 This new release of the Qualys Cloud Platform (VM, PC) includes improvements to Vulnerability Management and Policy Compliance.

More information

Administration GUIDE. Virtual Server idataagent (VMware) Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 225

Administration GUIDE. Virtual Server idataagent (VMware) Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 225 Administration GUIDE Virtual Server idataagent (VMware) Published On: 11/19/2013 V10 Service Pack 4A Page 1 of 225 User Guide - Virtual Server idataagent (VMware) Table of Contents System Requirements

More information

Qualys Cloud Platform (VM, PC) v8.x Release Notes

Qualys Cloud Platform (VM, PC) v8.x Release Notes Qualys Cloud Platform (VM, PC) v8.x Release Notes Version 8.18 March 11, 2019 This new release of the Qualys Cloud Platform (VM, PC) includes improvements to Vulnerability Management and Policy Compliance.

More information

vrealize Operations Management Pack for NSX for vsphere 3.5 Release Notes

vrealize Operations Management Pack for NSX for vsphere 3.5 Release Notes vrealize Operations Management Pack for NSX for vsphere 3.5 Release Notes Build: 4602207 Last document update: 14 November, 2016 Contents: Before You Install the Management Pack Upgrading from the Management

More information

Using VMware vsphere Web Client with Symantec ApplicationHA and Symantec Cluster Server (VCS)

Using VMware vsphere Web Client with Symantec ApplicationHA and Symantec Cluster Server (VCS) Using VMware vsphere Web Client with Symantec ApplicationHA and Symantec Cluster Server (VCS) September 2014 Since v5.1 of vsphere, VMware have focused on providing web based management for the vsphere

More information

Platform Services Controller Administration. Update 1 Modified on 11 DEC 2018 VMware vsphere 6.7 VMware ESXi 6.7 vcenter Server 6.

Platform Services Controller Administration. Update 1 Modified on 11 DEC 2018 VMware vsphere 6.7 VMware ESXi 6.7 vcenter Server 6. Platform Services Controller Administration Update 1 Modified on 11 DEC 2018 VMware vsphere 6.7 VMware ESXi 6.7 vcenter Server 6.7 You can find the most up-to-date technical documentation on the VMware

More information

Data Protection Guide

Data Protection Guide SnapCenter Software 4.0 Data Protection Guide For VMs and Datastores using the SnapCenter Plug-in for VMware vsphere March 2018 215-12931_C0 doccomments@netapp.com Table of Contents 3 Contents Deciding

More information

vrealize Operations Management Pack for NSX for vsphere Release Notes

vrealize Operations Management Pack for NSX for vsphere Release Notes vrealize Operations Management Pack for NSX for vsphere 3.1.1 Release Notes Build: 4247401 Last document update: 24 August 2016 Contents: Upgrading from the Management Pack for NSX for vsphere 2.0 What's

More information

1.0. Quest Enterprise Reporter Discovery Manager USER GUIDE

1.0. Quest Enterprise Reporter Discovery Manager USER GUIDE 1.0 Quest Enterprise Reporter Discovery Manager USER GUIDE 2012 Quest Software. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide

More information

ForeScout Extended Module for Symantec Endpoint Protection

ForeScout Extended Module for Symantec Endpoint Protection ForeScout Extended Module for Symantec Endpoint Protection Version 1.0.0 Table of Contents About the Symantec Endpoint Protection Integration... 4 Use Cases... 4 Additional Symantec Endpoint Protection

More information

Goliath Performance Monitor v11.7 POC Install Guide

Goliath Performance Monitor v11.7 POC Install Guide Goliath Performance Monitor v11.7 POC Install Guide Goliath Performance Monitor Proof of Concept Limitations Goliath Performance Monitor Proof of Concepts (POC) will be limited to monitoring 5 Hypervisor

More information

Active System Manager Version 8.0 User s Guide

Active System Manager Version 8.0 User s Guide Active System Manager Version 8.0 User s Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either

More information

IBM Control Desk 7.5.3

IBM Control Desk 7.5.3 IBM IBM Control Desk 7.5.3 Integrating with IBM Endpoint Manager for Software Deployment Version 1.0 1 Copyright International Business Machines Corporation 2014. US Government Users Restricted Rights

More information

Configuring ApplicationHA in VMware SRM 5.1 environment

Configuring ApplicationHA in VMware SRM 5.1 environment Configuring ApplicationHA in VMware SRM 5.1 environment Windows Server 2003 and 2003 R2, Windows Server 2008 and 2008 R2 6.0 September 2013 Contents Chapter 1 About the ApplicationHA support for VMware

More information

HYCU SCOM Management Pack for F5 BIG-IP

HYCU SCOM Management Pack for F5 BIG-IP USER GUIDE HYCU SCOM Management Pack for F5 BIG-IP Product version: 5.6 Product release date: November 2018 Document edition: First Legal notices Copyright notice 2015-2018 HYCU. All rights reserved. This

More information

Acronis Data Cloud Version 7.8

Acronis Data Cloud Version 7.8 Acronis Data Cloud Version 7.8 PARTNER'S GUIDE Revision: 10/5/2018 Table of contents 1 About this document...3 2 About Acronis Data Cloud...3 2.1 Services and offerings... 3 2.2 User accounts and tenants...

More information

What s New. New and Enhanced Features in NetSupport DNA v4. Welcome Dashboard. Auto Discovery. Platform Support

What s New. New and Enhanced Features in NetSupport DNA v4. Welcome Dashboard. Auto Discovery. Platform Support What s New New and Enhanced Features in NetSupport DNA v4 Welcome to NetSupport DNA version 4, the fresh approach to IT Asset Management. With any new release, the focus is not only on introducing innovative

More information

Tanium Discover User Guide. Version 2.5.1

Tanium Discover User Guide. Version 2.5.1 Tanium Discover User Guide Version 2.5.1 May 07, 2018 The information in this document is subject to change without notice. Further, the information provided in this document is provided as is and is believed

More information