We're running a Windows Server 2012 Hyper-V cluster (not R2) with four host nodes. The cluster is about 18 months old, hosting about 80 VMs (Win2008R2 and Win2012), and the fourth node was added just two weeks ago.
Since adding the fourth host, we've created three VMs, all running Windows Server 2008 R2 SP1. Prior to creating the new VMs, all of our VMs were running Integration Services version 6.2.9200.20873. However, the three new VMs are all showing their Integration Services version as 6.2.9200.16433.
When we attempt to upgrade the Integration Services for the three VMs using the Failover Cluster Manager or Hyper-V Manager consoles, the installer reports that all three are "already running the current version of Integration Services (version 6.2.9200.16433)".
When we run cluster validation in FCM, validation fails due to the three VMs which are listed under "The following virtual machines are running integration services that does not match the host computer. You must update the integration services on the virtual machines or the host computer to the same version."
All four hosts have the identical vmguest.iso file in the System32 folder.
Can anyone point us in the right direction out of this conundrum? We're concerned that we can't pass cluster validation at present.