How To Check If Hyper V Integration Services Is Installed

If you take the tech writing industry a footling too seriously, yous'd be led to believe that anybody is ever right at the forefront of technology, deploying new operating systems every bit soon as they hit the shelves and discarding quondam environments before they can go more than 1 version behind.

The reason for that is uncomplicated. Most tech writers fit 1 of three categories:

Beginning is the professional full-time writer, who mostly gets to write about the newest, hottest things.
2d is the trainer, who mostly gets called to teach nearly the newest, hottest things.
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 ix-5s in much the same way that you lot practice: dreamily reading all about the newest, hottest things on 1 monitor while feverishly remoted into some ailing, primitive organisation on the other.

Part of our reality is that nosotros take to maintain older guest operating systems on our hypervisors. One of the many issues that come up along with that is the maintenance of Hyper-5's Integration Services.

Start with Windows seven and Windows Server 2008 R2, the Integration Services are built-in. Unlike most other natively present operating organisation components, they are never updated by Windows Update or any other standard patch management organisation. Instead, versioning is handled by the host. Sort of. As a dandy 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 equally quick to point out is that Microsoft almost never backports any built-in operating arrangement engineering, and then this new feature will likely be exclusively bachelor to Windows 10 and Windows Server 2022 and after as both host and guests. If you lot adhere to the mythos created by the tech writing manufacture, and so you'll immediately chuck all of your 2022 R2 and lower operating systems and never take to deal with what I'm most to tell y'all. Even if you want to exercise that, you're not going to exist able to, so reading on is all the same worth your time.

Updating Integration Services

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

Open Hyper-5 Director and select the owning host in the left pane.
In the center pane, correct-click the virtual machine to update and click Connect.

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

VM Panel
It'southward not strictly necessary to log in first, but doing so allows you lot to have reward of Autoplay. Press [CTRL]+[ALT]+[End] to send an emulated [CTRL]+[ALT]+[Del] to the guest. Information technology'due south likewise the tiptop item nether the Activity bill of fare, pictured in the next screen shot.
When logged in, insert the Integration Services disk by selecting Insert Integration Services Setup Disk in the Action menu:

Insert Integration Services Deejay
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 post-obit screenshot. Click Install Hyper-V Integration Services.
  
  Integration Services Autoplay
2. If you lot weren't logged in when the disk was inserted or if autoplay is disabled, utilise Windows Explorer or an elevated command prompt in the invitee and navigate to D:supportx86. From there, run setup.exe.
  
  Integration Services setup.exe
For operating systems that already have components either integrated or previously installed, yous'll exist prompted to supercede them. Click OK.

Integration Services Upgrade Prompt
You'll be shown a progress bar with the text indicating which step it is on:

Integration Services Update Progress
Finally, you'll be asked to reboot the guest. One time the invitee finishes booting, the update process will be consummate.

Integration Services Restart Prompt
The Integration Services disk image will be left in the guest's virtual drive. To remove it, click the Media menu detail in the VMConnect console. And so hover over DVD Drive and click Squirt vmguest.iso on the sub-menu that appears.

Squirt Integration Services Disk

Detecting Outdated Integration Services

If your invitee operating system is older than your host, and so it's guaranteed to have outdated Integration Services. A patch of the host may crusade the image to exist updated so that fifty-fifty guests with a current Bone are out of date. There are three quick ways to know.

Detecting Outdated Integration Services Using Hyper-5 Director

Hyper-V Managing director is one of the fastest means to know if a virtual machine's Integration Services are out of engagement.

Open Hyper-V Manager. In the left pane, click the host that owns the virtual auto to check.
In the centre pane, check the bottom division that contains information about the invitee. Look for the Integration Services heading.

Hyper-5 Manager Integration Services Report

Exist aware that Linux guests will non report a status.

Detecting Outdated Integration Services Using Event Viewer

Effect Viewer contains a number of Hyper-V-related subtrees. You tin use two of them to detect out-of-appointment Integration Services. Get-go by opening Upshot Viewer on the virtual machine's host.

Result Viewer's Hyper-V-Integration Subtree

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

4000 is an error condition; the Integration Service indicated in the Source field volition 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

Integration Services Upshot ID 4010

Event Viewer's Hyper-V-Worker Subtree

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

Integration Services Event Id 23014

Integration Services Upshot Id 23014

Outcome Viewer's System Log

A few entries will bubble up all the way to the main system log. Result ID 27 from source Hyper-V-VmSwitch is a bulletin nigh the guest'due south network driver and looks much like consequence ID 23014 pictured higher up. It is not logged under the Hyper-Five-VmSwitch branch, even so. Event ID 6 from source storvsp is about the guest'southward storage driver. Information technology also looks like 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 car's simultaneously. The basic structure is like this:

Go-VM | select VMName, IntegrationServicesState

That will produce output similar the following:

PowerShell: Checking Integration Service Update Status

It'southward a bit to type, only the output is clear. Whatsoever VM not reporting a status is not turned on or is running Linux.

Integration Services Installation Notes

This mail service is intended to be a tutorial, not a deep dive into the Integration Services. For more information nigh what they are and what they provide, yous tin consult our previous commodity serial.
The vmguest.iso image exists in C:WindowsSystem32 on every host running Hyper-V. It is regenerated automatically at kick from the files in C:Windowsvmguest.
If you will performing a concrete-to-virtual (P2V) conversion, y'all can utilise the files from either location in the previous bullet point earlier making the conversion. This might ease some transition issues. The same is true for virtual-to-virtual conversions from a non-Microsoft hypervisor. Recall to remove any integration services from other hypervisors first!
For ordinary operations, leaving a disk in a virtual DVD drive isn't harmful. Considering vmguest.iso is mounted from the host'south C: bulldoze, it can prevent clustered virtual machines from being Live Migrated. Ensure that you lot remove the disk after updating Integration Services.
Practise not install Integration Services for a dissimilar level of the hypervisor than the guest volition be used with. It can atomic number 82 to cleaved components and erratic behavior.
Once installed, the Integration Services update tin can be removed, although it may not be obvious which it is. On Windows Server 2008 R2, you lot tin can set thePrograms and Features applet to View installed updates and look for KB955484.