While creating a Hyper-V replica broker in my HV cluster, I came across a problem. No matter what workaround I tried, my broker wont work. I tried pre-staging the computer account etc, as mentioned here but for my particular environment, it did not work. I read this:
Here is how I resolved it :
- I deleted the pre-staged computer account in AD, (which I had created manually, earlier for the replica broker)
- Configured the role in FCM, no errors while creation
- After that… yes, I got errors in the log (ignore for a minute)
- Then I recreated the AD computer name by hand and gave full control over that new account to the cluster’s computer account
- Went to FCM > cluster name > roles
- Noticed the HV replica role there (but it was in red, stopped)
- clicked “start role” on the right side action menu
- The role came online in a few seconds.
Now I can even ping the virtual IP address of this Hyper-V replica broker role!
I guess, for whatever reason, (at least in some environments) FCM cannot really use a “pre-staged” account for this role.
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.
While doing work on Fiber Channel fabric I ran into the need to find the wwn of an HBA installed in my server. Here is the quickest way to find that info:
Run this PowerShell cmdlet:
Oh, remember to run PS as administrator, otherwise you will get PermissionDenied!
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”