Skip to main content

Autoscaling

With autoscaling, virtual machines in a destination pool are scaled automatically based on defined load and user parameters.

Autoscaling in oneclick™ is controlled exclusively via destination pools and is not available for individual destinations.

oneclick™ supports two autoscaling modes:

  • Elastic: oneclick™ automatically creates and removes virtual machines based on a defined base VM.
  • Static: oneclick™ only starts and stops virtual machines that already exist in the destination pool. No virtual machines are created or deleted.

Load distribution is handled via load balancing and takes into account the number of users, CPU utilization, and RAM usage. In elastic mode, alternative instance types can optionally be used to ensure availability in the event of resource shortages.

Prerequisite

oneclick™ distributes only users who access the destinations in the pool via oneclick™ streaming and whose app instance is configured with Best destination of the load balancing pool. For utilization, however, oneclick™ counts all active Windows sessions on a destination, including logins that do not occur via oneclick™. For more information, see Load Balancing.

If local user profiles are required in your environment, they can be implemented using Windows built-in tools such as FSLogix.

Before setting up autoscaling, ensure that:

Autoscaling modes overview​

Elastic mode​

Elastic mode creates additional virtual machines when the existing capacity is not sufficient. When the load decreases, oneclick™ removes virtual machines that are no longer needed.

All automatically created systems are based on a base VM. Elastic mode is suitable for environments in which the required number of virtual machines fluctuates depending on the current load.

Static mode​

Static mode uses exclusively the virtual machines that already belong to the destination pool. oneclick™ starts and stops these systems depending on the current load.

Static mode:

  • does not require a base VM
  • does not create virtual machines
  • does not delete virtual machines
  • does not change the number of systems in the destination pool

You can use static mode, for example, to start and stop existing RDS hosts depending on the load, or to keep a fixed number of virtual desktops switched on and available.