Start with 7 free days of training.

Gain instant access to our entire IT training library, free for your first week.
Train anytime on your desktop, tablet, or mobile devices.

This VMware vCenter Orchestrator 5.5 video training course with Greg Shields introduces the foundations of datacenter orchestration and automation using VMware solutions. It discusses topics that are specifically relevant to vSphere virtual administrators, walking the viewer through a real-world use case that can be immediately implemented in a production vSphere environment....
This VMware vCenter Orchestrator 5.5 video training course with Greg Shields introduces the foundations of datacenter orchestration and automation using VMware solutions. It discusses topics that are specifically relevant to vSphere virtual administrators, walking the viewer through a real-world use case that can be immediately implemented in a production vSphere environment.

Recommended skills:
  • Familiarity with virtualization concepts
  • Familiarity with VMware Workstation, VMware vSphere, and VMware vCenter Server
  • Familiarity with basic installation of Windows Server 2012 R2

Recommended equipment:
  • One or more desktop or laptop computers with a combined 16 GB of RAM
  • One or more copies of VMware Workstation (latest version), VMware ESXi v5.5 or greater, and VMware vCenter Server v5.5 or greater
  • SSD hard disks recommended

Related certifications:
  • None

Related job functions:
  • IT professionals
  • Server administrators
  • Virtual administrators
  • Storage administrators
  • Network administrators

Ever wanted a self-service VM provisioning tool that was actually useful... because you created it? You can have one with vCenter Orchestrator and the skills you'll learn in this course.

vCenter Orchestrator 5.5 is a powerful tool for automating IT tasks. Using Orchestrator's graphical workspace, you’ll connect pre-built activity objects to quickly construct complex automation tasks. Almost no scripting is required. Once built, those tasks can be executed and/or scheduled from within the vSphere client, a customized Orchestrator web site, or other triggering mechanisms.

The hardest part about using Orchestrator is knowing where to start. This tool can be overwhelming. In this short "Foundations" course, veteran CBT Nuggets instructor Greg Shields offers a quick introduction to a handful of Orchestrator's most-useful features for vSphere administrators. You’ll participate in a real-world exercise that’ll leave you with a Orchestrator-driven, production-ready, self-service provisioning tool that you can immediately implement in your vSphere environment.
 show less
1. Installing vCenter Orchestrator (29 min)
2. Executing and Scheduling Workflows in the vSphere Client (13 min)
3. Introducing the Orchestrator Client (14 min)
4. Constructing a Basic Workflow (26 min)
5. Configuring Presentation (21 min)
6. Adding Looping to Workflows (17 min)
7. Integrating Active Directory Activities (36 min)
8. Executing PowerShell Commands through Orchestrator (29 min)
9. Customizing Orchestrator Webviews (23 min)

Installing vCenter Orchestrator


Do you remember the early days of virtualization when virtual machines were going to make all of our lives easier? Automation would mean that we wouldn't have to do all of the mundane scut work that had traditionally been associated with our jobs in IT.


Well, those days-- for a lot of us, they never happened. So we incorporated virtualization into our data centers. And somehow, we found ourselves probably doing more scut work than less scut work. You know, the virtual machine, by itself, maybe didn't bring about the kinds of automation that I think we were hoping that we would get.


And in fact, even some of the tools that we got, like the first level tools, like vSphere and the vCenter Server, the vCenter client-- even these tools didn't bring about the kinds of automation that I think we were promised, along with the jet packs that we were promised, as well.


Well, the good news is that virtualization has been around for long enough now that vSphere, and vCenter Server, and the vCenter client, we're beginning to recognize, are only kind of the first step in the process. For us to get automation, we have to have automation tools.


And these are tools that layer on top of our virtualization management solutions, like vCenter Server. This series-- this little micro-series-- is one that I have been wanting to do for a really long time because it's kind of the part two to that vSphere series that I've done for CBT Nuggets for a couple of versions now.


