IBM BigFix Inventory: Migration Cookbook A Practical ...

60
IBM BigFix Inventory Version 9 Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use Analysis 2.2 IBM

Transcript of IBM BigFix Inventory: Migration Cookbook A Practical ...

Page 1: IBM BigFix Inventory: Migration Cookbook A Practical ...

IBM BigFix InventoryVersion 9

Migration CookbookA Practical Implementation Guide for Migrating Data

from Software Use Analysis 2.2

IBM

Page 2: IBM BigFix Inventory: Migration Cookbook A Practical ...

Migration cookbook. A Practical Implementation Guide for Migrating Data from BigFix Inventory 2.2

This edition applies to IBM BigFix Inventory 9.2.3 (product number 5725-F57) and to all subsequent releases andmodifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2002, 2016.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Page 3: IBM BigFix Inventory: Migration Cookbook A Practical ...

Contents

Migration cookbook . . . . . . . . . 1Migration overview and requirements . . . . . . 1Data objects to be migrated . . . . . . . . . 3

Migration limitations . . . . . . . . . . 5Migration checklist . . . . . . . . . . . . 6Dividing endpoints into computer groups . . . . 6

Dedicated computer groups for phased endpointmigration . . . . . . . . . . . . . . 6Creating manual computer groups . . . . . . 7

Grouping migrated and unmigrated endpoints . . . 8Enabling the BigFix Inventory V9.2 Fixlet site . . . 11Applying the migration patch . . . . . . . . 12Installing BigFix Inventory V9.2 . . . . . . . 16Migrating endpoints . . . . . . . . . . . 23Verifying that endpoints are migrated . . . . . 29

Identifying migrated endpoints in BigFixInventory V9.2 . . . . . . . . . . . . 30

Manually re-creating parent computer groups inBigFix Inventory V9.2 . . . . . . . . . . . 32

Setting up the Admin_PCs role . . . . . . . . 33Migrating data objects . . . . . . . . . . . 34

Step 1: Obtaining the user token . . . . . . 35Step 2: Editing the migration configuration file 35Step 3: Simulating data migration . . . . . . 36Step 4: Verifying the simulation. . . . . . . 37Step 5: Running the migration . . . . . . . 41

Verifying the migration . . . . . . . . . . 42Verifying the csv reports . . . . . . . . . 42Verifying migrated data objects in product userinterfaces . . . . . . . . . . . . . . 46

Notices . . . . . . . . . . . . . . 51Trademarks . . . . . . . . . . . . . . 53Terms and conditions for product documentation. . 53

© Copyright IBM Corp. 2002, 2016 iii

Page 4: IBM BigFix Inventory: Migration Cookbook A Practical ...

iv IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use Analysis

2.2

Page 5: IBM BigFix Inventory: Migration Cookbook A Practical ...

Migration cookbook

Migration from Software Use Analysis V2.2 to BigFix Inventory V9.2 requires that you install the newserver and connect it to the same data source as Software Use Analysis V2.2. You can then migrate theendpoints and custom data objects between these two coexisting applications. A direct upgrade fromSoftware Use Analysis V2.2 to BigFix Inventory V9.2 is not supported because of differences between thetwo applications.

Migration overview and requirementsReview the requirements for the migration and the example Software Use Analysis V2.2 infrastructurethat a hypothetical company might want to migrate to BigFix Inventory version V9.2.

Overview

To migrate from Software Use Analysis V2.2 to BigFix Inventory V9.2, you must first install the V9.2server. While migrating, the servers are connected to a common IBM BigFix platform, which givesSoftware Use Analysis V2.2 access to Fixlets that are necessary to migrate your endpoints.

The migration does not limit the number of endpoints that you can migrate at once, but the easiest wayis to divide your environment into computer groups and migrate your endpoints group by group. Datathat was collected from your endpoints before the migration is frozen in Software Use Analysis V2.2, andyou can access it at any time. This data is not migrated because it can be collected by the new scans fromBigFix Inventory V9.2. In other words, historical data is stored in Software Use Analysis V2.2, whereas allcurrent data is from now on saved in BigFix Inventory V9.2. After you migrate the first group ofendpoints, you can proceed to migrating another one until your whole environment is reporting to thenew version.

Raw data and scan results are not migrated, but you can migrate the listed customizations that arespecific to your environment. The customizations include computer groups, users, custom signatures,contracts and contract custom fields.

Requirements

Table 1. Requirements for the migration

Requirement Details

IBM BigFix(Endpoint Manager)platform

IBM BigFix V9.x, and all supported databases.

Earlier BigFix server versions must be upgraded to version V9.x. For more information, seeUpgrading on Windows systems and Upgrading on Linux systems.

Supported SoftwareUse Analysis andBigFix Inventoryversions

v Software Use Analysis V2.2 patch 6 (2.2.150) or later. Earlier versions of Software UseAnalysis V2.2 must be upgraded to at least patch 6.

v BigFix Inventory 9.2.0.2, or later.

User permissionsThe migration tool requires the following access:

v To the database for the Software Use Analysis V2.2 server.

v To a BigFix Inventory V9.2 user token to access the BigFix Inventory V9.2 system via theREST APIs. You can obtain the token from the UI by going to Account > Profile.

Site subscription During the migration, you subscribe V2.2 endpoints to the IBM BigFix Inventory site. Theendpoints must also remain subscribed to the IBM Software Inventory site until the end ofmigration.

© Copyright IBM Corp. 2002, 2016 1

Page 6: IBM BigFix Inventory: Migration Cookbook A Practical ...

Hypothetical infrastructure

The hypothetical Software Use Analysis infrastructure is divided into two parent computer groups, whichare Software Use Analysis computer groups. One computer group comprises servers while the othergroup comprises desktop computers (including a notebook). Each of the parent computer groups has twochild computer groups that reflect another functional division, such as platform (Windows and Linux)and departments (engineers and the office).

Computer groups

This migration cookbook mentions two types of computer groups, which are independent.

The hypothetical infrastructure with parent and child computer groups

9.158.143.249

Desktop computer (Windows)

• Autodesk AutoCAD LT 2016

• Nero 2015 (custom signature)

9.167.43.29

Desktop computer (Windows)

• MS Visio Professional 2013

• MS Office Professional Plus 2013

• Soda PDF 7 (custom signature)

