About a year ago, I wrote about the complex requirements for enabling PRO Tips in System Center Virtual Machine Manager 2008 (SCVMM). That was the previous release — what has changed now that SCVMM 2008 R2 is available?
First Things First
Before you can use PRO to Live Migrate virtual machines between hosts (which is sort of the whole point), you need to first configure Hyper-V, failover clustering, and Cluster Shared Volumes — something eWeek found to be significantly more complicated than VMware ESX.
After Hyper-V and Live Migration are up and running, the next step is to install SCVMM 2008 R2 so you can integrate it with your System Center Operations Manager 2007 (SCOM) environment.
What’s that? You don’t have SCOM deployed? Go ahead and set it up. Come back in a few days when you’re ready to go to the next step.
After your environment has both SCVMM and SCOM up and running, it’s integration time! If you have ever thought that the next-next-finish Microsoft wizards were boring, then this is the task for you. You’ll get a chance to make configuration changes to various systems and possibly even Active Directory — haven’t you always wanted to learn about the SetSPN utility anyway?
But don’t let me spoil the excitement by giving away the ending — pick up your own copy of the 34-page integration guide and experience the thrill for yourself.
Some of you are probably thinking that this is an exaggeration, it can’t be all that bad. Let’s take a look from another perspective, presented in the Infrastructure Planning and Design (IPD) guide for SCVMM 2008 R2:
As you can see from the above excerpt, integrating SCVMM with SCOM clearly increases the time, effort, and complexity of your virtualization deployment. And don’t forget that SCOM is required for monitoring your Hyper-V infrastructure, too.
Unlike the Microsoft virtualization conglomeration, VMware DRS is an integral part of vCenter Server — purpose-built for virtualization. Talk about additional layers…