When you get to the end of the vSphere series, you look at what you've learned, and you realize you can now do virtualization without a problem. But you haven't done a lot of the neat automation things that I think many of us got really excited about.


Well, that's what we're going to talk about here, in this miniseries or micro-series that I've put together for CBT Nuggets. You can think of Orchestrator as just simply another solution that sits on top of vSphere. So I've got my hypervisor hosts here.


And I've got my vCenter Server that sits on top of those hypervisors. Well, vCenter Orchestrator, or vCO, is a tool that really sits on top of vCenter, itself-- another layer, if you will, of management. vCO is designed to automate, really, anything in your data center.


vSphere just happens to be one of the things that it can do. In this series, we're going to talk, not only about how vCenter Orchestrator can automate the vSphere part, but we'll talk even about Active Directory Integration, like users and groups, and things like that.


And we'll even go as far as to use vCenter Orchestrator to manage the virtual machines that are sitting on top of your hypervisors. So throughout this series, you're going to learn some really cool ways that you can incorporate automation right now, today.


Now, one of the things that I've tried to promise you, here, in the series, is the ability to accomplish everything we're talking about here without having to dig too deeply into scripting or into heavy duty code. vCenter Orchestrator can require quite a bit of JavaScript knowledge, if you want to do some of the crazier integrations.


But here in this series, I want to focus the content here, very specifically, on what an IT administrator, a virtual administrator, you-- the person who manages vSphere-- what you would need to use or want to use this tool with. Your developers have completely other uses.


They can do some really awesome things with moving code around. But you, as a vSphere administrator, have some needs, as well. And so I want to focus this in on the specific needs that you would possibly have in automating your vSphere environment. In fact, let's talk a minute about this-- the use case, the example that I want to do throughout this entire short series.


And that is a problem that I think a lot of us have pretty routinely. Right? You wake up one morning, and you're getting to work, and you're hoping to do some really awesome things at work. But you realize, when you get to work, that you've got a million tickets from your developers because your developers have a need to get virtual machines up and running so that they can test their code.


Well, imagine, in a perfect world, where instead of annoying you with all of these work orders and time-consuming work orders to create new virtual machines, you've incorporated vSphere. And as part of that, you've incorporated your own self-service provisioning portal that your developers can use.


Your developers have the ability to log on to that self-service provisioning portal. They are constrained by the amount of resources you've put in your resource pool, if you set up your resource pools appropriately, and I'll assume that you have. We won't talk too much about resource pools here, but you can get those in my vSphere series.


You've also constrained the developers just to a specific group of developers that have the abilities to create virtual machines. So you know that only the right people are going to be creating virtual machines. And then lastly, you've created a nifty little web page that gives the user the ability to define exactly what they want out of that virtual machine.


They can define what the name might be-- I don't know, VM18-- whether they want it on SSD storage or regular spinning disks, maybe how much RAM they might want as well-- 2048, as opposed to 4096. All of these are the kinds of things that really consume time when we're just trying to do our everyday jobs in IT.


But if I have a nice solution-- like this self-service provisioning portal-- put into place, well, I can give them the ability to service their own needs. And then, you and I, we can move on to the much more interesting things, here in IT. You know, in a perfect world, the self-service provisioning portal might pop up for the user and say, hey, go ahead and log in.


And after you've logged in-- I guess I've already logged in here. And after you've logged in, you get a nice view with, perhaps, your company's banner up here and a couple of tabs that identify different types of things that that person can do, a little header here that says, hey, developers, do you need a VM?-- this web view is the place to ask for them, and a link-- hopefully, your indenting is better than my indenting-- but a link, here, that says, hey, I need to provision the developer server.


Let me go ahead and provision that server. What hosting do you want? What kind of storage deal? And I have lots of different options for storage-- both high speed and standard speed storage. And then how much memory do you want for this virtual machine?


All of these are options that you can create with a tool like vCenter Orchestrator. And all of these are options that you will create throughout the next series of videos in this series. I think you're going to enjoy the awesome automation that you could put together here.