9.156.46.51

Desktop computer (Windows)

• Autodesk AutoCAD LT 2016

• Nero 2015 (custom signature)

9.167.40.170

BigFix Inventory V9

Computer group 1:

User:

Servers

Administrator

9.158.142.240

File and print

server

RedHat LinuxDatabase for IBM BigFix 9.2

and SUA 2.2

• MS SQL Server 2012

9.156.47.107

IBM BigFix 9.2 (Endpoint Manager)

and Software Use Analysis 2.2

Database

for BigFix Inventory V9

• MS SQL Server 2008

Computer group 2:

User:

PCs

Admin_PCs

Data migration:

JDBC over the network

9.167.42.209

Laptop (Windows):

• MS Office Professional Plus 2013

• MS Project Professional 2013

• AVG PC TuneUp 2015 (custom signature)

Child computer group:

PCs_engineers

Child computer group:

PCs_office

Child computer group:

Servers_Linux

Child computer group:

Servers_Windows

2 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use Analysis

2.2

Page 7: IBM BigFix Inventory: Migration Cookbook A Practical ...

Software Use Analysis or BigFix Inventory computer groupsThis type of computer groups is used to:v Ensure that each user views reports only for relevant computers.v Assign contracts to appropriate sets of computers.

BigFix computer groupsThese computer groups are used to:v Manage the infrastructure.v Assign computers to different Fixlet® sites.v Run Fixlets against selected endpoints.

Important: Groups that are created in Software Use Analysis or BigFix Inventory are not automaticallycopied to BigFix and the other way round.

Data objects to be migratedData objects that you can migrate are users, custom software signatures, computer groups, contracts, andcontract custom fields.

Computer groups

The following computer groups from Software Use Analysis V2.2 are going to be migrated to BigFixInventory V9.2.

If you already created a group in BigFix Inventory V9.2, migration will not create a duplicate computergroup.

Note: You must manually re-create in your BigFix Inventory V9.2 all the custom computer properties thatare used as conditions for computer groups in Software Use Analysis V2.2.

Users

Only one Software Use Analysis V2.2 user is going to be migrated to BigFix Inventory V9.2 during dataobjects migration.

Table 2. Users created in Software Use Analysis V2.2 that are going to be migrated

User Authentication Migrated Description

Administrator Password No Main administrator responsible for the whole infrastructure. Thisadministrator's main focus is the company servers. As this user iscreated by the BigFix Inventory V9.2 installation process, it will not bemigrated.

Admin_PCs Password Yes Supporting administrator whose main focus is company desktopcomputers.

Migration cookbook 3

Page 8: IBM BigFix Inventory: Migration Cookbook A Practical ...

Custom signatures

The following custom signatures from Software Use Analysis V2.2 are going to be migrated to BigFixInventory V9.2.

Contract custom fields

The following contract custom fields from Software Use Analysis V2.2 are going to be migrated to BigFixInventory V9.2.

Contracts

The following contracts that are defined in Software Use Analysis V2.2 are to be migrated to BigFixInventory V9.2.

4 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use Analysis

2.2

Page 9: IBM BigFix Inventory: Migration Cookbook A Practical ...

Migration limitationsReview the migration limitations before you start migrating your clients and data objects.

Computer groupsv Software Use Analysis V2.2 computer groups that use an ID filter (the ID of the computer) will not be

migrated to BigFix Inventory V9.2.v Software Use Analysis V2.2 computer groups that use data source filters will be migrated only if the

same data sources are defined in your Software Use Analysis V2.2 and V9.2 deployments.v Descendant computer groups will be migrated only if their parent computer group was successfully

migrated or manually created in BigFix Inventory V9.2.v If a computer group contains, in its definition, data source groups that are related to the BigFix server

that is not defined in BigFix Inventory V9.2, that particular computer group will not be migrated.v If you have a Software Use Analysis V2.2 computer group that uses a custom computer property filter

that you did not define in BigFix Inventory V9.2, the computer group cannot be migrated.

Note: If you already created a group in BigFix Inventory V9.2, migration will not create a duplicatecomputer group.

Usersv Software Use Analysis V2.2 users with authentication methods other than password are not migrated.v Users that were manually added to BigFix Inventory V9.2 before running the migration tool will not be

processed during migration.v Migration of LDAP users is not supported, so you must manually create the LDAP users in BigFix

Inventory V9.2.

Important: When you are creating Active Directory users in BigFix Inventory V9.2 you must includethe domain name in the user name, for example [email protected]. This limitation causes amismatch that prevents contracts from being migrated. You can resolve the mismatch by creating amatching password-authenticated user that matches the Active Directory user name that is used inSoftware Use Analysis V2.2.

Custom signaturesv The signature GUID (globally unique identifier) from Software Use Analysis V2.2 is used as the GUID

in BigFix Inventory V9.2. If the GUID exists in BigFix Inventory V9.2, the custom signature will not bemigrated.

Contract custom fieldsv All contract custom fields that are used in contract definitions must exist in BigFix Inventory V9.2.v All contract custom fields that are required in BigFix Inventory V9.2, must be defined also in Software

Use Analysis V2.2.v If you manually created a contract custom field in BigFix Inventory V9.2, the migration tool will not

change the manually created custom field.

Contractsv If you defined a contract in BigFix Inventory V9.2 with the same name as a Software Use Analysis V2.2

contract, it will not be migrated.v All users who created contracts in Software Use Analysis V2.2 (including LDAP users) must exist in

BigFix Inventory V9.2 before migrating contracts. If the user does not exist, the contract will not bemigrated.

v All computer groups for the contracts must exist in BigFix Inventory V9.2 before migrating contracts. Ifthe computer group does not exist in BigFix Inventory V9.2, the contract will not be migrated.

Migration cookbook 5

Page 10: IBM BigFix Inventory: Migration Cookbook A Practical ...

v The software catalog that is used by BigFix Inventory V9.2 must have the softwaretitle/version/release associated with the Software Use Analysis V2.2 contract. If the contract's softwareis not in the BigFix Inventory V9.2 catalog, the contract will not be migrated.

Migration checklistUse the following checklist to ensure that you complete all the necessary steps.

__ 1. Plan the migration.

Ensure that the computer on which you plan to install BigFix Inventory V9.2 fulfills all the hardware andsoftware requirements. Also, check the Supported operating systems for the servers.

