Was onsite the last few days deploying hyper-v, SCVMM and dpm, i taught i would share some of the hurdles that we found during the deployment.

So from the outset it was a basic windows 2003 sp2 environment with about 250gb of total data between the 2 systems to be virtualized.

they where sql test and development servers.

So the challenge was to virtualized the 2 boxes, upgrade the nodes to windows 2008 form a cluster and then deploy the vm’s back to it.

Use SCVMM to manage the cluster and dpm to back up the application data on the virtual machines.

Now…. easy enough … i hear you say nothing major to be worried about…

thats what i taught….

they where using symantec endpoint security and governed by group policy and a dns infrastructure they could not control.

So as i found out order is very important….

1. Install the operating system

2. disable all nics bare the management nic

3. set the ip

4. change the name and join to the domain

5. INSTALL the endpoint security software (cause if you dont endpoint gets mixed up with the ip’s and they the server cannot communicate with the rest of the network)

6. Install the failover cluster manager and mpio

7. Install the hyper-v role and reboot


9. Form the cluster

10. deploy a virtual machine – redirect config and vhd files to c:\clusterstorage\volume1\XXXX

11. do no turn on the virtual machine, instead go into failover cluster manager and configure a new service /application, select virtual machine and select the virtual machine you deployed.

12. deploy the scvmm agents (notice when you select one node it should select the cluster virtual node and second node) at this point verify the complete dns names as if you dont it will give you a complete headache…

13. once you are done , deploy dpm and gets the data replicated QUICKLY.


some other notes

live migration does not work in a cluster environment when you only have 2 nics (1 for cluster comms and 1 for both management and hyper-v) so you must have at least 3 nics in order for this to work correctly.

SCVMM agents must be under the local system account

winrm quickconfig is a very useful command 🙂

netstat –anb comes in very useful to ensure the agents, servers etc.. are listening on the right ports

if possible move the servers to an OU with group policy inheritance blocked during the setup this could make deployment an awful lot easier.


there is more the follow so stay tuned……