ZENworks Objects and Their Uniqueness
B
41
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
B
ZENworks Objects and Their
Uniqueness
During migration of asset management data, most of the asset management objects (e.g., Purchase
Records, Licensed Products) are migrated without checking for duplicate objects in ZENworks 10
Asset Management. This can lead to the following outcomes if there are objects in ZENworks 10
Asset Management that match objects being migrated from ZENworks Asset Management 7.5 (see
Section B.1, “Duplicate Object Details,” on page 41
for what constitutes a duplicate of each object
type):
If the migration process is restarted due to errors, the ZENworks Asset Management 7.5 data
has already been partially migrated. Because of the partially migrated data, the already
migrated objects are rejected and the migration utility reports duplicate key violations.
If you are migrating to ZENworks 10 Asset Management running on an SQL Server, you
can fix the duplicates and then restart the migration utility, making sure to turn off the
Stop
Migration on First Error
setting. However, restarting migration might result in loss of
data. If this possibililty is not acceptable, we recommend that you restore the ZENworks
Asset Management 7.5 and ZENworks 10 Asset Management database backups, resolve
the duplicates, then run the migration utility again.
If you are migrating to ZENworks 10 Asset Management running on either Sybase or
Oracle, you need to restore the ZENworks Asset Management 7.5 and ZENworks 10
Asset Management database backups, resolve the duplicates, then run the migration utility
again.
If the objects are duplicates and the ZENworks 10 Asset Management version of the object is
not in a subfolder, the migration utility produces an error. Some or all of the duplicate objects
that the migration utility was processing (e.g., licenses) are not moved to ZENworks 10 Asset
Management.
If the objects are duplicates but the ZENworks 10 Asset Management version of the object is in
a subfolder, the migration utility adds the object to ZENworks 10 Asset Management. You end
up with two objects in ZENworks 10 with matching names, but in different folders. The
exception to this is Contracts, which does not allow duplicate Contract ID’s in ZENworks 10
Asset Management, even in subfolders.
B.1 Duplicate Object Details
Section B.1.1, “Purchase Records,” on page 42
Section B.1.2, “Catalog Products,” on page 42
Section B.1.3, “Licensed Products,” on page 42
Section B.1.4, “Discovered Products,” on page 42
Section B.1.5, “Software Collections,” on page 42
Section B.1.6, “Contracts,” on page 42
Section B.1.7, “Date Notifications,” on page 43
Section B.1.8, “Documents,” on page 43
Содержание ZENWORKS 10 ASSET MANAGEMENT SP3 - MIGRATION GUIDE 10.3 23-03-2010
Страница 4: ...4 Novell ZENworks 10 Asset Management Migration Guide novdocx en 7 January 2010...
Страница 8: ...8 Novell ZENworks 10 Asset Management Migration Guide novdocx en 7 January 2010...
Страница 36: ...36 Novell ZENworks 10 Asset Management Migration Guide novdocx en 7 January 2010...
Страница 40: ...40 Novell ZENworks 10 Asset Management Migration Guide novdocx en 7 January 2010...
Страница 44: ...44 Novell ZENworks 10 Asset Management Migration Guide novdocx en 7 January 2010...