Wednesday 31 August 2016

Hyper-V - Creating VM, Export VM & Import VM - Part 5

Hello Everyone,

In this post, I will show the process the to create Virtual Machine, Export Virtual Machine & Import Virtual Machine step by step.

PART 1: To see Hyper-V Features, Click Here!

PART 2: To see Hyper-V Installation Process & Console Overview, Click Here!

PART 3: To see Hyper-V Network Configuration Concept & Process, Click Here!

PART 4: To see Hyper-V Console Overview & Configuration changes, Click Here!

Let's start in details...

How to Create Virtual Machine:

Open Hyper-V console, Click on New & then click on Virtual Machine in Actions Pane from Right Hand Side:

Give Name & Choose path for deployment (NOTE: If You have already defined VM deployment path in Hyper-V Settings then it will automatically pick the same path):

Choose Generations Type & Click Next: (To know difference between both generations, See Hyper-V Features: Click Here!)

Provide Startup Memory and tick mark to use dynamic memory if You want:


In Hyper-V 2012 R2: 

  • Maximum Memory Limit for Virtual Machine is 1 TB (1024 GB).
  • Support maximum 64 Virtual Processor per VM.

In Hyper-V 2016: 

  • Maximum Memory Limit for Virtual Machine is 16 TB (16384 GB).
  • Support maximum 240 Virtual Processor per VM.

Tag network if You want or You can add later as well, Click Next:

Now, You have to choose Disk: Either Create New Disk for OS or use existing VHD or add it later, give Path and size & click Next:

Select the OS ISO or add it later:

Check Summary & Click Finish:

Once VM is created, Open settings to change  Virtual Processor because by default it is 1:

Change Processor as per Your need and also You can set resource control options:

Once done, start VM to install OS: (OS Installation Process is same so I will not show that)

VM Installation is in process:

Virtual Machine is ready now:

How to Export Virtual Machine:

Either right click on VM & Click Export or Click on Export from Action Pane in right hand side of Hyper-V Console:

Give path and Click on Export:

VM Export status can be seen in Hyper-V Console:

Once export is done then it creates three folders: Snapshot, Virtual Hard Disk & Virtual Machine. If any snapshot was also created then it will export the same as well:

How to Import Virtual Machine:

Click on Import Virtual Machine from Action Pane at right hand side of Hyper-V Console:

Click Next:

Give path for Exported File & Click Next:

Click Next:

Choose Import Type from below & Click Next:

  • Register: If you have a virtual machine in which you have already put all of the virtual machine files exactly where you want them, and you just need Hyper-V to start using the virtual machine where it is then this is the option you want to choose.

  • Restore: If your virtual machine files are stored on a file share / removable drive / etc… and you want Hyper-V to move the files to the appropriate location for you, and then register the virtual machine then this is the option for you.
  • Copy: If you have a set of virtual machine files that you want to import multiple times (e.g. you are using them as a template for new virtual machines) this is what you want to choose.  This will copy the files to an appropriate location, give the virtual machine a new unique ID, and then register the virtual machine.

Check Summary & Click Finish:

NOTE: As I already have VM in my hyper-V so I deleted the same and will import from exported files.

Virtual Machine is Imported & it is in saved state:

Now, You can start the virtual Machine & Use it in different Hyper-V. When You start the Virtual Machine, It will start restoring all configurations:

NOTE: VM Export & Import is used when You need to move Your Virtual Machine from One Server to Another Server which are not in cluster... Also It is used to move Virtual Machine from 1 Cluster to Another Cluster as well... Multiple scenarios are possible...

After VM is restored, It is ready to use:

This is all about VM creation, export & import VM.

Happy Reading!!!

If You like my post then follow my updates:

Join my Facebook group for updates on trending technologies/technical references/issues etc:

Monday 29 August 2016

Hyper-V - Console Overview & Configurations changes which can be done using Hyper-V/VM Settings - Part 4

Hello Everyone,

In this post, I will show console overview with some of the useful tasks which can be performed using Hyper-V. 