__ 2. Upgrade Software Use Analysis to version V2.2 patch 6 or higher. The instructions for upgrading toSoftware Use Analysis V2.2 patch 10 are available on the BigFix Inventory wiki.

__ 3. Create manual computer groups.

__ 4. Group migrated and unmigrated endpoints.

__ 5. Enable the BigFix Inventory V9.2 Fixlet site.

__ 6. Apply the migration patch.

__ 7. Install the BigFix Inventory V9.2 server.

__ 8. Migrate your endpoints.

__ 9. Verify that the endpoints are migrated.

__ 10. Manually re-create parent computer groups in BigFix Inventory V9.2.

__ 11. Set up the Admin_PCs role.

__ 12. Migrate data objects.

__ a. Obtain the user token.

__ b. Edit the migration configuration file.

__ c. Simulate data migration.

__ d. Verify the simulation.

__ e. Run the migration.

__ 13. Verify the migration.

__ a. Verify the csv reports.

__ b. Verify migrated data objects in product user interfaces.

Dividing endpoints into computer groupsYou can use BigFix computer groups to incrementally migrate endpoints from Software Use Analysis V2.2to V9.2.

About this task

If you use computer groups, the migration of endpoints can be done one group at a time. When youmigrate endpoints to your V9.2 environment, as described in Migrating endpoints, select the endpointsby group.

Dedicated computer groups for phased endpoint migrationIf you are migrating several endpoints, you can divide them into BigFix computer groups and thenmigrate one group at a time. This approach makes verification easier and less time-consuming. The sizeof a group depends on the number of software instances that are installed on your endpoints.

The following computer groups are created for the phased migration.

PCs_IEM_cgroupThis BigFix group mirrors the Software Use Analysis computer group called PCs.

6 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use Analysis

2.2

Page 11: IBM BigFix Inventory: Migration Cookbook A Practical ...

Servers_IEM_cgroupThis BigFix group mirrors the Software Use Analysis computer group Servers.

Creating manual computer groupsUse the BigFix console to create computer groups for the phased migration.

Procedure1. Click the Computers icon in the Domain Panel navigation tree.2. In the List pane, press the Control button and click the computers you want to group.

3. Right-click the computers that you choose and select Add to Manual Group from the menu.

4. From the Select Manual Computer Group dialog, you can choose to add your selected computers toan existing group or create a new group for them.

Migration cookbook 7

Page 12: IBM BigFix Inventory: Migration Cookbook A Practical ...

This computer group is added under the Computer Group icon in the navigation tree and helps youto subdivide your networked computers down into more reasonably sized chunks.

5. Repeat this step for the other computer group.

Results

You have created two BigFix computer groups for phased endpoint migration.

Grouping migrated and unmigrated endpointsYou create two computer groups to group endpoints that are migrated and endpoints that are not yetmigrated. After you migrate the first group of endpoints, they are moved from one group to another.These two groups make it easier to select endpoints when you need to run certain actions.

About this task

These two computer groups do not affect any computer groups that you already have in IBM BigFix. Anendpoint can be in two computer groups at once. These two computers groups help you recognize the

8 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use Analysis

2.2

Page 13: IBM BigFix Inventory: Migration Cookbook A Practical ...

migrated and unmigrated endpoints, and also to target them by certain actions, such as software scans.

Procedure1. Log in to the IBM BigFix console, and from the menu bar select Tools > Create New Automatic

Computer Group.

2. Enter the name Migrated Computers for the group name, and select Relevance Expression and is truefrom the Include computers with the following property list.

This group uses the Migrated_to_BFI property to group endpoints that are migrated.3. Click Edit Relevance, enter the following text, and click OK.

exists settings whose (name of it equals "Migrated_to_BFI" AND value of it = "1") of client

4. From the IBM BigFix console menu bar, select Tools > Create New Automatic Computer Group.5. Enter the name Unmigrated 2.2 Computers for the group name, and select Relevance Expression and

is true from the Include computers with the following property list.

Migration cookbook 9

Page 14: IBM BigFix Inventory: Migration Cookbook A Practical ...

This group uses the Migrated_to_BFI property to group endpoints that are not migrated and that stillreport to Software Use Analysis 2.2.

6. Click Edit Relevance, enter the following text, and click OK.not (exists settings whose (name of it equals "Migrated_to_BFI" AND value of it = "1") ofclient)

Results

You created two computer groups. At this point, all your computers are in the Unmigrated 2.2 Computersgroup.

10 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 15: IBM BigFix Inventory: Migration Cookbook A Practical ...

Enabling the BigFix Inventory V9.2 Fixlet siteEnable the BigFix Inventory V9.2 Fixlet site to get access to Fixlets, tasks, and analyses that are requiredto work with the application.

Before you begin

Your IBM BigFix server must have Internet access if you want to enable the Fixlet site and download thecontent. If your server is in a separated network, see Downloading files in air-gapped environments.

About this task

The Fixlet site contains Fixlets, tasks, and analyses that are used to perform various actions related toBigFix Inventory. You can use them to download the BigFix Inventory installer, configure and initiatesoftware scans, or update the software catalog.

Procedure1. Log in to the IBM BigFix console.2. In the bottom-left corner of the console, click BigFix Management.

3. In the left navigation bar, click License Overview.

Migration cookbook 11

Page 16: IBM BigFix Inventory: Migration Cookbook A Practical ...

4. In the pane on the right, locate the entry called BigFix Inventory and accept the license agreement.

Applying the migration patchYou apply the migration patch to your Software Use Analysis V2.2 to make the changes that arenecessary to complete the migration.

Procedure1. Log in to the IBM BigFix console.2. Subscribe your Software Use Analysis V2.2 server to the new Fixlet site. Until you complete the

migration, the server remains subscribed to two Fixlet sites.a. In the navigation tree, click Sites > External Sites > IBM BigFix Inventory.b. In the Computer Subscriptions tab, select Computers which match the condition below, and

specify conditions to include your Software Use Analysis V2.2 server.

c. Click Save Changes.3. Download and apply the migration patch to Software Use Analysis V2.2. This step is required only

