Document toolboxDocument toolbox

(12.04-en) Overview of the IGEL UMS

Owned by Emese Pogany
Last updated: May 24, 2024 by Sarah Leitner
5 min read

With the IGEL Universal Management Suite (UMS), you can remotely configure and control IGEL OS devices. For an overview of devices supported by the IGEL UMS, see (12.04-en) Devices Supported by IGEL Universal Management Suite (UMS).

The UMS supports not only various operating systems but also databases and directory services such as Microsoft Active Directory. 

Typical Areas of Use of the IGEL UMS

  • Setting up devices automatically
  • Configuring devices, software clients, tools, and local protocols
  • Distributing updates
  • Diagnostics and support


 Attributes of the IGEL UMS

Quick installation:

A wizard helps you during the installation procedure. You can connect external database systems as an alternative to the integrated database.

Straightforward management at the click of a mouse:

Most hardware and software settings can be changed with just a few clicks.

Standardized user interface:

The UMS user interface is similar to that for local device configuration. The additional remote management functions give the administrator complete control in the familiar, proven environment.

No scripting:

Although scripting is supported, you will only need it for managing the device configuration in the most exceptional circumstances.

Asset management:

Automatic capturing of all your hardware information, licensed features, and installed hotfixes.

Commentary fields:

For various customer-specific information such as location, installation date, and inventory number.

Support for numerous operating systems:

The UMS Server can run on many common versions of Microsoft Windows Server and Linux.

Access independent of the operating system:

The UMS Console runs on any device with the Java Runtime Environment. The UMS Web App can be opened on any supported browser. 

Encrypted communication:

Certificate-based TLS/SSL-encrypted communication between remote management servers and clients to prevent unauthorized reconfiguration of the devices.

Failsafe update function:

If a device fails while the update is in progress, e.g. as a result of a power outage or loss of the network connection, it will still remain usable. The update process will then be completed when the device next boots.

Based on standard communication protocols:

There is no need to reconfigure routers and firewalls because the UMS uses the standard HTTP and FTP protocols.

Support for extensive environments:

The IGEL Universal Management Suite can be scaled to accommodate several thousand devices.

Group and profile-based administration:

The devices within a given organizational unit can be administered easily via profiles. If members of staff move to another department, the administrator can change the settings with a simple drag-and-drop procedure.

Trouble-free rollout:

If you configure default directory rules, IGEL OS devices can be automatically placed in a required directory, e.g on the basis of the relevant subnet. The devices will automatically receive the configuration settings that you have defined for this directory.

Comprehensive support for all configuration parameters:

Most IGEL device settings, e.g. device or session configurations, can be changed via the UMS user interface.

Transferral of administrative rights:

Large organizations can authorize a number of system administrators for different control and authorization areas. These administrative accounts can be imported from an Active Directory.

Planning tasks:

Maintenance tasks can be scheduled to take place during the night so that day-to-day operations are not disrupted.

VNC shadowing:

Members of the IT support team have remote access to device screens, enabling them to rapidly identify problems and demonstrate solutions directly to users.

IGEL UMS Components

The IGEL Universal Management Suite (UMS) comprises the following components:

  • UMS Server
  • UMS Administrator
  • UMS Console / UMS Web App

UMS Server

The UMS Server is a server application which requires a database management system (RDBMS). The database can be installed on the server itself or on a remote host. Detailed information on the supported environment can be found in the release notes. See also (12.04-en) Installation Requirements for the IGEL UMS.

Typically, the UMS Console and UMS Server are installed on different computers. 

The UMS Server communicates internally with the database and externally with the registered devices and the UMS Console / UMS Web App:


Data transmission between the UMS Server and devices as well as between the UMS Server and UMS Console / UMS Web App is encrypted.

For communication with IGEL OS 11 devices, there are two protocols running on separate communication ports (30001 and 30005) – one for devices to communicate with the UMS and another for the UMS to communicate with the device.

With the introduction of IGEL Cloud Services, also the Unified Protocol has been introduced. The Unified Protocol is used for all communication between the UMS and OS 12 devices. This single path of communication is now accomplished with a WebSocket connection, enabling persistent, bi-directional, full-duplex TCP connectivity between UMS 12 and OS 12 devices. Using a WebSocket connection makes it possible to reduce network traffic due to the compression of commands, increase security by using client certificates and security tokens for device onboarding, and introduce a new Device Connector service on the UMS and IGEL Cloud Gateways that prepares your IGEL environment for future cloud capabilities. For more information on ports, see (12.04-en) IGEL UMS Communication Ports.

All configurations for the managed devices are saved in the database. Changes to a configuration are made in the database and are transferred to the device if necessary. The device can retrieve the information from the database during the booting procedure or you can send the new configuration to the device manually. A scheduled configuration update is also possible.

UMS Administrator

The UMS Administrator is one of the UMS Server's administrative components.

The key parts of the UMS Administrator are as follows:

  • Network configuration (ports)
  • Database configuration (data sources, backups)

Further information regarding the UMS Administrator can be found under (12.04-en) The IGEL UMS Administrator.

UMS Console / UMS Web App

The IGEL OS devices and their configuration are administered via the GUI of the UMS Console and the UMS Web App.

The key tasks of the UMS Console and the UMS Web App are as follows:

  • Displaying the devices' configuration parameters
  • Setting up profiles and scheduled jobs
  • Administering IGEL OS updates

UMS Console

The UMS Console is the Java-based user interface to the UMS Server. You will find detailed information regarding the UMS Console under (12.04-en) UMS Console User Interface.

For how to log in to the UMS Console, see (12.04-en) Connecting the UMS Console to the IGEL UMS Server. 

UMS Web App

The UMS Web App is a web-based user interface to the UMS Server. For detailed information about the application, see (12.04-en) IGEL UMS Web App. For how to connect to the UMS Web App, see (12.04-en) How to Log In to the IGEL UMS Web App.

The UMS Web App can currently be used only in addition to the UMS Console. Some features are currently available only in the UMS Web App (e.g. creating profiles for IGEL OS 12 devices, managing IGEL OS Apps), others – only in the UMS Console (e.g. scheduled jobs, user permissions and access control). For the feature matrix, see (12.04-en) Feature Matrix: UMS Web App vs. UMS Console.