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.

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.

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.

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.

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:

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

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.

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.

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: