Problem

You work in a large environment in which new settings need to be rolled out to a great number of endpoint devices at once or in which the fail-safe rollout of new settings is mission-critical for the organization concerned. Too many simultaneous requests from the devices for one UMS Server may lead, however, to intermittent failures. As a result, the devices will not get new settings during the boot process.

Purpose

You need a method that ensures that every device can get new settings at any time, even at the start of a workday shift when a large number of devices may simultaneously contact the UMS Server via LANs, WLANs, and WANs, searching for new configuration profiles or firmware updates.

Solution

An upstream UMS Load Balancer handles load distribution. To ensure maximum process reliability and high availability, IGEL recommends that you use the UMS Load Balancer and UMS Server in a redundant setup.

For details of configuration options and installation requirements, see HA Manual.

This example shows the installation of the High Availability solution with real load distribution: UMS Server and UMS Load Balancer are installed twice on separate hosts.

A network token is created when installing the first components ( UMS Server or UMS Load Balancer) and is used when installing further components.

If a UMS Server is installed individually, the UMS Console and UMS Administrator applications for managing the installation are available in addition to the server services. If you install an individual load balancer, only its service will be installed and automatically launched. Only the option for uninstalling the Universal Management Suite will then be set up in the Windows Start Menu.

Installation HA network