Skip to main content

System Requirements

Network Infrastructure

DHCP Server

A basic requirement for running the openthinclient Management Server is the presence of a functioning DHCP server that assigns IP addresses to the thin clients. The virtual appliance also requires a DHCP server by default.

Since a wide range of easy-to-set-up DHCP solutions is already available and most networks include an integrated DHCP server, the openthinclient Management Server acts as a proxy DHCP server. It listens for DHCP traffic and supplements it with PXE boot information for the thin clients.

Note, DHCP can also assign static IP addresses.

Internet Connection

The openthinclient Management Server attempts to reach the following servers on the Internet:

  • archive.openthinclient.org Port 80 HTTP
    For installing OS packages and updating the manager and OS packages.
  • license.openthinclient.com Port 80 HTTP
    For updating and verifying purchased licenses.
  • statistics.openthinclient.com (redirects to Amazon Web Services) Port 443 HTTPS
    , transmit anonymized statistics to continuously improve the software.
Scenario: Existence of other proxy DHCP servers

If other proxy DHCP servers are already present in the target network, implement one of the following solutions.

  • Divide the network using VLAN (or similar techniques).
  • Use non-overlapping whitelists on the openthinclient Management Server and all other proxy DHCP servers.

The openthinclient Management Server uses a whitelist method by default. Control this behavior via the PXE service policy (see ProxyDHCP/PXE configuration).

openthinclient Management Server

To set up the openthinclient Management Server using the installer, ensure the following requirements are met:

  • 1 GB of free RAM
  • x86 64-bit CPU
  • Hard disk space:
    • Program: approx. 300 MB
    • Manager Home: min. 6 GB
  • Windows or Linux (any distribution)
Ports

Ensure these ports are available.

TCP
 UDP
 Service

67
 DHCP

68

DHCP only with eavesdropping PXE service

69
 TFTP
111
 111
 NFS portmapper

514
 syslog
2069
 2069
 NFS

4011
 DHCP
8080
HTTP Web Interface, REST
10389
LDAP

To use a static port with NFS, set the port for the mount daemon mountd . Edit the service.xml in the openthinclient-manager directory <Manager-Home>/nfs/service.xmlby setting the <mountdPort> value of 0 (for dynamic assignment) to a fixed value. This causes NFS to use this port for mount operations, allowing the firewall to remain open only for this port.

Virtual Appliance

Supported virtualization platforms:

Hardware requirements:

  • 4 GB RAM
  • 20 GB hard disk space

Thin Clients

Hardware requirements:

  • x86 64-bit CPU (PAE-capable)
  • 2 GB RAM
  • PXE-capable network card
Virtual Thin Client

For test scenarios, use a virtual thin client in a virtualization platform.

In addition to the hardware requirements listed above, observe the following settings:

  • Configure the network adapter in bridged mode.
  • Oracle VirtualBox requires the Extension Pack and an Intel network adapter for PXE boot.
  • VMware Workstation requires the "Safe" boot method for legacy boot (set in the hardware type).
Back to top