Welcome
Login  Sign up
Start a new topic
Answered

System level Power management

Leostream currently allows a user to start a workstation and leaving it running indefinitely. If the user starts the workstation but does not connect to the workstation (i.e. initiate a user session), then no power management is applied to the workstation, and it will remain switched on. In a cloud environment this can lead to substantial costs, with cloud instances left running for days or weeks, unless another tool is utilized to prevent this scenario.


My feeling is that if the Leostream Agent is installed on the workstation, it should be managing this scenario regardless of whether a user logs in or not, especially since it may have been the broker that turned the workstation on.


Best Answer

If the user is given permissions to start the desktop and uses "Start" instead of "Connect", then the user does not go through a desktop assignment and it falls out of the realm of Leostream Power Control. If the user uses the "Connect" option on a powered off desktop, Leostream assigns the desktop to the user and can leverage the "Release if user does not log in:" option in your Release Plan, which then triggers the power plan for "When Desktop is Released". As long as the policy has "Power on stopped or suspended desktops" enabled, then we will power on the machine when the user presses "Connect".


We have power control enhancements on the 2022 roadmap that will cover cases such as this, where a user powers on a machine but never attempts a connection.

1 Comment

Answer

If the user is given permissions to start the desktop and uses "Start" instead of "Connect", then the user does not go through a desktop assignment and it falls out of the realm of Leostream Power Control. If the user uses the "Connect" option on a powered off desktop, Leostream assigns the desktop to the user and can leverage the "Release if user does not log in:" option in your Release Plan, which then triggers the power plan for "When Desktop is Released". As long as the policy has "Power on stopped or suspended desktops" enabled, then we will power on the machine when the user presses "Connect".


We have power control enhancements on the 2022 roadmap that will cover cases such as this, where a user powers on a machine but never attempts a connection.

Login or Signup to post a comment