I just finished my migration from VMM 2008 R2 to VMM 2012 SP1. I have a total 15 hosts running 2008 R2 being managed right now. 3 clusters, 8 node, 3 node and 2 node plus 2 hosts in my DMZ that are stand alone.
New hardware is coming this week and I am going to start to convert these hosts to 2012 by rolling the upgrades in moving VM's etc, creating new CSV 2.0 volumes etc.
I have done a TON...and I mean a TON of reading on teaming and converged networking plus I have one of the new hosts that I have been testing stuff out on. I come from VMware, many years with it and to be honest SCVMM 2012 SP1 seems overly complex in comparison, very much so and for what reason I dont get. Not to mention with 4 ways to do things on a cluster (powershell, Hyper V manager, Failover cluster manager or SCVMM) it can be confusing again in comparison to doing everything in VMware from a vcenter client.
My question is this. It seems about 100x easier to build a powershell script that creates a team, a vswitch, vnics, applies qos and IP's the vnic's that applies in moments then join the host to SCVMM vs.....
going through SCVMM and building Logical Networks, Network sites (for specific host groups), IP Pools, VM Networks, Uplink Native Port Profiles, Virtual Native Port Profiles, Port Classifications, Logical switches, then pushing that to the host and during that process build the vNIC's. (do you see the complexity?)
If I go the power shell route for ease of administration am I losing anything critical in SCVMM other than managing the converged network of the host??????
I get if we had a large Data Center where we were adding new hosts on a regular basis that SCVMM would make this easier. However after I get 15 hosts to 2012 I wont touch them for 4 years. If we do add more hosts (no plans) it would be maybe one a year if that. However I could make the argument that running a simple powershell script would be easy as well.
Thanks, -Lindy