Unexpected warning and error messages in a virtualized Windows Server 2008 R2 failover cluster


In a Windows Server 2008 R2 failover cluster that has been configured to run as a guest (virtual machine) in a Hyper-V environment, the following messages are written to the logs that are indicated in the message details:

Warning message:

Log Name:  Microsoft-Windows-FailoverClustering-Manager/Admin
Source:  Microsoft-Windows-FailoverClustering-Manager/Admin
Event ID:  4694
Level:  Warning
Hyper-V management tools were not found on the system.  Creation and management of virtual machines will be disabled in Failover Cluster Manager.  Install Hyper-V role admin tools for servers or RSAT tools for clients to enable those options.

Error message:

Log Name:  Microsoft-Windows-Hyper-V-High-Availability/Admin
Source:  Hyper-V-High-Availability
Event ID:  21123
Level:  Error
Failed to set the migration networks at the VMMS: Class not registered (0x80040154)


These messages are registered because of the new functionality in Windows Server 2008 R2 failover clusters. This new functionality includes better interoperability with Hyper-V. Even when the failover cluster is running in a virtualized environment as a guest (virtual machine), the failover clustering feature expects aspects of the Hyper-V role to be available. When the failover cluster does not find these Hyper-V aspects, these messages are written to the logs in question.


To resolve the warning message, install the Hyper-V role Remote Server Administration tools.To add the Hyper-V Remote Server Administration tools, follow these steps:

  1. Click Start , click Administrative Tools , and then clickServer Manager
  2. In the navigation pane, click Features , and then click Add Features.
  3. Expand Remote Server Administration Tools.
  4. Click Hyper-V Tools, click Next, and then click Install.

There is no workaround or resolution for the error message. However, you can safely ignore this error message in this scenario.

More Information

In a Windows Server 2008 R2 IA-64 environment, there is no workaround for this error message because Hyper-V does not support the IA-64 architecture.