Hyper-V: Integration Services Must be Installed Before Primary or Replica Virtual Machines can use an Alternate IP Address after a Failover

Hyper-V: Integration Services Must be Installed Before Primary or Replica Virtual Machines can use an Alternate IP Address after a Failover

This article is intended to provide more information about a specific issue that can be identified by running a Best Practices Analyzer scan for Hyper-V. It also can be used without running a scan, as general troubleshooting and best practice information to help you configure your server appropriately. If you have troubleshooting steps or information that would improve this article, please add it. For instructions on how to edit a TechNet Wiki article, see Wiki: How to Use the Editor.

For more information about best practices and scans, see Run Best Practices Analyzer Scans and Manage Scan Results.

Operating System

Windows Server 2012

Product/Feature

Hyper-V

Severity

Category

Note: The following sections provide details about the specific issue. Italics indicates UI text that appears in the Best Practices Analyzer tool for the specific issue.

Issue

Virtual machines participating in replication can be configured to use a specific IP address in the event of failover, but only if integration services are installed in the guest operating system of the virtual machine.

Impact

In the event of a failover (planned, unplanned, or test), the Replica virtual machine will come online using the same IP address as the primary virtual machine. This configuration might cause connectivity issues. This impacts the following virtual machines: <list of virtual machines>

Resolution

Use Virtual Machine Connection to install integration services in the virtual machine.

Additional references

 

Sort by: Published Date | Most Recent | Most Useful
Comments
  • I don't see this article having a table as its tag indicates

Page 1 of 1 (1 items)