The update I referred to a little while ago for Virtual Machine Manager 2008 has been released as part of a rollup package. This update is said to deal with the unsupported cluster configuration alert. It also fixes a number of other issues.
“List of issues that are fixed:
Issue 1
When you migrate VMware virtual machines, the resource pools that are associated with the virtual machines are changed.
Issue 2
Hyper-V virtual machines have a status of "unsupported cluster configuration" if a node in a Windows Server 2008 Failover Cluster does not respond or has been restarted.
Issue 3
Differencing disks are lost when the following conditions are true:
- You migrate a virtual machine from a Virtual Server host.
- Multiple virtual machines share the same parent virtual hard disk file.
Issue 4
The agent status is not updated for Windows Server 2008 Failover Cluster nodes.
Issue 5
Hyper-V virtual machines in a Windows Server 2008 Failover Cluster have a status of "unsupported cluster configuration" if the cluster has a resource that has an MSCluster_Property_Resource_Cluster_Extension_XP_Type type. This resource type is typically used by storage replication software.
Issue 6
If you add a Virtual Center server by using an account that is a member of the Enterprise Admins group, you receive the following error message when the refresh host job runs:
Error (2951) Virtual Machine Manager cannot complete the VirtualCenter action on server servername.domainname.com because of the following error: Login failed due to a bad username or password. (InvalidLogin).”
EDIT #1:
Normally you’ll get this update via Microsoft Update or WSUS. However you can manually download it. Don’t just double click on the MSP otherwise you’ll get a baffling message: "Launch setup.exe for installing virtual machine manager server". It turns out I’m not the only person to get that one. I did some digging and found you need to run this command to install the update: "msiexec /p vmmServer64update.msp BOOTSTRAPPED=1”.
EDIT #2:
Part of this update was a request from myself through IT Pro Momentum. When you patched VMM 2008 managed Hyper-V nodes, 1 at a time, the state of VM’s in that cluster would change to "unsupported cluster configuration". I’ve installed the rollup update. On day 1 to test I downloaded security updates onto our redundant host in the cluster. There were no issues with VM’s. I forced a VM refresh using the refresh-vm cmdlet in the Powershell interface. On day 2 I installed Windows Server 2008 SP2. VMM saw that the agent was offline but the VM states remained managable.
Excellent. This seems to have fixed an anoying issue.