But before we can get into any of all of the effort here in creating web pages that are very-- because you can see how this web page is just, specifically, there to accomplish one thing. I'm not giving these developers access to a whole bunch of stuff, no-- just, indeed, to the exact kinds of things that they might need to require as a developer.


I'm not giving them access to the vSphere client. I'm not giving them access to a bunch of things that's, perhaps, inappropriate for them. I've tailored this down. We will tailor this down-- you and I, throughout this series-- so it, specifically, gives them what they need.


And not only does it give them the server that they need, it gives them a fully configured server with all of the windows, roles, and services, and perhaps, even some additional components, depending on how you construct your automations. Here, in this series, I've got three different hosts-- esxi1, 2, and 3.


They're all attached here, to a vCenter Server appliance. We're creating, here, just a very simple vSphere environment. These hosts are set up in a nice little cluster here. I've got a distributed virtual switch, so they're all talking appropriately over the correct networking.


They have their storage networking. They have their production networking. We've got vMotion set up-- all of the usual things that you're used to associating with a production running vSphere environment. We also have-- in this environment, we have a couple of different types of storage.


We have local storage, obviously, for each of the different hosts. Then we have SSD storage and standard storage that are attached to, via iSCSI. We'll work with both of these, throughout this series. And at last, they also have an NFS store here. I need to get access to some ISO files.


And so I've made available NFS so they can access this, as well. Now, the entirety of this environment is already set up and configured. But we need to go through the installation process just so we can see how vCenter Orchestrator can be installed into a vSphere environment.


So I've created this sort of mini environment here-- one host, one vCenter Server-- as the location where we can install our vCenter Orchestrator, just so we can see what it looks like. And then after we're done with that, we'll spend the rest of the series working with our production hosts, here-- esxi1, 2, and 3.


Had to do this so I could show you both the finished environment, as well as the starter environment that we'll kick off here, in this Nugget. So let's start by installing vCenter Orchestrator. We'll assume, at this point, that we have a functioning vCenter Server environment, it's plugged into a host, and so everything's ready to go, so that we can begin the installation of vCenter Orchestrator.


Now, the first thing that we need to do, in order to accomplish that, is get over to our vCenter Orchestrator server, which is vco2 for this Nugget-- it'll be vco for the remaining Nuggets. Here, on this server, vco2, it's a basic Windows server-- 2012 R2 server.


And really, it's kind of just right out of the box. With it installed and ready to go, start by launching the same installation file that we used when we installed our original vCenter Server. However, when you do this, you'll notice that the vCenter Server installation doesn't really include any parts of vCenter Orchestrator.


For us to get vCenter Orchestrator installed onto this additional server-- this separate Windows server-- we, actually, are not going to accomplish that here, in the vSphere-- the installer wizard. We need to get to it, instead, through Explorer. Let me right-click here.


I'm going to open. What's interesting is that the install of Orchestrator is a little bit hidden. I believe it can be a part of a Windows-based vCenter Server installation. But if you've got the vCenter server appliance, one of the hardest parts is, actually, just finding the silly Orchestrator bits.


In fact, the Orchestrator bits are a part of-- as you can see here-- the VMware management tool downloaded installation. So in here is vCenter Server. In here is the single slide on the inventory service, all of that stuff they are just associating with vCenter Server.


Inside of that installation, in the vCenter Server folder, there is a vco subfolder and then this executable, here, called vCenter Orchestrator. Really, really, really buried-- surprisingly so for what an important tool that it really is. I'm going to show you the Windows-based installation of vCenter Orchestrator for two reasons.


One-- that there is an appliance, for vCenter Orchestrator, that you can download and install just like the vCenter Server appliance. That appliance installation is relatively trivial. What's interesting is that if you need to evaluate this, and you don't have active vSphere licenses, getting access-- at least today, as of the time of this filming-- doesn't give you access to the appliance.


It only lets you have the access, here, to the Windows-based installation. So if you don't have the appropriate access on vmware.com, you're not going to be able to download the vCenter Orchestrator appliance. I don't know why they do it that way, but we'll do it this way.