There are many features which can be performed via Hyper-V... Some of them I will explain in this post and some of them I will share with separate posts like Hyper-V Replica, VM Export & Import etc.

To see Hyper-V Features, Click Here!

To see Hyper-V Installation Process & Console Overview, Click Here!

To see Hyper-V Network Configuration Concept & Process, Click Here!

Let's start learning features of Hyper-V with console overview...


By default, console of hyper-V looks like below screen:

From one console, You can connect to multiple hyper-v console by clicking on Connect to Server in Action Pane on right side. Only condition is Remote Hyper-V must be connected via network & should resolve name by ping. When You click on connect to server option then It will ask Name or IP of remote hyper-v server to connect:

When You click on Hyper-V Host Name then You have many options which includes: 

  • Virtual Machine Details like Name, Status, etc
  • Tasks Lists which can be performed on Host like create new VM, Create Disk, Edit Disk, Virtual Switch Manager configurations etc.
  • Task Lists on Virtual Machine like Connect, Start or Shutdown, Settings etc.
  • VM Details like Summary, Network Details, Memory Details, Replication status if configured or not.

Let's Discuss with some configurations which can be changed as per requirement in Hyper-V...

Hyper-V Settings:

Click on Hyper-V Settings then You can change below settings:

  • Virtual Hard Disk Path
  • Virtual Machine Path
  • Enable or Disable NUMA Spanning
  • Configure Live Migration settings like number of simultaneous live migrations, which IP should be used for live migration, configuration advance feature for live migration which includes authentication protocols & performance options configurations.
  • Storage Migration configuration 
  • Other options...

Virtual Machine Settings:

This helps in changing Virtual Machine settings which includes:

  • Add Hardware which can be network adaptor, SCSI controller, Fibre channel adapter.
  • Firmware configuration option
  • Memory Configuration
  • Processor Configuration
NOTE: If You are using static memory then You can not change memory while VM is running. If You are running dynamic memory then You can increase memory while VM is running but can not decrease memory while VM is running. This is till Hyper-V 2012 R2. 

Similar for CPU, if You want to increase or decrease, You have to shut down the Virtual machine till Hyper-V 2012 R2.

In Hyper-V 2016, You can increase or decrease memory while VM is running.

CPU cannot be changed while VM is running in Hyper-V 2016. (This I am not sure but I will confirm soon as I am going to start evaluating 2016 from 1st week of September)

  • SCSI Configuration
  • Network Configuration
  • Integration Services configuration
  • Checkpoint file location path can be checked where it will store... By default, it is created on VHD path only.
  • Automatic start/stop actions can be set

Other tasks which can be performed includes:

  • Start/Stop/Save/Delete Virtual Machine
  • Take Checkpoint/Snapshot of Virtual Machine 
  • Revert checkpoint if needed 
  • Enable replication 

These are the basic useful features of Hyper-V...

Now, In future posts, I will start separate series of Hyper-V features in details & step by step process.

Happy Reading!!!

If You like my post then follow my updates:

Join my Facebook group for updates on trending technologies/technical references/issues etc:

Sunday 28 August 2016

Hyper-V - Network Configurations Concept & Process - Part 3

Hello Everyone,

In this post, I will explain the concept & process for configuring Network in Windows Servers & Hyper-V Switch level.

I am not an expert but whatever I will share in this post will be based on my experience & knowledge... For different scenarios, it may also differ but I am sure that this post will definitely clear Your concept for network configurations...

I am not sharing complete network theory here... only concept which will be used for Hyper-V & Virtualisation environment will be shared.

Do share Your queries if any, I will try my best to answer Your queries... :)

To see Hyper-V Features, Click Here!

To see Hyper-V Installation Process & Console Overview, Click Here!

Let's start in details...

Download soft-copy for this post by Clicking Here!


For creating Virtual Environment over Hyper-V Server, Network configuration must be configured in correct way as per Your requirement. If this is not configured correctly before running in production environment and later needs to change or troubleshoot then this may cause down-time & business level impacts... So for creating new environment, You must plan & configure everything in sequence...

