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 Asset Management. However, we recommend that any server where you install the Primary Server software be used only for ZENworks 10 Asset Management purposes.

For example, you might not want the server to do the following:

  • Host Novell eDirectory

  • Host Novell Client32

  • Host Active Directory

  • Be a terminal server

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)

  • Windows Server 2003 R2 SP2 x86, 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 Asset 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.

Before you install a ZENworks Server on a SLES 11 x86_64 device, you must ensure that pam-32 bit libraries are installed on the device because the CASA rpms are dependent on these libraries.

To install pam-32 bit libraries:

  1. Log in to the Linux device as the root user.

  2. Insert the Linux installation media.

  3. Run Yast to open the YaST Control Center.

  4. Click Software > Software Management.

  5. In the Search option, specify CASA and click OK to list all the CASA packages.

  6. Select the pam-32 package and click Install > Apply.

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

  • SLES 11 SP1 x86, x86-64 (Intel and AMD Opteron processors)

 

Operating System additionally supported in Update for ZENworks 10 Asset Management SP3 (10.3.3)

Open Enterprise Server 2 (OES 2) SP3

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

 

Display resolution: 1024 × 768 with 256 colors minimum

 

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

 

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 Asset 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:

    • libgdiplus0
    • 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.

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

Remote Management is used only with ZENworks Asset Management.

 

5750

Used by Remote Management proxy.

Remote Management is used only with ZENworks Asset Management.

 

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.

Remote Management is used only with ZENworks Asset Management.

 

7628

Used by the Adaptive Agent for Quick Tasks.

 

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.

The Imaging TFTP is used only with ZENworks Asset Management.

 

997

Used by the Imaging Server for multicasting.

The Imaging Server is used only with ZENworks Asset Management.

 

 

 

 

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.

The zmgpreboot policy is used only with ZENworks Asset Management.

Virtual Machine Environments

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

  • VMware Workstation

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

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

NOTE:If a Primary Server is behind a NAT firewall, the devices on the Internet or public network cannot communicate with it. To resolve the issue, you must configure additional IP addresses or DNS names for the Primary Server through ZENworks Control Center. For more information on how to configure additional access to a Primary Server, see Configuring Additional Access to a ZENworks Server in the ZENworks 10 Asset Management System Administration Reference.