2012
11.13

I read on a Windows magazine website today (Monday 12th, November 2012) that the ability to run legacy operating systems, such as Windows NT 4.0 Server or Windows 2000 Server, was removed from Windows Server 2012 Hyper-V.  I would have commented but the publisher wanted me to register.  This feature was removed from the GUI, but it was not removed from Hyper-V.

Note: Neither Windows NT 4.0 Server or Windows 2000 are supported by Microsoft, although you might want to run really old applications in VMs because you can’t get hardware for them.

You can run the following to see the processor compatibility of a particular VM for legacy operating systems using PowerShell (where VM01 is the VM in question):

PS C:> Get-VMProcessor VM01 | fl CompatibilityForOlderOperatingSystemsEnabled

CompatibilityForOlderOperatingSystemsEnabled : True

You used to configure this setting in the processor settings of a VM.  Now you can configure it as follows:

Set-VMProcessor VM01 -CompatibilityForOlderOperatingSystemsEnabled $true

You can turn it off again by running:

Set-VMProcessor VM01 -CompatibilityForOlderOperatingSystemsEnabled $false

Note that enabling this setting requires that the VM be turned off.

This information has been brought to you by Windows Server 2012 Hyper-V Installation and Configuration Guide (available on pre-order on Amazon):

image

4 comments so far

Add Your Comment
  1. Very interesting. I have to migrate 4 x w2k physical servers to vm in hyperv 3. Is it possible¿ Do I have to use integration services from hyperv 2¿

    I suppose I have to create vm with powershell. Can you help me wirh commands?

    I promise I will buy your book :-). Thanks. Regards. Miguel

    • Windows 2000 Server is no longer supported (several years ago). You could continue to use the old integration components, but remember, there is no support for W2K; it is 13 years old and 5 generations old.

  2. This works amazingly well, will definitely come in handy for anyone that’s trying to help an extreme legacy system limp along for a few more years. Thanks for sharing!

  3. Excellent article, thanks very much for sharing as it appears *touch wood* to have solved and issue with one of our Server 2000 VMs that we’re looking to migrate from Hyper V 2008 to 2012.

    After moving the VM across to the new cluster, it would boot up fine and operate well, however as soon as I tried a Live or Quick Migrate the 2000 VM to a different node, it would BSOD with an NTOSKRNEL error as soon as the migration completed.

    I have just applied this setting for processor compatibility and the machine has migrated to a new node without a hiccup, however it appears that I have to wait a bit of time before migrating to a different node as, when I tried to migrate a couple of minutes after the first migration, it gave a BSOD pointing to trying to write to read-only memory.

Get Adobe Flash player