Installation and Sizing Guidelines for IGEL UMS

The following installation and sizing guidelines are intended to support you with setting up the IGEL Universal Management Suite (UMS) environment – UMS Server, UMS Console & UMS Web App, database, and, if required, load balancer and ICG instances. For information on the installation requirements, see Installation Requirements for the IGEL UMS.

The size and structure of the UMS setup depend mainly on the following criteria: 

• Number of devices 

• High Availability 

• ICG connection for devices outside of your company network  

General Preconditions  

The Installation and Sizing Guidelines apply for a standard UMS setup and describe the most common UMS environments. Any individual exceptions or requirements may not be covered by these scenarios.  

• System requirements: UMS 6.05 and newer, ICG 2.02 and newer

• 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.

• 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 are connected via ICG.

• Devices are not booted/rebooted frequently (once a day on average). 

• A maximum of 10 different firmware versions is 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 igelrmserver or the DHCP tag can only point to ONE UMS installation. Therefore, the installation of several separate UMS Servers (without the High Availability Extension) in one network is not recommended.