The appliance installation is relatively trivial. There's a couple of things that we have to set up here. The installation itself-- there's not that much, too, but there is some post-installation configuration that we'll have to do, once we get through this first part of the process.


I'll choose Next here, and we're going to go through just your basic stuff for an install. We'll accept the license agreement. We're going to throw it in that default folder, Program Files/VMware/Orchestrator. Here, we have the option of choosing the client, the server, or the client and the server.


In my case, I'm setting this up as a server. So I'm only interested in the server pieces. The separate client install, which I won't show you, is really basic. Next, Next, Finish, and you've got that client installed. We'll install the server, here, onto our computer, vco2, and put it in a new program group for VMware, and click the install button to go about that installation of vCenter Orchestrator.


Told you-- there wasn't that much to see here. Let me pause things, and when we come back, I'll have vCenter Orchestrator installed. And we'll see what it looks like for the configuration. And we're back. So I've completed the installation-- again, basic installation here, at this point.


What we want to do now is actually go through its configuration interface. And this configuration interface is something that is actually not enabled by default-- sort of interesting. When you first install the vCenter Orchestrator, you actually have to come down here into Services and start the vCenter Orchestrator configuration interface.


Notice that it's set up as a manual service. Now, I'm going to just set this up as an automatic service, and then also start the service. But the idea here is that by setting it as a manual service, you're not going to end up with, perhaps, an open opportunity for someone to reconfigure your Orchestrator Server.


As you'll learn, a little bit later on in this series, there's a lot of stuff that an Orchestrator Server can do, and so protecting the server is something you're definitely going to want to do. Once you actually start the configuration service, the way you actually go about configuring Orchestrator is through a web browser.


Now, for most of this series, we're going to end up using Chrome as our web browser because there's a lot of Java-based stuff, and there's also some ties into vCenter that I've just found tend to work a little better with Chrome, as opposed to IE11, at least today, as of this filming.


But at least for now, we're going to start by going to http://localhost and then port 8283 which is the configuration port. If you want, you can go through here for all of the variety of security certificates that you're going to see throughout this series.


You can go through here and reset the certificates so that they're appropriate and fully trusted and all of that. For the purposes of this series, I'm just going to pass through these certificate warnings throughout every-- whenever you see them. Now, the initial username and password for the configuration interface is, in both cases, vmware.


So vmware and vmware. And as soon as you try to log in, the first thing it's going to have you do is log in with a new password. This is going to be a complex password, so lowercase, uppercase, number, funny character. Hit the Apply changes button, here, and that'll bring us into the Orchestrator Configuration screen.


This Orchestrator Configuration screen provides the location where we make the initial set up, where we hook Orchestrator into vCenter-- vCenter Server-- and then where we also go through the configuration of SSO-- so dealing with all of the SSO tokens and things like that-- and where we do the initial installation of a lot of the plug-ins that Orchestrator will work with.


Let's step through a variety of these things so that we're aware of the things we need to be prepared for. There are a couple of tabs here for General. We can install applications or deal with some advance configuration stuff here. Most of this stuff you're not going to deal with during your initial installation.


One thing you do have to do, however, is set up a network for this machine. Now, I've set this up to And the host name here is vco2 and company.pri. These are the default ports that we're going to be using for some of the initial configurations here.


Once I set this up, I hit the Apply changes button, and we set up the network configuration appropriately. Now, when we're going about making the connection between vCenter Orchestrator and vSphere, or vCenter Server, one of the things we have to do is identify the certificates that vCenter Server is using.


One of the nice things about this interface is that we could just directly import in those certificates from the web server. So if I go here to Import from URL, I could literally type in the URL for the vCenter Server that I want to attach this vCenter Orchestrator machine to, which, in my case, will be https://vc2.company.pri.


Again, later on, we'll be using vc, but for this install, we're using vc2. If I've got certificates I could just download in a file, I can do those here as well. But this is a really slick little interface. This is a certificate. It is trusted. Do you want to import it?


