Sizing Guidelines for IGEL UMS 12 and IGEL OS 12
The following sizing guidelines are intended to support you with setting up the IGEL Universal Management Suite (UMS) 12 environment to manage IGEL OS 12 devices. The UMS environment includes the UMS Server, UMS Console & UMS Web App, database, and, if required, reverse proxy or IGEL Cloud Gateway (ICG) instances.
For information on sizing guidelines for UMS environments managing IGEL OS 11 devices, see Installation and Sizing Guidelines for IGEL UMS and IGEL UMS Sizing Guidelines & Architecture Diagrams .
General Prerequisites
The sizing guidelines describe the most common UMS environments. The individual exceptions or requirements may not be covered by these scenarios.
The following prerequisites apply for the IGEL UMS environments described in the sizing guidelines:
System Requirements
UMS version 12.01.100 or higher
ICG version 12.01 or higher
IGEL OS 12.01 or higher
UMS Console Requirements
UMS Console may be located inside the same (V)LAN as UMS Servers (no NAT, no proxies) or outside the VLAN with firewalls/routing configured according to IGEL UMS Communication Ports.
The UMS Console can be installed on single instances or separately, if required.
IGEL OS 12 Devices
Devices directly connected to the UMS Server are in the same (V)LAN as UMS Servers (no NAT, no proxies). If there is a firewall, it must be configured according to IGEL UMS Communication Ports.
Devices outside of the internal LAN can be connected through external reverse proxy solutions. As an alternative you can use ICG. For information on network configuration and reverse proxies, see IGEL Universal Management Suite Network Configuration.
Devices are booted/rebooted once a day on average.
UMS Server Requirements
Not more than 10 base system version and 40 apps or app versions are managed via UMS.
UMS backups and exports are not permanently stored on the UMS server host.
In the case of automatic device registration (see Registering Devices Automatically on the IGEL UMS): The DNS alias
igelrmserveror the DHCP tag can only point to ONE UMS installation. Therefore, the installation of several separate UMS Servers in one network is not recommended.
IGEL UMS Environment Sizing
The size and structure of the recommended UMS setup is mainly defined by the following:
Number of managed IGEL OS 12 devices
UMS installation type - Standard UMS or Distributed UMS
ICG / reverse proxy connection for devices outside of your company network
Use of UMS as Update Proxy
Recommendation for Large Installations
Large installations should always use the Distributed UMS. It is also recommended to use cluster FQDN for load balancing (see Server Network Settings in the IGEL UMS) or DNS-Round-Robin load balancing or ICG.
Sizing Overview
In the table below you can find the recommended UMS installation type and database type per number of managed device with the basic installation requirements.
Installation Requirements
The documented installation requirements are purely for the UMS / ICG services. Please check the documentation of your host OS on details about the OS requirements.
The installation requirements are specified with the understanding that the UMS Server setup includes the UMS Server, the UMS Console, and the UMS Web App.
For detailed installation requirements, see:
Installation Type | Number of Managed Devices | Database Type | Number of Servers | Installation Requirements |
|---|---|---|---|---|
Standard UMS | up to 5.000 simultaneously connected devices up to 2.000 simultaneously booting devices | Embedded database | 1 UMS server | |
up to 25.000 simultaneously connected devices up to 2.000 simultaneously booting devices | External database | |||
Standard UMS with ICG | up to 5.000 simultaneously connected devices up to 2.000 simultaneously booting devices | Embedded database | 1 UMS server 1 ICG server (The installation of more ICGs is supported, but it will not have a significant impact on throughput.) | |
up to 25.000 simultaneously connected devices up to 2.000 simultaneously booting devices | External database | |||
Distributed UMS | for 50.000 simultaneously connected devices up to 4.000 simultaneously booting devices | External database | 2 UMS servers | |
|
Above 50.000 devices When using distributed UMS, there is no fixed upper limit to the number of managed devices. The server requirements of large installations depend heavily on the use cases, as a general guideline, you should plan for approximately one additional UMS server for every 25.000 devices. | ||||
Embedded Database vs External Database
The embedded DB is a supported productive database for small environments, but it is always preferred to use external databases for production environments.
The benefits of an embedded DB are reduced costs and easy management, but it has limitations regarding performance and scalability (e.g. if the database grows big, it gets very slow and UMS updates might take hours).
If required, a standard UMS installation can be extended to a Distributed UMS installation by installing additional servers (and in the case of an embedded database, by switching preliminarily to an external data source).
Using ICG with IGEL OS 12
When managing IGEL OS 12 devices, the ICG provides a similar solution compared to an external reverse proxy solution. For an overview, see IGEL Cloud Gateway vs. Reverse Proxy for the Communication between UMS 12 and IGEL OS Devices .
There might be advantages regarding the security footprint when using an ICG. However, the security footprint of the reverse proxy setup can be mitigated with decent firewall rules. Paths for firewall setup can be found in IGEL Universal Management Suite Network Configuration.
UMS as Update Proxy and Disk Space Requirements
You need to have enough disk space in your UMS server to store app binaries to use the UMS as the update proxy for app distribution. The disk space is required for every installation type (Standard UMS, Distributed UMS) and applies to every UMS server.
IGEL recommends a minimum of 50 GB disk space, but the required space also depends on the stored apps and follows the size of apps shown in IGEL App Portal (e.g. 1,24 GB for a base system or 381 MB for Citrix Workspace App).
If the UMS server runs out of disk space, it can have serious effects. To prevent this, admins should monitor disk usage with the help of UMS notifications, see How to Configure Notifications in the IGEL UMS.
You can also set the IGEL App Portal as the app repository, for details, see Configuring Global Settings for the Update of IGEL OS Apps.