![]() Hack: you can edit/add these parameters and set values manually (of course, it’s unsupported)Įxample of outdated IS in VM with WS2012R2 on WS2016 host (DES provided values from VM, compared them with host’s and they are not the same): If DES has never been enabled on VMs – IS won’t be provided. These values should be existed in VM in order to get IS updates from WU. For such OSes, you need to verify that Data Exchange Service (DES) is turned on and running.ĭES provides shared registry values ( HostSystemOSMajor and HostSystemOSMinor under the hive HKLM\SOFTWARE\Microsoft\Virtual Machine\Guest\Parameters) between host and VMs for determining IS applicability. We have another picture for older OSes ( Windows Server 2012/Windows 8 and older). Hyper-V IS automatically get updates from WU in these OSes. It’s completely true if you have new OS inside VMs ( Windows 2012 R2/Windows 8.1 and later). ISO is not included and it’s not needed anymore. Now VMs get IS updates directly from Windows Update (WU). ![]() The process of Hyper-V IS upgrading has been changed since Windows Server 2016. If your question is not answered, just feel free to leave a comment Where is the integration services setup disk (VmGuest.iso)?Īll of us remember times when we had to insert ISO which was available on Hyper-V host, run it on each VMs and check it’s version from time to time for keeping them up-to-date (yes, vmguest.iso was updated via Windows Update). ![]() I’m frequently receiving questions about what’s wrong with Windows Server 2016 and how to manage Hyper-V IS.
0 Comments
Leave a Reply. |