Jul 13

Hyper-V 2016 New Features – Windows Containers (Part 3)

Hyper-V is the Microsoft’s virtualization platform that allows creating virtual infrastructures under Windows and/or Linux (Hyper-V 2016 Overview and Architecture Guide). Virtualization makes it possible to cohabit in isolation several operating systems on the same physical server (Hypervisor). Hyper-V 2016 version has been improved by Microsoft then they released a lot of new features such as network, installation mode, Nano Server, Virtual Machines and Security, administration, Nested Virtualization, QoS for storage, rolling Hyper-V Cluster upgrade, improved ReFS (Resilient File System), and virtual hard disk. Here’s the post to introduce Hyper-V 2016 and Windows Containers.

Original Network - Hyper-v 2016

Windows Server 2016 has the engine of Docker client to benefit from containerization platform. Windows containers provide application isolation, so it possibles to create several applications fully sealed from each other on the same machine. Basically, the concept of containers is completely different from Virtualization. With Virtualization, we can not isolate applications within the same Virtual Machine, however, with the containers, we can have three versions of the same application launched on three different containers on the same machine. This also allows for a fast and scale availability of applications. There are 2 types of containers with Windows Server: Windows Containers, and Hyper-V Containers. Hyper-V Containers offer better application isolation by launching each container in a small Virtual Machine, the isolation is setting up at the hardware level, which allows for an extra level of isolation. Here is the Hyper-V vocabulary associated with the technology of Windows Containers in order to understand this new concept:  


  • Container Host: It is the machine that hosts the containers, it can be physical or virtual;
  • Container Image: This image contains all the changes made from an image with OS Image container;
  • Container OS Image: Windows Server image provided by Microsoft;
  • Container Repository: Container images location on the target server (local);
  • Container Management Technlogy: Containers administration is possible via PowerShell or Docker client.

Global architecture of Windows and Hyper-V containers:

Original Network - HyperV 2016

Original Network - HyperV 2016


Need to be notified of our next Microsoft Community upcoming events or to propose a session, follow us on Twitter: @MUGMonaco and join our Meetup!

Hyper-V 2016 New Features – VMs (Part 2): Guide.

Hyper-V 2016 New Features – Network (Part 1): Guide.

Hyper-V upgrade from Windows 2012 R2 to 2016: Guide.

If you need to disable UAC Server on Windows Server 2016Script Guide.



Leave a Reply