Network configuration is major part which must be configured correctly... So, I have created some different scenarios based on my experiences which I am sharing with You all... 

Below are the different concepts which can be used to understand & implement in Your environment...

NOTE: I have assumed 6 physical network adaptor in Physical Server. This may differ in Your environment so You must change concept accordingly... From below concept, You will understand the logic used & process to configure the same.

Concept 1 - Network Configuration without Teaming:

Refer below architecture diagram:


There are 2 Layers defined in this concept:

  • Physical Network Layer: This are the physical adaptors which is visible on physical server (Hyper-V Host) in network connection console.
  • Hyper-V Switch Layer: This is created over physical network layer using Hyper-V Virtual Switch Manager which will be used in virtual servers for communication over network.
As You can see in above diagram, We have 6 physical network with no team... We have 2 NICs as disabled which can be used later for any different purpose in environment...

1 NIC (MGMT1) is used for Management Network where Management IP will be assigned to connect to the server via RDP.

1 NIC (PROD1) is used for Production Network where Production (Virtual Server IP) will be assigned and over which Hyper-V switch is created. That Hyper-V switch is tagged to Virtual Machines which helps in communication between Virtual Machines & Hyper-V Host.

Other 2 NICs are used for Heartbeat IP or Live Migration IP.

Concept 2 - Network Configuration with Teaming using default VLAN ID:

Refer below Architecture Diagram:


In this concept, One additional Layer is added between Physical Network Layer & Hyper-V Switch Layer known as Logical (Team) Network Layer.

As seen in the above diagram, All network adaptors are enabled.

2 NICs (MGMT1 & MGMT2) are teamed together to create new logical network over which MGMT IP is assigned. In this case if any of NIC got disabled or crashed, still network will be connected via another network adapter... This is concept of High Availability on network level from OS End.

Similarly, 2 NICs (PROD1 & PROD2) are teamed together to create new logical network and Hyper-V Switch is created on this teamed logical network where Production IP will be assigned to communicate with virtual servers from Hyper-V Host.

Other 2 NICs are used for Heartbeat IP or Live Migration IP.

Concept 3 - Network Configuration with Teaming for Multiple VLAN ID's:

Refer below architecture diagram:


Mostly used concept in many companies... Reason is because for 1 network segment, there may be multiple VLAN's used in production environment so in that case, how to configure multiple VLAN over 1 logical network is important to know.

As seen in above diagram, There are 4 layers now:
  • Physical Network
  • Logical (Team) Network
  • Logical Interface Layer over Logical (Team) Network
  • Hyper-V Switch 
Concept is similar to above one but one additional layer is added between Logical Network & Hyper-V switch known as Logical Interface Layer.

In this layer, Multiple Interface network with different VLAN ID's are created over 1 Logical (Team) network thereby segregating the 1 network segment into multiple sub-network segments with different VLAN ID's.

Hyper-V Switch is then created for each separate interface switch and tagged to virtual environment accordingly... In more simple term, You can tagged different VLAN ID Switch to different Virtual machine with segregation of IPs. 

Other 2 NICs are used for Heartbeat IP or Live Migration IP.

  • For Live Migration, we can use Production IP as well but due to network traffic, most of the company refer to configure separate network IP for live migration.
  • For Clustering Environment, it is recommended to have similar network configuration on all the clustered nodes. (Will explain in Network Configuration Process steps)


Concept is already explained with help of architecture diagram... This can be differ with environment so this is explained to understand logic...

Now, How to configure network based on requirement is important to know. I have noticed that in configuring many of IT Professionals do mistakes and later either in configuring fail-over cluster or any reason, they face challenges and need to either re-configure or troubleshoot issues...

So, it's better to understand the process and configure the same for all nodes in clustered environment...

Let's start with process...

NOTE: I am explaining this via my lab and I have only 1 server with 1 NIC... Other adaptors are for wifi etc...

Open network connection console using Run Command - ncpa.cpl:

Now, here understand the important thing...

