Discover which prerequisites will allow you to get the most out of this course. Because Orchestrator runbooks automate sys admin tasks, having server, network, and Microsoft Active Directory experience is helpful. You should also have a basic knowledge of PowerShell.
- Before diving into the details related to System Center Orchestrator, there are a few things that you should know ahead of time. One of them is not everything about Orchestrator. That's what the course is for; however, there are some other prerequisites. You should have a general knowledge of the Windows operating system, whether it's client or server. You should also have an idea about how Active Directory works in a Microsoft environment because we'll be taking a look at some Runbook activities that talk to Active Directory.
You should have a general sense about what Microsoft PowerShell is along with commandlets, modules and how it's used to automate tasks for administrators. Should also have a general sense of IT networking, connecting over the network and how different credentials might be needed when you do something over the network versus when you do something locally. Now when it comes to following along with some of the examples in this class, you might want to set up your own little lab environment, whether it's in the Cloud or if you have virtual machines you might be able to set up locally on premises or even physical machines.
So ideally, you're going to need at least one server. You can run everything on one server to go through this and learn Orchestrator and experiment. That server needs to be running at least Windows Server 2012 R2. Now to go through a lot of the Active Directory activities such as user provisioning, you're going to need Active Directory configured. It doesn't matter what it's called but there needs to be a functional Active Directory domain in the environment. You're going to need SQL Server 2012 Service Pack 2 or higher and that can be in the Standard or Enterprise editions, 64-bit.
Now if you have a newer version, that's fine but it is actually what holds the System Center Orchestrator database. Now whether that SQL Server runs on the same host or different host on the network, doesn't matter. But we do need access to it. And of course, you're going to need the Microsoft System Center Orchestrator 2016 installation media. Now you could go with one server, whether it's physical or virtual but you could also spread the roles out across multiple servers.
Now again, those multiple servers could be a combination of physical and virtual machines. It really doesn't matter, as long as they can communicate using TCP/IP version 4. So you might spread things out. You might have the Orchestrator management server running on one box or Runbook server running on a different box. You can install the Orchestrator Runbook Designer tool on a different box, even if it's a client-operating system, where designers can build Runbooks and activities. You might have an Active Directory Domain Controller on a separate computer and you might have a SQL Server on a separate computer.
Now again, these are not required but we're saying that if you already have a SQL server out there, you might just want to use it, instead of going through all of the time of setting one up just to follow along here. So if you have legitimate access to it, it could work well. Now other than that, the Runbooks that you'll see in the examples in this course will be made available as an exported file from my lab environment that you can import directly into yours and of course, you'll have to tweak some of the details, such as Active Directory credentials and so on, but they will be made available so it makes it a bit easier for you to follow along.
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