Hello all,
I have several tasks due this month that amount to building around 1,000 VM's with WIndows 7 OS. I have a template that we use to build the existing machines one at a time. We just got Orchestrator working last Friday and I successfully ran several different types of workflows. I need to automate building the remaining systems but I have limited experience with Orchestrator and I am not very strong at scripting. While I have looked through this discussion board, I am not sure if some of the more promising looking examples will fit me needs or not.
What I would like to have is a workflow where I can put in a list(s) VM's that are to be built. We follow a very standard naming convention and the machines are grouped by name in lots of 15 - 20 VM's. It would be a nice to have to be able to assign (some groups of) machines to resource pools and all the machines to group folders, but this can be done later easily enough.
All machines have the following naming convention---- DEPT~OS~Group#~ machine# (i.e. QA Win7 01 001~ 025, and finish at QA Win7 04 025 -- in this example each group has 25 machines giving us a total of 100) So we have sets of machines for DEV, QA, productions etc. each set starts at DEPT~OS~01~001.
The name of the machine is the only unique variable. All machines will be exactly the same otherwise. Resource allocations, Nic, Product Key, Admin password, run once scripts etc. This is being deployed to 3 different clusters so the cluster name for esx host and the data store cluster would be unique for the machines going to those locations.
Thanks,
Jamie
