Windows/Hyper-V Server 2012 R2: First Impressions

The release date for Windows Server 2012 R2 (and Windows 8.1) has been set for October 18th, 2013. I got a copy of the previews of both Windows Server and Hyper-V Server, from TechNet. Links for both were included in the rotating banner, but you won’t have much trouble finding them if you look.

There is a lot of material already about the new features in Hyper-V and failover clustering. Rather than write “Me-Too” article #429384 that just rewords what’s already been said, I’ll provide you with a list of my observations and thoughts.

  • The first thing I noticed is that their ISO packages are still putting the string “HYPERCORE” in the name of the image for Hyper-V Server. Dear Microsoft, that’s causing us headaches when we try to explain to people that there’s no such thing as “Hyper-V Core”. Please stop.
  • If you are using the Hewlett-Packard N40L Microserver from our sub-$2000 cluster document, you must disable the onboard adapter to install 2012 R2 Preview. I’m hoping that changes prior to release, but I’m fortunate enough to have plenty of pNICs in my boxes that I was able to live without the onboard. Someday, I might get enterprising and try to see if I can shoehorn a driver in there and get it to work. I am a little disappointed that a bum driver/hardware interface can prevent a modern OS from even booting, but this is a preview so I’ll withhold judgment until RTM.
  • As I was building up my converged fabric and virtual switches, I found that I no longer need to take special steps to configure jumbo frames (sometimes called jumbo packets) on the Hyper-V virtual switch. I just need to enable it for the individual adapters. Thank you Microsoft!
  • I still had to manually disable VMQ on the team adapter, since it didn’t detect that my pNICs don’t support VMQ. However, during preliminary testing, it didn’t seem that leaving VMQ enabled caused my performance to drop like it did on 2012.
  • Unlike a lot of other testers, my hardware isn’t good enough to test RSS. I did turn on SMB for Live Migrations and it worked right away.

    SMB Live Migration

    SMB Live Migration

  • Instead of named, dedicated, and separated Live Migration and Cluster Communications networks, I just have two cluster networks that are allowed for both traffic types. SMB multichannel automatically puts them to good use. Live Migration can also use multiple paths now, so I’m getting true link aggregation for both SMB and Live Migration all the time with no special effort on my part.

    Unified LM and Cluster Networks

    Unified LM and Cluster Networks

  • The Start button is back. I didn’t miss it that much, really, but I am getting use out of the right-click option to Shut Down. It’s really disappointing that “Disconnect” is there but “Log off” isn’t. It’s tough enough to get admins to do the right thing. It’s worse when the wrong thing is so much easier to do. Logging off is still a click at the bottom left and a jump up to the top right to click your name, and then “Sign off”.

    Shutdown on Start Button

    Shutdown on Start Button

  • The Start Menu is still gone, unfortunately. But, instead of making you click all the way at the bottom-left of the screen, right-clicking, and then traveling all the way to the right of the screen to click the “All Apps” button, there’s now a white down arrow that appears immediately to let you get to the other applications on your system.

    All Apps Button

    All Apps Button

  • Remember way back when it was “My Computer”? And then when it just became “Computer”? Now it’s “This PC”. I can’t think of any useful reason for this. Maybe they think that users won’t know it isn’t an XBox or a phone unless they’re told. Maybe Microsoft gets a kick out of making all of us technical writers say things like “right-click ‘My Computer’ or ‘Computer’ or ‘This PC’ or whatever you have this week” so that we spend more words covering all the bases than providing useful content.
  • The new resolution options for guest console connections provided by Enhanced Session Mode is very nice. It will be especially helpful on my laptop. It would be much more helpful if it worked with guests other than 2012 R2.

    VMC Options

    VMC Options

  • You can now use Copy-VMFile to copy files from the host to the guest. It’s a bit awkward to use but could be a real time saver. On the Integration Services tab of the virtual machine’s settings, you have to enable Guest Services.

    Guest Services

    Guest Services

  • Copy/paste of items between the guest and the console through the Virtual Machine Console only works if 2012 R2 is the guest.
  • I Live Migrated all my high availability VMs to node 2 and watched the SMB multichannel Live Migration do its magic. Then I rebooted node 2 and watched as it automatically Live Migrated all of the virtual machines right back prior to shutting down. I’m not sure why anyone would want to, but I haven’t found any way to shut this feature off.
  • After node 2 came back up, I logged on to my non-highly available virtual machines. They wanted to know why they had not been gracefully shut down. The feature that ignores my automatic shut down actions and just cuts off my VMs is one I’d like to disable. I may have neglected to upgrade Integration Components in those particular VMs, but still. Surely that portion hasn’t changed dramatically since 2012?
  • Everywhere I can find in the GUI, the word “snapshot” has been replaced with “checkpoint”. I would still prefer to keep the “snapshot” terminology, but there it is.
  • When I reboot node 2, I have about a 50/50 chance of it coming online in a stable condition. On the bad boots, you can’t connect to it and its VMs struggle to perform on the network. Node 1 doesn’t seem to have any troubles. Also, RDP sessions into it are flaky. The command line has some fairly severe artifacting.
  • The BIOS tab for Gen2 virtual machines is completely gone. It’s been replaced with a Firmwaretab. It allows you to enable secure boot. The option for NumLock on or off at boot is gone, but it appears to automatically turn on NumLock.

    Hyper-V R2 Firmware Tab

    Hyper-V R2 Firmware Tab

  • I was able to use the tools to expand a VHDX on the SCSI chain of a virtual machine. Online expansion doesn’t work for VHDX files on the virtual IDE controller, but I’m fairly certain that’s a limitation of the IDE specification and not Hyper-V.

