Migrating From A Previous Version Of Zenworks; Application Deployment Strategy; Section 6.2, "Migrating From A Previous Version Of Zenworks - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - SYSTEM PLANNING-DEPLOYMENT-BEST PRACTICES GUIDE 10.3 30-03-2010 System Planning Manual

Memory
Peak processor utilization
If servers are highly utilized and struggling to cope with the load placed on them by the managed
devices, it is necessary to review the Management Zone configuration and the number of Primary
Servers and Satellite devices.
6.2 Migrating From a Previous Version of
ZENworks
In addition to the topics described in the previous section, a number of key factors should be taken
into consideration when migrating from a previous version of ZENworks to ZENworks
Configuration Management.:
Section 6.2.1, "Application Deployment Strategy," on page 91
Section 6.2.2, "Application and Policy Migration," on page 92
Section 6.2.3, "Novell eDirectory ," on page 92
Section 6.2.4, "Repurpose Hardware Used by Previous Zenworks Products," on page 92

6.2.1 Application Deployment Strategy

If a customer already has a mature deployment of ZENworks Desktop Management, it is likely that
the customer manages an extensive application repository. In many cases, the customer is using the
Tiered Electronic Distribution component of ZENworks Server Management to tightly manage the
distribution of application software code to the file servers needed to support deployment to end-
users. In addition to these components, the customer might have already invested in processes and
work flows to facilitate application delivery, and therefore might be reluctant to start again with a
new system.
ZENworks Configuration Management provides an encrypted data store, known as the Content
Repository, that stores delivery content for applications, patch remediations, and ZENworks system
updates. When creating an application bundle, the delivery content is uploaded to the Management
Zone, encrypted, and subsequently synchronized to all ZENworks Primary Servers. This process
allows for applications to be delivered securely to devices using HTTP, regardless of the device's
physical location.
However, it is possible to create application bundles that refer to application repositories that are
external to ZENworks. For example, a customer might want to deliver applications with ZENworks
Configuration Management but refer to the same application content (MSIs) that ZENworks
Desktop Management is pointing to. The advantages of this approach are as follows:
Existing repositories can be used.
Existing processes for application management can be used. If a customer has invested in this
heavily, this is a compelling case to use the existing methods.
Some disadvantages of the approach are as follows:
The management of content is controlled outside of ZENworks Configuration Management.
Where the files reside and the rights users have to these locations must be managed outside of
the ZENworks Configuration Management management tools.
Deployment and Migration Scenarios 91