migrating from novell zenworks 7 desktop management to novell zenworks configuration management
DESCRIPTION
Novell ZENworks 10 Configuration Management is the latest release from the famed ZENworks product family. This new architecture builds on the success of Novell ZENworks 7 Desktop Management, taking its features and functionality to the next level. This session will provide a detailed description of the steps you need to take to migrate your existing ZENworks 7 Desktop Management infrastructure to ZENworks 10 Configuration Management and gives you the tools to ensure a smooth, successful transition.TRANSCRIPT
Migrating from Novell® ZENworks® 7 Desktop Management to Novell ZENworks Configuration Management
Laurence PittDirector, Outbound Product ManagementNovell, Inc./[email protected]
Mark SchoulsSenior Product ManagerNovell, Inc./[email protected]
© Novell, Inc. All rights reserved.২
Agenda
Architecture differences
Differences between Novell® ZENworks® 7 and ZENworks Configuration Management
Migration Utility
Planning the Migration
ZENworks® Architecture
© Novell, Inc. All rights reserved.4
Architecture Differences
ZENworks®
Desktop Management
Version 4.01, 6.5 and 7
ZENworksConfiguration Management
© Novell, Inc. All rights reserved.5
Traditional ZENworks®
Client-server Architecture
Back-end Servers
Managed Devices
ConnectivityWithin Firewall
eDire
ctor
y R
eplic
atio
n
Tier
ed E
lect
roni
c D
istri
butio
n
© Novell, Inc. All rights reserved.6
Traditional ZENworks®
Middle Tier Architecture
Back-end Servers
Middle Tier Servers
Outside Firewall Managed Devices
ConnectivityWithin Firewall
eDire
ctor
y R
eplic
atio
n
Tier
ed E
lect
roni
c D
istri
butio
n
ZENworks® Configuration Management Architecture
© Novell, Inc. All rights reserved.8
ZENworks® Configuration ManagementDatabase and
Directory Services
Primary Servers Satellite Servers Managed Devices
SybaseMicrosoft
Oracle
NovellMicrosoft
WindowsLinux
Open Enterprise Server
ContentImaging
CollectionAuthentication
Reporting
Configuration
WindowsLinux
Open Enterprise Server
ContentImaging
CollectionAuthentication
Windows
HandlersEnforcement
CollectionUser Management
Configuration
Differences Between ZENworks® 7 and ZENworks Configuration Management
© Novell, Inc. All rights reserved.10
Management Console
• Client 32 is not required, and there is no more ConsoleOne.
• The management console is task oriented.
© Novell, Inc. All rights reserved.11
Content Repository
• Encrypted area in the file system on the primary(s) ZENworks® Configuration Management server.
• All content is replicated to selected Primary Servers and Satellite Servers.
• Device/user rights do not have to be assigned.
• Location of content repository is built into the ZENworks Configuration Management code and cannot be modified.
• When using the migration tool all applications will be uploaded into the content repository for the server you are pointed to.
© Novell, Inc. All rights reserved.12
Directory Dependency
• Novell® eDirectory™ is no longer required.
• Management zones replaces eDirectory trees.
• Attributes, inventory and relationships stored in the ZENworks® Configuration Management database.
– Sybase, Microsoft SQL Server, and Oracle
• No schema extensions.
• Use existing LDAP directories (eDirectory , Active Directory) as the sources for users, groups and container structure.
© Novell, Inc. All rights reserved.13
ZENworks® Adaptive Agent
• Can be pushed via the ZENworks® Control Center (ZCC) or you can use other methods to push to your workstations.
• One agent, replaces the traditional ZENworks Desktop Management, Novell® ZENworks Asset Management and Novell® ZENworks® Patch Management agents.
– More is coming down the line on this as well with ZCM 11 – ZENworks Linux Management as well as ZENworks® Endpoint Security Management.
© Novell, Inc. All rights reserved.14
Application Management
• In ZENworks® Configuration Management, new software distribution functionality replaces much of the traditional ZENworks Application Management functionality.
New Terminology
Actions and Action SetsBundles Content
Migration Utility
© Novell, Inc. All rights reserved.16
ZENworks® Migration Console
16
© Novell, Inc. All rights reserved.17
Migration Utility Allows
• Allows you to model your migration before performing it.
• Provides a unique view of assignments created from traditional Novell® ZENworks® associations.
• Copies Novell® eDirectory™ objects and their attributes and associations to the ZENworks database, leaving eDirectory untouched in the process.
• 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 (NAL) applications into Configuration Management bundles.
• AOT applications that have streams (files) associated with them are migrated to MSIs by using the Macrovision* AdminStudio* Repackager, which is included with the ZENworks Migration Utility.
© Novell, Inc. All rights reserved.18
What's Not Migrated
User Objects Inventory Data
ZENworks® Patch Management
© Novell, Inc. All rights reserved.19
Migration Candidates
• ZENworks® Desktop Management agents
– 4.01
– 6.5
– 7.0
ZENworks Desktop Management 3.2 and prior are not supported
Note:
Planning Your Migration to ZENworks® Configuration Management
© Novell, Inc. All rights reserved.21
• Use existing applications, images and policies
• Use existing workstation objects
• Maintain current associations
What Do You Want to Migrate?
© Novell, Inc. All rights reserved.22
Methodology
• Planning, testing and documentation are vital for the success of a migration or co-existence project.
• The recommended methodology is the same as that for the green field deployment.
• The major difference is that during the migration there will be some period of coexistence.
22
© Novell, Inc. All rights reserved.23
Novell® Methodology
DeploymentBusiness Assessment
Technical Assessment
Design Development & Testing
© Novell, Inc. All rights reserved.24
Considerations for Migration
Coexistence of both ZENworks® systems
LDAP authentication
PXE devices
Incremental migration
© Novell, Inc. All rights reserved.25
Migration Order
1. Applications
2. Images
3. Policies
4. Zone settings
5. Workstations
6. Associations
© Novell, Inc. All rights reserved.26
Application Migration
• ZENworks® Configuration Management does not support/distribute traditional ZENworks snAppshot applications.
• Applications must be (re)packaged as Microsoft Installer (MSI) – with transforms if there is customization required.
• The Migration tool will bulk convert AOT->MSI if required. Applications can often be migrated successfully, despite warning messages
© Novell, Inc. All rights reserved.27
Images
• Migrated
– Scripted, Standard and Multicast Session Images
• ZENworks® Configuration Management imaging is backwards compatible
• Not migrated
– Add-on images
– Imaging Server and Workstation Policies (migrated through Zone Settings)
© Novell, Inc. All rights reserved.28
Policies
• Dynamic Local User (DLU)• Group• iPrint• Remote Control• Roaming Profile• SNMP Trap Targets
Policies that cannot be migrated are filtered
© Novell, Inc. All rights reserved.29
ZONE Settings
• Migrated as ZONE Settings.
– Imaging Server Policy settings
– Workstation Launcher Configuration settings
> Make sure you get these so you don't have to recreate the wheel
• Individual attributes can be migrated into ZENworks® Configuration Management.
© Novell, Inc. All rights reserved.30
Workstations
• Only migrate Windows 2000 SP4 to Windows XP (Vista or Windows 7 devices are not on the table here).
• Remember Launcher Configuration Settings are migrated with policies.
• Remember that just because you migrate the workstations, it doesn't mean that they are registered devices in the management zone.
– Some additional work is required
© Novell, Inc. All rights reserved.31
Associations
• Last step in the migration process.
• This is the most tricky step.
• If the object does not already exist in ZENworks® Configuration Management then you have the ability to manually migrate the missing object.
• Best practices state that you should always have target content to migrate associations to.
– PLAN
© Novell, Inc. All rights reserved.32
Next Steps
• Deploy the Novell® ZENworks® Configuration Management Agent to test workstations.
– Push agent from the Deployment interface
– Use current ZENworks to deploy the ZENworks Configuration Management agent
• Test the applications, policies, etc. just like you did in your lab BEFORE you started this whole process.
• Schedule and target other groups of machines.
• The backout plan would be to deploy the legacy ZENworks agent since the original production. environment is preserved
© Novell, Inc. All rights reserved.33
Coexistence During Migration
• There are several coexistence models:
33
Long Term Novell® ZENworks® Configuration Management only for Vista, only Vista machines during the organic replacement schedule get added to ZENworks Configuration Management
Medium Term ZENworks Configuration Management and ZENworks coexist for a period of time to allow a low-risk, cost-effective migration
Short Term Existing workstations are actively moved into ZENworks Configuration Management
© Novell, Inc. All rights reserved.34
Coexistence During Migration(cont.)
• There is no administrative integration between Novell® ZENworks® Configuration Management and traditional ZENworks
• The only commonality is the common identity vault – eDirectory™; and probably common applications, MSI packaged and introduced into ZENworks Configuration Management and traditional ZENworks
• For this period there will be two management solutions in place
34
ZENworks® Application Virtualization
© Novell, Inc. All rights reserved.36
Application Virtualization
Applications run isolated from host system. Nothing is
installed. Applications do not change the OS,
registry settings or .dll's.
© Novell, Inc. All rights reserved.37
Benefits
Higher Productivity: Reduces downtime and recovery time. Accelerates roll outs. Mobility. Fewer service desk calls.
Lower costs: Reduce testing. Eliminate service desk calls. Greater flexibility and interoperability.
Maintain Security: Protects during changes. Insures business continuity.
Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.