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.
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”
Inspite of my refreshing the VMs having this error……….fingers crossed……..sometimes the error went away….sometimes did not. I was getting really frustrated. Here is how to fix it, once and for all:
In Failover Cluster Manager, check the name of the VM….if it is something like – “SCVMM server_name Resources”… rename it to just server_name.
Then refresh the VM inside SCVMM’s Virtual machine Manager. VIOLA! the VM would be back to normal.
I just wasted a couple of hours troubleshooting this error 0xE000100 while installing Windows 2012 R2 on VMM 2012 SP1 (older version). At first I thought there was some data corruption, ended up downloading the ISO again, to no avail. Then I thought maybe you cannot install R2 on older VMM. I started googling the requirements for 2012 R2. After much googling I found out the problem. I created the VM with dynamic RAM, using the default 512MB startup and 10GB max. THAT is the problem. Check this out:
Under setup for virtual machines section, they say:
If you create a virtual machine with the minimum supported hardware parameters (1 processor core and 512 MB RAM) and then attempt to install this release on the virtual machine, Setup will fail.
Cowbanga!! Note to myself, never use dynamic RAM to install a VM’s OS!
I have used dynamic RAM on all older OSes from Windows, works fine…but with 2012 R2 it does not. I think it is best to make the switch to dynamic RAM later.