ZENworks System Requirements

The following sections provide the ZENworks 24.4 system requirements for hardware and software:

1.0 Primary Server Requirements

Ensure that the server where you install the Primary Server software meets the following requirements:

NOTE:The operating systems listed below are the ones on which the ZENworks Primary Server software can be installed. The list does not necessarily represent the operating systems that ZENworks Patch Management can update.

For this list, see the following links:

NOTE:ZENworks no longer supports Windows Server as a Primary Server from version 24.2 onwards. For more information, see End of Support for Windows Primary Server.

Item

Requirements

Additional Details

Server Usage

Your server might be capable of handling tasks in addition to the tasks that a Primary Server performs. However, we recommend that any server where you install the Primary Server software be used only for ZENworks.

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

  • Host NetIQ eDirectory

  • Host Active Directory

  • Host Terminal Services

Operating System Linux

  • SLES 12 SP5 x86_64

  • SLES 15 SP3 x86_64

  • SLES 15 SP4 x86_64

  • SLES 15 SP5 x86_64

  • SLES 15 SP6 x86_64

IMPORTANT:

  • Remote management is not supported on Linux devices at runlevel 3 (text-only, no X server).

  • If ZENworks is already installed on the system, do not perform a major in-place upgrade of the operating system (for example, from SLES 12 to SLES 15) as this might cause issues and the Primary Servers might have to be replaced.

    Minor, in-place upgrades of the operating system are supported. For example, from SLES 15 to SLES 15 SP1.

    For information on how to replace the servers, see Replacing Primary Servers in the ZENworks Disaster Recovery Reference.

Processor

Speed:2.0 GHz or faster

Type: Quad-core or faster

 

RAM

16 GB minimum

16 GB for 3000 devices. Add 1 GB RAM for every additional 3000 devices. If you are using Vertica, please refer to Vertica system requirements.

Disk Space

40 GB for installation. Depending on the amount of content you need to distribute the space.

For ZENworks database add 10 GB for every 1000 devices and for Audit database add 10 GB for every 5000 devices.

500 MB is recommended for the tmp directory. This disk space is required for rebuilding and editing the packages.

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.

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 Primary Server and Satellite 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.

The /etc directory requires less space.

DNS Resolution

The servers and workstations in the Management Zone must use properly configured DNS to resolve device hostnames; 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 including underscores; otherwise, ZENworks login fails. Acceptable characters include the letters a-z (uppercase and lowercase), numbers, and the hyphen (-). Non-english characters are not supported.

NOTE:If the host name of a Linux Primary Server contains upper case characters, the server host name should be included in the /etc/hosts file located on that server.

 

IP Address

The server must have a static IP address or a permanently leased IP address in the case of DHCP configuration.

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.

Firewall Settings: TCP and UDP Ports

Many TCP and UDP ports are opened by the ZENworks Installer during installation. If a port required by ZENworks is in use, the ZENworks Installer prompts you to configure an alternate port.

IMPORTANT:If the firewall is disabled during installation or upgrade, ensure that you manually open the ports in the firewall settings when the firewall is enabled.

For the list of TCP and UDP ports and how ZENworks uses them, see ZENworks TCP and UDP Ports.

Supported Hypervisors

ZENworks managed device software can be installed on the guest operating systems (VMs) of the following hypervisors:

  • XEN on SLES 12 SP3, SP4, SP5 and SLES 15 SP1, SP2, SP3, SP4, SP5 and SP6

  • VMware ESXi 6.5.x, 6.7.x, 7.x and 8.x

  • Microsoft Hyper-V Server Windows 2012, 2012 R2, 2016 and 2019

  • Citrix Hypervisor 8.x

  • Proxmox 8.x

  • Only released versions of guest operating systems (VMs) are supported. Experimental guest operating systems are not supported.

  • The guest operating system must match the operating system specified when creating the VM. For example, if during creation of the VM, the guest operating system is specified as Windows Server 2012, the actual guest operating system must be Windows Server 2012.

Docker Support

  • Docker: version 19.x or higher

  • Docker Compose: version 1.x

For more information, see Changes in the Primary Server Upgrade or Migration Process in the Upgrade guide.

 

2.0 Virtual Appliance Requirements

Item

Requirement

Additional Details