for Software Use Analysis V2.2 patch 6, 7, or 8. Starting from patch 10, the migration patch is installedwith the server and this step can be omitted.The patch replaces the scan_file.rb and raw_datasource_file.rb files with new versions of the files.a. In the IBM BigFix console navigation bar, click Sites > External Sites > IBM BigFix Inventory >

Fixlets and Tasks.b. In the upper right pane, select Download the endpoints migration patch for SUA 2.2, and in the

lower pane click Take Action.

12 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 17: IBM BigFix Inventory: Migration Cookbook A Practical ...

c. Select the Software Use Analysis V2.2 server as the target computer.

d. Click the Execution tab, specify the time when the task is to run and click OK.

Migration cookbook 13

Page 18: IBM BigFix Inventory: Migration Cookbook A Practical ...

Note: The Software Use Analysis V2.2 server is stopped temporarily, and will be restarted afterthe patch is applied.

Important: If the Software Use Analysis V2.2 service (TEMA) is running under the LocalSystemaccount, the patch is installed automatically. The original scan_file.rb andraw_datasource_file.rb files are backed up to the SUA2.2_install_dir\sua9_migration\sua2_scan_file_backup_copy directory, and the new files are applied. If the TEMA service isrunning under any other account, this task downloads the scan_file.rb andraw_datasource_file.rb files to the SUA2.2_install_dir\sua_migration\sua9_downloaded_scan_file directory. For more information on how to install the patch manually,see step 4 in the topic Applying the migration patch, which is available in IBM® KnowledgeCenter.

4. Create a computer property in Software Use Analysis V2.2 that can be used to identify migratedendpoints.a. Log in to Software Use Analysis V2.2.b. In the navigation bar click Management > Computer Properties.

14 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 19: IBM BigFix Inventory: Migration Cookbook A Practical ...

c. On the new page, click New.

d. In the Create Computer Property pane, specify the name of the property by selecting theMigrated to BFI property from the Data Source Property list. Click Create.

e. Import scan data to enable the new property, in the navigation bar click Management > Imports,and click Import Now.

Migration cookbook 15

Page 20: IBM BigFix Inventory: Migration Cookbook A Practical ...

Installing BigFix Inventory V9.2You install BigFix Inventory V9.2 and configure database connections to use the same data source as thedata source used for your Software Use Analysis V2.2 installation.

Before you begin

Ensure that MS SQL Server is installed and running on the target computer.

About this task

For more information about installing the BigFix Inventory server, see Installing BigFix Inventory.

Procedure1. Log in to the IBM BigFix console.2. Subscribe an endpoint on which you want to install BigFix Inventory V9.2 to the new Fixlet site.

Tip: It can be the same endpoint as your Software Use Analysis V2.2 server if it fulfills all hardwarerequirements.a. In the navigation tree, click Sites > External Sites > IBM BigFix Inventory.b. In the Computer Subscriptions tab, select Computers which match any of the conditions below,

and specify conditions to include the endpoint.

c. Click Save.3. Download the BigFix Inventory installer.

a. In the navigation bar of the console, click Sites > External Sites > IBM BigFix Inventory >Dashboards > IBM BigFix Inventory.

16 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 21: IBM BigFix Inventory: Migration Cookbook A Practical ...

b. Select a computer to which you want to download the installer, and click Deploy Installer.

A progress bar is being displayed.

c. When the download completes, click Continue.d. Go to the computer where you downloaded the installer. The BigFix Inventory installer was

downloaded to the following location.BES Installers\BFI_installer. The default location of BES Installers is C:\Program Files(x86)\BigFix Enterprise\BES Installers.

4. Extract the contents of the compressed file: Right click the zip file and click Extract All.5. Install BigFix Inventory V9.2 in interactive mode.

a. Right-click the setup-server-windows-x86_64.bat file and click Run as administrator.

Migration cookbook 17

Page 22: IBM BigFix Inventory: Migration Cookbook A Practical ...

b. A progress bar is first displayed and the splash screen opens. Select the language of theinstallation and click OK.

c. The installation wizard starts, and the welcome panel opens. Click Next.d. Read the terms of the license agreement, and if you accept them all, click Next.

18 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 23: IBM BigFix Inventory: Migration Cookbook A Practical ...

e. On the Installation Prerequisites pane, click Next. The installer verifies whether your computer hasthe necessary prerequisites installed.

f. Accept the default or provide the server installation path of your choice. Click Next.

g. Accept the default port or provide the port number of your choice. Click Next.

Migration cookbook 19

Page 24: IBM BigFix Inventory: Migration Cookbook A Practical ...

h. On the last panel, specify the user account for running the application service, and click Next.

i. On the Preinstallation Summary information pane, review the summary information and clickInstall.

20 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 25: IBM BigFix Inventory: Migration Cookbook A Practical ...

j. When the installation is complete, click Done to exit the wizard.

6. Configure the connections to the IBM BigFix server and the databases.a. Create a BigFix Inventory database. Enter the host name of the database server, the name of the

application database and select the authentication mode and click Create.The database instance is being created. In this example, SQL Server Authentication is chosen. Inthis mode, you authenticate with an SQL Server user. The user must have either the dbcreator orsysadmin role in SQL Server.

Migration cookbook 21

Page 26: IBM BigFix Inventory: Migration Cookbook A Practical ...

b. Create the BigFix Inventory administrator: Provide the login and password for the administrationuser and click Create.

c. In the first column, provide the connection parameters to the IBM BigFix database. The databasestores information about the endpoints and data that they discover. Specify the host, port, databasename, and credentials of the user that can access the IBM BigFix server database.

d. In the second column, configure the connection to the IBM BigFix server. The host name or IPaddress, and the API port number are automatically retrieved from the database. Specify only theadministrative user that you created while installing IBM BigFix (by default, IEMAdmin).

e. Optional: Configure the connection to the Web Reports database. Specify the database type, hostname, database name, and credentials of the Web Reports database user.

22 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 27: IBM BigFix Inventory: Migration Cookbook A Practical ...

f. Click Create to create the connections. Connections to the databases are created and configured. Anew page opens and a message about the data import is displayed.

7. Click Import Now to run the initial import.

Migrating endpointsTo migrate your endpoints to BigFix Inventory V9.2, you suspend the collection of data into Software UseAnalysis V2.2, mark the endpoints to migrate, and then enable the collection of data into V9.2 by startingthe new scans.

About this task

