Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, September 21, 2017 11:12 PM
I recently stood up a pair of Hyper-v hosts running Windows 2016 (core) in a failover cluster. I have migrated some VMs from an older cluster and also created a new Win2012R2 guest from scratch. When I run the Failover Cluster validation wizard the report shows that the integration services aren't up to date. I opened a case with Microsoft and they've been troubleshooting for WEEKS! I wanted to see if anyone else out there is having this behavior.
According to my MS support engineer, the latest integration services version for a Windows 2012 R2 guest is 6.3.9600.18692. However, when I run Windows updates on my Windows 2012 R2 guests, the most recent version it upgrades to is 6.3.9600.18398. And running a powershell command shows "Update required". The only guest that shows "up to date" is my Windows 2016 guest. Thoughts?
All replies (6)
Friday, September 22, 2017 4:06 PM âś…Answered
Might read through this one.
https://rlevchenko.com/2017/02/18/faq-windows-server-2016-and-hyper-v-integration-services/
Another option is to copy vmguest.iso from a patched 2012 R2 host (\Windows\System32\vmguest.iso) Gets recreated at every boot.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
Thursday, September 21, 2017 11:15 PM
You can download here. (note the prerequisites)
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
Friday, September 22, 2017 3:44 PM
Thanks Dave. Both myself and Microsoft support already installed this cab file. I just downloaded the link you supplied and installed again for good measure and the version still shows 6.3.9600.18398. So, let me rephrase my question.
I was wondering if anyone else out there can tell me what their experience is. What version of integration services are your Windows 2012 R2 guests running that are on Windows 2016 hosts? Are your guests on 6.3.9600.18398? And what does your Failover Cluster Validation report show in the section titled "Validate Hyper-V Integration Services Report"?
My report states "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."
Friday, September 22, 2017 4:40 PM
Thanks Dave! I think I read this article a few weeks ago but it all makes so much more sense now that I've been weeks into troubleshooting with MS support. I'm going to forward them this blog and see if they agree on the comment that Integration Services will show "update required" even though it's up to date". I will update here when I get a response. :)
Friday, September 22, 2017 4:41 PM
Sounds good, you're welcome.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows Server] Datacenter Management
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.
Friday, September 22, 2017 10:36 PM
Microsoft support agreed that although I'm seeing the message "Update Required" that we can ignore it because we verified that the version is at the latest. Unfortunately on all the VMs I migrate (except for the Win2016 guest), none of them will update to the latest version via Windows Updates. The MS support had to extract the cab file for the 2017-09 Cumulative update for Windows 2012 R2 and then we used the DISM command:
dism /online /add-package /packagepath:C:\test\expandcab2012R2\update.mum