Before automating Active Directory tasks, the Active Directory integration pack must be deployed. Next, Active Directory settings must be configured. Dan steps through how to configure Active Directory settings in the Runbook Designer.
- [Instructor] In this first demo, we're going to take a look at how to configure Active Directory settings within the Runbook Designer. This is going to be important if you're going to have various Runbook activities that need somehow to talk to Active Directory, whether it's the retrieval of information or writing information to Active Directory, that's always the first step. Next, we'll actually use that configuration to create an Active Directory computer account. This is going to be called upon by a later runbook so we can see how data is passed into and back out of runbooks in the parent and child relationship.
Here in the Runbook Designer, I'll start by setting up our Active Directory configuration, and I do that by going to the Options menu and choosing Active Directory. Although notice that we've got other options to configure other services, which really depends upon the Integration Packs that we've installed. Bear in mind that before we can use the Active Directory component, we have to have downloaded and installed and deployed the Integration Pack using the Deployment Manager tool. Then it becomes available here in the Runbook Designer.
We can see we currently do not have a configuration, so I'll click the Add button. Going to call this the name of my domain, which is FakeDomain1, and from the Type field, I'm going to choose Active Directory. Once we've selected that, I'll click OK, and it pops up with four properties that we need to populate down below. I'm going to put in my user name, the password that I want to use, I'm also then going to put in the FQDN or the DNS name of my domain controller, so I'll fill that in here.
Looks like a DNS domain name. Then the last thing I'll have to do, if I so choose, I don't have to, is to configure a default parent container, so that if I've got activities, that, for example, create a user in Active Directory, in that activity, if we don't specify the location in the hierarchy, it'll use this default container, so I'm going to fill it in. Going to put ou=users,ou=lasvegas, domain component, or dc=fakedomain1, in my case, and, domain component =local.
Then I'll click OK and Finish. We can see that if we take a look at the Active Directory structure in this sample environment, indeed, the domain is fakedomain1.local, we do have an OU down here called LasVegas, and also Users. That's how we get the information that is required to fill in our Active Directory configuration. In my case, I've used an administrator account. Realistically, you might want to use another service account that you've created only for this purpose.
Back here in the Runbook Designer, I've got a folder for Runbooks I've created already called CourseDemosBuild. What I want to do then is right-click on that and choose New > Runbook. This one is just called New Runbook by default, but I'll right-click on that tab at the top because I want to make sure that I rename it. What I'm going to call it is NewComputer. Now we've got a new runbook with nothing on the canvas. Now I want to look up my Activities over on the right, and in this case, it's for Active Directory. All we're going to do is select the Create Computer activity and drag that onto the canvas.
Now, the next thing I want to do is double-click on that activity to configure it. Notice that the first thing it needs here under the Properties tab is our Active Directory configuration, which we've configured previously. I'm going to go ahead and click on the ellipsis button and choose our config, which is called FakeDomain1, and I'll click OK. Down below, it's got the properties for this particular activity. It says Common Name, in this case, the common name of the computer. For example, maybe I'll just call this PCTest1.
I'll hardwire it for now. Down below, I've got an Optional Properties button, and when I click it, I get a number of other properties I can specify, in this case, related to this activity, creating a computer in Active Directory. I'm going to add the Container Distinguished Name, move that over to the Selected list on the right and click OK, because instead of sticking with the default location within our Active Directory config, I want this to be somewhere different. I'm going to put in ou=computers,ou=lasvegas, and then I'll specify the rest of the domain path, so domain component =fakedomain1, domain component =local.
OK, so now that I've done that, there's nothing else I want to configure within this activity, so I'll just go ahead and click on Finish. Now, I want to test this out, so I'm going to go ahead and click the Runbook Tester up at the top, that opens the new Runbook Tester window. Remember when you do test your runbooks, you're actually executing them. However, this gives us a little information about all the activities that are running as they're running. This is only a single activity, but that's OK. I'm going to go ahead and click the Run button in the upper left.
We can see now that the activity quickly ran and completed. We've got a checkmark icon. If I click Show Details, we can see what was related to that specific activity. There's the common name of our Active Directory computer. We can see the Container Distinguished path, and as we keep scrolling down, down, down, what we're really looking for is that this particular Activity status says success. Now, of course, there's no better way to verify that it worked in this particular example other than to go into Active Directory and see if that computer account was created.
Back here in Active Directory Users and Computers, I've navigated to the LasVegas/Computers OU, and indeed, we can see our newly created computer here, PCTest1. Now, that is a very simple runbook, but one of the things we have to bear in mind is runbook modularity, reuse. If we know that we would be creating a computer account under various different circumstances that might be used by different runbooks, then perhaps it should be its own separate runbook, which is our review point in this example.
We will be using this in a later runbook in our demos, and we'll make sure that we're not hard coding everything like we've done in this example.
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