So after scratching my heard for the most part of two hours, I found out the solution to my problem. The problem started happening after I had to restore the DB of my VMM 2012 R2 onto a new installation. I kept on getting Error 20552 when refreshing any server in VMM.
I finally resolved it by re-entering the password for the “run as account” for the VMM service in control panel.
PS: I had tried resetting the password inside VMM’s settings > Security > run as account > my host admin account. But that was not taking, throwing an error saying that the account was not found in the domain or something 🙁
Do you know that System Center Virtual Machine Manager (VMM) lets you create an identical clone of a running VM?
Yes! you do not even have to shut down a VM . How cool is that!
1) While going through the cloning process wizard in VMM, choose to leave the NIC disconnected
If you do not leave the NIC connected, you will have duplicate IP addresses on the network, when the cloned VM boots up.
2) After the cloning process completes, remember to run sysprep.
Yes, there have been some reports that VMM runs sysprep when it creates a clone, but I have confirmed myself (using psgetsid utility) that the clone and the original have the same SID and have the same hostname. They are virtually identical. So, you MUST run sysprep.
I have been troubleshooting a WinRM related problem which was the main cause of an error shown in SC Virtual Machine Manager as “Host not responding”. The error always pointed to Win RM or Windows Management. I tried a lot of fixes, but nothing worked. Eventually I thought to rebuild the Windows Management repository. Here are the steps I took to fix this issue:
- Run this command on the errant server: net stop winmgmt (You will have to do this multiple times, or the step #2 will give you an error, file in use)
- rename the folder ‘Repository’ underneath %windir%\system32\wbem
- restart the system
The repository will be rebuilt automatically, OR you can rebuild it manually by running this command winmgmt /resetrepository (I did not have to do this)
PS: This also fixes the error in Server Manager which shows up under NIC teaming – “Host Unmanagable”
OK so here is a tricky problem with an easy fix.
Sometimes, in SC VMM 2012 some of my VMs are shown as “missing”. I cannot do anything to them using VMM. An easy fix is to fire up FCM (Failover Cluster Manager) and live migrate or quick migrate the VM (depending upon whether the VM is running or not). After that VMM will immediately refresh the VMs state to the correct one….stopped or running.
From time to time, I run into this issue with our Hyper-V environment. No matter how many times I upgrade the VM additions, SCVMM still is not able to detect it. It always ends up saying “not detected”.
Eventually I noticed that one of the the 6 Hyper-V related services which are usually running on the VM was having some trouble – the heartbeat service. Hmmm…that makes sense!
If I tried to start this service, I got the following error:
Error 1083: The executable program that this service is configured to run in does not implement the service.
While doing some searching on the net, I found out the solution here !!THANK YOU!!
As mentioned by that guy, the two things I need to know are shown below:
So I open the registry and add vmicheartbeat to the bottom of this Multi-String entry, like this:
After I click OK and restart the VM, the heartbeat service starts without any problem (automatically). Just do a refresh in VMM and now I see the VM additions version number. Yeah baby!
Thanks a lot to Jeremy!