1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3...
  6. Migration manual

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

Hide thumbs Also See for ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Information Manual
AUTHORIZED DOCUMENTATION
ZENworks Migration Guide
Novell
®
ZENworks
10 Configuration Management SP3
®
10.3
March 30, 2010
www.novell.com
ZENworks 10 Configuration Management ZENworks Migration Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010

Summary of Contents for Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010

  • Page 1 AUTHORIZED DOCUMENTATION ZENworks Migration Guide Novell ® ZENworks 10 Configuration Management SP3 ® 10.3 March 30, 2010 www.novell.com ZENworks 10 Configuration Management ZENworks Migration Guide...
  • Page 2 Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
  • Page 4 ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 5: Table Of Contents

    Contents About This Guide 1 Migration Process 2 Differences between ZENworks 10 Configuration Management and Traditional ZENworks Architecture ............. . . 13 2.1.1 Traditional ZENworks Architecture .
  • Page 6 Migrating Management Zone Settings ......... . . 55 Migrating Workstations.
  • Page 7 Using Network Files ............96 Listing the Associations in the Migration Utility .
  • Page 8 ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 9: About This Guide

    ZENworks 10 Configuration Management SP3 documentation (http:// www.novell.com/documentation/zcm10/) Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
  • Page 10 When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux*, should use forward slashes as required by your software. ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 11: Migration Process

    ZENworks. To leverage the power and new features of ZENworks 10, you need to migrate from existing systems rather than perform a typical upgrade. To migrate to Novell ZENworks 10 Configuration Management, do the following: 1. Review Chapter 2, “Differences between ZENworks 10 Configuration Management and...
  • Page 12 ZENworks Configuration Management directly manages only Windows* devices. Therefore, if you want to manage Linux devices (servers or workstations), you must use Novell ZENworks Linux Management, which is available as part of the ZENworks 10 Configuration Management Enterprise Edition, or you can purchase Linux Management separately if you are installing the Standard or Advanced editions of Configuration Management.

  • Page 13: Differences Between Zenworks 10 Configuration Management And Traditional Zenworks

    Standard and Advanced editions of the Getting Started Guide. 2.1.1 Traditional ZENworks Architecture Your existing Novell ZENworks solution is powerful because: It is flexible: The logic is in the object store, making it simple to move content and services around without having to perform major architectural overhauls.
  • Page 14 ZENworks 10 Configuration Management and earlier versions of Novell ZENworks. Novell ZENworks 7.x is the final release patterned after traditional ZENworks architecture. Traditional ZENworks architecture is two-tiered and relies on direct access to the object store (Novell eDirectory ) for configuration information.

  • Page 15: The Next Generation Zenworks Architecture

    Business Logic Web Services In the new architecture, Novell ZENworks 10 Configuration Management has been decoupled from eDirectory, which is no longer a key requirement for the product to function. You no longer need to manage a directory in order to provide systems management services. This does not mean that you cannot benefit from integrating ZENworks 10 Configuration Management with your existing eDirectory environment.

  • Page 16: Management

    From an identity perspective, the user of a managed device authenticates directly to the identity store where user's object is stored, either Novell eDirectory or Microsoft Active Directory. The only identity-related information stored in the Novell ZENworks object store is a reference object pointing back to the actual identity, which increases the efficiency of user-based resource management.

  • Page 17: More Detail On The Architectural Changes

    Additional Primary Servers for computing tasks, which removes the workload from the managed device No more specific requirement for Novell eDirectory No more requirement for Novell Client32 to be installed on either the managed device or the server A new Web-based administrative console (ZENworks Control Center) to manage all...
  • Page 18 ZENworks 10 Configuration Management Administration Quick Start. iManager: If you already use Novell iManager to manage other Novell products, you can configure the ZENworks Control Center to be launched from iManager. For more information, “Accessing ZENworks Control Center through Novell iManager”...
  • Page 19 No Schema Extensions: Because Configuration Management stores all the data in the ZENworks database, it does not impact your Novell eDirectory schema. Any access to eDirectory is read-only for the purpose of referencing user information. User Sources: You can use eDirectory and Active Directory as the source for users. To do this, you define a read-only LDAP link to a directory and specify the contexts where users reside.

  • Page 20: System Management

    Agent uses HTTP and Web services requests to retrieve the content. NOTE: The latest version of the Novell client must be installed on the managed device before a Dynamic Local User policy or a Roaming Profile Policy that has Store User Profile in User’s Home Directory enabled is enforced on the device.

  • Page 21: Workstations

    Command Line Utilities: You can administer Configuration Management by using the zman and zac command line utilities. For more information, see the ZENworks 10 Configuration Management Command Line Utilities Reference. Errors and Messages: Traditional error messages and message logs have been replaced with the centralized Message Logging feature.

  • Page 22: Inventory

    You can determine a device’s status in ZENworks Control Center. For more information, see “ZENworks Icon” in the ZENworks 10 Configuration Management Software Distribution Reference. Asset Management has been configured to work with ZENworks 10. For more information, see ZENworks 10 Asset Management Reference.

  • Page 23: Application Management

    2.7 Application Management In ZENworks 10 Configuration Management, new software distribution functionality replaces much of the traditional ZENworks Application Management functionality. Bundles: A bundle is a package of files and information, similar to an Application Object and its files but with far greater power and flexibility. A bundle wizard lets you create a bundle, configure the actions associated with a bundle, and then assign bundles to devices or users.

  • Page 24: Additional Features

    ZENworks 10 Personality Migration Reference. ZENworks Linux Management: (Enterprise Edition only) You can continue to manage Linux workstations by using ZENworks Linux Management. For more information, see the ZENworks 7.2 Linux Management Installation Guide (http://www.novell.com/documentation/ zlm73/lm7install/data/front.html) and the ZENworks 7.2 Linux Management Administration Guide (http://www.novell.com/documentation/zlm73/lm7admin/data/front.html).

  • Page 25: Planning Your Migration To Zenworks Configuration Management

    Novell ZENworks Configuration Management provides the ZENworks Migration Utility that allows you to migrate your traditional ZENworks Novell eDirectory objects and attributes into the ZENworks Configuration Management database. Because Configuration Management uses a different architecture than previous versions of ZENworks, migrating your traditional ZENworks data is the only method for upgrading to Configuration Management.

  • Page 26: What The Zenworks Migration Utility Does

    Primary Server. The Migration Utility’s processes are CPU intensive and can noticeably slow down the server. Also, Novell’s license from Macrovision prohibits installing the utility on more than one device per Management Zone. Therefore, install the utility on a supported management workstation.

  • Page 27: Planning Your Migration

    ZAMmigration.exe 3. To run the utility on a supported Windows device, click Start > All Programs > Novell ZENworks > ZENworks Asset Management Migration Utility. PatchLink: PatchLink* Update is automatically installed with its latest patches as part of the installation of ZENworks Configuration Management.

  • Page 28: Coexistence Of The Zenworks Systems

    Section 3.4.6, “Management Zone Settings,” on page 31 Section 3.4.7, “Migrating Workstations,” on page 31 Section 3.4.8, “Identifying Users,” on page 32 Section 3.4.9, “Folder Usage in Configuration Management,” on page 32 Section 3.4.10, “Migration Modeling,” on page 33 Section 3.4.11, “What’s Next?,” on page 34 3.4.1 Coexistence of the ZENworks Systems When you introduce Configuration Management into your environment, the following takes place: Installation: Configuration Management is installed to a Primary Server in a Configuration...

  • Page 29: Pxe Devices And Server Referral Lists

    For reading information from eDirectory, the default port for LDAP SSL is 636. The default non- LDAP SSL port is 389. Although you can migrate without Novell Client32 running on the device where you are running ® the migration utility, Client32 might be necessary to access files on NetWare volumes.

  • Page 30: Incremental Migration

    The device is then instructed to send all future requests to the correct daemon. novell-proxydhcp If two server referral lists are active, do the following: 1 Install ZENworks Configuration Management.

  • Page 31: Management Zone Settings

    3.4.6 Management Zone Settings You can migrate the following eDirectory information for Novell Application Launcher configuration settings and for the Imaging policies; they become Management Zone settings in ZENworks Configuration Management: ZENworks Management Zone Settings for Migration from eDirectory Table 3-1...

  • Page 32: Identifying Users

    However, traditional ZENworks systems do not have directory objects in Active Directory to migrate. If Active Directory is configured in ZENworks Control Center and eDirectory and Active Directory are synchronized by using Novell Identity Manager or any similar utility, then the eDirectory user associations can be migrated to the Active Directory users.

  • Page 33: Migration Modeling

    You can use the migration screen to create new folders in Configuration Management. These folders can be nested in any fashion. You can then drag eDirectory objects into these folders no matter where they resided in eDirectory. You don’t need to maintain the same organization in Configuration Management that you have in eDirectory.

  • Page 34: What's Next

    3.4.11 What’s Next? In addition to planning your migration on paper, you can use the migration screen to model your migration. To get started with using the migration screen, continue with Chapter 4, “Migrating to ZENworks Configuration Management,” on page ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 35: Migrating To Zenworks Configuration Management

    ZENworks 7.x Desktop Management IMPORTANT: For your current installation of a traditional ZENworks system, you must have ® a Novell eDirectory tree with the ZENworks schema installed and have ZENworks eDirectory objects listed in the tree. The ZENworks Migration Utility cannot be used to create...
  • Page 36 3 Use ZENworks Control Center to configure the user source for your users so that the eDirectory items that they are associated with allows for a successful migration. For more information on configuring the user source, see “User Sources” in ZENworks 10 Configuration Management System Administration Reference.

  • Page 37: Starting The Zenworks Migration Utility

    Step 5 on page To start the ZENworks Migration Utility: 1 On a supported Windows device, click Start > Programs > Novell ZENworks > ZENworks Configuration Management Migration Utility > Launch. 2 (Conditional) By default, What’s New window appears for the first time. If you do not want the window to appear every time you start the utility, select the Do not show this message again option.
  • Page 38 ZENworks Configuration Management Migration Utility Figure 4-1 NOTE: To launch the What’s New window, click on the top right-hand corner of the utility. 4 Continue with Section 4.3, “Selecting the Migration Source,” on page ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 39: Selecting The Migration Source

    4.3 Selecting the Migration Source To identify and log into your migration source Novell eDirectory tree: Migration Source Figure 4-2 1 Fill in the following fields to authenticate to your migration source eDirectory tree: Tree: This field is not displayed the first time that you access the eDir Login dialog box.

  • Page 40: Selecting The Migration Destination

    3 To select the migration destination, continue with Section 4.4, “Selecting the Migration Destination,” on page 4.4 Selecting the Migration Destination To identify and log into your migration destination Novell ZENworks Configuration Management Management Zone: Migration Destination Figure 4-3 1 Fill in the following fields to authenticate to your destination Management Zone: Zone: This field is not displayed the first time that you access the Zone Login dialog box.

  • Page 41: Section 4.5, "Migrating Applications

    Each time you use this dialog box, the last zone that you logged into is displayed here. To add a Management Zone that is not listed, select the <New Zone> default option, fill in the other fields, then click OK. Thereafter, the zone is available in the drop-down list. Username: Specify the username for the zone.

  • Page 42: Migrating Applications

    4.5 Migrating Applications To migrate applications from eDirectory to Configuration Management: 1 Click (the Migration Tool Settings icon), then do the following: ® 1a To overwrite existing Application objects in the ZENworks database, click General, then select the Overwrite objects that already exist option. WARNING: This overwrites any existing Application objects in the database, including those that were previously migrated.
  • Page 43 Setting Description Migrate failed MSI builds The Migrate failed MSI builds option forces application migration when the utility fails to migrate one or more attributes to the MSI. An MSI bundle is considered failed when a warning is produced while converting an AOT Application object to an MSI.
  • Page 44 Setting Description Migrate distribution options as The Migrate distribution options as individual actions individual actions option lets you migrate the distribution options in applications as individual actions such as Edit INI action, Registry Edit action, or Run Script action that can be edited.
  • Page 45 3 To model the migration, do the following: 3a In the Source eDir Tree panel, navigate the eDirectory contexts to locate the Application objects to be queued for migration. To stop listing of the objects in the Source eDir Tree, click The eDirectory information that is displayed is filtered according to the type of information that you are migrating.
  • Page 46 4 Repeat Step 3 as necessary to locate and queue all of the Application objects that you want to model for migration at this time. IMPORTANT: Every Application object that you queue in the Destination Zone panel is migrated when you click the Migrate Now button. 5 Review your selections in the Destination Zone panel.
  • Page 47 Instructions for handling failed migration items are covered in Step Chained applications are displayed individually on the Migration History tab, but the Migration Log column displays a GUID rather than a log for them. Only the main Application object to which the others are chained displays a View Log button in that column.

  • Page 48: Migrating Images

    8c If you have failed items that you do not want to migrate, you can delete only those that are queued (still dimmed) from the queue in the Destination Zone panel. Right-click anywhere on the Items to Migrate tab and select Delete all items. This empties the Items to Migrate tab listing.
  • Page 49 WARNING: This overwrites any existing Image objects in the database, including those that were previously migrated. The Skip saving/loading history option allows you to dramatically improve performance on large migrations by not storing the local history. 1b To overwrite the existing image file on the content server, click Imaging, then select the Overwrite the existing image file on the content server option.
  • Page 50 As you drag items from one panel to the other, the items listed in the Destination Zone panel are automatically sorted. If you drag an item multiple times, it is only queued once. If you migrate incrementally, you should queue only the objects that you want to migrate at this time because all items that are queued in the Destination Zone panel are migrated when you click the Migrate Now button.
  • Page 51 The teal color persists, so the next time you open the Migration Utility and navigate the Source eDir Tree contexts and Destination Zone folders, you can see what you have previously migrated. Objects that failed migration continue to be displayed with their icons dimmed. Instructions for handling failed migration items are covered in Step During migration, a temporary working folder is created on the workstation for each...

  • Page 52: Migrating Policies

    Section 4.13, “Managing Your Traditional ZENworks Installation,” on page NOTE: After migrating to ZENworks 10 Configuration Management, you must use the novell- proxydhcp service to perform Imaging operations in the PXE mode. If you use the BOOTP parameters, 66 and 67, to perform Imaging operations, the operation fails with an error. For more information, see “Unable to connect to Preboot Server.
  • Page 53 You might want to determine the folder structure for your Policy objects, and create and migrate those folders before queueing Policy objects to them. You can also migrate existing eDirectory containers and all of their Policy objects (including subcontainers). The containers are converted into folders containing all of the Policy objects that exist in eDirectory under those contexts.
  • Page 54 You can use the Ctrl and the arrow keys or Shift and the arrow keys to select multiple items for deletion. This includes folders and their contents. Items queued for migration have their icons and texts dimmed. If you select dimmed items for deletion, they are only deleted from the queue.

  • Page 55: Migrating Management Zone Settings

    8b On the Items to Migrate tab, click the Failed - View Log button for each item that failed to migrate, and determine the best course of action. You can either fix the problem and migrate the item, or you can delete it from the Items to Migrate tab, which also deletes it from the queue in the Destination Zone panel.
  • Page 56 To stop listing of the objects in the Source eDir Tree, click IMPORTANT: The individual components of the Novell Application Launcher settings or Imaging policies are displayed so that you can selectively migrate them, instead of migrating all of the settings or policy information.

  • Page 57: Migrating Workstations

    Traditional ZENworks Installation,” on page 4.9 Migrating Workstations If you do not have associations to workstations or workstation GUIDs to preserve from Novell eDirectory, and you want to set up your workstations as managed devices in the ZENworks Management Zone by using ZENworks Control Center to discover them and deploy the Adaptive Agent to them, then skip the migration of workstations.
  • Page 58 To migrate workstations from eDirectory to Configuration Management: 1 To overwrite existing Workstation objects in the ZENworks database, click (the Migration Tool Settings icon), select the General option, select the Overwrite objects that already exists option, then click Save Settings to exit the dialog box. WARNING: This overwrites any existing Workstation objects in the database, including those that were previously migrated.
  • Page 59 If you migrate incrementally, you should queue only the objects that you want to migrate at this time because all items that are queued in the Destination Zone panel are migrated when you click the Migrate Now button. On the Items to Migrate tab, the number of items you are migrating (copied to the Destination Zone panel) is represented in parentheses on the tab’s label.
  • Page 60 Instructions for handling failed migration items are covered in Step During migration, a temporary working folder is created on the workstation for each workstation being migrated. These folders are deleted as each workstation is successfully migrated. IMPORTANT: The migrated workstations do not immediately display in the Workstations section on the Devices tab in ZENworks Control Center.

  • Page 61: Migrating Associations

    To migrate associations, click Step 6: Associations in the Migration Tasks field. If you have completed all eDirectory object and association migrations, clean up your traditional ZENworks installation by continuing with Section 4.13, “Managing Your Traditional ZENworks Installation,” on page 4.10 Migrating Associations You can migrate user associations and workstation associations for bundles, user associations and workstation associations for policies, and workstation associations for images.
  • Page 62 Setting Description If an associated object does not exist, Stops the migration when an object to be associated stop the migration and prompt for does not exist in the ZENworks database and redirection to the appropriate migration prompts you to be redirected to the appropriate task to create the object Migration Tasks step to migrate the object.
  • Page 63 The following options determine what associations are displayed: Option Purpose Bundles <--> users Displays only the associations existing in eDirectory for bundles and users or user groups. A user source must be configured in ZENworks Control Center before you migrate these associations. Bundles <-->...
  • Page 64 Destination User Source: Lists the user sources available in ZENworks Configuration Management. By default, the user source that is listed as the migration source is selected. 3b In the Source eDir Tree panel, navigate the eDirectory contexts to locate the objects to be associated and drag them into the Destination Zone panel.
  • Page 65 WARNING: If you select colored items (with teal or black text), they are deleted from the ZENworks database and are no longer available in ZENworks Control Center. 7 To migrate all of the dimmed items displayed in the Destination Zone panel, including all dimmed items contained in subfolders, click the Migrate Now button.

  • Page 66: Setting Up Migrated Workstations To Be Managed

    8b On the Items to Migrate tab, click the Failed - View Log button for each item that failed to migrate, and determine the best course of action. You can either fix the problem and migrate the item, or you can delete it from the Items to Migrate tab, which also deletes it from the queue in the Destination Zone panel.

  • Page 67: Managing Your Traditional Zenworks Installation

    Consult your traditional ZENworks documentation for information on uninstalling those versions of ZENworks. However, if you need users for Configuration Management because you migrated associations to them, or you need users for the Novell Client , you need to retain a working installation of eDirectory with your user objects.
  • Page 68 ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 69: A Migration Data

    Configuration Management uses a new security model for access control. Auto Start feature This feature caused Novell Application Launcher to add itself to the start menu so that it could automatically start when the user logged in. This is now ®...
  • Page 70 ConsoleOne . For example, you could tell Novell Application Launcher to only copy files marked “Request Confirm.”. Because MSI does not allow a granular (file-by-file) setting, this feature cannot be migrated if the application is migrated as a bundle with Install MSI action.
  • Page 71 The new content system does this automatically. Thin client settings Configuration Management only supports a subset of the features Novell Application Launcher used to support. The following attributes have been dropped: Thin client user name (no credentials are passed to the terminal server)

  • Page 72: Images

    Feature Comment Volume file system rights Configuration Management does not automatically assign rights to any file system. A.2 Images The administrator performing image file migration must have sufficient file rights to read the image files ( .zmg The following can be migrated: Standard image Scripted image Multicast session image...
  • Page 73 The following are not migrated: Policy Features Not Migrated to Configuration Management Table A-2 Feature Comment Computer Extensible Extensible policies do not exist in Configuration Management. Policies Group Policy The following settings are not migrated: Cache User Configuration: Does not exist in Configuration Management.

  • Page 74: Management Zone Settings

    Feature Comment zenwmWorkstationImport Although it is technically possible to migrate a workstation import policy to a Management Zone setting, it is simply easier to set the few global zone settings manually in ZENworks Control Center to migrate them. In Configuration Management, you can set a registration rule on any folder level hierarchically, but in ZENworks 7.x you had to set a Workstation Import policy on a Server Package that was associated to one or more servers.
  • Page 75 Because there are multiple launcher configuration settings in any given tree, it is easier for the administrator to manually set the one set of Management Zone settings in ZENworks Control Center. The following launcher configuration settings can be migrated to the new ZENworks Explorer Configuration policy: Display icon on the Desktop (becomes the root folder name) Enable folder view...

  • Page 76: Workstations

    Enable timed refresh (User) Enable writing to the cache (user) Enable writing to the cache (workstation) Read groups for applications (User) Read groups for applications (Workstation) Save window size and position Set application inheritance level (user) Set application inheritance level (workstation) Set refresh frequency (User) Specify E-mail attribute Top object...

  • Page 77: Associations

    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.
  • Page 78 ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 79: B Migration Options

    Migration Options Before migrating objects to ZENworks Configuration Management you can choose to configure various settings. The following sections provide more information on configuring the migration options: Section B.1, “Using the Migration Utility to Configure Migration Options,” on page 79 Section B.2, “Using the Registry Editor to Configure Additional Options for Migrating MSI Applications,”...

  • Page 80: General

    B.1.1 General When you are migrating an object that already exists in ZENworks Configuration Management, you can use the Overwrite objects that already exist option to cause the latest object being migrated to be ® used instead. The existing object is overwritten with the new migration object in the ZENworks Configuration Management database.

  • Page 81: Associations

    If the Migrate distribution options as individual actions option is enabled, then the applications are migrated as specific actions: An application having registry changes is migrated as a bundle with Registry Edit action. An application having INI settings is migrated as a bundle with an Edit INI File action. An application having text file changes is migrated as a bundle with an Edit Text File action.

  • Page 82: Policies

    B.1.5 Policies ® When you are migrating Launcher Configuration settings from Novell eDirectory , select the Skip assignment creation for launcher configuration policies option to convert the settings into a Launcher Configuration policy in Configuration Management. During migration, an assignment...
  • Page 83 1 Open the Registry Editor. 2 Go to HKLM\Software\Novell\ZCM\Migration\MSIOptions\ 3 Right-click Silent and click Modify. 4 In the Edit String dialog box, specify in the Value data option.
  • Page 84 ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 85: C Understanding The Migration Utility

    Understanding the Migration Utility The ZENworks Migration Utility consists of a migration screen where you can model and perform the migration: ZENworks Migration Utility Figure C-1 Review the following sections for more information on the Migration Utility’s organization and its functions: Section C.1, “Migration Tasks,”...

  • Page 86: Migration Tasks

    Section C.11, “Overall Progress,” on page 90 C.1 Migration Tasks ® There are several types of Novell eDirectory data that you can migrate. You can model all types in one session or more (because the modeling information is saved); however, you can only migrate one type at a time.

  • Page 87: Cancel Button

    C.4 Cancel Button This button can be clicked at any time during a migration to stop the process. Items already migrated remain migrated; items yet to be migrated continue to be displayed in the Destination Zone panel with dimmed icons and text. C.5 Exit Closes the Migration Utility.

  • Page 88: Destination Zone

    Stop Listing of Objects in the Source eDir Tree: Stops listing the objects in the Source eDir Tree field. If you right-click an item in the list, you have two options: View Attributes: Displays attributes for the selected object in the Generic Attributes dialog box.

  • Page 89: Items To Migrate Tab

    Delete Selected Object: Deletes the item that has a dimmed icon from the list, not from eDirectory or the ZENworks database. If the item has a colored icon, it was either previously migrated or it was originally created in ZENworks Control Center. If you select the Delete Selected Object icon, it deletes the item from the ZENworks database and it is no longer viewable in ZENworks Control Center.

  • Page 90: Migration History Tab

    Delete Successful: All items that were originally in the list before clicking Migrate Now remain in the list, showing their migration status. This option allows you to delete all successfully migrated items, leaving those that were unsuccessful for review and handling. Because these options can apply to selected items or to the panel as a whole, right-click the item for options applicable only to specific items.

  • Page 91: D Troubleshooting

    The following sections explains the scenarios that you might encounter while migrating your ® ® ® traditional ZENworks software to Novell ZENworks 10 Configuration Management. “Application versions might not be migrated” on page 91 “The schedule of an application is not correctly migrated” on page 91 “Application icons might not be available after migration”...
  • Page 92 Application icons might not be available after migration Explanation: If an application object is migrated as an MSI bundle to ZENworks Configuration Management, some of the application icons might not be available and the following error is displayed in the logs: ISDEV : error -1024: message string.
  • Page 93 Action: Perform the following steps to migrate the application as an individual action instead of an MSI: 1. Launch the Migration Utility. 2. Click the Migration Tool Settings icon, then click Application. 3. Select the Migrate distributions options as individual actions option. 4.
  • Page 94 Action: None. How do I to enable debug logs Action: To enable the logs, see TID 3418069 in the Novell Support Knowledgebase. (http://support.novell.com/search/kb_index.jsp). Unable to use the migrated add-on images Explanation: Add-on images that are created by exporting applications in traditional ZENworks are not valid in ZENworks Configuration Management.

  • Page 95: E Best Practices

    The following sections contain information on the best practices to follow while migrating your ® ® ® traditional ZENworks software to Novell ZENworks 10 Configuration Management Section E.1, “Running the Migration Utility on a Windows Vista device,” on page 95 Section E.2, “Selecting a Migration Option,” on page 95 Section E.3, “Uploading Objects to the Content Server,”...

  • Page 96: Migrating Applications As Actions Or Msi

    While migrating large applications that should be uploaded to the content server, the connection to the server might be lost, resulting in failure of the migration. Ensure that Get response timeout in the Web Client Configuration is set to None in order to establish a persistent connection with the server.

  • Page 97: Listing Application Objects With The Appfsrights Attribute In The Migration Utility

    Migration Utility. To list such applications for the migration, remove the AppFsRights attribute. For more information on removing attributes, search for LDAP Attribute Remover article at Novell Cool Solutions Community (http://www.novell.com/communities/coolsolutions). E.8 Specifying the File Upload HTTP Port and...
  • Page 98 ZENworks 10 Configuration Management ZENworks Migration Guide...

  • Page 99: F Documentation Updates

    This section contains information on documentation content changes that were made in this ® ® ZENworks Migration Guide after the initial release of Novell ZENworks 10 Configuration Management SP3. The information can help you to keep current on updates to the documentation.
  • Page 100 100 ZENworks 10 Configuration Management ZENworks Migration Guide...

This manual is also suitable for:

Zenworks 10 configuration management sp3

Table of Contents