follows:
Windows Server 2016
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2 SP1
Windows Server 2008 SP2
Windows 10
Windows 8.1
Windows 8
Windows 7
Windows Vista SP2
CentOS 5.2 and above
Red Hat Enterprise Linux 5.2 and above
SUSE Linux Enterprise Server 11 SP2 and above
FreeBSD 8.4 and above
Debian 7.0 and above
Ubuntu 12.04 and above
Oracle Linux 6.4 and aboveMost of the Linux distributions have Integration Services built-in. However, the
previously mentioned article documents which ones need the Linux Integration
Services downloaded and installed manually. At the time of this writing, the latest
Linux Integration Services version is 4, and it is available from the following location:
http://www.microsoft.com/en-us/download/details.aspx?id=46842
This large list covers pretty much every operating system that is used in organizations
today. But what if a company has another operating system? If it’s not on this list of
supported operating systems, will it not work? Remember that what Hyper-V provides
in a generation 1 virtual machine is a virtual environment that does not require the
guest operating system to be enlightened. To the guest, it appears that the virtual
hardware being presented is a physical system that includes items such as the IDE
controller and the emulated legacy network adapter. Even in the Windows Server 2016
version of Hyper-V, the processor compatibility for older operating systems (-
CompatibilityForOlderOperatingSystemsEnabled), which was aimed at NT 4 systems,
is still configurable using PowerShell. These nonenlightened systems that do not
understand VMBus will have a higher overhead and see poorer performance because
of the emulated nature of the storage and networking, but most likely they will work.