It’s time to retire “vCO”

Before anyone gets in a huff, I’m not suggesting that a key part of VMware’s automation, orchestration and cloud functionality be consigned to the bin. This is about the name.

It was Q3 / Q4 last year (2014) that VMware announced the changes to its product names. A whole year ago! Of course, it can take time for a change to take effect, particularly when any of the following are a factor:

  • Older projects and environments using older versions of the products that contain original branding
  • Document, diagram and presentation re-use where the older names are used
  • Investment in any other IP or collateral
  • Ingrained habits, especially if you’ve been using these products for years

But by now “vCO” should be a thing of the past. That’s not its name anymore. I won’t be removing the tag from my blog but I’ll be making an effort not to use it anymore (after this post) and I’m going to remove the search from my Twitter client too:



Open Orchestrator JNLP files on OSX

New job. New laptop. But of course it isn’t set up like the old one. It doesn’t have all of the tweaks that I made over the years on it.

One annoyance, what with me being a heavy and frequent user of vRealize Orchestrator, is that client.jnlp files downloaded from the vRO web interface don’t have an application association by default. I’m writing this as a quick reference just in case I need it again anytime soon.

  1. Having downloaded and saved the client.jnlp file as normal, use the finder app to select the file, right click and select “Open with > Other…”.
  2. Browse to this path: /System/Library/CoreServices
  3. Select the executable Java-Web-Start.app
  4. Tick the “Always Open With” option.
  5. Click “Open”.