Additional properties

This page allows you to optimize the VDI provider resources usage by controlling the power state of guest VMs after they are prepared. When you deploy a large number of guest VMs and run them automatically after they are ready, it can lead to the VDI provider resources overcommitment. Additionally, in Microsoft Azure, needlessly allocated guest VMs can also lead to unnecessary fees. You can control the guest VM power state and other related settings by specify the following options:

• Keep available buffer: The minimum number of guest VMs to always keep unassigned and session free for the template. As soon as the number of free and unassigned desktops drops below the setting value, it forces the template to create another guest VM. The template uses its own settings for guest VM creation including initial power state.
• Guest VM state after the preparation: Select the power state that should be applied to a guest VM after it is prepared. Choose from Powered on, Powered off, or Suspended. Note that when the power state is set to Power off or Suspended, the number of running (fully ready and waiting for incoming connections) guest VMs is controlled by the Keep available buffer setting (see above). For example, let's say the maximum guest VMs value is set at 200, the number of guest VM deployed on wizard completion is 100, and the power state after preparation is "Powered off". The result of such a configuration will be 100 clones deployed and powered off.
• Delete unused guest VMs after: Select what to do with unused guest VMs to save resources. Choose whether to never delete them or specify the time period after which they should be deleted.