Novell ZENWORKS 10 ZENworks Migration Guide
Novell®
www.novell.com
AUTHORIZED DOCUMENTATION
ZENworks Migration Guide
ZENworks® 10 Configuration Management SP3
novdocx (en) 16 April 2010
10.3
March 30, 2010
ZENworks 10 Configuration Management ZENworks Migration Guide
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. 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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
novdocx (en) 16 April 2010
Copyright © 2007 - 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced,
photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
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.
novdocx (en) 16 April 2010
novdocx (en) 16 April 2010
4 ZENworks 10 Configuration Management ZENworks Migration Guide
Contents
About This Guide 9
1 Migration Process 11
2 Differences between ZENworks 10 Configuration Management and Traditional
ZENworks 13
2.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 Traditional ZENworks Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.2 The Next Generation ZENworks Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.3 More Detail on the Architectural Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.3 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.4 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.5 Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.6 Remote Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7 Application Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.8 Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
novdocx (en) 16 April 2010
3 Planning Your Migration to ZENworks Configuration Management 25
3.1 Migration Candidates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Installing the ZENworks Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.3 What the ZENworks Migration Utility Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.1 Migrated. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.2 Not Migrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3.3 Other Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4 Planning Your Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.4.1 Coexistence of the ZENworks Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4.2 LDAP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4.3 PXE Devices and Server Referral Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4.4 Incremental Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4.5 Migration Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.4.6 Management Zone Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4.7 Migrating Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4.8 Identifying Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.4.9 Folder Usage in Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.4.10 Migration Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.4.11 What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4 Migrating to ZENworks Configuration Management 35
4.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2 Starting the ZENworks Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3 Selecting the Migration Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.4 Selecting the Migration Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.5 Migrating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.6 Migrating Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.7 Migrating Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Contents 5
4.8 Migrating Management Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.9 Migrating Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.10 Migrating Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.11 Setting Up Migrated Workstations to be Managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.12 Make an Image of the Migrated Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.13 Managing Your Traditional ZENworks Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
A Migration Data 69
A.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A.2 Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.3 Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
A.4 Management Zone Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A.5 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
A.6 Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
B Migration Options 79
B.1 Using the Migration Utility to Configure Migration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
B.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
B.1.2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
B.1.3 Associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
B.1.4 Imaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
B.1.5 Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
B.1.6 Zone Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
B.1.7 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
B.1.8 Web Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
B.2 Using the Registry Editor to Configure Additional Options for Migrating MSI Applications . . . 82
novdocx (en) 16 April 2010
C Understanding the Migration Utility 85
C.1 Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
C.2 Migration Source/Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
C.3 Migrate Now Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
C.4 Cancel Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
C.5 Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
C.6 Select Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
C.6.1 Source eDir Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
C.6.2 Destination Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
C.7 Items to Migrate Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
C.8 Migration History Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
C.9 What’s New Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
C.10 Options Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
C.11 Overall Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
D Troubleshooting 91
E Best Practices 95
E.1 Running the Migration Utility on a Windows Vista device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
E.2 Selecting a Migration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
E.3 Uploading Objects to the Content Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
E.4 Migrating Applications as Actions or MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6 ZENworks 10 Configuration Management ZENworks Migration Guide
E.5 Using Network Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
E.6 Listing the Associations in the Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
E.7 Listing Application Objects with the AppFsRights attribute in the Migration Utility. . . . . . . . . . 97
E.8 Specifying the File Upload HTTP Port and Web Service Port to Log In to the Migration
Destination Management Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
E.9 Migrating Group Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
F Documentation Updates 99
F.1 March 30, 2010: SP3 (10.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
novdocx (en) 16 April 2010
Contents 7
novdocx (en) 16 April 2010
8 ZENworks 10 Configuration Management ZENworks Migration Guide
About This Guide
novdocx (en) 16 April 2010
This Novell ZENworks 10 Configuration Management ZENworks Migration Guide contains the
information, steps, and processes that you need to move from traditional Novell
Novell ZENworks 10 Configuration Management SP3, the next generation of ZENworks. The
information in this guide is organized as follows:
Chapter 1, “Migration Process,” on page 11
Chapter 2, “Differences between ZENworks 10 Configuration Management and Traditional
ZENworks,” on page 13
Chapter 3, “Planning Your Migration to ZENworks Configuration Management,” on page 25
Chapter 4, “Migrating to ZENworks Configuration Management,” on page 35
Appendix A, “Migration Data,” on page 69
Appendix B, “Migration Options,” on page 79
Appendix C, “Understanding the Migration Utility,” on page 85
Appendix D, “Troubleshooting,” on page 91
Appendix E, “Best Practices,” on page 95
Appendix F, “Documentation Updates,” on page 99
Audience
This guide is intended for ZENworks Configuration Management administrators.
®
ZENworks® to
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to the Novell Documentation Feedback site (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Additional Documentation
ZENworks 10 Configuration Management is supported by other documentation (in both PDF and
HTML formats) that you can use to learn about and implement the product. For additional
documentation, see the 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 (
trademark.
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
About This Guide 9
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.
novdocx (en) 16 April 2010
10 ZENworks 10 Configuration Management ZENworks Migration Guide
1
Migration Process
Novell® ZENworks® 10 Configuration Management introduces architecture that is different from
previous versions of 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
Traditional ZENworks,” on page 13 to gain an understanding of how Configuration
Management is different from traditional ZENworks.
2. (Optional) For an overview of Configuration Management, see “Product Overview” in the
ZENworks 10 Configuration Management Enterprise Edition Getting Started Guide. (Similar
information is contained in the Standard and Advanced editions of the Getting Started Guide.)
3. Install ZENworks 10 Configuration Management to at least one server to establish the
Management Zone where traditional ZENworks information can be migrated. For installation
instructions, see the ZENworks 10 Configuration Management Installation Guide.
novdocx (en) 16 April 2010
1
4. Migrate your traditional ZENworks installation to Configuration Management by using the
instructions in:
Chapter 3, “Planning Your Migration to ZENworks Configuration Management,” on
page 25
Chapter 4, “Migrating to ZENworks Configuration Management,” on page 35
5. (Optional) Migrate your traditional ZENworks Asset Management installation to Configuration
Management by using the instructions in the Novell ZENworks 10 Asset Management
Migration Guide.
6. (Optional) Install other software included in the various editions of Configuration Management
by using the following guides:
AdminStudio 9.5 ZENworks Edition Installation Guide (http://www.novell.com/
documentation/zcm10/pdfdoc/adminstudio/AS95ZENInstallGuide.pdf)
Allows you to continue to standardize the way that you package, test, distribute, and
manage your applications and patches.
Endpoint Security Suite Installation Guide (http://www.novell.com/documentation/
zesm35/install/index.html?page=/documentation/zesm35/install/data/bookinfo.html)
(Enterprise Edition only)
Simplifies endpoint security by combining security policy enforcement for data, devices,
and connectivity under a single management console, allowing organizations to manage,
control, and enforce security policies for Removable Storage, Wireless Communications
including MESH and WiMAX, Application Control, Machine Posture/Integrity, Data
Encryption, and Advanced Personal Firewall.
USB/Wireless Security Installation Guide (http://www.novell.com/documentation/zesm35/
install/index.html?page=/documentation/zesm35/install/data/bookinfo.html) (Advanced
Edition only)
Provides administrators control over the use of local optical media (CD-R/W, DVD+/-R/
W) and all attached storage devices (USB thumb drives, floppy drives, flash memory
cards, ZIP drives, SCSI PCMCIA cards, and other removable media types), providing
Migration Process
11
policy-based restrictions on device access privileges, protecting the integrity and
confidentiality of data on the endpoints, while simultaneously protecting the endpoint
from the introduction of malware and any other unauthorized activities.
ZENworks Linux Management Installation Guide (http://www.novell.com/documentation/
zlm72/lm7install/data/front.html) (Enterprise Edition only)
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.
ZENworks Handheld Management Installation Guide (http://www.novell.com/
documentation/zenworks7/hm7install/data/a20gkue.html) (Enterprise Edition only)
Provides comprehensive management of handheld devices.
7. Get started in Configuration Management with the ZENworks 10 Configuration Management
Administration Quick Start, which shows how to perform tasks to get you up and running.
novdocx (en) 16 April 2010
12 ZENworks 10 Configuration Management ZENworks Migration Guide
2
Differences between ZENworks 10
novdocx (en) 16 April 2010
Configuration Management and
Traditional ZENworks
To migrate to Novell® ZENworks® 10 Configuration Management, you should first understand how
Configuration Management is different from traditional ZENworks, then migrate the traditional data
to your new Configuration Management installation.
The following sections describe what is new or different in ZENworks 10 Configuration
Management:
Section 2.1, “Architecture,” on page 13
Section 2.2, “System Management,” on page 20
Section 2.3, “Workstations,” on page 21
Section 2.4, “Inventory,” on page 22
Section 2.5, “Imaging,” on page 22
Section 2.6, “Remote Management,” on page 22
Section 2.7, “Application Management,” on page 23
Section 2.8, “Additional Features,” on page 24
2
2.1 Architecture
Like previous versions of ZENworks Desktop Management, ZENworks 10 Configuration
Management provides comprehensive management of Windows servers and workstations. However,
its underlying architecture has changed extensively.
The following sections explain the architectural differences:
Section 2.1.1, “Traditional ZENworks Architecture,” on page 13
Section 2.1.2, “The Next Generation ZENworks Architecture,” on page 15
Section 2.1.3, “More Detail on the Architectural Changes,” on page 17
For additional information about the new architecture, see “System Architecture” in the ZENworks
10 Configuration Management Enterprise Edition Getting Started Guide. This information is also
contained in both the 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.
It is simple: Services fit together very easily, and the architecture is very easy for
administrators to understand, deploy, and manage.
Differences between ZENworks 10 Configuration Management and Traditional ZENworks
13
It is scalable: No other systems management product on the market scales to the level of
Middle-Tier Servers
eDirectory Replication
and Tiered Electronic
Distribution
Within the Firewall
Managed DevicesBack-End Servers
Outside
the Firewall
ZENworks (in fact, there are no known limits to how many users a single ZENworks system
can manage).
You will want your new infrastructure to be as flexible, simple, and scalable as your existing
environment. Thus, it’s helpful to have a solid understanding of the architectural differences
between existing versions of 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
TM
(Novell eDirectory
TM
Client32
installed or Middle tier configured in order to access ZENworks services—specifically
) for configuration information. Every workstation was required to have Novell
object information, or logic, stored in the directory.
In traditional ZENworks, it is important to note that the bulk of the logic and processing is done on
the client side in the form of policy searching, launcher refreshing, and so on. In other words, the
client does most of the work. This setup has a dramatic effect on the scalability of the product.
Instead of one server doing all of the work for 100 clients, the total workload is spread across all 100
clients.
novdocx (en) 16 April 2010
Figure 2-1 illustrates the traditional architecture for Novell ZENworks Desktop Management:
Figure 2-1 ZENworks Desktop Management Architecture
Traditional ZENworks architecture is characterized as follows:
The ZENworks Management Agent is installed on every workstation
Client32 is required in a NetWare
The use of the middle-tier server is required when the Novell Client
®
environment
the managed devices
14 ZENworks 10 Configuration Management ZENworks Migration Guide
TM
is not installed on
eDirectory is the key requirement as the object store for all users’ workstations and ZENworks
Database
Data
Model
Persistence
Business Logic
Web Services
Identities File System
objects
Novell ConsoleOne
All access to the eDirectory environment is via the NetWare Core Protocol
The product is cross-platform and supports services running on Linux, NetWare, and Windows
®
is required to manage the ZENworks infrastructure
TM
(NCPTM)
2.1.2 The Next Generation ZENworks Architecture
Novell ZENworks 10 Configuration Management features a three-tier architecture, commonly
known as Services-Oriented Architecture (SOA). This architecture separates the components,
making the product far more modular. Now the various tiers can be updated independently, making
it easier to change business logic or add new modules.
With Novell ZENworks 10 Configuration Management, the server-side infrastructure consists of
two tiers (see Figure 2-2). The first is the data model, and the second comprises the file system (to
store actual files), the database (for storing ZENworks information), and the optional identity store,
which allows user-based resource management. With the release of ZENworks 10 Configuration
Management, Novell eDirectory and Microsoft* Active Directory* are supported natively as user
sources for user identity information.
novdocx (en) 16 April 2010
Figure 2-2 ZENworks 10 Three-Tier Architecture
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. In fact, you can continue to use your existing directory infrastructure for
user identity information, but you do not need to extend the schema or install the product on a server
that runs eDirectory.
Another major architectural change is the way that the client and server communicate with each
other (see Figure 2-3). You continue to run a Novell ZENworks agent (ZENworks Adaptive Agent)
on the managed device, but the bulk of the work (logic and workload) happens on the server side. As
seen in Figure 2-3, the client initiates communications with the server side (the Web server on the
ZENworks 10 Configuration Management Primary Server), but the server can also communicate
Differences between ZENworks 10 Configuration Management and Traditional ZENworks 15
directly with the client. The client and server use industry-standard protocols, such as HTTP,
Primary Agent
Core ZENworks
Tomcat Server
WSSDK
Extensions
Handlers
Web Services
Data Abstraction
File System
RDBMS
ZENworks Managed
Device
ZENworks Server
HTTPS, SOAP, CIFS, and LDAP. The client communicates with the server over HTTP or HTTPS,
and the server communicates with the Adaptive Agent via SOAP (Simple Object Access Protocol)
over HTTPS.
Figure 2-3 ZENworks 10 Client-Server Architecture
novdocx (en) 16 April 2010
From an architectural perspective, the managed device communicates with the server back-end Web
service, and the Primary Server tells the client what to do and where to obtain content (see Figure 2-
4). In effect, the server sends instructions to the client, and the client uses the required handler to
perform the task, such as installing software, applying a policy, managing systems remotely, and so
on.
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.
16 ZENworks 10 Configuration Management ZENworks Migration Guide
Figure 2-4 ZENworks 10 Architecture
ZENworks Servers
Managed Devices
Distribution Point
Database
Primary
Server
LDAP
Directory
novdocx (en) 16 April 2010
The new Novell ZENworks 10 Configuration Management architecture includes the following
important characteristics:
Installation of the ZENworks Adaptive Agent on every managed device
Three-tier SOA
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
ZENworks objects, configurations, and functions
Native support for both Novell eDirectory and Microsoft Active Directory
Based on industry-standard protocols
Direct, one-time server installation, then managed devices are deployed from the server
through ZENworks Control Center
Installation of Primary Server software on either Windows Server 2003, Windows Server 2008,
®
or SUSE
2.1.3 More Detail on the Architectural Changes
Linux Enterprise Server
The following sections provide further detail on the architectural differences:
“Management Console” on page 18
“Software Repository” on page 18
Differences between ZENworks 10 Configuration Management and Traditional ZENworks 17
“Novell eDirectory” on page 18
“Object Management” on page 19
“User Management” on page 19
“Client Agents” on page 20
“Middle Tier Server” on page 20
Management Console
ZENworks Control Center, a Web-based management console is used as a graphical management
interface for Configuration Management and it replaces ConsoleOne that is used in tradional
ZENworks:
Administrator Roles: ZENworks Control Center provides robust administrator roles unique to
its new architectural design. For more information, see “Administrators” in the ZENworks 10
Configuration Management System Administration Reference.
Watch Lists: ZENworks Control Center provides watch lists on a Home page where you can
see the current status of selected devices and bundles, as well as overall Management Zone
statistics. For more information, see “Creating a Watch List” in the 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,
see “Accessing ZENworks Control Center through Novell iManager” in the ZENworks 10
Configuration Management System Administration Reference.
novdocx (en) 16 April 2010
Software Repository
Every Primary Server in the Management Zone contains the same content, providing redundancy for
all managed devices in the zone. For more information, see “Content Repository” in the ZENworks
10 Configuration Management System Administration Reference.
In Configuration Management, content replication and closest server rules replace the traditional
load balancing techniques for fault tolerance. For more information, see both “Content Replication”
and “Closest Server Rules” in the ZENworks 10 Configuration Management System Administration
Reference.
Novell eDirectory
Novell eDirectory is no longer required for data storage. Instead, the ZENworks Configuration
Management database is used. This is different from traditional ZENworks in several ways:
ZENworks Database: A new ZENworks database replaces the old ZENworks database and all
eDirectory tree object information stores. Instead of eDirectory containers and contexts,
Configuration Management uses database folders and the inheritance functionality relevant to
folder/object hierarchy. The new database is the content repository for all Configuration
Management data.
For more information on which databases can be used with Configuration Management, see
“Database Requirements” in the ZENworks 10 Configuration Management Installation Guide.
For more information on maintaining your selected database, see“Database Management” in
the ZENworks 10 Configuration Management System Administration Reference.
18 ZENworks 10 Configuration Management ZENworks Migration Guide
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.
ZENworks creates references to the users in its own database that allow for ZENworks
management activities to occur completely within the ZENworks database rather than in the
directory. If you only plan to manage devices through device assignments rather than user
assignments, user sources are not needed. For more information, see “User Management” on
page 19.
Management Zone: Primary Servers and managed devices are organized into a Management
Zone, replacing the organization provided by the eDirectory tree.
Object Management
Configuration Management uses ZENworks Control Center objects instead of eDirectory objects.
The following describes some of the differences:
Dynamic Groups: This is a new feature in Configuration Management. Both groups and
dynamic groups are available. From the perspective of software and policy assignments, groups
and dynamic groups have the same function. The only difference between the two types of
groups is the way that devices are added to the group. With a group, you must manually add
devices. With a dynamic group, you define criteria that a device must meet to be a member of
the group, and then devices that meet the criteria are automatically added.
novdocx (en) 16 April 2010
Several dynamic groups are predefined, but you can define your own.
For more information, see “Groups” in the ZENworks 10 Configuration Management
Administration Quick Start.
Inheritance: You can set configurations in several ways:
Globally for all ZENworks Control Center objects (devices or bundles) in the
Management Zone
For all objects in a folder and its subfolders
For a group of objects (predefined, user-defined, and dynamic groups are available)
For an individual object
For more information, see “Organizing Devices: Folders and Groups” in the ZENworks 10
Configuration Management Administration Quick Start.
Associations: In Configuration Management, ZENworks Control Center objects are assigned
to each other (such as bundles to devices), instead of being associated with eDirectory objects.
The differences between assignments and associations should be considered when migrating to
Configuration Management. For more information, see Section 4.10, “Migrating
Associations,” on page 61.
User Management
Configuration Management references existing LDAP user sources, in either eDirectory or Active
Directory. Users are not migrated to Configuration Management. This way, ZENworks knows
immediately of any changes done natively to user objects. For more information, see “User Sources”
in the ZENworks 10 Configuration Management System Administration Reference.
Differences between ZENworks 10 Configuration Management and Traditional ZENworks 19
Client Agents
The ZENworks Adaptive Agent replaces the ZENworks Desktop Management Agent. The
differences include the following:
Deployment: You can use the ZENworks Control Center to deploy the Adaptive Agent to any
workstation whose IP address or LDAP directory context you know (or have discovered using
the network discovery of LDAP directory discovery technologies included in ZENworks).
Functionality: All functionality (software distribution, imaging, remote management,
policies) is automatically included with the installation of the Adaptive Agent. The only
functionality you can choose to remove from the agent installation is remote management.
No Network Client: The Adaptive Agent does not require network clients (Novell Client or
Microsoft Client) to retrieve content (applications, etc.) from Primary Servers. The Adaptive
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. To obtain the latest version of Novell
ClientTM, see the Novell Download Web site (http://download.novell.com/index.jsp).
novdocx (en) 16 April 2010
Integrated Interface: The separate client programs (Workstation Manager, Remote Control,
etc.) have been replaced with a common interface called the ZENworks Icon. The ZENworks
Icon is displayed in the notification area at the bottom of the desktop. The NAL Window and
NAL Explorer views are still available.
Configuration Settings The Adaptive Agent behavior is now controlled through a
combination of configuration settings and policy settings (ZENworks Explorer Configuration
policy) rather than through the Launcher Configuration settings only. This allows for greater
flexibility in determining which devices receive specific settings.
Inventory-Only Module: If you have workstations that don’t meet the requirements for
installing the Adaptive Agent (see “Managed Device Requirements” in the ZENworks 10
Configuration Management Installation Guide), you can still receive inventory information
from these workstations by installing the Inventory-only module. For more information, see
“Deploying the Inventory-Only Module” in the ZENworks 10 Configuration Management
Discovery and Deployment Reference.
For more information, see “ZENworks Adaptive Agent Deployment” in the ZENworks 10
Configuration Management Discovery and Deployment Reference.
Middle Tier Server
The Middle Tier Server does not exist in Configuration Management. Instead, the ZENworks
Adaptive Agent communicates directly with the Primary Server through Web services and HTTP
requests.
2.2 System Management
Configuration Management provides several methods for managing ZENworks:
ZENworks Control Center: This is the main Configuration Management administration
interface. For more information, see “ZENworks Control Center” in the ZENworks 10
Configuration Management System Administration Reference.
20 ZENworks 10 Configuration Management ZENworks Migration Guide
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. For more information, see the ZENworks 10
Configuration Management Message Logging Reference and “Viewing System Messages” in
the ZENworks 10 Configuration Management Administration Quick Start.
Software Updating: The process of updating the ZENworks software is now automated in
Configuration Management with the System Updates feature. For more information, see
“Introduction to ZENworks System Updates” in the ZENworks 10 Configuration Management
System Administration Reference.
Reporting: Configuration Management has totally new reporting capabilities:
ZENworks infrastructure reporting is performed by using BusinessObjects* Enterprise XI.
For more information, see ZENworks 10 Configuration Management System Reporting
Reference.
Reporting on your inventoried assets is performed using Asset Inventory’s reporting
capabilities. For more information, see ZENworks 10 Configuration Management Asset
Inventory Reference.
novdocx (en) 16 April 2010
2.3 Workstations
Traditional workstation management using policies and importing into eDirectory is replaced by
managed devices in Configuration Management.
Devices in Configuration Management include both Primary Servers, managed devices (Primary
Servers and workstations), and inventoried-only devices. For Configuration Management, only
Windows devices can be managed. Linux devices can be only Primary Servers and inventoried-only
devices. For more information, see “System Requirements” in the ZENworks 10 Configuration
Management Installation Guide.
Managing workstations is done in the following ways
Workstations are imported into the Management Zone by using the new discovery and
deployment feature. Devices are discovered on the network, registered in the Management
Zone, and have software deployed to them. For more information, see “Discovering Network
Devices” in the ZENworks 10 Configuration Management Administration Quick Start, and also
see the ZENworks 10 Configuration Management Discovery, Deployment, and Retirement
Reference.
.csv
To manually import devices, you can use a
Devices from CSV Files” in the ZENworks 10 Configuration Management Discovery,
Deployment, and Retirement Reference.
Servers become a member of the Management Zone when you install Configuration
Management on them. For more information, see the ZENworks 10 Configuration Management
Installation Guide.
file. For more information, see “Importing
Registration rules and keys replace workstation importing and policies. For more information,
see “Registering Devices” in the ZENworks 10 Configuration Management Administration
Quick Start.
Differences between ZENworks 10 Configuration Management and Traditional ZENworks 21
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
the ZENworks 10 Asset Management Reference.
Many policies are essentially the same between traditional ZENworks and Configuration
Management. However, some have been discontinued, some moved to become Management
Zone configurations, and a new policy has been added. For more information, see the
ZENworks 10 Configuration Management Policy Management Reference.
2.4 Inventory
Asset Inventory replaces Workstation Inventory. This is a completely new feature that is based on
the Configuration Management content model. For more information, see ZENworks 10
Configuration Management Asset Inventory Reference.
Primary Servers can be hierarchically organized in the Management Zone so that all database
information can be rolled efficiently to the one Primary Server that hosts the ZENworks database.
However, the database can reside externally on a server that is not a Primary Server in the zone. For
more information, see “Server Hierarchy” in the ZENworks 10 Configuration Management System
Administration Reference.
novdocx (en) 16 April 2010
2.5 Imaging
In Configuration Management, automated imaging is performed using bundles, instead of using
traditional policies and eDirectory imaging objects. However, the ZENworks Imaging engine is
.zmg
much the same, and the file type for images continues to be
Some improvements have been made to the imaging software, but it’s essentially the same. You
simply perform automated imaging differently. Manual imaging is similar, but enhanced.
The basic repository for image files is hard-coded, but you can create subfolders for organizing your
images.
For more information, see the ZENworks 10 Configuration Management Preboot Services and
Imaging Reference.
.
2.6 Remote Management
This feature has been enhanced, including the use of Virtual Network Computing (VNC). For more
information, see ZENworks 10 Configuration Management Remote Management Reference.
22 ZENworks 10 Configuration Management ZENworks Migration Guide
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.
There are four types of bundles: Windows, Directive, File, and Imaging. For more information,
see the ZENworks 10 Configuration Management Software Distribution Reference.
Actions and Action Sets: A bundle contains actions to perform with its content. All actions
are divided into six categories, referred to as action sets: Install, Launch, Verify, Uninstall,
Terminate, and Preboot. You can identify your actions at the time you create the bundle, and
you can also add or subtract the actions later in ZENworks Control Center. For more
information, see “Actions” in the ZENworks 10 Configuration Management Software
Distribution Reference.
Content: Applications and files, along with policy files, are referred to as content. Content is
stored in a directory structure, called the content repository, on the Primary Server. The Primary
Server and ZENworks Adaptive Agent (running on the managed device) communicate via
standard Web protocols to provide access to the content. Unless you configure your system
differently, content is automatically replicated among Primary Servers to ensure that it is
available from all Primary Servers. For more information, see “Content Delivery” in the
ZENworks 10 Configuration Management System Administration Reference.
Cache: Each managed device still uses a cache directory. However, the cache location has
moved from
drive_root\nalcache
cache directory before installation. By default, this copy occurs when the bundle is first
launched on the device.
Forced Caching: You can use a distribution schedule to force cache a bundle so that it is
immediately available for installation when the user launches it. The schedule can initiate an
immediate distribution of the bundle, or delay distribution to a future time.
Forced Running: You can use a launch schedule to force an application to run. For example,
run the application immediately or when the device refreshes. For more information, see
“Launching a Bundle” in the ZENworks 10 Configuration Management Software Distribution
Reference.
to
zenworks_home\cache
. All bundles are copied to the
novdocx (en) 16 April 2010
Distribution Points: To improve content access for a group of devices without creating
another Primary Server, you can create a Content Distribution Point on any managed device.
Distribution Points are useful in slow WAN configurations. For more information, see
Understanding the Satellite Roles in the ZENworks 10 Configuration Management System
Administration Reference.
Dependencies: Dependencies are now created automatically whenever you select specific
types of actions for a bundle. For more information, see “Creating a Bundle with Content and
Dependency on Another Bundle” in the ZENworks 10 Configuration Management Software
Distribution Reference.
Proximity and Load Balancing: Site lists (proximity) and source lists (workload) are replaced
by a feature called Closest Server Rules. These are rules that you create to direct managed
devices to the Primary Server from which they will receive content and configuration
information. For more information, see “Closest Server Rules” in the ZENworks 10
Configuration Management System Administration Reference.
Differences between ZENworks 10 Configuration Management and Traditional ZENworks 23
2.8 Additional Features
Depending on the edition of Configuration Management (Standard, Advanced, or Enterprise), the
following other software features are provided with Configuration Management:
Additional Security: New for ZENworks 10.
Endpoint Security (Enterprise Edition). For more information on Endpoint Security, see
the Endpoint Security Suite User Guide (http://www.novell.com/documentation/zesm35/
userguide/index.html?page=/documentation/zesm35/userguide/data/bookinfo.html).
USB/Wireless Security (Advanced Edition). For more information on USB/Wireless
Security, see the USB/Wireless Security Reference (http://www.novell.com/documentation/
zesm35/admin/index.html?page=/documentation/zesm35/admin/data/bookinfo.html).
Patch Management: You can continue to automate patch application to minimize
vulnerabilities and compliance issues. For more information, see the ZENworks 10 Patch
Management Reference.
For a synopsis, see “Patching Software ” in the ZENworks 10 Configuration Management
Administration Quick Start.
For the Standard Edition, Patch Management is provided as 60-day evaluation-only software.
Asset Management: You can continue to monitor software license compliance, track software
usage, manage contracts, and manage licenses. For more information, see the ZENworks 10
Asset Management Reference. Also see “Monitoring License Compliance” in the ZENworks 10
Configuration Management Administration Quick Start.
novdocx (en) 16 April 2010
For the Standard and Advanced Editions, Asset Management is provided as 60-day evaluationonly software.
AdminStudio: You can continue to standardize the way that you package, test, distribute, and
manage your applications and patches. For more information, see the AdminStudio 9.5
ZENworks Edition Installation Guide (http://www.novell.com/documentation/zcm10/pdfdoc/
adminstudio/AS95ZENInstallGuide.pdf) (PDF only).
Personality Migration: You can migrate the personality settings of one or more users on a
Windows managed device. For more information, see the 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).
ZENworks Handheld Management: (Enterprise Edition only) You can continue to manage
handheld devices by using ZENworks Handheld Management. For more information, see the
ZENworks 7 Handheld Management Installation Guide (http://www.novell.com/
documentation/zenworks7/hm7install/data/a20gkue.html) and the ZENworks 7 Handheld
Management Administration Guide (http://www.novell.com/documentation/zenworks7/
hm7admin/data/a20gkue.html).
24 ZENworks 10 Configuration Management ZENworks Migration Guide
3
Planning Your Migration to
novdocx (en) 16 April 2010
ZENworks Configuration
Management
Novell® ZENworks® Configuration Management provides the ZENworks Migration Utility that
allows you to migrate your traditional ZENworks Novell eDirectory
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.
The Migration Utility allows you to migrate eDirectory objects in batches so that you can migrate
incrementally. You can queue and migrate several hundred objects at a time. The utility provides
modeling, object selection, simple raw attribute viewing, migration, and error reporting.
You cannot install AdminStudio 9.5 ZENworks Edition and the Migration Utility on the same
device. However, you can install AdminStudio 9.5 ZENworks Edition and the Migration Utility on
different devices in the same Management Zone.
The following sections provide concepts on migrating to Configuration Management:
Section 3.1, “Migration Candidates,” on page 25
Section 3.2, “Installing the ZENworks Migration Utility,” on page 25
Section 3.3, “What the ZENworks Migration Utility Does,” on page 26
Section 3.4, “Planning Your Migration,” on page 27
TM
objects and attributes into the
3
3.1 Migration Candidates
The following ZENworks product can be migrated to ZENworks 10 Configuration Management:
ZENworks for Desktops 4.0.1
ZENworks Desktop Management 6.5
ZENworks 7.x Desktop Management
Migration of other ZENworks products will be added in a future version of Configuration
Management.
3.2 Installing the ZENworks Migration Utility
Perform the following steps to download and install the ZENworks Migration Utility executable to
the Windows device where you will be running the utility
1 (Conditional) If an earlier version of the utility is already installed on the device, then uninstall
it before installing the latest version.
2 In your Web browser, access the following URL:
http://zenworks_primary_server_id/zenworks-setup/?pageId=tools
Planning Your Migration to ZENworks Configuration Management
25
novdocx (en) 16 April 2010
and download
ZENmigration.exe
to a temporary location.
Because the ZENworks Migration Utility saves its work files locally, you should plan to always
run this utility from the same workstation in order to provide migration history information that
you can use in both planning and during migration. These work files are not transferable to
other workstations where you might install the utility. You will have disjointed histories if you
use multiple workstations to perform the migration.
IMPORTANT: Novell strongly recommends that you do not run the Migration Utility from
the 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.
3 Run ZENmigration.exe to install it on your workstation.
3.3 What the ZENworks Migration Utility Does
The ZENworks Migration Utility is provided with Configuration Management (see Step 5 on
page 36 in Section 4.1, “Prerequisites,” on page 35). You copy and install it to your workstation
from an executable file that resides on your Primary Server. The utility consists of a migration
screen where you can model and perform the migration.
The following sections explain what is or is not migrated:
Section 3.3.1, “Migrated,” on page 26
Section 3.3.2, “Not Migrated,” on page 27
Section 3.3.3, “Other Software,” on page 27
3.3.1 Migrated
The ZENworks Migration Utility does the following:
Allows you to model your migration before performing it.
Provides a unique view of assignments created from traditional ZENworks associations.
Copies eDirectory objects and their attributes and associations to the ZENworks database,
leaving eDirectory untouched in the process.
Prompts you to resolve duplicates from site listed applications.
Provides a status log of non-migrated attributes for your traditional ZENworks system’s
eDirectory objects that do not exist in Configuration Management.
Converts Novell Application Launcher
bundles.
MSI and AOT applications that have streams (files) associated with them are migrated to MSIs
by using the AdminStudio Repackager, which is included with the ZENworks Migration
Utility.
TM
(NAL) applications into Configuration Management
26 ZENworks 10 Configuration Management ZENworks Migration Guide
3.3.2 Not Migrated
The ZENworks Migration Utility does not migrate the following:
User Objects: These are not migrated. Instead, in ZENworks Control Center, you simply point
to their user sources. Therefore, any change to a user in eDirectory or Active Directory is
immediately known in ZENworks Control Center.
Inventory Data: Your traditional inventory data and the related eDirectory attributes are not
migrated by this utility. For how to migrate ZENworks Asset Management inventory data, see
Section 3.3.3, “Other Software,” on page 27.
For details on what is not migrated and what is changed during migration, see Appendix A,
“Migration Data,” on page 69.
3.3.3 Other Software
The following are upgraded or migrated with other methods:
Inventory Data: The ZENworks Asset Management Migration Utility can migrate your
traditional inventory data, including inventory history, from ZENworks 7 to ZENworks
Configuration Management. To access and run this utility:
novdocx (en) 16 April 2010
1. In your Web browser, access the following URL:
http://zenworks_primary_server_id/zenworks-setup/?pageId=tools
and download
2. Run
3. To run the utility on a supported Windows device, click Start > All Programs > Novell
PatchLink: PatchLink* Update is automatically installed with its latest patches as part of the
installation of ZENworks Configuration Management.
AdminStudio: AdminStudio ZENworks Edition is provided on the Novell ZENworks
Configuration Management CD. It is an optional installation. The portion of AdminStudio that
is needed by the ZENworks Migration Utility for migrating Novell Application Launcher
applications is automatically installed with the Migration Utility.
ZAMmigration.exe
ZENworks > ZENworks Asset Management Migration Utility.
ZAMmigration.exe
to install it on your workstation.
to a temporary location.
3.4 Planning Your Migration
To upgrade your traditional ZENworks to Configuration Management, you simply need to
determine which eDirectory objects and associations to migrate from your traditional ZENworks
system. You do not need to migrate all of them, or organize them the same way as they are organized
in eDirectory.
Consider the following as you plan your migration:
Section 3.4.1, “Coexistence of the ZENworks Systems,” on page 28
Section 3.4.2, “LDAP Authentication,” on page 28
Section 3.4.3, “PXE Devices and Server Referral Lists,” on page 29
Section 3.4.4, “Incremental Migration,” on page 30
Section 3.4.5, “Migration Order,” on page 30
Planning Your Migration to ZENworks Configuration Management 27
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
Management Zone. This server cannot be running traditional ZENworks software.
Installation sets up a Management Zone and a ZENworks database. The first Primary Server
installed hosts the database if you are not using an external database on another server.
Migration: eDirectory data is migrated to the ZENworks database on the Primary Server by
using read-only access.
Migration to Configuration Management consists of reading eDirectory data to create similar
objects, attributes, and assignments in the ZENworks database. Users are not migrated to
Configuration Management. Configuration Management simply uses eDirectory for a user
source, if you have user associations to be migrated.
You must create the user source in ZENworks Control Center before migrating user
associations.
Managed Devices: The ZENworks Adaptive Agent is installed on each device to be managed
by Configuration Management, such as workstations and Primary Servers in the Management
Zone.
Installing the Adaptive Agent also deletes the traditional ZENworks Agent software from the
managed device, so there are no managed device conflicts.
novdocx (en) 16 April 2010
Certain considerations affect coexistence:
The Configuration Management software cannot be running on the same server as your
traditional ZENworks software.
Configuration Management uses its own database, not eDirectory.
The Adaptive Agent replaces the traditional ZENworks Agent on managed devices.
Because of these things, the Configuration Management and traditional ZENworks systems can run
concurrently in your environment without conflicts. The Configuration Management and traditional
ZENworks systems do coexist but are not interoperable. They remain as separate management
software for the devices where their respective agents are running.
3.4.2 LDAP Authentication
The ZENworks Migration Utility authenticates to both the source eDirectory tree by using LDAP
and the destination ZENworks Management Zone by using Web services, and both rely on SSL for
security over TCP/IP. LDAP must be enabled, which is the default for eDirectory trees.
28 ZENworks 10 Configuration Management ZENworks Migration Guide
For eDirectory login, you must provide a fully distinguished user name that has sufficient rights to
read eDirectory. Writing to eDirectory is not required because the migration process only reads
.zmg
eDirectory. If you are migrating images, the migration user must also have rights to read
imaging files.
For reading information from eDirectory, the default port for LDAP SSL is 636. The default nonLDAP SSL port is 389.
TM
Although you can migrate without Novell Client32
the migration utility, Client32 might be necessary to access files on NetWare
running on the device where you are running
®
volumes.
Authentication to the ZENworks Management Zone is done using the administrator login name and
password that you established when installing Configuration Management. If you added other
administrator logins in ZENworks Control Center after installation, these are also valid, provided
they have the necessary Read rights to eDirectory and Write rights to the ZENworks Configuration
Management database.
For writing to the zone’s database, the default port for SSL is 443.
3.4.3 PXE Devices and Server Referral Lists
novdocx (en) 16 April 2010
If you have both Configuration Management and ZENworks Linux Management systems running
concurrently, the following information might apply:
PXE Devices: When a PXE device boots, it makes a broadcast request on the network for PXE
services. The ZENworks Proxy DHCP server (the
novell-proxydhcp
daemon) responds to
this request with information that includes the IP address of an imaging server where the device
can send requests for assigned preboot work.
Because PXE devices can exist in an environment with both newer and traditional ZENworks
systems running concurrently, the device can fail to determine its assigned preboot work if it
cannot find the imaging server for its own ZENworks version.
In ZENworks Configuration Management, devices can exist in multiple Management Zones. It
is essential that the PXE device contact PXE services associated with its home zone so that it
can correctly determine if there is any preboot work assigned to it. When there is only a single
Management Zone, this is easy to do because all Proxy DHCP servers provide addresses to
services that belong to the same zone. Any device can request preboot work from any imaging
server in the same zone and get the same response.
The PXE device’s initial request for PXE services is sent as a broadcast to the network, and all
Proxy DHCP servers respond with information pertaining to their respective zones (in
ZENworks Configuration Management and ZENworks Linux Management) or Proxy DHCP
servers in their trees (in traditional ZENworks versions using Windows or NetWare imaging
servers). Because it is impossible to determine which Proxy DHCP server responds first (if
multiple Proxy DHCP servers respond), or which server’s response is used by the device, it is
impossible to ensure that each PXE device contacts servers in its home zone or tree.
Server Referral Lists: For a ZENworks environment that has PXE services, the Server
Referral List configuration section provides a method for getting PXE devices to connect with
their proper imaging servers. Server referral lists are only used by PXE devices, and in
ZENworks Configuration Management only one Management Zone needs to have an active
Proxy DHCP server and server referral list. Because you can only have one referral list active
Planning Your Migration to ZENworks Configuration Management 29
in a network segment, if you have ZENworks Linux Management running with a referral list
configured, you need to disable the Proxy DHCP service for Linux Management. This allows
the Configuration Management referral list to be used by all PXE devices.
A server referral list allows you to ensure that all devices contact their home zone or tree for
preboot work assignments. The list should contain the IP address of an imaging server in each
known Management Zone or traditional ZENworks system’s tree. When a device requests
preboot work from a server, the server first determines if the device belongs to the same zone or
tree as the server. If it does not, that server refers the request to each server in its server referral
list until it finds the device’s home zone or tree. The device is then instructed to send all future
requests to the correct
If two server referral lists are active, do the following:
1 Install ZENworks Configuration Management.
For instructions, see the ZENworks 10 Configuration Management Installation Guide.
2 Configure a server referral list in your Configuration Management system.
3 Disable the Proxy DHCP service in your Linux Management system.
novell-proxydhcp
daemon.
novdocx (en) 16 April 2010
3.4.4 Incremental Migration
The migration screen’s design provides granularity that allows you to migrate one item or thousands
of items at a time. Therefore, you can migrate any number of items in a session and you can use as
many sessions as you need.
Because traditional ZENworks and Configuration Management can run concurrently, but are not
interoperable, you can migrate eDirectory objects incrementally, such as by department or
geographical region.
When migrating, the ZENworks Migration Utility preserves GUIDs and version numbers, but cache
is not used. Therefore, we recommend when you migrate Workstation objects that you migrate all
eDirectory associations related to those workstations before you register the workstations in
Configuration Management.
3.4.5 Migration Order
The following list represents what can be migrated and shows the suggested migration order.
However, you can migrate in any order, including any subsets of these migration types:
1. Applications
2. Images
3. Policies
4. Zone Settings
5. Workstations
6. Associations
This order is recommended because of possible dependencies, such as associations that require their
applications and associated objects to already exist in order to re-create those associations in
Configuration Management.
30 ZENworks 10 Configuration Management ZENworks Migration Guide
Loading...