Archive for Registering Orchestrator in vSphere

Deploying Orchestrator 6.0.3 into vSphere 6

vRARobot2

Deploying Orchestrator 6.0.3 into vSphere 6

Software versions in my lab environment

  • vCenter v6.0.0, 3018524
  • vSphere Hosts v6.0.0, 3029758
  • VMware-vCO-Appliance-6.0.3.0-3000579_OVF10.ovf

and

screen-shot-2016-11-23-at-11-01-06

Instructions

  • Download and deploy VMware-vCO-Appliance-6.0.3.0-3000579_OVF10.ovf into vCenter – File > Deploy ovf template

screen-shot-2016-11-22-at-20-26-33 screen-shot-2016-11-22-at-20-26-47 screen-shot-2016-11-22-at-20-28-11 screen-shot-2016-11-22-at-20-28-35 screen-shot-2016-11-22-at-20-29-07 screen-shot-2016-11-22-at-20-29-36 screen-shot-2016-11-22-at-20-29-59 screen-shot-2016-11-22-at-20-30-47 screen-shot-2016-11-22-at-20-31-58 screen-shot-2016-11-22-at-20-35-35 screen-shot-2016-11-22-at-20-37-18

  • Power on the VM
  • Log into a web browser using the Orchestrator appliance web address. In my case https://192.168.1.123:5480

screen-shot-2016-11-22-at-20-52-23

  • Change the time zone to Europe/London or whichever your timezone is and click Save Settings

screen-shot-2016-11-22-at-20-53-03

  • Click the Network tab and check the settings on the 3 tabs

screen-shot-2016-11-22-at-20-54-10 screen-shot-2016-11-22-at-20-56-20 screen-shot-2016-11-22-at-20-57-02

  • Click the Admin tab and click Time Settings are correct. I have Use Host Time but you can use Time Server

screen-shot-2016-11-22-at-20-57-49 screen-shot-2016-11-22-at-20-58-59

  • Click Save Settings

NEXT

  • Log into a web browser using the Orchestrator web address. In my case https://192.168.1.123:8283
  • Use the vmware username and the password you set up in the OVF deployment

screen-shot-2016-11-22-at-21-01-17

  • You will reach the below screen

screen-shot-2016-11-22-at-21-02-27

  • Click on the Network tab on the left hand side and select your IP Address and check all other details are correct. Click Apply Changes at the bottom right of the screen

screen-shot-2016-11-22-at-21-03-40

  • Click on Authentication and scroll down the screen until you see a link for SSL Certificates. Click on this link

screen-shot-2016-11-22-at-21-05-05

  • Put in your vCenter server in the following format – techlabvcs001.techlab.local:7444 and click Import

screen-shot-2016-11-22-at-21-08-01 screen-shot-2016-11-22-at-21-21-36

  • Put in your Single Sign On/PSC server in the following format – techlapsc001.techlab.local:7444 and click Import

screen-shot-2016-11-22-at-21-12-04 screen-shot-2016-11-22-at-21-14-28

  • Go back to the Authentication tab
  • Put in your Single Sign On server and click Advanced
  • put in your Admin username and password
  • Click Register Orchestrator

screen-shot-2016-11-22-at-21-23-15

  • It should look like the below with further configuration to do

screen-shot-2016-11-22-at-21-24-52

  • Choose your SSO Domain which can be the local domain, LAN domain or the vsphere.local domain.
  • In my case I chose my main domain techlab.local where I have set up a group called vro-group which contains user accounts I want to use as Admins

screen-shot-2016-11-22-at-21-26-22

  • Click Accept Orchestrator Configuration

screen-shot-2016-11-22-at-21-28-40

  • Click Test login and try one of your users

screen-shot-2016-11-22-at-21-30-20

  • Check your license

screen-shot-2016-11-22-at-21-33-50

  • Check the Plugins are all ok

screen-shot-2016-11-22-at-21-34-50

  • Click Startup options and restart both services
  • Log back in and check everything is green

screen-shot-2016-11-22-at-21-36-17 screen-shot-2016-11-22-at-21-37-48 NEXT

  • Open a web page and navigate to your Orchestrator configuration page which in my case is https://techlaborc001.techlab.local:8281
  • Click on Start Orchestrator Client

screen-shot-2016-11-22-at-23-17-55

  • Click on the drop down to Design
  • Navigate to Library > Microsoft > Active Directory > Configuration > Add an Active Directory server
  • Add in the relevant details for your AD server and add others as necessary

screen-shot-2016-11-22-at-23-19-53 screen-shot-2016-11-22-at-23-17-19

  • Next navigate to Library > vCenter > Configuration > Add a vCenter Instance

screen-shot-2016-11-22-at-23-23-34

  • Click Next and fill in the next screen

screen-shot-2016-11-22-at-23-24-27

  • Next we need to run the workflow Register vCenter Orchestrator as a vCenter extension

screen-shot-2016-11-22-at-23-27-40

  • Next type in the external address to advertise this Orchestrator
  • this needs to be for example https://techlaborc001.techlab.local:8281

screen-shot-2016-11-22-at-23-30-38

  • It should say it has been registered as per below

screen-shot-2016-11-22-at-23-32-04

  • We can check it has been registered by opening a web browser and putting in the vCenter server address as per below
  • https://techlabvcs001.techlab.local/mob
  • Click on Content

screen-shot-2016-11-22-at-23-34-17

  • Click on ExtensionManager

screen-shot-2016-11-22-at-23-34-51

  • Look for extensionList[“com.vmware.vco”] which should only exist when the workflow has run correctly.

screen-shot-2016-11-22-at-23-35-44

  • Click on Client

screen-shot-2016-11-22-at-23-37-23

  • You should see the below in url string. This will also appear in the Web Client which we’ll see further on in the instructions
  • You can put this link into a web browser and it should try and download the zip

screen-shot-2016-11-22-at-23-38-00

  • If you need to remove an extension, follow this useful blog below

Removing extensions link http://blog.mwpreston.net/2014/05/02/to-the-point-removing-stranded-vcenter-orchestrator-servers-from-vcenter

  • You now need to restart the web client
  • When the Web Client has restarted and come up again, Go to the Home screen and select the Orchestrator icon

screen-shot-2016-11-22-at-23-53-49

  • You should now see the vCenter and the Orchestrator server listed and you’ll see the information which we saw in the mob web page

screen-shot-2016-11-22-at-23-56-07

  • If you click on Workflows under Inventory trees, you will see the whole library of workflows

screen-shot-2016-11-22-at-23-57-45

  • You can then use the inbuilt workflows or create your own in Orchestrator
  • If you run the List the vCenter Orchestrator extensions of vCenter server, you will see it will pop up in the Recent Tasks list at the bottom of vCenter

screen-shot-2016-11-22-at-23-59-13

  • Pretty funky stuff 🙂

Next

  • In the vSphere Web Client > Click Home > Orchestrator, click on the Workflow icon and expand vCenter > Virtual Machine Management > Basic

screen-shot-2016-11-28-at-14-24-30

screen-shot-2016-11-28-at-14-25-38

  • Right click “Create simple virtual machine”, here is where you can run a workflow directly from within vSphere Web Client.

screen-shot-2016-11-28-at-14-27-55

 

Optimization WordPress Plugins & Solutions by W3 EDGE