Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - NETWORK DISCOVERY DATABASE... User manual

Novell®
www.novell.com
novdocx (en) 16 April 2010
AUTHORIZED DOCUMENTATION
ZENworks 10 Configuration Management Installation Guide
ZENworks ® 10 Configuration Management SP3
10.3
March 30, 2010
Installation Guide

novdocx (en) 16 April 2010
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.
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).

novdocx (en) 16 April 2010
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.

4ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010

Contents 5
Contents
novdocx (en) 16 April 2010
About This Guide 7
1 System Requirements 9
1.1 Primary Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Satellite Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.1 Windows Device Performing Satellite Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2.2 Linux Device Performing Satellite Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Management Zone Version Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4 Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.5 LDAP Directory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.6 Managed Device Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.7 Inventoried-Only Device Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.8 Administration Browser Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.9 Installation User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2 Coexistence with Other ZENworks Products 29
2.1 ZENworks Desktop Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2 ZENworks Asset Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3 ZENworks Patch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4 ZENworks Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.5 ZENworks Linux Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6 ZENworks Handheld Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3 Preparation 33
3.1 Understanding What the ZENworks Installation Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2 Gathering Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3 Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.1 Verifying That the Minimum Requirements Have Been Met . . . . . . . . . . . . . . . . . . . 34
3.3.2 Creating an Installation DVD from the ISO Download . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.3 Creating an External Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.4 Installing an External ZENworks Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3.5 Installing Mono 2.0.1-1.17 on SLES 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4 Installing the ZENworks Server 47
4.1 Performing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.1.1 Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.2 Performing an Unattended Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.2.1 Creating Your Response File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.2.2 Performing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.3 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
5 Installing the ZENworks Adaptive Agent on Windows 65
6 Installing the ZENworks Adaptive Agent on Linux 67
7 Uninstalling ZENworks Software 69
7.1 Correct Order for Uninstalling ZENworks Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.2 Uninstalling a Windows Primary Server, Satellite, or Managed Device . . . . . . . . . . . . . . . . . . 70
7.3 Uninstalling a Linux Primary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.3.1 Uninstalling ZENworks Software and Removing the Device from the Zone . . . . . . . 74
7.3.2 Uninstalling ZENworks Software While Retaining the Device in the Zone . . . . . . . . 75
7.4 Uninstalling ZENworks 10 Configuration Management SP3 Linux Satellite. . . . . . . . . . . . . . . 76
7.4.1 Zone-Level Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.4.2 Local Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
A Installation Executable Arguments 79
B Troubleshooting 81
B.1 Troubleshooting Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
B.2 Uninstallation Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
C Documentation Updates 87
C.1 March 30, 2010: SP3 (10.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

About This Guide 7
novdocx (en) 16 April 2010
About This Guide
This ZENworks 10 Installation Guide includes information to help you successfully install a
Novell®ZENworks®10 Configuration Management SP3 system.
ZENworks 10 Configuration Management SP3 is also available as a software appliance that can be
deployed to the supported virtual infrastructure. This software appliance is built on the customized
SUSE®Linux Enterprise Server 10 SP2 (SLES 10 SP2) and is pre-installed with ZENworks 10
Configuration Management SP3 Server and ZENworks 10 Configuration Management SP3
ZENworks Reporting Server.
For more information on how to deploy and manage ZENworks Appliance, see the ZENworks 10
Configuration Management Appliance Deployment and Administration Reference.
The information in this guide is organized as follows:
Chapter 1, “System Requirements,” on page 9
Chapter 2, “Coexistence with Other ZENworks Products,” on page 29
Chapter 3, “Preparation,” on page 33
Chapter 4, “Installing the ZENworks Server,” on page 47
Chapter 5, “Installing the ZENworks Adaptive Agent on Windows,” on page 65
Chapter 6, “Installing the ZENworks Adaptive Agent on Linux,” on page 67
Chapter 7, “Uninstalling ZENworks Software,” on page 69
Appendix A, “Installation Executable Arguments,” on page 79
Appendix B, “Troubleshooting,” on page 81
Appendix C, “Documentation Updates,” on page 87
Audience
This guide is intended for ZENworks administrators.
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 documentation (http://
www.novell.com/documentation/zcm10/).

8ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
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 (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
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.

System Requirements
1
9
novdocx (en) 16 April 2010
1
System Requirements
The following sections provide the Novell®ZENworks®10 Configuration Management SP3
requirements for hardware and software:
Section 1.1, “Primary Server Requirements,” on page 9
Section 1.2, “Satellite Requirements,” on page 14
Section 1.3, “Management Zone Version Requirements,” on page 17
Section 1.4, “Database Requirements,” on page 20
Section 1.5, “LDAP Directory Requirements,” on page 21
Section 1.6, “Managed Device Requirements,” on page 21
Section 1.7, “Inventoried-Only Device Requirements,” on page 25
Section 1.8, “Administration Browser Requirements,” on page 27
Section 1.9, “Installation User Requirements,” on page 27
1.1 Primary Server Requirements
The server where you install the Primary Server software must meet the following requirements:
Table 1-1 Primary Server Requirements
Item Requirements Additional Details
Server Usage Your server might be capable of
handling tasks in addition to the tasks
a Primary Server performs for
ZENworks 10 Configuration
Management. However, we
recommend that any server where you
install the Primary Server software be
used only for ZENworks 10
Configuration Management purposes.
For example, you might not want the server
to do the following:
Host Novell eDirectoryTM
Host Novell Client32TM
Host Active Directory*
Be a terminal server

10 ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
Operating System Windows*:
Windows Server* 2003 SP1 /
SP2 x86, x86-64 (Enterprise and
Standard editions)
Windows Server 2008 SP1 / SP2
x86, x86-64 (Enterprise and
Standard editions)
Windows Server 2008 R2 x86-64
(Enterprise and Standard
editions)
Linux*:
SUSE®Linux Enterprise Server
10 (SLES 10) SP1 / SP2 / SP3
x86, x86-64 (Intel* and AMD*
Opteron* processors)
Open Enterprise Server 2 (OES
2) SP1 / SP2 x86, x86-64
SLES 11 x86, x86-64 (Intel and
AMD Opteron processors)
All the Core and Data Center Editions of
Windows Server 2003 and Windows Server
2008 are not supported as Primary Server
platforms. Windows Server 2008 Core is not
supported because it does not support the
.NET Framework.
ZENworks 10 Configuration Management is
supported on Windows Server 2003 and
Windows Server 2008 editions with or
without Hyper-V.
IMPORTANT: If you want to install
ZENworks Reporting Server on a Primary
Server, you must install it either on SLES
10, OES 2, Windows Server 2003, or
Windows Server 2008 platforms. ZENworks
Reporting Server is currently not supported
on SLES 11 and Windows Server 2008 R2.
For more information, see TID 7004794 at
Novell Support web site (http://
www.novell.com/support/microsites/
microsite.do).
Hardware Processor: Minimum - Pentium* IV
2.8 GHz (x86 and x86-64), or
equivalent AMD or Intel processor
If the Primary Server is running Patch
Management, we recommend a fast
processor, such as the Intel Core* Duo
processor
RAM: 2 GB minimum; 4 GB
recommended
Disk Space: 3 GB minimum for
installing; 4 GB recommended for
running. Depending on the amount of
content you need to distribute, this
number can vary greatly.
Patch Management file storage
(downloaded patch content) requires
at least 25 GB of additional free disk
space. All content replication servers
also require this same amount of
additional free disk space if Patch
Management is enabled. If you use
Patch Management in additional
languages, each server also requires
this additional amount of free space
for each language used.
Because the ZENworks database file and
ZENworks content repository can each
become very large, you might want a
separate partition or hard drive available.
For information on changing the default
content repository location on a Windows
server, see “Content Repository” in the
ZENworks 10 Configuration Management
System Administration Reference.
For Linux servers, you might want the
/
var/opt
directory to be located on a large
partition. This is where the database (if
embedded) and content repository are
stored.
Display resolution: 1024 × 768 with
256 colors minimum
Item Requirements Additional Details

System Requirements 11
novdocx (en) 16 April 2010
Hostname
Resolution
The server must resolve device
hostnames by using properly
configured DNS, otherwise some
features in ZENworks will not work
properly.
Server names must support DNS
requirements, such as not having
underscores in their names, or
ZENworks login fails. Acceptable
characters are the letters a-z
(uppercase and lowercase), numbers,
and the hyphen (-).
IP Address The server must have a static IP
address or a permanently leased
DHCP address.
An IP address must be bound to
all NICs on your target server.
Installation hangs if it is trying to use a NIC
that does not have an IP address bound to
it.
Microsoft .NET
(Only for
Windows)
The Microsoft* .NET 2.0 software and
its latest updates must be installed
and running on the Windows Primary
Server in order to install ZENworks 10
Configuration Management.
You are given the option to launch the .NET
installation during installation of ZENworks.
If you select the option, .NET 2.0 is
installed. For better performance and
stability, you should upgrade to the latest
support packs and patches of .NET 2.0
through Windows Automatic Updates or
Patch Management on the agent.
.NET 2.0 SP2 is the latest version supported
by Microsoft on Windows Server 2003 and
Windows Server 2008. On Windows Server
2003, you can directly download and install
.NET 2.0 SP2 or upgrade to .NET 3.5 SP1,
which includes .NET 2.0 SP2. On Windows
Server 2008, you must upgrade to .NET 3.5
SP1 to get the .NET 2.0 SP2 update
installed.
Mono (Only for
SLES 11)
Mono®2.0.1-1.17 must be
installed on the SLES 11 Primary
Servers.
The following RPM packages
must be installed on the Linux
Primary Servers:
libgdiplus 0
mono-core
You can choose to either install Mono during
the installation of ZENworks or download
the recommended Mono version and the
RPM packages from the Mono Download
Web site (http://www.go-mono.com/mono-
downloads/download.html).
Item Requirements Additional Details

12 ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
Firewall Settings:
TCP Ports
80 and 443 Port 80 is for Tomcat non-secure port.
Port 443 is for Tomcat secure port. It is also
used by default to download system
updates from NCC and to download Product
Recognition Update (PRU).
Primary Server downloads patch license
related information and checksum data over
HTTPS (port 443), and the actual patch
content files over HTTP (port 80).
ZENworks Patch Management license
information is obtained from the Lumension*
licensing server (http://
novell.patchlink.com), the patch content and
checksum data is retrieved from an AKAMAI
hosted content distribution network
(novell.cdn.lumension.com). You must
make sure that the firewall rules allow
outbound connections to these addresses
because the patch content distribution
network is a large fault tolerant network of
cache servers.
Port 443 is also used for CASA
authentication. Opening this port allows
ZENworks Configuration Management to
manage devices outside of the firewall. It is
a good practice to make sure that the
network is configured to always allow
communication on this port between the
ZENworks Server and ZENworks Agents on
managed devices.
If other services are running on ports 80 and
443, such as Apache, or are used by OES2,
the installation program asks you for new
ports to use.
IMPORTANT: If you plan to use
AdminStudio 9.0 ZENworks Edition, it
requires that the Primary Server is using
ports 80 and 443.
2645 Used for CASA authentication. Opening this
port allows ZENworks Configuration
Management to manage devices outside of
the firewall. It is a good practice to make
sure that the network is configured to
always allow communication on this port
between the ZENworks Server and
ZENworks Agents on managed devices.
5550 Used by Remote Management Listener by
default.You can change this port in the
Remote Management Listener dialog box in
ZENworks Control Center.
Item Requirements Additional Details

System Requirements 13
novdocx (en) 16 April 2010
NOTE: If a Primary Server is behind a NAT firewall, the devices on the Internet or public network
cannot communicate with it.
5750 Used by Remote Management proxy.
5950 Used by Remote Management service by
default. You can change this port in the
Remote Management Settings panel of the
Remote Management Configuration page in
ZENworks Control Center.
7628 Used by the Adaptive Agent.
8005 Used by Tomcat to listen to shutdown
requests. This is a local port, and cannot be
accessed remotely.
8009 Used by Tomcat AJP connector.
Firewall Settings:
UDP Ports
67 Used by proxy DHCP when it is not running
on the same device as the DHCP server.
69 Used by the Imaging TFTP, but will not work
across firewall because it opens random
UDP port for each PXE device.
997 Used by the Imaging Server for
multicasting.
1761 Port 1761 on the router is used to forward
subnet-oriented broadcast magic packets
for Wake-On-LAN.
4011 Used for proxy DHCP when it is running on
the same device as the DHCP server. Make
sure that the firewall is configured to allow
the broadcast traffic to the proxy DHCP
service.
13331 Used by the zmgpreboot policy, but will not
work across firewall because it opens
random UDP port for each PXE device.
Virtual Machine
Environments
ZENworks Configuration Management
server software can be installed in the
following virtual machine
environments:
VMware Workstations
Microsoft Virtual Server
XEN (Novell SLES 10 and Citrix
XenServer)
VMWare ESX
Windows 2008 Hyper Visor
When using a SLES 10 32-bit guest OS on
VMware ESX 3.5, do not use the VMI
kernel. For more information, see TID
7002789 in the Novell Support
Knowledgebase (http://support.novell.com/
search/kb_index.jsp).
Item Requirements Additional Details

14 ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
1.2 Satellite Requirements
A satellite is a device that can perform certain roles that a ZENworks Primary Server normally
performs. A satellite can be a managed device (Windows) or an unmanaged device (Linux) that has
the ZENworks Adaptive Agent installed on it.
The following sections contain more information:
Section 1.2.1, “Windows Device Performing Satellite Roles,” on page 14
Section 1.2.2, “Linux Device Performing Satellite Roles,” on page 15
1.2.1 Windows Device Performing Satellite Roles
In addition to their usual functions, Windows devices can be used as satellites. Make sure that when
you use these managed devices for satellites, they are capable of performing the satellite functions.
A Windows device performing satellite roles must meet the minimum requirements of a Windows
managed device listed in Section 1.6, “Managed Device Requirements,” on page 21 with the
following exceptions:
Windows Embedded XP is not a supported workstation operating system for Satellite devices.
Satellite devices require additional TCP and UDP ports to be open.
The following table lists the additional TCP and UDP ports that must be open on a Satellite device:
Table 1-2 Additional Ports Required for a Managed Device Performing Satellite Roles
Item Requirements Additional Details
Firewall Settings: TCP
Ports
80 Make sure that the port is same as the HTTP port used
by the parent Primary Server.
IMPORTANT: If you plan to use AdminStudio 9.0
ZENworks Edition, it requires that the Primary Server is
using port 80.
443 Port 443 is used for CASA authentication. Opening this
port allows ZENworks Configuration Management to
manage devices outside of the firewall. It is a good
practice to make sure that the network is configured to
always allow communication on this port between the
ZENworks Server and ZENworks Agents on managed
devices.
998 Used by Preboot Server.
Firewall Settings: UDP
Ports
67 Used by proxy DHCP when it is not running on the same
device as the DHCP server.
69 Used by the Imaging TFTP, but will not work across
firewall because it opens random UDP port for each PXE
device.
997 Used by the Imaging Server for multicasting.

System Requirements 15
novdocx (en) 16 April 2010
1.2.2 Linux Device Performing Satellite Roles
Currently, ZENworks Configuration Management lets you manage Windows devices only.
However, you can use an unmanaged Linux device to perform satellite roles.
The Linux device performing satellite roles must meet the following requirements:
Table 1-3 Linux Device Performing Satellite Roles Requirements
4011 Used for proxy DHCP when it is running on the same
device as the DHCP server. Make sure that the firewall is
configured to allow the broadcast traffic to the proxy
DHCP service.
13331 Used by the zmgpreboot policy, but will not work across
firewall because it opens random UDP port for each PXE
device.
Item Requirements Additional Details
Operating System:
Servers
SLES 10 SP1 / SP2 / SP3 x86, x86-
64 (Intel and AMD Opteron*
processors)
OES 2 SP1 / SP2 x86, x86-64
SLES 11 x86, x86-64 (Intel and
AMD Opteron processors)
Operating System:
Workstations
SUSE Linux Enterprise Desktop 10
(SLED 10) SP1 / SP2 x86, x86-64
SLED 11 x86, x86-64
Hardware Processor: Minimum - Pentium* IV
2.8 GHz 32-bit (x86) and 64-bit
(x86-64), or equivalent AMD or Intel
processor
RAM: 512 MB minimum; 2 GB
recommended
Disk Space: 128 MB minimum for
installing; 4 GB recommended for
running. Depending on the amount
of content you need to distribute,
this number can vary greatly.
Display resolution: 1024 × 768
with 256 colors minimum
Item Requirements Additional Details

16 ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
Hostname Resolution The server must resolve device
hostnames by using a method such
as DNS (recommended).
Server names must support DNS
requirements, such as not having
underscores in their names, or
ZENworks login fails. Acceptable
characters are the letters a-z
(uppercase and lowercase),
numbers, and the hyphen (-).
If you use DNS, it must be properly
set up, or some features in
ZENworks might not work.
IP Address The server must have a static IP
address or a permanently leased
DHCP address.
An IP address must be bound to all
NICs on your target server.
The agent installation hangs if it is
trying to use a NIC that does not
have an IP address bound to it
TCP Ports 80 80 is for Tomcat non-secure port.
If the server is running other
services on ports 80 and 443, such
as Apache, or are used by OES2,
the installation program asks you
for new ports to use. However, you
must make sure that the new port is
same as the HTTP port used by the
parent Primary Server.
998 Used by Preboot Server.
7628 Used by the Adaptive Agent.
8005 Used by Tomcat to listen to
shutdown requests. This is a local
port, and cannot be accessed
remotely.
8009 Used by Tomcat AJP connector.
UDP Ports 67 Used by proxy DHCP when it is not
running on the same device as the
DHCP server.
69 Used by the Imaging TFTP, but will
not work across firewall because it
opens random UDP port for each
PXE device.
997 Used by the Imaging Server for
multicasting.
Item Requirements Additional Details

System Requirements 17
novdocx (en) 16 April 2010
1.3 Management Zone Version Requirements
If you are installing another Primary Server into an existing Management Zone, the product version
of the installation media must be compatible with the product version of the Management Zone. For
example:
Table 1-4 Management Zone Version Compatibilities with Installation Media Versions
4011 Used for proxy DHCP when it is
running on the same device as the
DHCP server. Make sure that the
firewall is configured to allow the
broadcast traffic to the proxy DHCP
service.
13331 Used by the zmgpreboot policy, but
will not work across firewall
because it opens random UDP port
for each PXE device.
Virtual Machine
Environments
ZENworks Configuration Management
server software can be installed in the
following virtual machine environments:
VMware Workstations
Microsoft Virtual Server
XEN (Novell SLES 10 and Citrix
XenServer)
VMWare ESX
Windows 2008 Hyper Visor
Management Zone Product Version Compatible Installation Media Incompatible Installation Media
10.0.0: ZENworks 10
Configuration Management (initial
release, electronic-only).
The version is established by
installing the first server in the
Management Zone.
ZENworks 10 Configuration
Management (10.0.0: initial
release, electronic-only).
Any version of the product
that is newer than the
Management Zone’s
version.
10.0.1: ZENworks 10
Configuration Management
(media and electronic release).
The version is established by
installing the first server in the
Management Zone.
ZENworks 10 Configuration
Management (10.0.1: media and
electronic release).
or
To perform an update from
version 10.0.0, see TID 3407754
in the Novell Support
Knowledgebase (http://
support.novell.com/search/
kb_index.jsp).
ZENworks 10 Configuration
Management (10.0.0: initial
release, electronic-only).
Any version of the product
that is newer than the
Management Zone’s
version.
Item Requirements Additional Details

18 ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
10.0.2: Update for ZENworks 10
Configuration Management.
The version is established by
updating the ZENworks database
in the Management Zone to
version 10.0.2 using the System
Update feature in ZENworks
Control Center. This is done by
the Primary Server that performs
the update task.
For more information on System
Updates, see “Introduction to
ZENworks System Updates” in
the ZENworks 10 Configuration
Management System
Administration Reference.
ZENworks 10 Configuration
Management (10.0.1: media and
electronic release). The newly
installed server is automatically
updated to version 10.0.2 under
one of the following conditions:
If only part of the zone has
been updated, after the new
server is installed it is
automatically updated when
the update moves to the
remaining devices in the
zone.
If the configured update
stages have all been
completed, the new server
is automatically updated
after it is installed.
If you have selected to
bypass staging, the new
server is automatically
updated after it is installed.
ZENworks 10 Configuration
Management (10.0.0: initial
release, electronic-only).
Any version of the product
that is newer than the
Management Zone’s
version.
Management Zone Product Version Compatible Installation Media Incompatible Installation Media

System Requirements 19
novdocx (en) 16 April 2010
10.0.3: Update for ZENworks 10
Configuration Management.
The version is established by
updating the ZENworks database
in the Management Zone to
version 10.0.3 by installing from
the new installation media or by
using the System Update feature.
For more information on System
Updates, see “Introduction to
ZENworks System Updates” in
the ZENworks 10 Configuration
Management System
Administration Reference.
ZENworks 10 Configuration
Management update (10.0.3:
media and electronic release).
The newly installed server is
automatically updated to version
10.0.3 under one of the following
conditions:
If only part of the zone has
been updated, after the new
server is installed it is
automatically updated when
the update moves to the
remaining devices in the
zone.
If the configured update
stages have all been
completed, the new server
is automatically updated
after it is installed.
If you have selected to
bypass staging, the new
server is automatically
updated after it is installed.
If you try to use the install from a
previous version’s media (prior to
version 10.0.3), authentication to
the zone fails and you receive the
following error message:
The credentials you
entered cannot be
validated on the
specified primary server.
Please verify your server
address and credentials,
and/or network
connectivity and try
again.
ZENworks 10 Configuration
Management (10.0.0: initial
release, electronic only).
ZENworks 10 Configuration
Management (10.0.1: initial
media release).
Any version of the product
that is newer than the
Management Zone’s
version.
10.1.x ZENworks 10 Configuration
Management (10.1.0).
ZENworks 10 Configuration
Management (10.0.x).
10.2.x ZENworks 10 Configuration
Management (10.2.0 / 10.1.0).
ZENworks 10 Configuration
Management (10.0.x).
10.3.x ZENworks 10 Configuration
Management (10.3.0 / 10.2.0).
ZENworks 10 Configuration
Management (10.1.0 / 10.0.x).
Management Zone Product Version Compatible Installation Media Incompatible Installation Media

20 ZENworks 10 Configuration Management Installation Guide
novdocx (en) 16 April 2010
1.4 Database Requirements
If you choose to use a database for the ZENworks database other than the embedded Sybase SQL
Anywhere database that is available as the default for ZENworks 10 Configuration Management, the
other database must meet the following requirements:
Table 1-5 Database Requirements
Item Requirement
Database Version Sybase* SQL Anywhere 10.0.1; Sybase SQL Anywhere 10.0.1.3519 or later
for ZENworks Reporting Server
Microsoft SQL Server* 2005 (Enterprise and Standard editions are supported)
Oracle* 10g Standard Release 2 - 10.2.0.1.0
Default Character Set For Sybase and MS SQL, the UTF-8 character set is required.
For Oracle, the NLS_CHARACTERSET parameter must be set to AL32UTF8
and the NLS_NCHAR_CHARACTERSET parameter must be set to
AL16UTF16.
TCP ports The server must allow Primary Server communication on the database port.
For MS SQL, make sure to configure static ports for the database server.
The default ports are:
1433 for MS SQL
2638 for Sybase SQL
1521 for Oracle
IMPORTANT: You can change the default port number if you have a conflict.
However, you must make sure that the port is opened for the Primary Server to
talk to the database.
WAN consideration Primary Servers and the ZENworks database must reside on the same network
segment. Primary Servers cannot write across a WAN to the ZENworks
database.
Collation ZENworks 10 Configuration Management is not supported with a case-
sensitive instance of the MS SQL database. Hence, you must make sure that
the database is case insensitive before setting it up.
Database User Make sure that there is no restriction for the ZENworks database user to
connect to a remote database.
For example, if the ZENworks database user is an Active Directory user, make
sure that the Active Directory policies allow the user to connect to a remote
database.