You can migrate single endpoints or all of them at once, but if your environment is divided intocomputer groups, use them to migrate your endpoints group by group. Such an approach gives you morecontrol over the migration and if you decide to postpone it for some computer groups, you can restartthe collection of data into Software Use Analysis V2.2 for chosen endpoints by resuming the scans.

Migration cookbook 23

Page 28: IBM BigFix Inventory: Migration Cookbook A Practical ...

Stop all actions

for the group

( )

first

Servers_IEM_cgroup

Subscribe the first

group to the BFI V9

Fixlet site

Overview of endpoint migration

Migrate

the endpoints

from the first group

Install scanners

and run scans

on the migrated

endpoints

Run a data

import

Stop all actions

for the second

computer group

( )PCs_IEM_cgroup

Subscribe the second

group to the BFI V9

Fixlet site

Migrate

the endpoints

from the second group

Install scanners

and run scans

on the migrated

endpoints

Run a data

import

Activate

the migration

analysis

Migrate

the

group

first

Migrate

the

group

second

For more information about creating computer groups, see “Dividing endpoints into computer groups”on page 6.

Procedure1. Activate the migration analysis to be able to recognize which endpoints are migrated.

a. In the IBM BigFix Inventory v9 Fixlet site, click Analyses.b. Select the SUA 2.2 Endpoint Migration analysis, right-click, and select Activate.

c. After you mark the endpoints to be migrated, they will be listed in the Results tab.2. Log in to the IBM BigFix console.3. Stop all Software Use Analysis V2.2 actions for the fist computer group (Servers_IEM_cgroup).

a. In the navigation tree, click Actions.

24 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 29: IBM BigFix Inventory: Migration Cookbook A Practical ...

b. Select all open actions for the first, PCs_IEM_cgroup computer group in the IBM Software Inventorysite, right-click, and select Stop Action.

4. Subscribe the first computer group to the new Fixlet site.a. In the navigation tree, click Sites > External Sites > IBM BigFix Inventory.b. In the Computer Subscriptions tab, select Computers which match the condition below.

c. Specify conditions to subscribe single endpoints, or select a computer group to subscribe the wholegroup.

d. Click Save Changes. Your endpoints are subscribed.5. Migrate the first group of endpoints from V2.2 to V9.2.

a. In the Fixlet site, click Fixlets and Tasks.b. Select Migrate SUA 2.2 Endpoints and click Take Action.

c. Select the endpoints that you want to migrate. You can select computers individually or by group,however the groups must be previously defined.

Migration cookbook 25

Page 30: IBM BigFix Inventory: Migration Cookbook A Practical ...

The clients are being progressively migrated.

6. Activate all BigFix Inventory V9.2 analyses, install the scanner, and initiate the BigFix Inventory V9.2software and capacity scans for the migrated endpoints.a. In the Fixlet site, click Analyses. Select all analyses, right-click, and then click Activate.

26 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 31: IBM BigFix Inventory: Migration Cookbook A Practical ...

b. Click Fixlets and Tasks, and run the following tasks to start scanning:1) Run Install or Upgrade Scanner.2) Run Initiate Software Scan. This tasks becomes relevant only when the scanner is installed.3) Run Upload Software Scan Results. This task becomes relevant only when the software scan

finishes collecting the results.4) Run Run Capacity Scan and Upload Results.

Tip: To run the tasks only against the migrated endpoints, after you click Take Action, open theTarget tab. Select the Dynamically target by property check box, and then chooseServers_IEM_cgroup .

Migration cookbook 27

Page 32: IBM BigFix Inventory: Migration Cookbook A Practical ...

Example flow for the Initiate Software Scan task.

1. Click IBM BigFix Inventory > Fixlets and tasks > Initiate Software Scan.

2. Click Take Action. In the window that opens select Dynamically target by property, then in the lower paneselect Servers_IEM_cgroup.

3. On the Execution tab, specify the time when the task is to run and click OK.

7. After scans complete collecting the data for migrated endpoints, import it into BigFix Inventory V9.2.a. Log in to BigFix Inventory V9.2b. In the navigation bar, click Management > Imports.c. Click Import Now.The scan results for the migrated endpoints are now available in BigFix Inventory V9.2 web UI.

Computers panel

28 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 33: IBM BigFix Inventory: Migration Cookbook A Practical ...

Hardware Inventory panel

8. Repeat steps 2-7 to migrate the endpoints from second computer group (PCs_IEM_cgroup). Note thatthe Analyses have been created once.

Results

Software inventory reports for migrated endpoints are now reported only in BigFix Inventory V9.2.Migrated endpoints will no longer report in Software Use Analysis V2.2, but the data collected so far isfrozen and you can access it.

Verifying that endpoints are migratedYou verify that endpoints are successfully migrated by checking that Software Use Analysis V2.2 is nolonger collecting data for migrated endpoints.

Procedure1. Log in to Software Use Analysis V2.2, in the navigation bar, click Reports > Computers.

2. In the upper-right corner, click Configure View to access the filtering options.3. Select the Migrated to BFI check box, and click Submit.

Migration cookbook 29

Page 34: IBM BigFix Inventory: Migration Cookbook A Practical ...

4. Order the report columns by the Migrated to BFI column.5. Check the value in the Migrated to BFI column is set to True for a selection of computers that you

migrated.

Identifying migrated endpoints in BigFix Inventory V9.2You can use the same steps to identify migrated endpoints in BigFix Inventory V9.2. To do this, you mustfirst create a new property in BigFix Inventory V9.2.

Procedure1. Log in to BigFix Inventory V9.2, in the navigation bar click Management > Computer Properties, and

click New.

30 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 35: IBM BigFix Inventory: Migration Cookbook A Practical ...

2. In the Create Computer Property pane, specify the name of the property by selecting the Migrated toBFI property from the Data Source Property list. Click Create.

3. Import scan data to enable the property, in the navigation bar click Management > Data Imports, andclick Import Now.

4. Configure the view in your Computers report to display the Migrated to BFI column.

Migration cookbook 31

Page 36: IBM BigFix Inventory: Migration Cookbook A Practical ...

Note: If you compare some reports between Software Use Analysis V2.2 and V9.2, a number ofdifferences might be present. These dissimilarities are due to catalog differences between the versions.