Overall, there is nothing really surprising or difficult about R2. If you’ve been using 2012, you should be able to slip right into it without any headaches.

8/28/2013 additional note: The New-VMSwitch documentation still says that the default bandwidth reservation mode (QoS) is Weight. It is still wrong, just as it was in 2012. The default mode is Absolute. This can’t be changed after the switch is created, so if you care about QoS then pay attention in your creation scripts.

What are YOUR first impressions of 2012 R2?

Leave a comment below!


Altaro Hyper-V Backup
Share this post

Not a DOJO Member yet?

Join thousands of other IT pros and receive a weekly roundup email with the latest content & updates!

13 thoughts on "Windows/Hyper-V Server 2012 R2: First Impressions"

  • Rob Marshall says:


    In your post you mentioned “I still had to manually disable VMQ on the team adapter, since it didn’t detect that my pNICs don’t support VMQ. However, during preliminary testing, it didn’t seem that leaving VMQ enabled caused my performance to drop like it did on 2012.”

    How were you able to determine that there were performance issues in 2012 when VMQ was enabled?

    • Eric Siron says:

      Mine exhibited stuttering behavior. Communications would work in bursts, then pause, then burst, etc.
      I don’t know if that’s normative for what everyone encountered. There are a lot of permutations to configure teaming and virtual switches. I do recall multiple threads on the TechNet forums where people complained of various problems and disabling VMQ fixed it for them. As I recall, most people were just using Task Manager and watching the Mbps ticker on a file copy.

  • tom miller says:

    Hi Eric,
    Follow your post all the time. Based upon your networking post on my Hyper-V 2012 Servers I load the OS then run the powershell script which basically sets up all the networking, management, Live Mig, HB, iSCSI. Works great.

    Something has changed in R2? I’m running Hyper-V 2012 R2 with the same scripts and for some reason I can not ping out from my hyper-v host and of course can not ping in. Can’t figure it out.

    I even reloaded hyper-V 2012 and ran the same scripts and they work fine, but not on R2? Potentially may be related to “-allowmanagementos” but like I said the script works fine with Hyper-V 2012. Struggling to figure out what changed in R2.

    Thanks, Tom

    • Eric Siron says:

      I don’t know of anything that changed that would cause that sort of behavior. I didn’t rebuild my R2 systems from script, but I didn’t do anything that I wouldn’t have done on 2012.
      The only thing -AllowManagementOs does is immediately create a virtual adapter on the switch. It doesn’t do anything else at all.
      I would tear down all switches and teams and see if you can get a straight physical adapter to communicate with the network. My thought process is to make sure it likes your physical cards before trying to stack layers of other stuff on them.

  • tom miller says:

    Behavior has changed related to teaming, creating vmswitch, and allowmangementos 1. When I do this the managment IP address dies. As soon as I remove the vmswitxh the mgt IP works again. This is definately different from hyper-v 2012.

  • Marjan says:

    in the post, you can change the resolution “VMC Options”, but how to get this console.
    thank you

    • Eric Siron says:

      It opens automatically when you connect to a guest running Windows Server 2012 R2. Earlier operating systems do not support this feature.

  • tom miller says:

    I’m convinced there is a bug with teams, management IP, and creating a vmswitch with the option of allowmanagementos 1. My team had 3 NICs, created a vmswitch on the team and stated to allowmanagementos 1. Drops management IP. Workaround for the moment is to remove 1 NIC from the team and use that for management – of course I have no failover with just 1 NIC for mgt. DID NOT have this issue with Hyper-V 2012, same servers, same NICs.

    Also 2012 R2 still has the VLAN bug; Please see this article:
    Took me a while to figure this out – thanks to the blogger.

    • Eric Siron says:

      It’s entirely possible that there’s a bug. I never set the allow option so I wouldn’t come across it myself.
      I’ve never run into that VLAN bug either, at least not that I know of. If I create a virtual adapter and it doesn’t honor my VLAN setting, I Live Migrate the guest to another node and it almost always starts working immediately. I’ve never had it not work in the management OS.
      Would you mind reporting this on the TechNet forums? That way we can get some more eyes on it and maybe figure out what’s going on?

  • Andy Wendel says:


    i tried to install Altaro-Fre-Edition on my N40L ( onboard Nic disabled ) – but i get the error:

    An error occured while querying…” – so my vms aren´t found…

    Any Tips?

    Thanks in advance!


Leave a comment or ask a question

Your email address will not be published. Required fields are marked *

Your email address will not be published.

Notify me of follow-up replies via email

Yes, I would like to receive new blog posts by email

What is the color of grass?

Please note: If you’re not already a member on the Dojo Forums you will create a new account and receive an activation email.