Orchestrator Client on Windows x64

I recently needed to install vCenter Orchestrator client on a Windows 7 x64 machine, to connect to an Orchestration server on the infrastructure. (As was typically the case, I’ve done this already then forgotten how to do it, so this is a reminder for me as well as a how-to for you!)

Previously, there was a standalone client installer for 32-bit Windows installations, and installing a standalone client was easy. If you try to install that on 64-bit Windows, you get the obvious failure. So, how can you install it?

The 64-bit installer is captured on the latest vCenter installer ISO, so you need to login and download this from VMware.

Next, download Virtual Clone Drive (SlySoft, see here), to mount the ISO as an emulated CD/DVD drive. (Other tools are available, but I just use this out of habit….)

Mount the vCenter ISO as a virtual drive, then browse the contents (cancelling the autoplay option).

Open the following folder location: <DVD Root> / <vCenter-Server> / vCO.

Launch the vCenter Orchestratoer <version number> executable.

Follow the default options, and at the following option, select ‘Client’. (It will highlight, it’s not a button).

Select a programme group (typically VMware if you are already a VMware Admin, choose your own preference).

JRE will be installed automatically if needed, as will the default ports.

That’s it! vCO Client should now be installed and ready to configure.

vCenter Orchestrator Silent Install

Article by Michael Poore (@mpoore)

Is it possible to install vCO on a Windows server silently? Yes.

If you have the EXE file (DVDDrive:\vCenter-Server\vCO\vCenterOrchestrator.exe) available on the server then installing is as simple as:

D:\vCenter-Server\vCO&gt;vCenterOrchestrator.exe -i silent

It takes a few seconds to complete but at the end of it the vCO Configuration service is present and running:

Of course that’s just installing vCO, it’s not configured – that’s still to be done (see my earlier article on configuring vCO).

So, what’s the point of doing such an install then? Where’s the benefit? If you look at vCO’s Configuration Maximums it’s not entirely obvious is it?

Item Maximum
Connected vCenter Server systems 10
Connected ESX/ESXi servers 300
Connected virtual machines spread over vCenter Server systems 15000
Concurrent running workflows 150

You’d need a very large environment to *need* more than one vCO server let alone to need a method of automatically deploying them. Either that or a very particular use case.

Install vCenter Orchestrator on a Dedicated Server

Article by Michael Poore (@mpoore)

The binaries for vCenter Orchestrator (vCO) come bundled alongside vCenter Server and are installed by default when vCenter is installed. But what if, and it’s probably a better practice, you want to install vCO on a separate server to vCenter. How’s that done?

Before running through that, first let’s cover requirements. vCO server components must be installed on a 64-bit Windows OS. The client component can happily sit on 32-bit. The minimum recommended RAM is 4GB but in a lab or non-production environment you can get away with less depending on if the database is co-located or not. [Read more...]

Configuring vCenter Orchestrator

Article by Michael Poore (@mpoore)

vCenter Orchestrator (vCO) is a no charge extra for vCenter Server owners. In fact the binaries are installed alongside vCenter Server itself.

This post covers what you need to configure vCO and start to use it. It’s based on the GA release of vCenter 5.0. (Of course I should point out that other orchestration products are available.) [Read more...]