Yep. Let's go ahead and import it. And we're done. So very simple interface, here, for getting the certificate authentication set up between vCenter Orchestrator and vCenter. Just love this right here. We have to do some work over here, enter authentication, as well.


VCenter Orchestrator will make use of the same kinds of SSO authentication that we have for our vCenter Server environment. In fact, that makes things really nicely because I can just plug-in here the fact that I'm using SSO and associate it with the SSO site on my vCenter Server.


If all of this is completely confusing to you, there's a whole bunch of Nuggets over in my vSphere series for how to configure and work with vSphere SSO. So I'll assume you kind of understand what those foundations are. Let's go ahead and identify the SSO information, here, for my vCenter Server, which will be vc2.company.pri with the original admin user name of administrator@vsphere.local and then the admin password that's tagged to that account.


I believe, if I did that correctly, we should-- oops, I've got to go here, to the SSL certificates, as well. Actually-- oops, nope, there's my problem. The SSL certificate common name says localhost.localdom. And that's not going to work as a functioning certificate.


So let me pause things really quick. I'm just going to go over to my vCenter Server. I'm going to regenerate the certificates, which is something you should know you can accomplish in vCenter Server's Configuration screen. We'll reboot the box, regen the certificates, and we'll end up-- hopefully-- here, with a certificate that shows something better than localhost.localdom.


It'll actually be the URL we're looking for. Hold on just a second. All right. And we're back. So that little certificate problem is something that's actually bothered me in the past. So you notice how it said localhost.localdom? The reason for that is-- I will show you.


If I go to my vCenter Server, here, and I attempt to log in-- so now I've got the certificate-- well, if you don't actually check this very important check box, well, you don't end up with a certificate that's been issued to the actual host's name. So in order to fix that, you have to go here, to-- let's see, 52-- 5480.


Oops, not 5380-- 5480. You have to go into your vCenter Server, 5480. Once you go into that the vCenter Server, there's one very important setting that you have to put in there, which is right here, under-- let's see, I think it's under System. Make sure that you have the certificate regeneration enabled any time you do any name changes to your vCenter Server.


I think I mentioned that in the vSphere exam or in the vSphere series. But if I didn't, that Yes, right there, is very important because that is what will allow you to-- if we come back here-- to actually import in the certificate. So https://vc2.company.pri should work here at this point.


Let's see. company.pri. And Import. That one is a better looking certificate. Yay. And in fact, good-- it's all of the two certificates that we require. So with that, we can now come down here to Authentication and punch in the password for SSO. Let's register our Orchestrator Server.


And boom. There is the registration, successfully, for our Orchestrator Server. So apologies for the extra steps here, but sometimes it's actually nice to see something break so that you can indeed validate that this thing is exactly what it's supposed to be.


Once you register your Orchestrator Server, you can then identify what you want your filter to be. So how do you want to filter things into Orchestrator? Maybe you want a subset of your SSO objects to be those that Orchestrator is actually going to work with.


If you're OK with that, you can go ahead and accept the Orchestrator configuration, there. And you'll notice that once you've accepted the configuration, or if I would have changed what the filtering will be, here, on the vCO Admin domain and group, in the groups filter, any time I do that, then this little red dot, here, turns to green.


Our goal here, with this configuration, is to get all of those red dots turning to green dots. Let's do a test to validate that, indeed, we do have a successful authentication from Orchestrator over to vCenter. If I go administrator@vsphere.local and then a password, I should end up with a successful test.


Yep. User logged on successfully-- so we are good to go. Then, here in Startup Options are some locations that you will use from time to time because the vCenter Orchestrator service occasionally gets a little cantankerous. And if you ever are experiencing problems, and you just can't quite put your finger on it-- why things aren't behaving in the way that they should-- never hesitate to come back here and restart the vCO Server service.