Manually re-creating parent computer groups in BigFix Inventory V9.2Re-create parent computer groups in BigFix Inventory V9.2 to be able to successfully migrate all the childcomputer groups.

Procedure1. Log in to the BigFix Inventory V9.2 web UI.2. Click Management > Computer groups.3. In the upper right part of the page, click New.

32 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 37: IBM BigFix Inventory: Migration Cookbook A Practical ...

4. Specify the name and description for the first computer group, and click Create.

5. Repeat the step for the second parent computer group.Example:

Name Servers.

DescriptionAll company servers.

Setting up the Admin_PCs roleFor the migration to run successfully, you must set up an additional administrator role that you willassign to the Admin_PCs user. A role is a collection of permissions that correlates to a list of privileges. Theadministrator assigns roles to each user according to the privileges the user needs to efficiently operatethe application.

Before you begin

You must be an Administrator to perform this task.

Important: The Administrator role is set by default and cannot be modified.

Procedure1. In the top navigation bar, click Management > Roles.2. To add a role, click New.3. Specify the name and permissions for the Admin_PCs role, and click Create.

Migration cookbook 33

Page 38: IBM BigFix Inventory: Migration Cookbook A Practical ...

Results

You have set up the role for the supporting administrator. You can now run the migration.

Migrating data objectsYou can migrate your data objects directly into BigFix Inventory V9.2. You can also run a simulation tosee the expected result of the migration without saving the information in the target installation.

Before you beginv During migration, the BigFix Inventory V9.2 server must be running.v You can run the migration tool repeatedly if you want to break down the migration into parts. The

items that are already migrated are skipped.

34 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 39: IBM BigFix Inventory: Migration Cookbook A Practical ...

v If you want to migrate to multiple BigFix Inventory servers, treat each of them as a separate migration.First, specify the access details to one of the servers and start the migration. When it is completed,change the access details to another server and repeat the migration.

v If you encounter any problems during migration, see the migration.log file for more details.v Before you start the migration of your data objects, you must re-create the computer properties and

user roles in the BigFix Inventory V9.2 UI. For more information, see: “Setting up the Admin_PCs role”on page 33 and Setting up computer properties.

About this task

Migration includes your custom data for users, computer groups, catalog signatures, contracts, andcontract custom fields.

Note: Before starting the migration, make sure that your BigFix Inventory V9.2 server is not running animport. Migration cannot be done while an import is running.

Step 1: Obtaining the user tokenProcedure1. In the web UI, click Management > Users.2. Click the name of the user who is to run the migration, and then click Show token.

3. Select, copy the token and save it in a text file. You will need the token when editing the migrationconfiguration file.

Step 2: Editing the migration configuration fileProcedure1. From the BigFix Inventory V9.2 installation directory, go to migration/SUA_2.x.2. Edit the migration22.properties file and specify all parameters that are listed in it.

The migration22.properties file is a configuration file in which you specify the configuration detailsof the Software Use Analysis V2.2 and V9.2 servers. In this file, you can also specify whether youwant to migrate your custom catalog signatures.

Migration cookbook 35

Page 40: IBM BigFix Inventory: Migration Cookbook A Practical ...

# 2.2 to 9.x MIGRATION.PROPERTIES FILE## The migration tool uses this file to read the access details of your servers# to recognize the source and target for migrating your data. After you# specify all of the values included in this file, you can start the migration.

# SOURCE OF MIGRATION: SUA 2.2# SUA 2.2 database userSUA22_DB_USER=sa

# SUA 2.2 database passwordSUA22_DB_PASSWORD=sua22pwd

# SUA 2.2 database host# In case of named instances used on MSSQL Server the property# should be set as <host>\\<instance_name> (for instance localhost\\TEM)SUA22_DB_HOST=9.156.47.107

# SUA 2.2 database port# This is an optional property. By default it is 1433.# It is ignored when named instance is set in SUA22_DB_HOSTSUA22_DB_PORT=1433

# SUA 2.2 database name# The default value is tem_analyticsSUA22_DB_NAME=tem_analytics

# TARGET OF MIGRATION: SUA 9.x

# SUA authentication token:# To view your unique token, log in to SUA, hover over your user name,# and click Profile > Show Token.SUA9x_TOKEN=46696d7c324cc07668f53a3534f336f7a0b3c663

# SUA server host:SUA9x_HOST=localhost

# SUA server port number:SUA9x_PORT=9081

# SUA communications protocol (http/https):SUA9x_PROTOCOL=https

# SUA connection timeout in milliseconds:SUA9x_PROTOCOL_TIMEOUT=240000

# Migration of catalog custom signatures (true/false)# Specifies whether custom signatures are migratedMIGRATE_SIGNATURES=true

Step 3: Simulating data migrationSimulate the migration to check which items are migrated without saving them in the targetenvironment. Items that are not included in the simulation are not migrated.

36 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 41: IBM BigFix Inventory: Migration Cookbook A Practical ...

Procedure1. Open the Windows command prompt and change to C:\Program Files\IBM\BFI\migration\SUA_2.x.2. To simulate the migration, run the following command:

migration.bat -migrate [-dir directory] -simulate

Where -dir directory specifies a directory to save your csv files to. If you omit this parameter, thecsv files are created in the root directory of the migration tool.

3. Check the summary of simulation that is displayed after the simulation is completed.

Note: The user Administrator has been skipped because it was created while the BigFix Inventoryserver was being installed.

Step 4: Verifying the simulationOnly the csv reports can be checked because the information is not saved to the target environment.

Migration cookbook 37

Page 42: IBM BigFix Inventory: Migration Cookbook A Practical ...

About this task

Note: The import of some data elements depends on the import of other data elements and thesimulation does not verify whether dependent elements were migrated. You must check all the existingdependencies yourself.

Example:After you migrated all Software Use Analysis users, in the csv report there is information that auser was imported successfully but the user is not linked to a computer group. Review thecomputer_groups_report.csv report to verify that the computer group for this particular user wasmigrated. The same dependency exists in case of contracts: they will be imported only after allother data items were imported successfully.

Procedure1. Open the computer_groups_report.csv file.

Verify that the computer groups in the report correspond with the computer groups in Software UseAnalysis V2.2.

2. Open the users_report.csv file.Verify that the users in the report correspond with users in Software Use Analysis V2.2.