ZENworks Virtual Appliance

  • RAM: 16 GB recommended

  • Cores: 8

  • Disk Space: 80 GB minimum

NOTE:

  • For more information on the system requirements for Vertica, and Kafka servers click here.

  • By default, the appliance is configured with the requirements for a Vertica-based environment. For a non-Vertica environment you can decrease the number of cores from 8 to 4.

ZENworks Virtual Appliance, based on SLES 12 SP5, can be deployed in the following virtual machine environments:

  • VMware ESXi 6.5.x, 6.7.x, 7.x, 8.x

  • Microsoft Hyper-V Server Windows 2012, 2012 R2, 2016 and 2019.

  • XEN on SLES 12, SLES 15 SP3 and SP4 and the support packs.

  • Citrix Hypervisor 8.x, XENServer 8

  • Proxmox 8.x

3.0 Managed Device Requirements

The ZENworks Agent is the management software that is installed on all managed devices, including Primary Servers.

NOTE:

  • After updating the Primary and Satellite Servers to ZENworks 2020 Update 3, all managed devices with ZENworks 2017 Update 1 or older agents will cease to communicate with servers. 

    It is recommended that you update managed devices with ZENworks 2017 Update 1 or older agents to ZENworks 2020 Update 2 before updating servers.

  • Managed devices using anti virus software should have the paths that are referenced in the TID 7007545, added to the AV exclusion list, before installing, updating, or upgrading the ZENworks Agent on a client device.

  • The operating systems listed below are the ones on which the ZENworks Agent software can be installed. The list does not necessarily represent the operating systems that ZENworks Patch Management can update.

    For this list, see the following links:

  • To install the ZENworks Agent on devices with the latest version of operating systems that are still not a part of the support matrix, see Adding Support for Newly Released Versions of Operating Systems

3.1 Windows Managed Device Requirements

ZENworks 2020 or later versions can manage any Windows workstation and server that meets the following requirements:

Item

Requirements

Additional Details

Operating System: Windows Servers

  • Windows 2012 Server x86_64 (Foundation, Essential, Standard, Datacenter)

  • Windows 2012 R2 Server x86_64 (Foundation, Essential, Standard, Datacenter)

  • Windows 2016 Server x86_64 (Essential, Standard, Datacenter and Storage)

  • Windows 2019 Server x86_64 (Essential, Standard, Datacenter and Storage)

  • Windows 2022 Server x86_64 (Essential, Standard, Datacenter and Storage)

IMPORTANT:In the backward compatibility mode, the 11.3.x version of the agent cannot be updated. However, it can be managed. You can also register new managed devices with the older versions of the agent to the zone, and manage them, but you cannot upgrade the older agents.

 

Operating System: Windows Workstations

  • **Windows 10 x86, x86_64 (Professional, Enterprise, Education, up to version 22H2)

  • **Windows 10 x86, x86_64 (Up to the 2016 Enterprise and 2016 LTSB editions)

  • **Windows 10 Enterprise LTSC 2019, x86, x86_64

  • **Windows 10 Enterprise x86_64 (Enterprise 2021 LTSC)

  • Windows 10 IoT (Enterprise 2019 LTSC)

  • Windows 11 x86_64 (Professional and Enterprise, up to 24H2)

A managed device name must not exceed 32 characters. If a device name exceeds 32 characters, that device is not inventoried. In addition, ensure that the device name is unique so that the device is recognized appropriately in the inventory reports.

 

IMPORTANT:

  • ** Indicates that support is provided for the demotion and re-configuration of existing 32-bit Satellites but not for the promotion and addition of new Satellite roles for 32-bit platforms.

  • Windows 7 is not supported.

IMPORTANT:

  • ZENworks supports Windows 10 that is migrated from older versions (Windows 7, Windows 8, and Windows 8.1).

    Microsoft does not retain the applications from the older versions of Windows to Windows 10 across editions. Hence, ZENworks will not be available if you migrate to Windows 10 from different editions (Windows older versions).

    For example:

    Windows 7 Enterprise to Windows 10 Enterprise or Enterprise LTSB is supported.

    Windows 8 Enterprise to Windows 10 Education is not supported.

