Hyper-V Program Manager
I have been using SCVMM (System Center Virtual Machine Manager) more and more in my home environment of late. But I also keep getting myself in trouble – usually because I keep on trying to do things the “Hyper-V way”.
Recently– I tried to do a quick storage migration of a running virtual machine from my production server to my dev / test server (yes – I do have production and dev / test Hyper-V servers at home) and the migration failed. I retried the migration through SCVMM and it failed again.
At this point in time I should have chosen to undo the operation through the SCVMM console. Unfortunately – I instead dived into the Hyper-V Management console and deleted the snapshots that SCVMM had created as part of the quick storage migration.
This left me in a bad position.
SCVMM still had this virtual machine marked as failed – and any attempt to repair the virtual machine would fail too – as whenever I tried to repair, or undo, the migration the first thing SCVMM would do is to look for the virtual machine snapshots that I had deleted. To make things even worse – the “failed” virtual machine was running on my production Hyper-V server, which I really did not want to reboot to help SCVMM sort out the state of the system.
After searching the web and thinking about it for a bit – I came up with a simple solution.
I removed my production Hyper-V server from SCVMM, and then added it back. Neither of these operations affect the virtual machines running on the Hyper-V server – and it effectively resets the state of the server for SCVMM.
The whole process took about 5 minutes and I soon had all my virtual machines correctly listed in SCVMM.
That is pretty simple. Another way would be to open up your VMM database with SQL Managment Studio, then edit your db0.tbl_WLC.VObject table, find your VM name and change the status column to 0 or 1. This will trigger VMM to refresh the VM to its correct status. Works for other stuck statuses in VMM like the occational "Missing" status that can get VMM confused after a cluster node failure.
I've had to use this method a few times but in our environment we are heavily reliant on some of the vmm attributes like owner, quota points, template name etc which all gets lost doing this. We resorted to manually editing the SQL tables but this isn't ideal either.
Does this rectify the problem also? It has worked for me in the past for similair issues
i had a few problems like this, probably caused myself because of doing stuff in hyperv manager. with my first VMM server i had the thing hanging on removing a hyperv manager from VMM, which broke the whole thing and decided to do a reinstall.
As i said, i probably caused this myself because of doing stuff in hyperv manager, but.. I also think doing normal stuff in the hyperv manager should not break VMM. Ive seen som e other ppl having trouble aswell and blogs how to edit VMM's SQL DB, but i dont think that should be considered to be normal. Although i like Hyperv and VMM, i dont think VMM is ready for main use without experts managing it.
I have had to resort to this hack of sorts also. and i dont think its the correct way to handle it.
lately i have been more and more relegating vmm to a second place and do everything from the cluster manager and hyper-v manager. and im only using vmm for p2v migrations.
its refresh time is not good/annoying. machines tend to appear in weird states....
im not happy with it.
I have had a bad luck previously from removing and re-adding servers from/to SCVMM. I have a 2 nodes failover cluster running HyperV and I tried to remove and re-add the cluster usign SCVMM admin console. The problem is half (or all? forogt) VMs (they are production VMs) got failed over to another node!
I agree with all here. I feel SCVMM as a frontend that use other system apps to do the work (as the things Cluster Admin, Hyper-V Admin, etc. does). The problems is that it's a BAD FRONTEND.
For example, you can't add a virtual machine for not HA use in a node that is part of a Hyper-V Cluster. You must do this using the Hyper-V Admin. Also, the Library of VMM is a hell. You can't move the library, but if you need to use a hard disk for a virtual machine, it must be in the library directory VHD, if not, you won't be allowed to add it. Same with ISOs and FDD's.
Still I haven't seen any advantage of using SCVMM, not to mention that I didn't found only one reason to pay for it.
Hate to say it, and this is probably the wrong place for it, but I'm not a fan of SCVMM either. It has two main advantages over Hyper-V Manager and Cluster Admin:
1. It's a prettier, consolidated interface. You can do it all from one place.
2. It has expanded functionality like P2V, self-service portal, etc.
But generally speaking, it is faster and easier (and with a more responsive interface) to do anything that needs done with Hyper-V Manager or Cluster Admin. And I've had customers who have told me the same thing...they hate SCVMM.