So with all of my budget money taken away, I've had a few extra cycles to sit down and learn how to use vCO.
A major problem we've been having is complications around our operations team deploying EZProxy servers consistently. An EZP VM is a 10gb SuSE VM with 1 CPU and 2GB Ram. IP and Hostname are requested during the customization specification. However, we've found numerous 4 CPU 8, 16, and 32GB ram VM's.... how do I fix this? I've trained them, I've documented EVERYTHING, yet these issues still happen.
Along comes Orchestrator 
vCO is one of those under-documented, under-used, super-powerful tools that most people don't even know they own. Not to mention, it has a fantastic web interface!
So, I was thinking... an operations user goes to our vCO web interface:
They log in using their AD credentials...
They're dropped into a "Operations Portal"...
They select the Provision EZproxy workflow and click execute...
STAY WITH ME GOOSE!
They enter the Hostname and IP of the to be provisioned EZP VM...
And once they click finish... voila! the system is built!
Pretty tough to mess that up right? Lets build the workflow...
