How To Install Integration Services in Hyper-V

If you take the tech writing industry a little too seriously, you’d be led to believe that everyone is always right at the forefront of technology, deploying new operating systems as soon as they hit the shelves and discarding old environments before they can get more than one version behind.

The reason for that is simple. Most tech writers fit one of three categories:

1. First is the professional full-time writer, who mostly gets to write about the newest, hottest things.
2. Second is the trainer, who mostly gets called to teach about the newest, hottest things.
3. The third is the reseller/implementer/sales engineer that gets called to demonstrate and sell the newest, hottest things.

Guys like me are the exception. We’re the ones that pass our 9-5s in much the same way that you do: dreamily reading all about the newest, hottest things on one monitor while feverishly remoted into some ailing, archaic system on the other.

Part of our reality is that we have to maintain older guest operating systems on our hypervisors. One of the many issues that come along with that is the maintenance of Hyper-V’s Integration Services.

Beginning with Windows 7 and Windows Server 2008 R2, the Integration Services are built-in. Unlike most other natively present operating system components, they are never updated by Windows Update or any other standard patch management system. Instead, versioning is handled by the host. Sort of. As a great many of those previously mentioned tech writers are anxious to point out, Microsoft is planning to shift this behavior so that the Integration Services are delivered via Windows Update.

What they’re not as quick to point out is that Microsoft almost never backports any built-in operating system technology, so this new feature will likely be exclusively available to Windows 10 and Windows Server 2016 and later as both host and guests. If you adhere to the mythos created by the tech writing industry, then you’ll immediately chuck all of your 2012 R2 and lower operating systems and never have to deal with what I’m about to tell you. Even if you want to do that, you’re not going to be able to, so reading on is still worth your time.

Updating Integration Services

Fortunately, updating Integration Services is a very simple process using VMConnect.exe. This tool is most easily accessed using Hyper-V Manager.

1. Open Hyper-V Manager and select the owning host in the left pane.
2. In the center pane, right-click the virtual machine to update and click Connect.
   

   Connect to the Virtual Machine

    

3. This will open the VMConnect.exe application, which functions like a console connection to the virtual machine.
   

   VM Console

    

4. It’s not strictly necessary to log in first, but doing so allows you to take advantage of Autoplay. Press [CTRL]+[ALT]+[End] to send an emulated [CTRL]+[ALT]+[Del] to the guest. It’s also the top item under the Action menu, pictured in the next screen shot.
5. When logged in, insert the Integration Services disk by selecting Insert Integration Services Setup Disk in the Action menu:
   

   Insert Integration Services Disk

    

6. What happens next depends on your logged in status and if autoplay is enabled.
   1. If you are logged in and autoplay is enabled, you will see the following screenshot. Click Install Hyper-V Integration Services.
      

      Integration Services Autoplay

       

   2. If you weren’t logged in when the disk was inserted or if autoplay is disabled, use Windows Explorer or an elevated command prompt in the guest and navigate to D:supportx86. From there, run setup.exe.
      

      Integration Services setup.exe

       

7. For operating systems that already have components either integrated or previously installed, you’ll be prompted to replace them. Click OK.
   

   Integration Services Upgrade Prompt

    

8. You’ll be shown a progress bar with the text indicating which step it is on:
   

   Integration Services Update Progress

    

9. Finally, you’ll be asked to reboot the guest. Once the guest finishes booting, the update process will be complete.
   

   Integration Services Restart Prompt

    

10. The Integration Services disk image will be left in the guest’s virtual drive. To remove it, click the Media menu item in the VMConnect console. Then hover over DVD Drive and click Eject vmguest.iso on the sub-menu that appears.
    

    Eject Integration Services Disk

Detecting Outdated Integration Services

If your guest operating system is older than your host, then it’s guaranteed to have outdated Integration Services. A patch of the host may cause the image to be updated so that even guests with a current OS are out of date. There are three quick ways to know.

Detecting Outdated Integration Services Using Hyper-V Manager

Hyper-V Manager is one of the fastest ways to know if a virtual machine’s Integration Services are out of date.

1. Open Hyper-V Manager. In the left pane, click the host that owns the virtual machine to check.
2. In the center pane, check the bottom division that contains information about the guest. Look for the Integration Services heading.
   

   Hyper-V Manager Integration Services Report

    

Be aware that Linux guests will not report a status.

Detecting Outdated Integration Services Using Event Viewer

Event Viewer contains a number of Hyper-V-related subtrees. You can use two of them to detect out-of-date Integration Services. Start by opening Event Viewer on the virtual machine’s host.

Event Viewer’s Hyper-V-Integration Subtree

Navigate to Applications and Services Logs -> Microsoft -> Windows -> Hyper-V-Integration -> Admin. If you see event IDs 4000 and/or 4010, they’ll tell you precisely which service on which virtual machine is outdated.

4000 is an error condition; the Integration Service indicated in the Source field will not work at all until the Integration Services are updated:

Integration Services Event Id 4000

4010 is a warning condition; the Integration Service indicated in the Source field might work, but might not have complete functionality until the Integration Services are updated:

Integration Services Event ID 4010

Event Viewer’s Hyper-V-Worker Subtree

Navigate to Applications and Services Logs -> Microsoft -> Windows -> Hyper-V-Worker -> Admin. If you see event ID 23014, this will indicate that one of the drivers in the guest operating system is out of date:

Integration Services Event Id 23014

Event Viewer’s System Log

A few entries will bubble up all the way to the main system log. Event ID 27 from source Hyper-V-VmSwitch is a message about the guest’s network driver and looks much like event ID 23014 pictured above. It is not logged under the Hyper-V-VmSwitch branch, however. Event ID 6 from source storvsp is about the guest’s storage driver. It also looks similar to 23014 and is also not found in the Hyper-V-specific logs.

Detecting Outdated Integration Services Using PowerShell

PowerShell is likely the quickest way to detect the status of multiple virtual machine’s simultaneously. The basic structure is like this:

Get-VM | select VMName, IntegrationServicesState

That will produce output like the following:

PowerShell: Checking Integration Service Update Status

It’s a bit to type, but the output is clear. Any VM not reporting a status is not turned on or is running Linux.

Integration Services Installation Notes

• This post is intended to be a tutorial, not a deep dive into the Integration Services. For more information about what they are and what they provide, you can consult our previous article series.
• The vmguest.iso image exists in C:WindowsSystem32 on every host running Hyper-V. It is regenerated automatically at boot from the files in C:Windowsvmguest.
• If you will performing a physical-to-virtual (P2V) conversion, you can use the files from either location in the previous bullet point before making the conversion. This might ease some transition issues. The same is true for virtual-to-virtual conversions from a non-Microsoft hypervisor. Remember to remove any integration services from other hypervisors first!
• For ordinary operations, leaving a disk in a virtual DVD drive isn’t harmful. Because vmguest.iso is mounted from the host’s C: drive, it can prevent clustered virtual machines from being Live Migrated. Ensure that you remove the disk after updating Integration Services.
• Do not install Integration Services for a different level of the hypervisor than the guest will be used with. It can lead to broken components and erratic behavior.
• Once installed, the Integration Services update can be removed, although it may not be obvious which it is. On Windows Server 2008 R2, you can set the Programs and Features applet to View installed updates and look for KB955484.