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:

Operating System additionally supported in Update for ZENworks 10 Configuration Management SP3 (10.3.1)

Hardware

If the Primary Server is running Patch Management, we recommend a fast processor, such as the Intel Core Duo processor

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.

For Linux servers, you might want the /opt/novell directory to be located on a large partition. This is where the ZENworks Installables are stored and it is likely that the content in this directory might increase in size after each upgrade, until the Managed Zone is baselined.

Hostname Resolution

The servers and workstations in the Management Zone must resolve device hostnames by using properly configured DNS, otherwise some features in ZENworks will not work properly. If the DNS is not properly configured, the servers cannot communicate with each other, and the workstations cannot communicate with the servers.

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 (-).

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.

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, 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.

5550

Used by Remote Management Listener by default.You can change this port in the Remote Management Listener dialog box in ZENworks Control Center.

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.

8005

Used by Tomcat to listen to shutdown requests. This is a local port, and cannot be accessed remotely.

Firewall Settings: UDP Ports

67

Used by proxy DHCP when it is not running on the same device as the DHCP server.

997

Used by the Imaging Server for multicasting.

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.

Virtual Machine Environments

ZENworks Configuration Management server software can be installed in the following virtual machine environments:

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.

For more information on Primary Servers running on ESX, see Tasks to be performed on VMware ESX