You work in a large thin client environment in which new settings need to be rolled out to more than 500 thin clients at once, or in which the fail-safe rollout of new settings is mission-critical for the organization concerned. This leads to intermittent failures and the thin clients will not get any new settings during the boot process.
This is caused by the fact that there are too many thin client requests for one UMS server at the same time.
You need a method which ensures that every thin client can get new settings at any time, even at the start of a workday shift when several hundred or even several thousand devices may simultaneously contact the UMS server via LANs, WLANs and WANs, searching for new configuration profiles or firmware updates.
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 the manual.
This example shows the installation of the High Availability solution with real load distribution: server and load balancer are installed twice on separate Hosts.
A network token is created when installing the first components (server or 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.