3. Open the custom_signatures_report.csv file.Verify that the signatures in the report correspond with the custom signatures in Software UseAnalysis V2.2.

38 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 43: IBM BigFix Inventory: Migration Cookbook A Practical ...

4. Open the contract_custom_fields_report.csv file.Verify that the contract custom fields in the report correspond with the contract custom fields inSoftware Use Analysis V2.2.

5. Open the contracts_report.csv file.Verify that the contracts in the report correspond with the contracts in Software Use Analysis V2.2.

Migration cookbook 39

Page 44: IBM BigFix Inventory: Migration Cookbook A Practical ...

Note: During the simulation, a warning is issued that informs about items not migrated. The warningis issued because the items that your contracts depend on are not written to the target database. Inthe following example line breaks were added to improve readability of the data.The contract was added to SUA 9.x, but some warnings were reported:Computer Group PCs_office does not exist,Software Soda PDF 7 does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group PCs_engineers does not exist,Software Nero 2015 16 does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group Servers_Windows does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group Servers_Windows does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group PCs_office does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group PCs_engineers does not exist,

40 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 45: IBM BigFix Inventory: Migration Cookbook A Practical ...

Software AutoCAD LT 20.1 does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group PCs_office does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

The contract was added to SUA 9.x, but some warnings were reported:Computer Group PCs_office does not exist,Contract custom field values Purchase Order Date does not exist,Contract custom field values Contract Administrator does not exist,Contract custom field values Short Description does not exist,Contract custom field values Purchase Order Number does not exist.

Step 5: Running the migrationMigrate the information directly from Software Use Analysis V2.2 to BigFix Inventory V9.2.

Procedurev To start the migration, run the following command:

migration.bat -migrate [-dir directory]

Where -dir directory specifies a directory to save your csv files to. If you omit this parameter, the csvfiles are created in the root directory of the migration tool.

v Review the migration summary to check if all items have been migrated.

Migration cookbook 41

Page 46: IBM BigFix Inventory: Migration Cookbook A Practical ...

The summary is the same as the simulation summary.

Verifying the migrationWhen you migrate your information directly from Software Use Analysis V2.2 to BigFix Inventory V9.2,you can view the summary of simulation or migration in the five csv reports. If the information in thosereports is accurate and complete, you can log in to BigFix Inventory V9.2 to verify that your custom datawas migrated.

Verifying the csv reportsAs the first verification step, review the contents of the five csv reports. The reports describe the detailsof migrating computer groups, users, custom software signatures, contract custom fields, and contracts.

About this task

For more information about statuses that are displayed in the reports, see Statuses.

Procedure1. Open the computer_groups_report.csv file.

Verify that the computer groups in the report correspond with the computer groups in Software UseAnalysis V2.2.

2. Open the users_report.csv file.Verify that the users in the report correspond with users in Software Use Analysis V2.2.

3. Open the custom_signatures_report.csv file.Verify that the signatures in the report correspond with the custom signatures in Software UseAnalysis V2.2.

4. Open the contract_custom_fields_report.csv file.Verify that the contract custom fields in the report correspond with the contract custom fields inSoftware Use Analysis V2.2.

42 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 47: IBM BigFix Inventory: Migration Cookbook A Practical ...

5. Open the contracts_report.csv file.Verify that the contracts in the report correspond with the contracts in Software Use Analysis V2.2.

Results

If some items were not migrated, check the explanation in the csv reports and correct the problems. Themigration can be repeated as many times as you want. Items that are already migrated are skipped.

What to do next

Run a data import for the migrated data items to be visible in your reports.1. In the navigation bar, click Management > Data Imports.2. To import data, click Import Now.

Migration csv reportsWhen you export information from Software Use Analysis V2.2, it is saved in the csv files, each dedicatedto a particular type of migrated item.

Computer groups

Table 3. Description of columns that are in the computer_groups_report.csv file

Column Description

Item COMPUTER_GROUP.

Status Succeeded, Skipped, Failed.

Description Reason for the status.

Computer GroupName

Name of the computer group.

Computer GroupParent Name

Name of the parent computer group.

Computer GroupDescription

Description of the computer group.

Computer GroupDefinition

Definition of the computer group.

Users

Table 4. Description of columns that are in the users_report.csv file

Column Description

Item USER.

Status Succeeded, Skipped, Failed.

Description Reason for the status.

User name User name in the Software Use Analysis V2.2 environment.

Contact Info Other contact information.

Email Address The user's email address.

Locale The locale that is set in the user's computer.

Roles The roles that are assigned to the user.

Computer Group The name of the computer group that the user can access.

Custom signatures

Migration cookbook 43

Page 48: IBM BigFix Inventory: Migration Cookbook A Practical ...

Table 5. Description of columns that are in the custom_signatures_report.csv file

Column Description

Item CUSTOM_SIGNATURE.

Status Succeeded, Skipped, Failed.

Description Reason for the status.

Publisher Publisher of the signature.

Publisher GUID Globally Unique Identifier of the publisher.

Software component Name of the software component.

Software componentGUID

Globally unique identifier of the software component.

Signature GUID Globally unique identifier of the software signature.

File Rules Filter parameters used for file-based signatures.

Filter Rules Filter parameters used for package-based signatures.

Contract custom fields

Table 6. Description of columns that are in the contract_custom_fields_report.csv file.

Column Description

Item CONTRACT_CUSTOM_FIELD.

Status Succeeded, Skipped, Failed.

Description Reason for the status.

Name Name of the custom field.

Type Type of data (string, integer, float, Boolean or date).

Required Indicates whether the field is required.

Contracts

Table 7. Description of columns that are in the contracts_report.csv file.

Column Description

Item CONTRACT.

Status Succeeded, Skipped, Failed.

Description Reason for the status.

Contract Name Name of the contract.

Software Names Names of the software products, versions, and releases that were purchased under thecontract.

User Name Name of the user.

Access ComputerGroup Name

The computer group that a user had access to while creating the contract.

Computer GroupName

Name of the computer group.

Seats Number of users who have access to the software product under a particular contract.

Acquisition Cost The cost of purchasing a software product.

Maintenance Cost The cost of purchasing maintenance plan for a software product.

Entitlement Start The start date for a particular contract.

Entitlement End The end date for a particular contract.

