HyperV 2016 and Integration Services

[mitchell1981]

Has anyone migrated to Hyper-V 2016?

 

Mostly working ok here, but when I run a cluster validation, it is saying that every VM has outdated Integration Services. See screenshot below.

 

Apparently the only way to update Integration Services is though Windows Update, but all these servers are completely up to date. Is it just a bug with the Validation, or am I missing something. If anyone else is on HyperV 2016 and clustered, can you check your validation and see if you get the same? Most of these VMs are Server 2012 R2.

 

Thanks.

 

[Sagima]

Have you updated the configuration version of the VMs to 7 (from 5)

I thought it might encourage it to look for the new integration tools

[FN-GM]

Have you updated the configuration version of the VMs to 7 (from 5)

I thought it might encourage it to look for the new integration tools

 

Its version 8 actually.

 

We have the same issue with one or 2 machines. All are on version 8 here.

[mitchell1981]

It looks like my VMs are on version 8!

[Tallwood_6]

Did you get anywhere with this, we have different integration versions across all the windows servers from 2008 to 2016 now under hyper-v and how the updated integration services are supposed to be delivered seems to be pretty sketchy i.e. windows update via WSUS that needs approval, via the host itself?

[mitchell1981]

Sorry only just saw your question. No, never got anywhere with this. All our servers show out of date Integration services in the cluster report, and all of the servers are completely up to date so don't really know what else to try.

 

Everything I've read online suggests that Windows update is supposed to handle it, but it apparently doesn't.

 

Did you make any further progress?

[Fazza]

With Server 2016 Hyper-V the integration tools are no longer installed via a mounted ISO. They are instead installed via Microsoft/Windows Updates.

[IanT]

integration tools on Server 2016 are now installed via Windows Update

 

https://rlevchenko.com/2017/02/18/faq-windows-server-2016-and-hyper-v-integration-services/

[mitchell1981]

Supposedly but doesn't seem to work when you have 2012 r2 VM on a 2016 Host. The Integration services reports a mismatch as per the screenshot in the first post, even with the host and VM completely up to date. I have noticed that 2016 VMs, on 2016 host do not report the mismatch.

 

I'm not too worried as everything is working fine, but it just seems strange.

[Fazza]

doesn't seem to work when you have 2012 r2 VM on a 2016 Host

 

What configuration version are the 2012R2 VMs? I suspect if they are V5 and not V8 then that may be the issue. Easy to change to V8 but it's a oneway process and V8 configuration VMs will only work on a 2016 Hyper-V Host so once updated to V8 you can't move it or replicate it to a 2012R2 Hyper-V Server.

[mitchell1981]

Sorry, only just spotted this reply. Thanks for suggestion, but no, they are all V8.