Hyper-V 2012 integration services version doesn't match

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.


Frederick, MD
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Have you run windows update against the guests yet? As I recall, there are a few updates that are listed as security updates that do impact the integration services version.
Dimarc67Author Commented:
All identified available Windows and Microsoft Updates, including optional updates, have been installed on the guests.  (I should've mentioned that.)
Cliff GaliherCommented:
And the new host node is also up-to-date?  16433 was part of 2770917 so it is odd that your ICs are neither RTM nor as new as they should be. This makes me suspect the newest node had windows update run against it once, but because of precedence, was not updated again (2012 requires about three runs of WU to be fully up-to-date these days.)  Since 2008 R2 would actually ship with a 6.1.x version of IC and not 6.2 at all, this would indicate that someone installed/updated the ICs from a 2012 server, but that server was not as up to date as the others.

I find that whole scenario odd as usually the FCM would fail validation just because the nodes themselves are not of the same version.  The only other thing I can think of is if the older VMs (with the newer ICs) were actually created on another machine and then later migrated to the cluster.  

Regardless, right now, the fact that FCM is actually complaining about a guest to host version mismatch, I'd think that rerunning the IC setup from a known-good node would resolve the issue.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dimarc67Author Commented:

Looks like you were right.  After reconfirming that the vmguest.iso files on our four host nodes were identical in size, I went a step further to actually mount each one and determine the Integrated Services version within--and found that they weren't all the same.

We only recently added the fourth host, and right before that we had to reinstall the OS on one of the original three hosts due to an unrelated hardware issue.  So two hosts have fresh Win2012 OS installs, while two hosts have been running fine for a year.  But, the validation report says they don't have the same MS updates installed as each other--despite some of the "missing" updates absolutely being installed.  And, all four hosts have all available MS updates installed, including optional updates, and all have been restarted and checked multiple times.  If I try to manually install updates that the validation report says are missing, the installer says that the update isn't applicable.

I'm past the Integration Services issue for now.  One of our four nodes (one of the two older hosts) had the later Integrated Services version (6.2.9200.20873), while the other three had the older version (6.2.9200.16433).  I was able to copy the later version vmguest.iso file to the other three nodes, and then successfully updated the three new VMs.

Throwing you the points.  Thanks for your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.