44 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 49: IBM BigFix Inventory: Migration Cookbook A Practical ...

Table 7. Description of columns that are in the contracts_report.csv file. (continued)

Column Description

Maintenance Start The maintenance plan start date for the software products.

Maintenance End The maintenance plan end date for the software products.

Contract custom field(can occur multipletimes)

The values of the custom fields.

Statuses in migration reportsEach migrated item is described with a status and an explanation that summarizes the result of themigration.

SucceededItem was successfully migrated.

Additionally, some warnings can be displayed during simulation. For example:

The contract was added to SUA 9.x, but some warnings were reported: User name user_namedoes not exist.

You must check the users_report.csv file to verify that the user named user_name wassuccessfully migrated. For more information, see the warning information in Migratingdata objects.

SkippedItems were not migrated because they are already defined in BigFix Inventory V9.2. Such a statusmight occur if you repeated the migration, in which case the items were migrated during theprevious migration.

Failed

This status can be related to the problems with items that you want to migrate as well as to theerrors that are returned from the BigFix Inventory V9.2 server. Such a status might be the resultof connection problems. Each of the server errors is saved in the tema.log file, in the followingdirectory on your BigFix Inventory server.v /opt/ibm/BFI/wlp/usr/servers/server1/logs/

v \Program Files\IBM\BFI\wlp\usr\servers\server1\logs

Examples of messages for failed actions:

Migration cookbook 45

Page 50: IBM BigFix Inventory: Migration Cookbook A Practical ...

Table 8. Messages for failed actions

Failed computergroup migration Cannot add the computer group to SUA 9.x: Definition is invalid. Computer Property ID

is not supported.The computer group cannot be migrated because the field ID was used in thecomputer group definition.

Cannot add the computer group to SUA 9.x: Definition is invalid. Computer PropertyCUSTOM_PROPERTY is not supported.

The computer group cannot be migrated because the custom property was notcreated in BigFix Inventory V9.2.

Cannot add the computer group to SUA 9.x: Parent does not exist.The child computer group cannot be imported into BigFix Inventory V9.2 because itsparent computer group was not migrated.

Cannot add the computer group to SUA 9.x: Data source for host host_name does notexist. The computer group cannot be migrated because a data source that does not exist

was added to its definition.

Cannot add the computer group to SUA 9.x: Data source group data_source_group_ID fordata source host host_name does not exist.

The computer group cannot be migrated because a data source group was definedfor a data source that does not exist in BigFix Inventory V9.2.

Failed usermigration Cannot add the user to SUA 9.x: Role role_name does not exist.

The user cannot be migrated to BigFix Inventory V9.2 because the role role_name wasnot created.

Failed contractmigration Contracts import failed. Software software_name does not have a signature that is

assigned to it.The import of contracts failed because the product that was specified in the contractdid not have a signature in the catalog that was imported into BigFix InventoryV9.2.

Cannot add the contract to SUA 9.x: Computer Group group_name does not exist.The contract cannot be imported into BigFix Inventory V9.2 because the computergroup for which the contract was created was not migrated.

Cannot add the contract to SUA 9.x: User name user_name does not exist.The contract cannot be imported into BigFix Inventory V9.2 because the user whocreated it was not migrated.

Cannot add the contract to SUA 9.x: Contract custom field custom_field_name does notexist. The contract cannot be migrated because the contract custom field for this particular

contract was not created in BigFix Inventory V9.2.

Cannot add the contract to SUA 9.x: Software software_name 1.2 does not exist.The contract cannot be migrated because it was created for the software title (orversion or release) that does not exist in the catalog that was imported into BigFixInventory V9.2.

Verifying migrated data objects in product user interfacesOpen the Software Use Analysis V2.2 and BigFix Inventory V9.2 user interfaces, and check if all itemshave been successfully migrated.

Procedure1. Compare BigFix Inventory computer groups in both versions of the application. In Software Use

Analysis V2.2 click Management > Computer Groups.

46 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 51: IBM BigFix Inventory: Migration Cookbook A Practical ...

In BigFix Inventory V9.2 click Management > Computer Groups.

2. Compare users: In Software Use Analysis V2.2 click Management > Users.

In BigFix Inventory V9.2 click Management > Users.

3. Compare the items in the customized catalog: In Software Use Analysis V2.2 click Management >Customize Catalog.

Migration cookbook 47

Page 52: IBM BigFix Inventory: Migration Cookbook A Practical ...

In BigFix Inventory V9.2 click Management > Catalog Customizations.

4. Compare users: In Software Use Analysis V2.2 click Management > Contract Custom Fields.

48 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 53: IBM BigFix Inventory: Migration Cookbook A Practical ...

In BigFix Inventory V9.2 click Management > Contract Custom Fields.

5. Compare contracts: In Software Use Analysis V2.2 click Management > Contracts.

In BigFix Inventory V9.2 click Management > Contracts.

Migration cookbook 49

Page 54: IBM BigFix Inventory: Migration Cookbook A Practical ...

50 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 55: IBM BigFix Inventory: Migration Cookbook A Practical ...

Notices

This information was developed for products and services that are offered in the USA.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program,or service that does not infringe any IBM intellectual property right may be used instead. However, it isthe user's responsibility to evaluate and verify the operation of any non-IBM product, program, orservice.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785United States of America

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certain transactions, therefore, thisstatement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

© Copyright IBM Corp. 2002, 2016 51

Page 56: IBM BigFix Inventory: Migration Cookbook A Practical ...

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurements may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:

52 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 57: IBM BigFix Inventory: Migration Cookbook A Practical ...

Portions of this code are derived from IBM Corp. Sample Programs.

© Copyright IBM Corp. _enter the year or years_. All rights reserved.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web atwww.ibm.com/legal/copytrade.shtml.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that allproprietary notices are preserved. You may not distribute, display or make derivative work of thesepublications, or any portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided thatall proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THEPUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OFMERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Notices 53

Page 58: IBM BigFix Inventory: Migration Cookbook A Practical ...

54 IBM BigFix Inventory: Migration Cookbook A Practical Implementation Guide for Migrating Data from Software Use

Analysis 2.2

Page 59: IBM BigFix Inventory: Migration Cookbook A Practical ...
Page 60: IBM BigFix Inventory: Migration Cookbook A Practical ...

IBM®

Printed in USA