Skip to main content

List of supported Operating Systems for Hyper-V R2

Supported Server Operating Systems

The following server operating systems are supported on Hyper-V:

  • Windows Server 2008 R2 Standard

  • Windows Server 2008 R2 Enterprise

  • Windows Server 2008 R2 Datacenter

  • Windows Web Server R2 2008

  • Windows Server 2008 Standard x64

  • Windows Server 2008 Enterprise x64

  • Windows Server 2008 Datacenter x64

  • Windows Web Server 2008 x64

  • Windows Server 2008 HPC Edition x64

  • Windows Server 2008 Standard without Hyper-V x64

  • Windows Server 2008 Enterprise without Hyper-V x64

  • Windows Server 2008 Datacenter without Hyper-V x64

  • Windows Server 2008 Standard x86

  • Windows Server 2008 Enterprise x86

  • Windows Server 2008 Datacenter x86

  • Windows Web Server 2008 x86

  • Windows Server 2008 HPC Edition x86

  • Windows Server 2008 Standard without Hyper-V x86

  • Windows Server 2008 Enterprise without Hyper-V x86

  • Windows Server 2008 Datacenter without Hyper-V x86

  • Windows Server 2003 Standard x86 Edition with Service Pack 2

  • Windows Server 2003 Enterprise x86 Edition with Service Pack 2

  • Windows Server 2003 Datacenter x86 Edition with Service Pack 2

  • Windows Server 2003 Web x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Standard x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Enterprise x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Datacenter x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Web x86 Edition with Service Pack 2

  • Windows Server 2003 R2 Standard x64 Edition with Service Pack 2

  • Windows Server 2003 R2 Enterprise x64 Edition with Service Pack 2

  • Windows Server 2003 R2 Datacenter x64 Edition with Service Pack 2

  • Windows Server 2003 Standard x64 Edition with Service Pack 2

  • Windows Server 2003 Enterprise x64 Edition with Service Pack 2

  • Windows Server 2003 Datacenter x64 Edition with Service Pack 2

  • Windows 2000 Server with Service Pack 4

  • Windows 2000 Advanced Server with Service Pack 4

  • SUSE Linux Enterprise Server 10 with Service Pack 1 (x86 Edition or x64 Edition)

  • SUSE Linux Enterprise Server 10 with Service Pack 2 (x86 Edition or x64 Edition)

  • SUSE Linux Enterprise Server 11 (x86 Edition or x64 Edition)

  • Red Hat Enterprise Linux (RHEL) 5.2, 5.3 and 5.4 (x86 Edition or x64 Edition)

Supported Client Operating Systems

The following client operating systems are supported on Hyper-V:

  • Windows 7 Professional x86 Edition

  • Windows 7 Enterprise x86 Edition

  • Windows 7 Ultimate x86 Edition

  • Windows 7 Professional x64 Edition

  • Windows 7 Enterprise x64 Edition

  • Windows 7 Ultimate x64 Edition

  • Windows Vista Business x86 Edition with Service Pack 1

  • Windows Vista Enterprise x86 Edition with Service Pack 1

  • Windows Vista Ultimate x86 Edition with Service Pack 1

  • Windows Vista Business x64 Edition with Service Pack 1

  • Windows Vista Enterprise x64 Edition with Service Pack 1

  • Windows Vista Ultimate x64 Edition with Service Pack 1

  • Windows XP Professional x86 Edition with Service Pack 3 (VMs configured with 1 or 2 virtual processors)

  • Windows XP Professional x86 Edition with Service Pack 2 (VMs configured with 1 virtual processor)

Windows XP Professional x64 with Service Pack 2 (VMs configured with 1 or 2 virtual processors)


http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx


Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...