Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a Hyper-V 2008 R2 failover cluster with 3 nodes. I added new 3 Virtual Machines to the failover clusters, one of them failed with errors:

Event ID: 1069
Cluster resource 'Virtual Machine Configuration [server]' in clustered service or application '[server] failed.

and

Event ID: 21502
'Virtual Machine Configuration [server]' failed to register the virtual machine with the virtual machine management service.

I can't bring the resource online at all. I see I can right click on the resource and choose "delete." I just wanted to make sure that would be deleting it only from the Failover Cluster and not from Hyper-V Manager.

How do I delete the failed virtual server from the Failover Cluster Manager and retain the virtual machine in the Hyper-V Manager?

share|improve this question
    
I don't have a Windows Server 2008 R2 failover cluster to check at the moment but deleting the VM from Failover Cluster Manager should remove it as a clustered role/service but leave the VM intact. It should be the equivalent to the Remove option in a Windows Server 2012 Failover Cluster. As a precaution, create a dummy VM, cluster it, then delete it from the cluster and see what happens. –  joeqwerty Apr 23 at 15:22
    
@joeqwerty Yeah, that looks to be the ticket. I wanted to double check. Got to love test servers! Add the answer and I'll give you credit. Thanks again –  Nixphoe Apr 23 at 16:11

1 Answer 1

up vote 2 down vote accepted

I don't have a Windows Server 2008 R2 failover cluster to check at the moment but deleting the VM from Failover Cluster Manager should remove it as a clustered role/service but leave the VM intact. It should be the equivalent to the Remove option in a Windows Server 2012 Failover Cluster.

share|improve this answer
    
Deleting from failover cluster manager does turn the VM into a normal non-HA VM which you can manage from hyper-v manager on whichever cluster node it was left on. You can then bring it back into cluster manager to make it HA again. –  Grant Apr 23 at 16:19
    
Looks like the root of the issue of setting this up correctly was the snapshot file was set to a path that was not on the storage cluster. I moved it to match all the other servers and was able to get this working correctly. Thanks again –  Nixphoe Apr 23 at 16:35
    
Glad to help and glad you got it resolved. –  joeqwerty Apr 23 at 16:48

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.