Sometimes you just end up where the server service gets hung. Same thing down here with the Configuration Server. This is the server that we're looking at right here. So the vCO Server is what actually does the work, and the Configuration Server is what we're doing to configure the vCO Server.


OK. And down here, take a look at some logs, as well. Do some troubleshooting. But the real meat of Orchestrator happens down here, in the bottom, or the setting up of the meat of Orchestrator happens down here, at the bottom. It is here where I can install one or more of what we call plug-ins that extend Orchestrator's capabilities to do different things.


So Orchestrator, as you can imagine, is an orchestration solution. And the idea of Orchestrator is that I want to be able to create a variety of objects. So these objects do things. So I don't know. Create a VM is one object. Maybe another object is to create a data center.


Well, in order for me to create a virtual machine, I probably have to have the Create a data center object. If not before it, well, then at least assume that the data center is created. In addition to working with vSphere, there are going to be other types of data center resources that Orchestrator can work with, as well.


Perhaps, in addition to creating a virtual machine, I also, then, want to create a user. Well, in order to do that, that Create a User object, itself, has to have some sort of integration with your Active Directory. And it's the plug-ins that help facilitate those additional configurations.


You'll find down at the box, we have here one for Active Directory, we have another one for Mail, an SSH, a REST, and a SOAP API that I can use, and then vCenter, itself. There are also other objects that I can add in, or plug-ins that I can add in, from VMware's Solutions Exchange.


And if I copy and paste right here, I should be able to show you exactly where that Solutions Exchange exists. Nope, I can't. So https://solutionexchange.vmware.com/store. It is in this location where you can find additional plug-ins for other third-party solutions or solutions that exist out in the data center.


We are looking here, in this location, to browse the marketplaces. And we are looking for-- let's see, what are we looking for? Here-- vCO Plug-ins. These vCO plug-ins come in a variety of different flavors. Down here, there are ones from EMC. There are a bunch from VMware, itself.


There's one here from NetApp, if I want to use those. And I can flip through the various different lists of plug-ins to add them here, into my vCenter environment-- into my Orchestrator environment. So if I've got vCAC here, at a certain level, if I've got Active Directory-- a different upgraded-- version, I can use that.


Here's a lovely one, here, for Windows PowerShell. fact, this is a plug-in we might want to download because working with Windows PowerShell gives us some really rich capability of configuring our virtual machines after we provision them in vSphere. I've actually already downloaded the PowerShell plug-in.


And I've got a copy of it right here. Here is a copy of the PowerShell plug-in. Here is also a copy of-- an updated copy of the Active Directory plug-in and a plug-in for VMware Update Manager which will allow us to control VM through our Orchestrator environment.


These are nice because I can just import them directly into the configuration interface, and all of the activities that are a part of this plug-in become available when it comes time to start designing them, when we get to the workspace part of this.


In fact, let's go ahead and add in these plug-ins so that we can make use of them later on in this series. We come down here, to the plug-ins view. And I want to-- let's see here. I want to add-- I think I can do this down here, by identifying what the plug-in file is.


Go to the desktop, my plug-ins location, and I'll add in the PowerShell plug-in. Hit the Upload and Install button. Accept the terms of the license agreement. And you'll see that the plug-in gets installed. I can do the same thing for the Active Directory one and the VMware Update Manager one.


They're all fairly similar in the way that they get installed. So installing them here, in this location, will, a little bit later on, make them available for us when it comes time to actually work with them in the client side half of vCenter Orchestrator.


Now, for many of these plug-ins that we're bringing in, there will be additional configuration that has to occur. We'll talk a little more about the PowerShell plug-in and how to deal with it, and the Active Directory plug-in and how to configure those in an upcoming Nugget.


But for now, I want to show you where you can go about making the configuration to set up the plug-in for vSphere here within vCenter Orchestrator. I'll come here to vCenter Server. And you'll notice that, here, under vCenter Server, I need to identify SSL certificates, which I already have, and then, under the vCenter Server host is where I can identify where my vCenter Server is going to be.


