Browse by Tags

if you have two Hyper-V failover clusters managed by VMM 2008 R2, it is possible that you can't migrate over the network (LAN migration) a VM from one of the clusters to the other cluster. This issue will only appear if ALL of the following conditions are met. · VM is created using Hyper-V...

it has come to our attention that there are some customer complaints with regards to missing virtual machines in the administrator console after a cluster failover. Since it is not easy to remove those VMs from the VMM administrator console, Gokcen from our team wrote a script that will allow you to...

A few folks have been experiencing errors and long delays in adding a single-node (i.e. a 1 node cluster) cluster under management in Virtual Machine Manager. This issue stems from the fact that VMM has an overcommitted property for each cluster. By default, a single-node cluster will always be overcommitted...

Running VMM inside a Virtual Machine is a fully supported way of running VMM. Our team tests this scenario and we have some customers deploying VMM in such an enviroment. If you would like to deploy VMM in such an environment, it is recommended to place the SQL server in a separate server, especially...

If you have a Failover Cluster managed by VMM 2008, it is possible that you will get a placement page similar to the one below if you try to clone a Highly Available Virtual Machine that is part of the cluster. The placement page in the new-vm wizard below incorrectly states that the transfer type will...

We had a few customers ask us to clarify high availability (HA) with regards to Virtual Networks (VN). In the VMM/Clustering case, there are a few considerations around virtual networks: A VN to be considered HA has to have the same exact name in all nodes of the cluster (Virtual Network names...