Installing / Upgrading to IGEL UMS 12

IGEL Cloud Gateway (ICG) with IGEL OS 12 and IGEL OS 11 Devices

If you exclusively manage IGEL OS 12 devices, you may not need an IGEL Cloud Gateway (ICG) between your UMS 12 and your devices, regardless of whether the devices are inside or outside the company network. Whether an ICG is required or not depends on your particular use case or policy. See Universal Management Suite > Installation and Update > UMS Installation > Installation and Sizing Guidelines > IGEL Cloud Gateway vs. Reverse Proxy for the Communication between UMS 12 and IGEL OS Devices. If you manage remote IGEL OS 11 devices and want to manage also your remote IGEL OS 12 devices via ICG, ICG 12 is required.

If you manage your remote IGEL OS 12 devices without ICG and your remote IGEL OS 11 devices with ICG, you can use ICG 12 or ICG 2.x.

Please note the following, especially if you use any special policies or other components between the devices and the IGEL Universal Management Suite (UMS) or the IGEL Cloud Gateway (ICG):

• IGEL OS 12 devices use TLS 1.3

• IGEL OS 11 devices use TLS 1.2

The hardware requirements for ICG 12 are the same as for ICG 2.x with the exception that ICG 12 requires 4 GB of RAM instead of 2 GB, see IGEL Cloud Gateway > ICG Manual > Prerequisites.

You can update to UMS version 12.01.110 or higher from

• UMS 6.x

If you participated in the program for validation and testing of IGEL OS 12, you can also update to UMS 12.01.110 from

• UMS 12.00.900

• UMS 12.01.x

Before the update, it is always recommended to make a backup of your current system. For details on how to create backups, see Creating a backup.

For Update Installations Only

• As of UMS 12, the MDM feature is no longer available. Cancel the upgrade to UMS 12 if you still need the MDM feature:

  

• Only if you have a Distributed UMS installation: During the update installation, it will be checked whether only one UMS Server is running and the others are stopped. If not, stop all UMS Servers except one and proceed with the update; otherwise, you risk losing data. After the update on this server is complete, you can update the remaining UMS Servers, either simultaneously or one after another. But see also Universal Management Suite > UMS Release Notes > Notes for Release IGEL UMS 12.01.110 > Known Issues UMS 12.01.110.

UMS 12 Communication Ports

If you are going to make network changes, consider the following ports and paths:

• For IGEL OS 12 devices, TCP 8443 /device-connector/* is required.
  SSL can be terminated at the reverse proxy / external load balancer (see Universal Management Suite > UMS Articles > IGEL UMS Communication Ports > NGINX: Example Configuration for as Reverse Proxy in IGEL OS with SSL Offloading) or at the UMS Server.

• For importing IGEL OS 12 Apps to the UMS from the IGEL App Portal, the URL https://app.igel.com/ (TCP 443) is required.

• For the UMS Web App, TCP 8443 /webapp/* and /wums-app/* are required.

• For the UMS Console, the root is required, i.e. TCP 8443 /*

• For IGEL OS 11 devices, TCP 30001 and TCP/UDP 30005 are required.

For more information on UMS ports, see IGEL UMS Communication Ports.

The web server port (default: 8443) can be changed under UMS Administrator > Settings. If you do not configure the Cluster Address, it is recommended to change the port before registering any IGEL OS 12 devices. This is due to the fact that the already registered IGEL OS 12 devices won't be manageable anymore after the change of the web server port if no Cluster Address is configured. In this case, you will have to register these devices anew.

The FQDN and port of your external load balancer / reverse proxy must be specified in the UMS Console under UMS Administration > Global Configuration > Server Network Settings > Cluster Address. Information on the Cluster Address can be found under Universal Management Suite > UMS Reference Manual > UMS Administration > Global Configuration > Server Network Settings in the IGEL UMS.