As usually, I would thank you for continuing browsing my blog although I haven’t uploaded for couple of months. I was caught by my personal errands till, today, one of my friends said, “Silver, why don’t you update your blog? Even just write some nonsense into it”.
Well, personally, I don’t write any useless information in this tech blog. But I do need to update. So here it is. Hope you can enjoy it.
I will show you how to configure VMware Orchestrator. This software is coming with vSphere but it is installed silently and you need to manually configure it. Reason to use VMware Orchestrator will be 2.
A. You have very large and complex Vmware environment and you would like to dig deep and become guru.
B. You need to prepare for VCAP-DCA exam.
Regardless which reason you may have, this post will give you a hand and knock the door for you.
Configure VMware Orchestrator
The first thing you need to do is to check out Service “VMware vCenter Orchestrator Configuration” is running. In default, it is manual for start up.
Once you started the Orchestrator Configuration, you can just run “Configuration”
You should see this page coming from IE.
The default username and password is vmware/vmware.
You should see main interface like this.
There is nothing you need to configure in the General class for now.
so Let’s jump on “Network”. the network configuration is for Orchestrator. So You need to put IP and DNS and keep settings. No drama on that.
Notice “SSL Certificate” page here, but we don’t configure it for now. You can choose to use CA certificate or your own certificate. In this case, we will generate Orchestrator own certificate first, then we can configure it. Please see Chapter “Server Certificate” below.
The purpose of LDAP is to let you use AD account to log in to Orchestrator client.
You need fill those blank with your DC servers, and LDAP path.
For the root and other group path information, you don’t need to run some scripts to get it. All what you need to do is to run AD Users and computers.
Right click the object (for example, the root of your AD) and click –> “Properties” and go to Attribute Editor and find distinguishedName as follow.
Same thing for the rest of page.
It’s pretty straight forward for configuring database. I’m using SQL database and
Once you install the database, jump on SQL server and verify it.
You should generate your own Server certificate here. For some reason, the certificate generate by my Domain CA doesn’t work well here. so I would suggest you do it by yourself.
Once you generate certificate, you need to export it to a file protected with password.
The next step supposes to import certificate back to “Network –>SSL configuration”. If you don’t that, you won’t get “License” right.
This is where you gain license from vCenter and also license for plug-ins.
If you don’t import SSL certificate here, you won’t get right result. Because we need to use secure channel.
You need to import your license which you export above.
This will also setup Network configuration->SSL part as well.
please be noticed: You may need to restart vCenter to let license work!!
Start up option:
You must make sure the status is “Running”. I was stuck at “Unknown” status for a very long time even after I restart vCenter and Orchestrator services and server. The only way to resolve it is to click those “Restart” buttons in this page. Trust me, they are here for reasons.
The rest parts are very easy to configure. I just paste picture here as guide.
This is for connection to your hosts.
This is where you configure your vCenter.
once you finished the configuration, you can get into Orchestrator now via it’s own client. Run it under Vmware you shall see this interface.
There are some tricks to setup Orchestrator. But the difficult part is actually to use it since there are lack of good examples and documents.
I would suggest VMworld Orchestrator Lab manual is a very good start. If you do want to know me to give you some examples, please leave your messages.