Our design calls for a separate Orchestrator server. The documentation states "To enhance the availability and scalability of your Orchestrator setup, install Orchestrator on a computer different from the computer on which vCenter Server runs". What is confusing is that vSphere 5.1 appears to install Orchestrator by default. There isn't a way to exclude Orchestrator from the install.
I do see the Orchestrator icon under vCenter Home so, if one does decide they want to separate Orchestrator on a different server how is the initial installation to be treated?
1) There is no redirection. The initial installation will just be another vCO managed by the vSphere User Interface. It can be turned of with stopping the vCenter Orchestrator service and the vCenter Orchestrator configuration service.
2) The original DB, tables, will stay. If not used it will keep a very low footprint.
The reason to separate vCenter and vCO is to avoid having both using CPU/Memory and particularly I/Os on the DB at the same time. If not used the vCO installed with vCenter will not affect vCenter.
Christophe.
Thanks for the quick reply. Maybe I'm being to picky but, it does seem a little bit messy. I'd prefer an option to exclude Orchestrator from the original installation.
Any idea if there is a switch or command to install vCenter without Orchestrator. Not sure I would even bother going that route but, curious if one exists.
There is definitely a technical way to avoid installing it but I do not know it. IMHO you should not bother
Orchestrator DB schema is not created during installation. You have to create database and db user manually and use Configuration tool to create schema objects. So, all you have to do is uninstall Orchestrator from "Control Panel\Programs\Programs and Features". If you want to uninstall it with msiexec tool look in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall for Orchestrator product id.