Highly Available Virtual Machines Lose Configuration Settings after Failover in Windows Server 2008 Failover Clusters

This article has been archived. It is offered "as is" and will no longer be updated.

Changes that are made to a highly available virtual machine with the Hyper-V Management snap-in may not be reflected on another node in the cluster when the virtual machine fails over or is (quick) migrated to that node.


The primary tools that are used to change the settings for a Hyper-V virtual machine are the Hyper-V Management snap-in that is installed with the Hyper-V role, the Remote Server Administration Tools (RSAT) on a non-Hyper-V Server or the System Center Virtual Machine Manager (SCVMM) 2008 product.

Hyper-V is unaware it is running in a highly available environment and therefore some configuration changes that are made to a highly available virtual machine by using the Hyper-V Management snap-in may not be automatically replicated to all nodes in the cluster. This can result in failures when a virtual machine is migrated from one cluster node to another. If the same configuration change process is executed in SCVMM 2008, the changes are propagated to each node in the cluster.

The configuration changes that are not replicated between cluster nodes automatically include changes to the networking or the storage configuration in a virtual machine. Without the replicated changes, a failure of the virtual machine might be encountered during a migration between cluster nodes.


If a virtual machine configuration is changed after it was made highly available, then you will have to run the Refresh virtual machine configuration process for each virtual machine before migrating it to any other node in the cluster.

Execute the following procedure on each virtual machine where changes were made to make sure that the configuration changes are replicated completely.

Note: This process will cause a service interruption for the particular virtual machine

1. In the Failover Cluster Management snap-in, expand Services and Applications in the left navigation pane.
2. Highlight the group that contains the virtual machine that had changes that were made to its configuration.
3. Right-click the group in the left navigation pane and select Refresh virtual machine configuration from the drop-down list.
4. When this process is run, the virtual machine is put in a Saved state and a report is generated when the process completes. 
5. Review the report to make sure that there are no Failures and, if there are, correct them and rerun the process until it finishes without Failures.

Note: The report will always complete with one Warning.  The Warning can be ignored because it basically says no changes to the virtual machine configuration were detected.

6. As soon as the process completes the virtual machine can be brought back Online in the cluster and a failover can be executed.
7. To move the virtual machine to another node in the cluster, Select the Group in the left navigation pane in the cluster and then in the right side actions pane select Move virtual machine to node <cluster_node_name>. 
8. Verify the virtual machine successfully comes Online on the node that you selected.


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2000016 - Last Review: 01/14/2015 12:59:33 - Revision: 1.0

  • kbnosurvey kbarchive KB2000016