NAME & DEVICE NAME are 2 important thing in configuring network connection on clustered nodes... 

You must sort them with Device Name & then change Name in sequence... See example below.


I have 6 NICs with Name & Device Name as shown below:

As shown in diagram, All NICs are sorted in ascending order & Named in sequence as first 2 NICs for Management & next 2 NICs for Production & Next 2 NICs for Heartbeat & LiveMigration respectively.

For clustering environment, where you need to create cluster with multiple node, network configuration must be similar like if You name each network adaptors with device name as shown in above then this should be configured in same manner on all clustered nodes.

This is the main concept/logic to start configuring network which most of the IT Professionals do wrong configurations and later result in trouble due to any reason.

Once this is done, Now  process comes to configure Team between network adaptors...

How to configure Team between 2 network adaptors:

Open Server Manager, Click on Local Server & Then click on Disabled in-front of NIC Teaming:

A new window will open. I have marked 3 numbers (1, 2 & 3) which are the important points in NIC Teaming:

Number 1 - Teaming: In this, Logical (Team) Network is created by clicking on Task & then New Team.

Number 2 - Adaptors & Interface: In this, You can view network adaptors available with speed & team interfaces details.

Number 3 - Team Interface: In this, You create multiple team interface over the Logical (Team) Network with different VLAN IDs.

In Team Section, Click on Tasks & then Click on New Team:

Here You need to define Team Name, Select Adaptor & configure Advance Properties as per Your need:

NOTE: See Standby Adaptor: This gives You option to configure Team in Active-Passive mode where 1 NIC will be active & 1 NIC will be in passive state... By default both NICs are in active-active state.

Click OK... Team Adaptor is created. Now click on Team Interface by selecting Team Adaptor, then click on Task & then Click on Add Interface:

Here, You can define Interface Name & VLAN ID and Click OK:

This is how You can create multiple VLAN ID Interface on single Logical (Team) Network over which You can created and map separate Hyper-V Switch to each interface.

As I can not create Team in my server so I will now show You how to create Hyper-V switch using physical adaptor only... same process will be used for concept 2 & 3...

How to Create Hyper-V Switch:

Open Hyper-V Console and Click on Virtual Switch Manager:

Now, You will see 3 types of switch:

  • External
  • Internal
  • Private

Click on External & then Click on Create Virtual Switch:

Give Name, Select Network Adaptor, Give VLAN ID if any, Click Apply & OK:

NOTE: When You create teamed logical network & team interfaces then they are listed in drop down with device name so map them accordingly.

Once it is created then You can see the same in Network Connection:

Now, This Hyper-V Switch will be tagged to Virtual Machines for communication over network.

This is all about Network Configuration Concept & Process.

Happy Reading!!!

If You like my post then follow my updates:

Join my Facebook group for updates on trending technologies/technical references/issues etc:

Wednesday 24 August 2016

Hyper- V - Installation Process & Console Overview - Part 2

Hello Everyone,

This post will help You understand the Hyper-V installation process & console overview...

As already explained in my previous post, Hyper-V is a in-built role of Windows Server Operating System which needs to be installed from server manager.

Let's see how to install this role in Windows Server 2012 R2... (Process is same in all versions i.e. it is installed from Server Manager).

To see Hyper-V Features, Click Here!


Open Server Manager & Click on "Add Roles & Features" in Dashboard. A new window will open:

Click Next:

Click Next:

This will display the Server Name & IP Details on which You are going to install roles & features, Click Next:

Select Hyper-V Role & Click Next, Next & Install:

I have already installed so it is showing as Installed... 

How to open Hyper-V Console:

Press Window Key on Keypad, Type Hyper-V on Search option, You will see Hyper-V Manager, Click on It:

Hyper-V Console will open:

This is the only installation process for Hyper-V from Server Manager.

Now, before proceeding to further showcase for features, I will show the concept for network configuration on host level & Hyper-V Switch level in details in next post.

Happy Reading!!!

If You like my post then follow my updates:

Join my Facebook group for updates on trending technologies/technical references/issues etc: