You can set up AWS and Azure computers to automatically start up and shut down at specific hours of the day. Shutting down computers automatically can save your organization a lot of money in hourly fees when employees forget to turn them off. You start by setting up a location for any of the start-up and shut-down times you will use, and then you tag each computer with the time that you want it to start up or shut down. This allows you to set different times for different employees, allowing those who work later to carry on without interruption.
You can set one time for each computer, either a start or a stop. You can choose from four start times and four stop times. Their search tags are as follows:
|
The StartStopAWSInstancesPermWF permanent workflow checks for these tags each time it runs. When it detects a tag for the current hour, it then starts or stops the computer. For this reason, the exact timing of the start or stop of the computer depends on when the workflow first runs within the hour set. For example, if the workflow runs at 8:58 a.m., it is not triggered by a 9AM tag, so the computer is not started until the next time the workflow runs. These start and stop times only take effect on week days. |
The schedule location becomes the parent for all of the schedule times.
Although you can add a computer to the time via the Resources Directly Assigned to Zone (Location) accordion, you cannot add the necessary tag to it from there. For that reason, we set it up on the computer itself. However, once you have set it up on various computers, you can expand the Resources Directly Assigned to Zone (Location) accordion to see which computers use it.
The next time the StartStopAWSInstancesPermWF permanent workflow runs and detects that the hour portion of the current time is 9, it checks for this tag and starts any computers set up with this tag and location.
The exact timing of the start or stop of the computer depends on when the workflow first runs within the hour set. For example, if the workflow runs at 8:58 a.m., it is not triggered by the Start9AM tag, so the computer is not started until the next time the workflow runs. |
|
|