Join Daniel Lachance for an in-depth discussion in this video How to use the exercise files, part of Learning System Center 2016 Orchestrator.
- [Instructor] If you have access to the exercise files that go along with the movies, you might find it helpful to download the ZIP file and extract it and then go into the corresponding folder for the movie where you're going to find the runbooks that I use in the demonstrations. Otherwise, if you choose, you can simply follow along with the movies and build the runbook workflows yourself. There are some other considerations about the use of the exercise files. First of all, you import them into the Runbook Designer, and we'll take a look at that in just a moment.
We also have to realize that there may be some settings that need to be tweaked compared to the environment I built the runbooks in versus where you will be running them. We have to think about integration packs that need to be installed, such as the Active Directory integration pack if you're going to perform Active Directory tasks through runbook activities. Then we have to consider things like changing server names that might be hard coded into activities. If you've got different server names than I used in my demos, you'll have to account for that.
There's also the fact that you might have to set different credentials that are used to execute runbooks, depending on how many servers you happen to have in your environment where you're actually running these runbooks. Some of the workflow activities that I've done in the demos refer to a location on a server on drive C in a folder called TMP where you've got sample files that can be deleted by an activity, so if you want to follow things verbatim, you would need to make sure that that is taken care of. Also, some other specifics to some other activities such as the fact that we would need a sample folder for log output, such as c:\logs.
Of course, these can be tweaked and changed to suit your environment, just remember to go into the activities and look at the details to make sure that they will run correctly for you. Let's just take a quick look at how we would import runbooks into the Orchestrator Runbook Designer. Here in the Runbook Designer, I can right click on runbooks and I can choose import. If you're using the exercise files, then you can simply browse for that file location, here I'm going to select the System Center Orchestrator sample runbooks export file, and I'll click open.
I'm going to leave all the check marks on to import not only runbooks but any variables, computer groups, counters, and so on, even though there aren't many there. If you've already done this before in our environment, you might get messages about overwriting existing items. I'm going to go ahead and click finish. We can now see it's importing all of the sample runbooks and even though you're bringing in these sample runbooks they may not work perfectly in your environment. Make sure that you go through them, look at all of the individual runbook activities such as opening them up and making any of the required changes.
This would serve as a good starting point then, to actually tweak and start learning about building your own runbooks.
This course teaches administrators how to automate the monitoring and deployment of data center resources using Orchestrator 2016. Instructor Daniel Lachance begins with a discussion of Orchestrator components and interactions, and walks through the installation of an Orchestrator environment. Then he explores Runbook Designer, the tool for creating various automation solutions related to file management, user onboarding, and more. Follow along and learn how to create your own runbooks with this integral tool, and optimize and reduce your workload.
- Understanding the Orchestrator architecture: from database to console
- Planning an Orchestrator deployment
- Verifying the installation
- Exploring Runbook Designer
- Creating runbooks