Moving from Novell ZENworks 7 Desktop Management
to Novell ZENworks 11 for Greater IT Efficiency
Written by Jason Blackett
The above reports can be created by leveraging the eDirectory ODBC driver to run queries against eDirectory using reporting tools such as the ODBC query tool, OpenOffice Base, Crystal Reports or Microsoft Access. You can also use an eDirectory reporting tool such as BindView.
Simply put, Novell ZENworks Configuration Management 11 will increase the efficiency of your IT department and the productivity of your users.
Move Your Data
The Novell ZENworks Migration Utility will allow you to move most of the configuration data stored in your Novell ZENworks 7 eDirectory tree to the new Novell ZENworks Configuration Management zone. (See Figure 2.) The utility will guide you through the migration of the following data types:
Application objects of all application types
This includes thin client, Web, AOT/AXT, MSI and simple. Application objects are migrated as Windows bundle objects with the same name as the original application. In most cases, the utility simply copies the existing data to the new bundle. Objects with distribution information will be automatically converted to individual actions or MSIs. Files associated with applications are uploaded to the content repository on the primary server.
Image objects and their associated image files
This includes scripted image objects, simple image objects and server-based image multicast sessions. The utility migrates the image object content to an image bundle of the same name in the zone, and updates the paths to the images referenced by simple or server multicast session objects. After the migration, you'll need to copy any image files referenced by image scripts to the repository images directory, update scripts to reflect the new location, create images for add-on applications in the console and update their references, and clean up any image files that are no longer needed.
Policies still supported by ZENworks Configuration Management 11
This includes Dynamic Local User (DLU), Group, Imaging Server, Imaging Workstation, iPrint, Remote Control, Roaming Profile, and SNMP Trap Target policies. For most policies, the migration utility can create a similar type of policy.
Image server policy settings and workstation launcher configure settings (Management Zones)
These settings will be moved into the ZENworks 11 environment as management zone settings. The launcher configuration settings that can apply to a whole management zone will not be migrated since they can be more easily configured as a global management zone setting.
Workstation, folder and group objects
You need to make sure you move all folders and groups that have associations. You can skip the migration of workstations if you don't have associations to workstations or workstation GUIDs that you need to preserve from Novell eDirectory. You can also skip this step if you want to set up your workstations as managed devices in a management zone by using the ZENworks Control Center to discover them and deploying the ZENworks Adaptive Agent to them. Currently, the utility only supports the migration of Windows 2000 Support Pack 4, Windows XP SP2, and Windows XP SP3 workstations.
Although there are architectural differences between the product versions, the Novell ZENworks 11 platform has been designed with Novell ZENworks 7 customers in mind.
Novell eDirectory object associations
Associations will be migrated as assignment objects in ZENworks 11, which establishes a one-to-one relationship between two objects, such as "App A is assigned to User 1." So, to move an association to an assignment object, you have to include both the ZENworks object and its associated object. For user-associated policies or applications, you need to define a user source for the zone. For workstation-associated policies, applications and images, you need to move their associated folders, workstation groups and workstations.
Test and Publish Your Data
Even though the migration tool simplifies the movement of your Novell ZENworks 7 data to your new Novell ZENworks 11 environment, you should still extensively test the migrated objects to confirm they work as expected. This is especially true for applications that the migration utility needs to convert from AOT format to MSI format. The sandbox feature in ZENworks 11 facilitates this testing. By default, the migration utility can move your bundles, policies and other data into a sandbox, such that they can only be seen by test workstations that you specify. This allows you to validate your move and make any needed changes in a non-production environment. Once you're satisfied that your new ZENworks 11 environment is ready, you can begin to publish your data by deploying the ZENworks Adaptive Agent.
When you push out the ZENworks Adaptive Agent to a device, the old ZENworks 7 Desktop Management agent will be removed, and the device will automatically begin to be managed by your new ZENworks Configuration Management 11 environment. You can push the agent out to only a few or all of your devices. If you want to further ensure the integrity of your move, you might want to move just a few devices at a time. The point is that you can make the move as slowly or as quickly as you like. The nice thing is that this parallel setup approach lets you execute the move without any downtime.
To learn more about how you can benefit by moving to ZENworks Configuration Management 11, visit www.novell.com/products/zenworks/configurationmanagement, or contact your Novell account manager or Novell partner.