Operating System: Thin Client sessions

  • Windows Server 2012 SP2

  • Windows Server 2012 R2 SP1

  • Windows 2016 Server x86_64

  • Windows 2019 Server x86_64

  • Windows 2022 Server x86_64

  • XenApp 7.6 LTSR, 7.15 LTSR

  • Citrix Virtual Apps & Desktops 1912 LTSR, 2203 LTSR, 2305, 2308, 2311, 2402 LTSR, 2407

Hardware

The following are minimum hardware requirements. Use these requirements or the hardware requirements provided with your operating system, whichever is greater.

  • Processor: Pentium III 700 MHz, or equivalent AMD or Intel

  • RAM: 256 MB minimum; 1 GB recommended

  • Disk Space: 230 MB minimum for installing; 4GB recommended for running. Depending on the amount of content you need to distribute, this number can vary greatly.

    If an agent is promoted to a content or imaging satellite role, ensure that you increase the disk space accordingly.

 

Microsoft .NET

The Microsoft .NET 4.8 framework and its latest updates must be installed and running on the Windows managed device in order to install ZENworks 2020 or later versions.

On Windows Server 2012, .NET is available by default. However, you must enable the .NET framework before deploying the agent on these devices.

Microsoft Windows Installer

The Microsoft Windows Installer 4.5 or later must be installed and running on the Windows managed device in order to install ZENworks 2020 Update 3 or later versions.

If you choose to deploy the PreAgentPkg_AgentCompleteDotNet.exe standalone package, Windows Installer 4.5 is automatically installed. If you choose to deploy the PreAgentPkg_Agent.exe network package or the PreAgentPkg_AgentComplete.exe standalone (.NET required) package, you must manually install Windows Installer 4.5 or later before you begin to install the agent.

TCP Port

5950

For Remote Management where the ZENworks Agent is running, the device listens on port 5950.

You can change the port in ZENworks Control Center (Configuration tab >Management Zone Settings > Device Management > Remote Management).

Remote Management is used only with ZENworks Configuration Management.

Supported Hypervisors

ZENworks managed device software can be installed on the guest operating systems (VMs) of the following hypervisors:

  • XEN on SLES (XEN on SLES 12 SP3, SP4, SP5 and SLES 15, SP1, SP2, SP3, SP4, SP5, SP6)

  • VMware ESXi 6.5.x, 6.7.x, 7.x, 8.x

  • Microsoft Hyper-V Server Windows 2012, 2012 R2, 2016 and 2019.

  • Citrix Hypervisor 8.x

  • Proxmox 8.x

Only released versions of guest operating systems (VMs) are supported. Experimental guest operating systems are not supported.

The guest operating system must match the operating system specified when creating the VM.

Deployment of ZENworks Virtual Appliance is not supported on the Citrix XenServer

Supported Virtual Desktop Interface

ZENworks managed device software can be installed in the following VDI environments:

  • VMware Horizon View 7.x, 8.x

  • Microsoft VDI Windows 2012, 2012 R2, 2016, 2019, 2022

  • Citrix Virtual Apps and Desktops (7 1912 LTSR, 7 2203 LTSR, 2305, 2308, 2311, 2402 LTSR, 2407)

  • Citrix XenApp (7.6 LTSR and 7.15 LTSR)

 

Client for Open Enterprise Server 2 SP4/Novell Client

The Novell Client is not required. However, if you choose to use the Novell Client on the managed device, the following versions are supported with ZENworks:

  • Client 2 SP4 and higher (for Windows 7, 8, 8.1 and Windows 10)

  • Client 2 SP4 and higher (for Windows Server 2008, 2008 R2 and 2012)

 

3.2 Linux Managed Device Requirements

ZENworks can manage any Linux workstation and server that meets the following requirements:

Item

Requirements

Operating System: Servers

  • SLES 12 SP4 x86_64

  • SLES 12 SP5 x86_64

  • SLES 15 SP1 x86_64

  • SLES 15 SP2 x86_64

  • SLES 15 SP3 x86_64

  • SLES 15 SP4 x86_64

  • SLES 15 SP5 x86_64

  • SLES 15 SP6 x86_64

  • Open Enterprise Server 2018 SPE and SP3 (OES 2018 SP2 & SP3) x86_64

  • Open Enterprise Server 2023 (OES 2023) x86_64 - Available only with ZENworks 2020 Update 3 - FTF 20.3.0.957 or later.

  • Open Enterprise Server 2023.4 (OES 23.4) x86_64

  • Open Enterprise Server 24.1

  • Open Enterprise Server 24.2

  • Open Enterprise Server 24.3

