1. Home
  2. Windows Server 2016
  3. Hyper V Server 2012 and later Installation
  1. Home
  2. Hyper V
  3. Hyper V Server 2012 and later Installation
  1. Home
  2. Windows Servers
  3. Windows Server 2012
  4. Hyper V Server 2012 and later Installation

Hyper V Server 2012 and later Installation

This article assumes you already have a core server set up. If not click HERE first


These are the same steps required for setting up any version of Window Hyper V server.

There are essential 2 ways to add a virtual server to a core server. This article will discuss both ways as well as added tips and tricks that I learn on the way.

  • New server install
  • Virtualise an existing system then add it to the server core

NEW SERVER INSTALL

So the first thing to remember regardless of method is to keep this ordered and logical. It is VERY easy to get confused.

This is how I feel a good file format would look:

  • On the Core Server D: Drive using a UNC patch create a  VMDATA folder (This assumes you have a C: drive partition for the core OS and a D: drive partition for the client OS)
  • On new versions of Server Core, you may need to disable the firewall first, and allowing ping functionality (Option 4) before being able to create these folders.

Use the following commands:

  • NetSH ADVFirewall Show Allprofiles will show if firewall is on or off.
    NetSH ADVFirewall Set Allprofiles State ON will switch it on.
    NetSH ADVFirewall Set Allprofiles State OFF will switch it off.


  • Now add 3 folders. ISOImages, VMHardDisks, VMMachines. This only needs doing once on a new Core Server.

  • Use the ISOImages for the various installation files and images
    Use the VMHardDisk folder for where the virtual drives will be stored
    Use the VMMachine folder for where the virtual machine information will be stored

By breaking the drive down into these 3 folders you should be able to keep track of what goes where. It is better to manually create these folders in advance based on what the new server name will be BEFORE creating the server.

  • Keep the VM name and the OS running on it the same to prevent confusion!

You can now use Server Manager on another server to connect and continue the installation.

To add the new server, open up Server Manager, right click All Servers > Add Servers > Add the name of your new server > Find Now > Add Server > OK

This should allow you to manage the server remotely.

Your next step is adding the Hyper V Role if you did not add it during server core OS install:

  • In Server Manager > All Servers, right click the server and select > Add Roles and Features
  • Next > Role-based or feature-based installation > Next > Select Server > Next
  • Tick the Hyper V option > Add Features > Next . Next . Next. Next and eventually Install!
  • Don’t worry about virtual switches or any of the other options yet. This will be set up later

Important!

2 things: Team your network cards and create your virtual switch BEFORE creating the Hyper V Server!

Click HERE for the instructions

So, lets get started by creating a new Virtual Machine

  • Right click Core server > New > Virtual Machine
  • Add name (Keep the same as the VM name) and make sure the location is correct. Remember to browse to the folder you created earlier. KEEP IT LOGICAL!
  • Browse to the folder you created earlier for the virtual machine location. Browsing does not always work properly, so if the image is on the D: drive, type D in the browse bar BEFORE browsing.
  • Select Gen 1 (Best for Server 2008) or Gen 2 (Best for Server 2012) as per the description – I am selecting Gen 2
  • Assign startup memory. Multiply 1024 x the amount to get the correct allocation. (May need to leave processor and memory for the host server)
  • Under networking, select the virtual switch created *
  • Connect virtual hard disk – Because this is a new install select create a virtual hard disk then add size and location. Save it into the folder you created earlier
  • Installation Options > You can now install the OS by selecting an ISO file. Have this saved in your ISOImages folder
  • Browse to the folder and select the image
  • Then finish
    Important!

    Before starting the Server, you need to assign the correct number of processors in Hyper V Manager! Right click new server > Settings


  • You now need to start the Hyper V Server and proceed with the various steps to complete the installation.

You may potentially receive an error if you chose a Gen 2 setup. Initially this puzzled me but the solution is simple. If you reset the server and hit the space button while booting up, you will now get the installer running the mounted ISO image file.

More about the error can be read HERE

Your Setup should now start and run as though it is a standard installation.

  • When setup is complete, log onto the system as per normal. You will now be able to add the various required services and roles
  • You may also want to add a static IP Address

Something important to get your head around is the naming of the various systems.

The server Core install will have a name, then the Virtual Machine will have a name AND the OS running on the Virtual Machine will have a name! This is why it is good to keep this all logical!

Managing the Hyper V server is easiest using Server Manager on another system. Go Server Manager > All Servers, right click then > Add Server. Search for the name and add the server.

VIRTUALISE AN EXISTING SYSTEM

Important!

Ok, so there is an issue I have discovered while trying to do this. It is important information I wish I had known about a week ago.

If you have virtualised a 2008 Server image that has come from a NON UEFI server, the new Server Core has to be NON UEFI.

Modern servers seem to default to a UEFI build which will only allow you to create a new virtual machine from scratch, or import 2012 or later.

I think the issue is that we are using Server 2008 on a Gen 1 build. I think if it were Server 2012 or later the UEFI would not have been an issue.

The steps below will work if you have the correct virtualised system.

 

This article assumes you have already virtualised the server. If not, you can read about how to do it HERE

On the Core Server create a VMDATA folder.

Now add 2 folders. VMHardDisks and VMMachines. This only needs doing once on a new Core Server. You dont need to create the IsoImages folder as we are not using any.

  • Use the VMHardDisk folder for where the virtual drives will be stored
  • Use the VMMachine folder for where the virtual machine information will be stored

Inside VMHardDisk and VMMachine, create a folder called the Server name. Now you can copy the virtualised image you created into the VMHardDisk folder.

Important!

2 things: Team your network cards and create your virtual switch BEFORE creating the Hyper V Server!

Click HERE for the instructions

So, lets import a new Virtual Machine from a pre existing image

  • First, copy the existing image into the VMData > VMHardDisk folder
  • New > Virtual Machine
  • Add name (Keep the same as the VM name) and make sure the location is correct. Remember to browse to the folder you created earlier. KEEP IT LOGICAL!
  • Browse to the folder you created earlier for the virtual machine location
  • Select Gen 1 (Best for Server 2008) or Gen 2 (Best for Server 2012) as per the description – I am selecting Gen 2
  • Assign startup memory. Multiply 1024 x the amount to get the correct allocation. (May need to leave processor and memory for the host server)
  • Under networking, select the virtual switch created *
  • Connect virtual hard disk – Browse to the folder location where you have placed the pre existing image
  • Then finish
    Important!

    Before starting the Server, you need to assign the correct number of processors in Hyper V Manager!


  • You now need to start the Hyper V Server and proceed with the various steps to complete the installation.

Updated on July 27, 2020

Related Articles