The migration utility is used to migrate inventory data, which is defined by your ZENworks Asset Management 7.5 collection domains, and asset management data. This data includes the following:
Devices (including deleted devices, if desired. See Section 1.6.1, Migrating Inventory Data)
Local software products
Administrator-defined fields (known as user-defined fields in ZENworks Asset Management 7.5)
Asset management data
Asset management usage data
Asset management custom reports
Asset management administrator-defined fields (known as user-defined fields in ZENworks Asset Management 7.5)
Contracts and date notifications
Network devices and contract-network relationships are not migrated. Contract-to-network-device relationships can be reestablished after a network discovery process is run within ZENworks 11 SP3 Asset Management.
Inventory data can be migrated by individual device or as a group. Asset management data is migrated as a group.
When you migrate inventory data, by default you are also migrating the following:
Local Product Definitions: Local product definitions defined in ZENworks Asset Management 7.5. These product definitions are migrated as a group; they cannot be migrated individually. If you want to migrate just the local product definitions without the inventory data, see Migrating Local Product Definitions.
Administrator-Defined Field Definitions: Asset management and inventory administrator-defined fields defined in ZENworks Asset Management 7.5 (Administrator-defined fields are known as user-defined fields ZENworks Asset Management 7.5). These field definitions are migrated as a group; they cannot be migrated individually. If you want to migrate just the administrator-defined field definitions without the inventory data, see Using the Migration Utility.
Custom Reports: Asset management and inventory custom reports defined in ZENworks Asset Management 7.5. The reports are migrated as a group. If you want to migrate custom reports without the inventory data, see Migrating Custom Reports.
Migrating inventory data also migrates the following asset management data:
The migration utility requires the following:
Windows XP Professional 5.1 SP 2, Windows XP Professional 5.1 SP 3, Windows Vista SP1 x86, Windows Server 2003 5.2 SP2, or Windows Server 2008 x86; Windows 2000 and Windows 2008 are not supported
Network connectivity to source and destination database servers
Migration source: ZENworks Asset Management 7.5
Migration destination: ZENworks 11 SP3 Asset Management
Microsoft .NET Framework Version 2.0 Re-distributable Package (x86)
(Optional) ZENworks 11 SP3 Asset Management. This product is required to view migrated asset management data.
The following combinations of databases can be used to migrate data:
SQL Server to SQL Server
SQL Server to Sybase
Oracle to Oracle
For migration purposes, the Oracle databases can be Oracle 9.2, Oracle 10.1, or Oracle 10.2. If you are using an Oracle database, please observe the following:
The Oracle client must be installed on the machine that runs the migration utility. For versions 10.1 and 10.2, this must be Administrator, not InstantClient.
For the Oracle 10.2 client, you must apply patch 5473334 (Doc ID 387818.1). Of the several data access components included in the patch, Oracle Provider for OLEDB version 10.2.0.2.20 is required.
TNSNAMES.ORA must contain entries for both the source and destination database services. To create these entries automatically, log on to the ZENworks Asset Management 7.5 and ZENworks 11 SP3 Asset Management databases using the Oracle Enterprise Manager Console or Net Configuration Assistant—Local Net Service Name configuration. Note that the names used for the entries must match the corresponding service name exactly.
The Oracle bin directory (e.g., C:\oracle\product\10.2.0\client_1\BIN) must be in your PATH setting; however, directories from other Oracle products and installs must not be in your PATH setting.
The user associated with the schema for the ZENworks Asset Management 7.5 Oracle database (NCSYSTEM by default) must have the “DBA” role while migration is running (by default, NCSYSTEM only has the “CONNECT” role).
Migrating objects (inventory data, custom reports, and so on) consists of six steps:
Installing the migration utility. For more information, see Section 1.3, Downloading and Installing the ZENworks Migration Utility.
Backing up both source and destination databases before starting migration and after each successful staging.
Selecting the migration source. For more information, see Section 1.4, Selecting the Migration Source.
Selecting the migration destination. For more information, see Section 1.5, Selecting the Migration Destination.
If you have selected a destination zone previously, for example, for a pilot migration, a dialog appears asking if you want to clear the migration status data stored in the ZENworks Asset Management 7.5 source database, which is necessary if you change your migration destination. Click OK to clear the migration status data.
WARNING:You cannot reselect a migration destination. For example, if you choose a pilot migration destination, then switch to a production destination, you cannot switch back to the pilot destination.
Selecting objects to migrate.
Administrator-defined field definitions, local product definitions, and custom reports are migrated by default the first time inventory data is migrated. To migrate them separately, see Section 1.6, Migrating Objects. Some custom reports are not migrated because of database schema changes. For more information, see Section 1.6.7, Migrating Custom Reports.
When selecting objects to migrate, keep the following in mind:
Inventory data and asset management data must be migrated using the same version of the migration utility.
You can only migrate objects once.
You need to migrate inventory data before asset management data.
Workstations that have not been inventoried are not migrated. In addition, if the workstation is associated with a contract, the contract-workstation relationship isn’t migrated, either.
If you want to do a staged migration, select a subset of workstations to migrate. Do not migrate asset management data until all staging is complete. For more information about staging, see Staging a Migration.
Initiating the migration.
Migration can take several hours to complete, depending on the size of the database being migrated. During the migration, the migration utility may become unresponsive at times. If migration is interrupted or canceled, it can be restarted. The migration then continues from the last migrated record in the migration process. If any errors are listed when the migration process is run again, you can ignore them. For more information, see Section 1.6, Migrating Objects.