NOTE:ZENworks Patch Management will not be detected on Appliance and OES devices.

Operating System: Workstations

  • SLED 12 SP4 x86_64

  • SLED 12 SP5 x86_64

  • SLED 15 x86_64

  • SLED 15 SP1 x86_64

  • SLED 15 SP2 x86_64

  • SLED 15 SP3 x86_64

  • SLED 15 SP4 x86_64

  • SLED 15 SP6 x86_64

  • OpenSUSE Leap 15.3, 15.4, 15.5

  • RHEL 8.2, 8.4, 8.6, 8.8, 8.10 (without RHN subscription)

  • RHEL, 9.2, 9.4 (without RHN subscription)

  • RHEL 8.7 (x86, x86_64) - Available only with ZENworks 2020 Update 3 - FTF 20.3.0.957 or later

  • **RHEL 7.9 x86_64 (without RHN subscriptions)

    NOTE:Installing ZENworks Agent on RHEL 8.x is registered as RHEL 8.1 Workstation. For more information on setting the device type, see the Troubleshooting section in the ZENworks Agent Guide.

  • CentOS 8.x

  • **Scientific Linux 7.9 x86, x86_64 (without RHN subscription)- (Supported in Backward Compatibility Mode - Installed Agent continues to work)

* Indicates that the platform is supported in the backward compatibility mode, with the 11.x version of the agent running on them.

** Indicates that support is provided for the demotion and re-configuration of existing 32-bit Satellites but not for the promotion and addition of new Satellite roles for 32 bit platforms.

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: 230 MB minimum for installing; 4 GB recommended for running. Depending on the amount of content you need to distribute, this number can vary greatly.

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; otherwise, ZENworks login fails. Acceptable characters are the letters a-z (uppercase and lowercase), numbers, and the hyphen (-). If the server host name contains upper case characters, the server host name should be included in the /etc/hosts file located on that server.

    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.

  • If you have multiple NICs, we recommend that you bind the IP addresses on all the NICs. However, ZENworks works even if one IP address is configured.

Supported Hypervisors

ZENworks managed device software can be installed in the following hypervisors:

  • XEN ( SLES 12, SLES 15)

  • VMware ESXi 6.5.x, 6.7.x, 7.x, 8.x

  • Microsoft Hyper-V Server Windows 2012, 2012 R2, 2016 and 2019.

In addition, the following requirements apply:

  • Only released versions of guest operating systems (VMs) are supported. Experimental guest operating systems are not supported.

  • The guest operating system must match the operating system specified when creating the VM. For example, if the guest operating system is specified as SLES 12 during creation of the VM, the actual guest operating system must be SLES 12.

3.3 Macintosh Managed Device Requirements

ZENworks can manage Macintosh workstations that run the following operating systems:

NOTE:

  • * Indicates that the platform is supported only in the backward compatibility mode.

  • In ZENworks 2020 Update 3, the ZENworks Patch Management advanced feed does not support patching of macOS devices. Update to ZENworks 23.3 to gain support for patching macOS devices using the advanced patch feed.

*Macintosh 10.8.3 (Mountain Lion)

Item

Requirements

Version

10.8.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

*Macintosh 10.9.x (Mavericks)

Item

Requirements

Version

10.9.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

*Macintosh 10.10.x (Yosemite)

Item

Requirements

Version

10.10.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

*Macintosh 10.11.x (EL Capitan)

Item

Requirements

Version

10.11.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

*Macintosh 10.12.x (Sierra)

Item

Requirements

Version

10.12.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

Macintosh 10.13.x (High Sierra)

Item

Requirements

Version

10.13.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

Macintosh 10.14.x (Mojave)

Item

Requirements

Version

10.14.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

Macintosh 10.15.x (Catalina)

Item

Requirements

Version

10.15.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

NOTE:For Mac devices the minimum RAM required is 2 GB and the recommended RAM is 4GB.

Macintosh 11.x (Big Sur)

Item

Requirements

Version

11.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Apple M1

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

NOTE:For Mac devices the minimum RAM required is 2GB and the recommended RAM is 4GB.

