Associations - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010 Migration Manual

If you plan to migrate associations to containers that contain Workstation objects, you should
migrate the container in the Workstation task. This is the only migration task that preserves the
Unique ID of the container so that the associations to the container are preserved. For user
associations, this is not an issue because the Unique ID is always the same as in the old ZENworks
system because Configuration Management relies on User Sources to point to the same User object.
A.6 Associations
The Migration tool displays and migrates only direct associations. Configuration Management has
the same concept of indirect associations that previous ZENworks products have. An indirect
association is created when you associate an object to a container and everything inside that
container becomes associated to the object by virtue of its existence inside that container. If all of the
direct associations are migrated and the migrated objects are placed in the same folder structure,
then all of the indirect associations should be automatically migrated.
The association task is purposely listed as the last step on the migration screen. This is because the
inherent nature of an association (an assignment in Configuration Management) is to simply
establish a one-to-one relationship between two objects, such as "App A is assigned to User 1."
There is no view of direct associations in ConsoleOne, which can cause some ZENworks
environments to become rather complex. The Migration Utility attempts to break down this
complexity by relying on display filters to show a subset of the existing associations in eDirectory.
Each object is presented based on the selected container and the selected filter. Below each object
you should see all of that object's associations. Each association has a two-way arrow <--> overlay
icon on its object type icon. Multiple associations can be selected and dragged to the right side, or
the whole object can be dragged, causing all of its associations to be put in the Items to Migrate
queue. The view on the right simply displays all of the existing associations based on the selected
filter.
The Migration Utility adds two extra filters to this view to help speed up the display of associations.
The first filter forces the display to only show various combinations that you can select for bundles,
users, workstations, containers, and policies. Or you can simply select the last option to show all
object types. The second filter shows all objects, either ineligible or eligible, or shows you only the
eligible associations. Eligible associations are eligible because both of the objects that the
association points to exist in Configuration Management. Calculating which associations are eligible
can take several minutes, so this option is not the default. The filter is called Show both ineligible
and eligible (show warning), and it causes the utility to determine which associations are ineligible
and display a reason in the last display column. All eligible associations are also shown.
The actual migration of an association is simple. Configuration Management creates a new
Assignment object that points to both objects. For applications, Configuration Management also
migrates its Location Mask and Availability Schedule during the migration process.
Migration Data 77