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 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 also manage remote IGEL OS 11 devices, 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