February 11, 2005 (Support Pack 1)

Updates were made to the following sections for ZENworks 6.5 Support Pack 1 (SP1).


Preparation

The following changes were made in this section:

Location Change

Information You Need to Know

and

Novell eDirectory Requirement

Added new information about a "ZENworks" tree with a link to an appendix in the ZENworks Desktop Management Administration Guide, where the use of a tree dedicated to ZENworks objects is recommended for ease of tree management.

Dedicated ZENworks Tree

Added this new section about a dedicated ZENworks tree, and in the process reorganized two of the sections around it.

Server Requirements

Updated this section with new support for two operating systems: Novell Open Enterprise Server (OES) and Citrix* Metaframe.


Installation

The following changes were made in this section:

Location Change

Server Selection

Added the following note under Step 3:

IMPORTANT:  If you choose to remotely install the Inventory Agent or the Remote Management Agent on a Windows 2003 server configured as Domain Controller, you must specify the hostname or the IP address of the server in the Add Server Via Hostname/IP Address field.

Policy and Distribution Services

Removed the "Setting Up the Distributor in a Mixed Network Operating System Environment" section, because it no longer applies. ZENworks 6.5 SP1 or SP2 Distributors can only be on servers running eDirectory 8.x, and therefore you can no longer have the problem of Distributor servers not being able to authenticate to eDirectory 8.x.


Upgrade

The following changes were made in this section:

Location Change

Upgrade

Replace all "Interim Release 1" references with "Interime Release 2," which is the current minimum supported release for ZENworks for Servers 3.0.2.

Upgrading ZENworks 6.5 Server Management to a ZENworks Support Pack

Added this new section pointing to instructions for upgrading ZENworks 6.5 Server Management to a ZENworks support pack.

For guides translated into other languages after English SP1 version was released, also added the following note under the second bullet in Step 2 of the Select the Servers to Upgrade section:

IMPORTANT:  If you choose to remotely install the Inventory Agent or the Remote Management Agent on a Windows 2003 server configured as Domain Controller, you must specify the hostname or the IP address of the server in the Add Server Via Hostname/IP Address field.

Post-Upgrade Manual Distribution Task

Added this section, because the manual Distributions created in the ZENworks 6.5 version of the Manual Distribution Wizard do not work in SP1. They must be re-created using the SP1 or SP2 version of the Manual Distribution Wizard, because re-baselining of manual Distributions will no longer be necessary for manual Distributions created in SP1 or SP2.

What's New in ZENworks 6.5 Server Management Support Pack 1

Added this new section describing what's new in ZENworks 6.5 SP1.

ZENworks 6.5 Server Management Support Packs

Added this new section with instructions on upgrading ZENworks 6.5 Server Management to a ZENworks support pack.

This section contains instructions for all Server Management components to be upgraded to the support pack.


Interoperability

The following changes were made in this section:

Location Change

Interoperability

Replace all "Interim Release 1" references with "Interime Release 2," which is the minimum supported release for ZENworks for Servers 3.0.2.

Interoperability in Inventory

Updated this section with many changes for Support Pack 1.


Uninstalling

The following changes were made in this section:

Location Change

Uninstalling the Web Components

Rewrote this section with iManager 2.0.2 corrections and new steps for iManager 2.5.


Appendixes

The following changes were made in this section:

Location Change

ZENworks Server Management in a Clustered Environment

Updated this section with information related to installing Server Inventory in the Novell Cluster Services environment.

Installation Steps

Inserted a new step (4) and re-arranged the order of the remaining steps. This is to account for incomplete Inventory startup files when a database is installed in a cluster.