...
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.
Include Page | ||||
---|---|---|---|---|
|
Info |
---|
Recommended Additional InformationIGEL UMS Communication Ports: Find a list with all ports that are relevant for the communication with the UMS. Latest release notes: Find in the Supported Environment section the list of supported servers, clients, and backend databases. High Availability (HA): Find useful how-tos and the reference guide around your HA installation. /wiki/spaces/ENLITEICGP/pages/73306290128221666 : Find how-tos, the reference guide, and additional information concerning the management of endpoints outside the company network. |
...