Macintosh 12.x (Monterey)

Item

Requirements

Version

12.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Apple M1

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

NOTE:For Mac devices the minimum RAM required is 2GB and the recommended RAM is 4GB.

Macintosh 13.x (Ventura)

Item

Requirements

Version

13.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Apple M- series (M1 and M2)

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

NOTE:For Mac devices, the minimum RAM required is 2GB and the recommended RAM is 4GB.

Macintosh 14.x (Sonoma)

Item

Requirements

Version

14.x

Supported Architecture

64 bit

Hardware

  • Processor Intel Core 2 Duo

  • Apple M- series (M1 and M2)

  • Disk space: 2 GB recommended for running.

  • Display resolution:1024 × 768 with 256 colors minimum

TCP ports

7628

NOTE:For Mac devices, the minimum RAM required is 2GB and the recommended RAM is 4GB.

4.0 Satellite Requirements

A Satellite is a managed device that can perform some of the roles that a ZENworks Primary Server normally performs, including authentication, information collection, content distribution, and imaging. A Satellite can be any managed Windows, or Linux device (server or workstation), but not a Primary Server.

The following sections contain more information:

4.1 Windows Satellite Requirements

A Windows device performing Satellite roles must meet the minimum requirements of a Windows managed device, as listed in Windows Managed Device Requirements with the following exception:

The following table lists additional Windows Satellite requirements:

Item

Requirements

Additional Details

ZENworks Agent Version

Same version as the ZENworks Primary Server

When you create a Satellite, you designate a ZENworks Primary Server as the parent server for the Satellite. The Satellite’s agent version must be the same version as the parent Primary Server version. For example, the Satellite’s agent version cannot be 11.4.3 if the parent Primary Server version is 2020 or later.

 

443

Used for CASA authentication.

998

Used by Preboot Server (novell-pbserv).

The Preboot Server (novell-pbserv) is used only with ZENworks Configuration Management.

 

7019

Used by Join Proxy.

Firewall Settings: Open 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 the firewall because it opens a random UDP port for each PXE device.

The Imaging TFTP is used only with ZENworks Configuration Management.

 

997

Used by the Imaging Server for multicasting.

The Imaging Server is used only with ZENworks Configuration Management.

 

4011

Used for proxy DHCP when it is running on the same device as the DHCP server. Ensure 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 the firewall because it opens a random UDP port for each PXE device.

The zmgpreboot policy is used only with ZENworks Configuration Management.

4.2 Linux Satellite Requirements

A Linux device performing Satellite roles must meet the minimum requirements of a Linux managed device, as listed in Linux Managed Device Requirements.

The following table lists additional Linux Satellite requirements:

Item

Requirements

Additional Details

ZENworks Agent Version

Same version as the parent ZENworks Primary Server

When you create a Satellite, you designate a ZENworks Primary Server as the parent server for the Satellite. The Satellite’s agent version must be the same version as the parent Primary Server version. For example, the Satellite’s agent version cannot be 11.4.3 if the parent Primary Server version is 2020 or later.

Firewall Settings: Open TCP Ports

443

Used for CASA authentication.

 

998

Used by Preboot Server (novell-pbserv).

The Preboot Server (novell-pbserv) is used only with ZENworks Configuration Management.

 

7628

Used by the ZENworks 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.

 

7019

Used by Join Proxy.

Firewall Settings: Open 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 the firewall because it opens a random UDP port for each PXE device.

The Imaging TFTP is used only with ZENworks Configuration Management.

 

997

Used by the Imaging Server for multicasting.

The Imaging Server is used only with ZENworks Configuration 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 the firewall because it opens a random UDP port for each PXE device.

The zmgpreboot policy is used only with ZENworks Configuration Management.

5.0 Database Requirements

The database must meet the following requirements:

Item

Requirement

Database Version

  • Oracle 19c including Cluster and RAC

  • Oracle 21c including Cluster and RAC

  • Oracle 23ai

  • Microsoft SQL Server 2016, 2016 SP1 and later, including Cluster (Standard and Enterprise editions)

  • Microsoft SQL Server 2017, including Cluster (Standard and Enterprise editions)

  • Microsoft SQL Server 2019

  • Microsoft SQL Server 2022

  • Embedded PostgreSQL 16.x

    NOTE:To update to Embedded PostgreSQL 16.x, refer to PostgreSQL Upgrade tool.

  • External PostgreSQL 12.x, 13.x, 14.x, 15.x, 16.x

