As a looping Runbook, we understand a Runbook contains an activity that loops until a condition is met. As we have seen in our previous examples, each activity is running only one time. A looping activity runs as much as the condition changes.
In this example, we will build a simple reboot Runbook where we restart a server and wait until the server is going down and is coming up again, therefore we will need a looping activity.
Perform the following steps in the Runbook Designer to prepare for the activity steps in this recipe:
- In the Runbook Designer, expand the connection to the SCO 2016 server.
- Navigate to our created 1.2-Chapter 4 folder.
- Create a new sub-folder called 1.2.2-Reboot...