So vc2.company.pri. The port is 443. Secure channel. I'll set up all of the machines to share a unique section with that administrator@vsphere.local and password setup. Hopefully, this will work here. And if I've done everything correctly, we have a successful connection between vCenter Server and vCenter Orchestrator.


This is necessary because in a little bit, we're going to be making use of activities here at Orchestrator, to make changes in vCenter Server-- to create clusters, and to move virtual machines around, and to instantiate virtual machines. All of these are going to happen and be authenticated by the connection that's set up here, in this plug-in.


Now, once you're done with your configuration here, of Orchestrator, it's generally a good idea just to restart your vCenter Orchestrator machine. That will ensure that any of the changes that you've made will get locked in appropriately. You may also need to restart the vCenter Orchestrator service, as well.


In fact, one of the common sort of issues-- at least with this version-- is immediately after a restart of your vCenter Orchestrator Server, it can sometimes be necessary to come back in and restart the service after the reboot. Don't ask me why, but that's just one of the things that has occurred in the past.


So be aware, here, of these server startup options because they'll come in handy when it comes time to figure out why things aren't working appropriately. Once you've completed the restart, pretty much the rest of your time you're actually going to spend inside of the Orchestrator client.


And the Orchestrator client is something that we can find. It's actually kind of hard to find the first couple of times because everything's URL-based. But what we're looking for here is https:// host name-- vco2.company.pri. So host name. Port 8281, and then vco.


That will take you to what I like to call the start page for Orchestrator. And this start page is where I can find documentation, where I can get access back to that same configuration interface that we worked with just a minute ago-- so the Orchestrator Configuration Interface-- also, where I can get access to the Web Operator screen, which is something we'll talk about in a couple of Nuggets, and lastly, where I can actually download and launch the Orchestrator client, itself.


The client arrives as a JavaScript, or as it is-- a Java Applet. And so this is one of the reasons why I actually like Chrome for this-- because Java and Chrome seem to work very well together. I also find it sort of humorous that as a Java Applet, Chrome says, hey, wait a minute, this file could harm your computer.


Go ahead and keep the file because that's the location where you're going to need to download in order to launch the VMware Orchestrator client. Typical Java security warnings here. Continue through, and then continue through all of the different dialogue boxes that pop up.


And that will take you to the log on interface for the Orchestrator client. So what have we talked about in this Nugget? We have talked about the installation and the initial configuration of vCenter Orchestrator. We went through all of the things you need to do in order to get Orchestrator up on a Windows device, talked a little bit about the Orchestrator appliance that's available out there, went through the necessary bits in order to get the Orchestrator client up and running so that we can log in.


And now, coming up next in our next Nugget, we're going to spend some time actually looking through the different workflows that this integration now exposes for us, not only in vCenter Server, but also inside of Orchestrator, itself. I think you're going to be excited about what you're about to see.


Now, all of that's a topic for our next Nugget, so until then, I hope this has been informative for you, and I'd like to thank your for viewing.

Executing and Scheduling Workflows in the vSphere Client

Introducing the Orchestrator Client

Constructing a Basic Workflow

Configuring Presentation

Adding Looping to Workflows

Integrating Active Directory Activities

Executing PowerShell Commands through Orchestrator

Customizing Orchestrator Webviews

Please help us improve by sharing your feedback on training courses and videos. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Intermediate 4 hrs 9 videos


Training Features

Practice Exams
These practice tests help you review your knowledge and prepare you for exams.

Virtual Lab
Use a virtual environment to reinforce what you are learning and get hands-on experience.

Offline Training
Our iOS and Android mobile apps offer the ability to download videos and train anytime, anywhere offline.

Accountability Coaching
Develop and maintain a study plan with one-to-one assistance from coaches.

Supplemental Files
Files/materials that supplement the video training.

Speed Control
Play videos at a faster or slower pace.

Included in this course
Pick up where you left off watching a video.

Included in this course
Jot down information to refer back to at a later time.

Closed Captions
Follow what the trainers are saying with ease.