Database Server Hostname

The database server hostname must be resolvable by the Domain Name Server Service.

TCP Ports

The server must allow Primary Server communication on the database port. For MS SQL, ensure that you configure static ports for the database server.

Default Ports:

  • 1433 for MS SQL

  • 1521 for Oracle

  • 54327 for embedded PostgreSQL

  • 5432 for external PostgreSQL

You can change the default port number if there is a conflict. However, you must ensure that the port is opened for the Primary Server to talk to the database.

UDP Ports

1434 for MS SQL (if ZENworks uses named instance of 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.

Default Character Set

For MS SQL, ZENworks does not require any specific character set. ZENworks supports all character sets supported by MS SQL.

For Oracle, the NLS_CHARACTERSET parameter must be set to AL32UTF8, the MAX_STRING_SIZE parameter must be set to Standard and the NLS_NCHAR_CHARACTERSET parameter must be set to AL16UTF16. If the existing Oracle Database is installed with another character set, then to migrate to the AL32UTF8 character set, contact Oracle Support.

Collation

ZENworks is not supported with a case-sensitive instance of the MS SQL database. Therefore, you must ensure that the database is case insensitive before setting it up.

Database User

Ensure 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, ensure that the Active Directory policies allow the user to connect to a remote database.

6.0 Reporting Server Support

Item

Requirements

ZENworks Reporting Server Platform

ZENworks Reporting 8.1.x Appliance

ZENworks Reporting Server backward compatibility (support for the older versions).

ZENworks Reporting appliance released with ZENworks 2020 Update 2

Browser

Refer to Administration Browser Requirements

Database

Refer to Database Requirements

7.0 User Source Requirements

ZENworks can reference user sources such as eDirectory, Active Directory and Azure Active Directory (ZENworks 23.3 onwards) for user-related tasks such as assigning content to users and associating users with devices. LDAP (Lightweight Directory Access Protocol) is the protocol used by ZENworks for interacting with directories.

Item

Requirements

Authoritative user source

  • eDirectory 9.0 or above (on all supported platforms)

    If you use eDirectory as the user source, ensure that no two eDirectory users have the same user name and password. Even if the user names are the same, ensure that the passwords are different.

  • Microsoft Active Directory (as shipped with Windows 2016 or later)

  • Domain Services for Windows (DSfW)

LDAP version

LDAP v3

OPENLDAP is not supported. However, if you have eDirectory installed on a SUSE Linux server, you can use that as a user source. LDAP v3 can be used to access eDirectory on the Linux server by using the alternate ports that you specified for eDirectory when installing it (because OPENLDAP might have been using the default ports).

LDAP user access

ZENworks requires only read access to the LDAP directory. For more information, see Connecting to User Sources in the System Configuration.

LDAP Authentication

Simple bind

With simple bind, an application provides a Distinguished Name (DN) and the clear text password for that DN. To use a simple bind, the client must supply the DN of an existing LDAP entry and a password that matches the userPassword attribute for that entry. The Administrator can also enter the DN and the clear text password by using the Configuration page in ZENworks Control Center.

8.0 Inventoried-Only Device Requirements

You can use ZENworks to inventory workstations and servers by deploying the Inventory-Only module on these devices.

IMPORTANT:In situations where ZENworks product issues are caused by an issue with the platform, the following support standards apply:

  • Platforms that are generally supported by platform vendors are supported.

  • If the platform vendor provides support for installation through a special agreement (such as extended support), Open Text Support expects you to extend this support infrastructure to resolve the issue.

  • If the platform vendor does not support the platform, no additional support if provided.

The inventoried-only devices must meet the following requirements:

Item

Requirements

Operating System: Servers

  • Windows 2012 Server x86_64 (Foundation, Essential, Standard, Datacenter)

  • Windows 2012 R2 Server x86_64 (Foundation, Essential, Standard, Datacenter)

  • Windows 2016 Server x86_64 (Essential, Standard, Datacenter and Storage)

  • Windows 2019 Server x86_64 (Essential, Standard, Datacenter and Storage)

  • SLES 12 SP4 x86_64

  • SLES 12 SP5 x86_64

  • Support for following operating systems in ZENworks can be added by populating required platforms in the custom_ostargets.xml file.

  • SLES 15 x86_64

  • SLES 15 SP1 x86_64

  • SLES 15 SP2 x86_64

  • SLES 15 SP3 x86_64

  • SLES 15 SP4 x86_64

  • SLES 15 SP5 x86_64

  • Open Enterprise Server 2018 SP2 (OES 2018 SP2) x86_64

  • Open Enterprise Server 2018 SP3 (OES 2018 SP3) x86_64

  • Open Enterprise Server 2023 (OES 2023) x86_64 - Available only with ZENworks 2020 Update 3 - FTF 20.3.0.957 or later

  • Open Enterprise Server 2023.4 (OES 23.4) x86_64

  • Open Enterprise Server 24.1

  • Open Enterprise Server 24.2

  • Open Enterprise Server 24.3

  • OpenSUSE Leap 15.3, 15.4, 15.5

Operating System: Workstations

  • *Mac OS 10.8.3 to 10.10

  • Mac OS X 10.11

    NOTE:Mac OS 10.15 (Catalina) and Mac OS 11.x (Big Sur) and other newer versions of mac devices are no longer supported as Inventory-only devices.

  • **Windows 10 x86, x86_64 (Professional, Education, Enterprise, up to the April 2018 Update)

  • **Windows 10 1809 x86, x86_64

  • **Windows 10, 1903 x86, x86_64

  • **Windows 10, 1909 x86, x86_64

  • Windows 11 x86_64 (Professional and Enterprise, up to 23H2)

  • SLED 12 SP3 x86_64

  • SLED 12 SP5 x86_64

  • SLED 15 x86_64

  • SLED 15 SP1 x86_64

  • SLED 15 SP2 x86_64

  • SLED 15 SP3 x86_64

  • SLED 15 SP4 x86_64

  • SLED 15 SP5 x86_64

  • * RHEL 7.0, 7.1, 7.2 x86, x86_64 (without subscription)

  • RHEL 7.3, 7.4, 7.5, 7.6, 7.7, 8.0, 8.1, 8.2, 8.4, 8.6, 8.7, 8.8, 9.0, 9.1, 9.2 (without subscription)

  • RHEL 8.7 (x86, x86_64) (without subscription) - Available only with ZENworks 2020 Update 3 - FTF 20.3.0.957 or later

  • *Scientific Linux 7.0, 7.1 and 7.2 x86 and x86_64 (without RHN subscription)

  • **Scientific Linux 7.8, 7.9 x86_64 (without RHN subscription)

* Indicates that the platform is supported in backward compatibility mode (with the 11.x version of the agent installed)

** Indicates that support is provided for the demotion and re-configuration of existing 32-bit Satellites but not for the promotion and addition of new Satellite roles for 32 bit platforms.

Operating System: Thin Client Sessions

  • Windows Server 2012 SP2

  • Windows Server 2012 R2 SP1

  • Windows 2016 Server x86_64

  • Windows 2019 Server x86_64

  • Citrix XenApp 6, 6.5,7.6 onwards, 7.1x, 7 1906 7.6 LTSR , 7.15 LTSR, 7 1912 LTSR, 7 2203 LTSR, 7 2109, 7 2112, 7 2206, 7 2209, 7 2212, 7 2303.

Inventory Only Module

After installing ZENworks 2020 or later to your network, you must install this module on the above-listed devices to inventory them. For more information, see Deploying the Inventory-Only Module in the ZENworks Discovery, Deployment, and Retirement Reference.

Hardware: Disk Space

The Inventory-Only module requires the following minimum disk space:

  • Linux: 900 KB

  • Windows: 15 MB

9.0 Mobile Management Support

Item

Requirements

Browser Support - EUP

  • Google Chrome 95 onwards

  • Firefox ESR 91.x

  • Edge with Chromium Engine 95 onwards

  • Latest version of Safari

Browser Support - Mobile Devices

  • Google Chrome for Android devices

  • Safari for iOS devices

Mobile OS support

  • ZENworks Agent version 23.4 app supports Android 14

  • Android 10.x and higher

  • iOS 10.x and higher

    NOTE:ZENworks now supports the iPadOS platform that are iPad devices with iOS version 13 or later installed. This feature is by default in a disabled state and needs to be enabled after migrating to the ZENworks 2020 Update 1 or later versions. For more information, see Supported Devices for Mobile Management in the ZENworks Mobile Management Reference.

  • Windows 10.0 and higher (ActiveSync only)

ActiveSync Server Support

  • ActiveSync Server version 12.1 bundled with:

    • Microsoft Exchange 2007 and higher

    • GroupWise Mobility 2014.x and 2018.x

ActiveSync Client Support

  • Exchange ActiveSync 12.0 and higher. Tested on supported mobile operating system platforms.

10.0 Administration Browser Requirements

Ensure that the workstation or server where you run ZENworks Control Center to administer your system meets the following requirements:

Item

Requirements

Web Browser

The following web browsers are supported:

  • Firefox version 95 and higher

  • Firefox ESR 91.x

  • Chrome version 95 and higher

  • Edge Chromium 95 and higher

NOTE:Administration of features dependent on ZCC Helper is supported only on Windows and SUSE Linux Enterprise devices.

Display Resolution

1024 × 768 minimum screen resolution required for ZENworks Control Center

TCP Ports

To fulfill a user’s request for a remote session on a managed device, you must open port 5550 on the device, in order to run Remote Management Listener.

11.0 Installation User Requirements

The user running the installation program must have administrator or root privileges on the device. For example:

  • Windows: Log in as a Windows administrator.

  • Linux: If you log in as a non-root user, use the su command to elevate your privileges to root, then run the installation program.

12.0 Supported Smart Cards and Smart Card Readers

For information about smart cards and smart card readers supported for ZENworks login, see Novell Enhanced Smart Card Method Installation and Administration Guide.

If you are using ZENworks Full Disk Encryption, see Supported Smart Card Terminals and Tokens in the ZENworks Full Disk Encryption Agent Reference for information about smart cards supported for both ZENworks Full Disk Encryption Pre-Boot Authentication and general ZENworks login.

13.0 Platforms No Longer Supported

The following section displays the list of platforms that are not supported in ZENworks 24.4, but were supported in ZENworks 24.2.

Table 1 Unsupported Platforms

Item

Platforms

Primary Server

SLES 11 SP4 and earlier

SLES 12 SP4 and earlier

SLES 15 SP2 and earlier

Win 2003, Win 2008, Win 2008 R2

RHEL all versions

Windows Server all versions

Managed Device

Inventoried-Only Device Requirements

Agents with ZENworks 2017 Update 1

RHEL 8.5

RHEL 6.8 and earlier

SLES 11 SP4 x86_64

SLES 12 SP3 x86_64

Windows XP SP3 x86 (Professional and Enterprise)

Windows 8 x86, x86_64

Windows Embedded 8.1

Open Enterprise Server 2018 x86_64

Open Enterprise Server 2018 SP1 (OES 2018 SP1) x86_64

RHEL 6.x

Scientific Linux 6.9 and 6.10 x86 - without RHN subscription

Scientific Linux 7.0, 7.1 and 7.2 x86 and x86_64, 7.3 to 7.7, and 7.8 (without RHN subscription)

OpenSUSE Leap 42.3, 15 and 15.1, 15.2

Database Requirements

Oracle 12c R1 with version 12.1.0.2 Standard, Enterprise Edition and Oracle RAC (with or without partitioning).

Oracle 12c R2 with version 12.2.0.1 Standard, Enterprise Edition and Oracle RAC (with or without partitioning).

Oracle 18c R1 including Cluster and RAC

Oracle 20c including Cluster and RAC

Database Version

Microsoft SQL Server 2012 SP3 and later, including Cluster (Standard, Enterprise, and Business Intelligence editions)

External PostgreSQL 11.x

Thin Client

XENApp 6, 6.5, 7.x (7.6 onwards) - 7.1x, 7 1906, 7 2106

VDI support (XENDesktop and XENApp)

7 1906, 7 2106, 7 2109, 7 2112, 7 2206, 7 2209

7 1912 LTSR, 7 2203 LTSR, 7 1906, 7 2106, 7 2109, 7 2112, 7 2206, 7 2209, 7 2212, 7 2303

14.0 Legal Notice

For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see .

© Copyright 2008 - 2024 Open Text

The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.