Tag: Windows Server

Last updated by at .

Install Hyper-V on Windows Server using PowerShell

Install Hyper-V on Windows Server using PowerShell

If you want to install Hyper-V on Windows Server you can use the following PowerShell command to install the Hyper-V role. If you want to run Hyper-V, make sure your server does include the following requirements.

  • 64-bit Processor with Second Level Address Translation (SLAT)
  • CPU support for VM Monitor Mode Extension (VT-c on Intel CPU’s)
  • Processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology
  • Hardware-enforced Data Execution Prevention (DEP) must be available and enabled. Intel: XD bit (execute disable bit) AMD: NX bit (no execute bit)
  • Minimum of 4 GB memory

If you are looking for installing Hyper-V on Windows 10, check the following blog post: Install Hyper-V on Windows 10 using PowerShell

 



Azure Nested Virtualization

How to setup Nested Virtualization in Microsoft Azure

At the Microsoft Build Conference this year, Microsoft announced Nested Virtualization for Azure Virtual Machines, and last week Microsoft announced the availability of these Azure VMs, which support Nested Virtualization. Nested Virtualization basically allows you to run a Hypervisor in side a Virtual Machine running on a Hypervisor, which means you can run Hyper-V within a Hyper-V Virtual Machine or within a Azure Virtual Machine, kind a like Inception for Virtual Machines.

Azure Nested Virtualization

You can use Nested Virtualization since Windows Server 2016 or the same release of Windows 10, for more details on this, check out my blog post: Nested Virtualization in Windows Server 2016 and Windows 10

With the release of the Azure Dv3 and Ev3 VM sizes:

  • D2-64 v3 instances are the latest generation of General Purpose Instances. D2-64 v3 instances are based on the 2.3 GHz Intel XEON ® E5-2673 v4 (Broadwell) processor and can achieve 3.5GHz with Intel Turbo Boost Technology 2.0. D2-64 v3 instances offer the combination of CPU, memory, and local disk for most production workloads.
  • E2-64 v3 instances are the latest generation of Memory Optimized Instances. E2-64 v3 instances are based on the 2.3 GHz Intel XEON ® E5-2673 v4 (Broadwell) processor and can achieve 3.5GHz with Intel Turbo Boost Technology 2.0. E2-64 v3 instances are ideal for memory-intensive enterprise applications.

With the upgrade to new Intel Broadwell processors, Microsoft enabled Nested Virtualization, which will allows a couple of different scenarios, when you create a Virtual Machine running Windows Server 2016.

  • You can run Hyper-V Containers (Windows Containers with additional isolation) inside an Azure VM. With future releases we will also be able to run Linux Containers in Hyper-V Containers running on a Windows Server OS.
  • You can quickly spin up and shut down new demo and test environments, and you only pay when you use them (pas-per-use)

How to Setup Nested Virtualization in Azure

Deploy Azure VM

To setup Nested Virtualization inside an Azure Virtual Machine, you first need to create a new Virtual Machines using one of the new instance sizes like Ev3 or Dv3 and Windows Server 2016.I also recommend to install all the latest Windows Server patches to the system.

Optional: Optimize Azure VM Storage

This step is optional, but if you want to better performance and more storage for your Nested Virtual Machines to run on, this makes sense.

Azure VM Data Disks

In my case I attached 2 additional data disks to the Azure VM. Of course you can choose more or different sizes. Now you can see 2 new data disk inside your Azure Virtual Machine. Do not format them, because we gonna create a new storage spaces pool and a simple virtual disk, so we get the performance form both disks at the same time. In the past this was called disk striping.

Azure VM Storage Spaces

With that you can create a new Storage Spaces Storage Pool and a new Virtual Disk inside the VM using the storage layout “Simple” which basically configures it as striping.

Azure VM Storage Spaces PowerShell

I also formatted the disk and set the drive letter to V:, this will be the volume where I will place my nested virtual machines.

Install Hyper-V inside the Azure VM

Install Hyper-V on Windows Server using PowerShell

The next step would be to install the Hyper-V role in your Azure Virtual Machine. You can use PowerShell to do this since this is a regular Windows Server 2016.This command will install Hyper-V and restart the virtual machine.

Azure VM Hyper-V

After the installation you have Hyper-V installed and enabled inside your Azure Virtual Machine, now you need to configure the networking for the Hyper-V virtual machines. For this we will use NAT networking.

Configure Networking for the Nested Environment

Hyper-V NAT Network inside Azure VM

To allow the nested virtual machine to access the internet, we need to setup Hyper-V networking in the right why. For this we use the Hyper-V internal VM Switch and NAT networking. I described this here: Set up a Hyper-V Virtual Switch using a NAT Network

Create a new Hyper-V Virtual Switch

First create a internal Hyper-V VM Switch

Configure the NAT Gateway IP Address

The Internal Hyper-V VM Switch creates a virtual network adapter on the host (Azure Virtual Machine), this network adapter will be used for the NAT Gateway. Configure the NAT gateway IP Address using New-NetIPAddress cmdlet.

Configure the NAT rule

After that you have finally created your NAT network and you can now use that network to connect your virtual machines and use IP Address from 172.21.21.2-172.21.21.254.

Now you can use these IP Addresses to assign this to the nested virtual machines. You can also setup a DHCP server in one of the nested VMs to assign IP addresses automatically to new VMs.

Optional: Create NAT forwards inside Nested Virtual Machines

To forward specific ports from the Host to the guest VMs you can use the following commands.

This example creates a mapping between port 80 of the host to port 80 of a Virtual Machine with an IP address of 172.21.21.2.

This example creates a mapping between port 82 of the Virtual Machine host to port 80 of a Virtual Machine with an IP address of 172.21.21.3.

Optional: Configure default Virtual Machine path

Since I have created an extra volume for my nested virtual machines, I configure this as the default path for Virtual Machines and Virtual Hard Disks.

Create Nested Virtual Machines inside the Azure VM

Azure Nested Virtualization

Now you can basically start to create Virtual Machines inside the Azure VM. You can for example use an existing VHD/VHDX or create a new VM using an ISO file as you would do on a hardware Hyper-V host.

Some crazy stuff to do

There is a lot more you could do, not all of it makes sense for everyone, but it could help in some cases.

  • Running Azure Stack Development Kit – Yes Microsoft released the Azure Stack Development Kit, you could use a large enough Azure virtual machine and run it in there.
  • Configure Hyper-V Replica and replicate Hyper-V VMs to your Azure VM running Hyper-V.
  • Nested a Nested Virtual Machine in a Azure VM – You could enable nesting on a VM running inside the Azure VM so you could do a VM inside a VM inside a VM. Just follow my blog post to created a nested Virtual Machine: Nested Virtualization in Windows Server 2016 and Windows 10

In my opinion Nested Virtualization is mostly help full if you run Hyper-V Containers, but it also works great, if you want to run some Virtual Machines inside a Azure VM, for example to run a lab or test something.



Linux on Windows 10

Crazy times – You can now run Linux on Windows 10 from the Windows Store

In the past weeks some really crazy things are happening. Think you’re way back in the time of 2003, could you have ever imagined that Microsoft offers you to run Linux on Windows? Well this is exactly what is happening in the past months.

With one of the Windows 10 releases Microsoft added the Windows Subsystem for Linux, which basically allowed you to run a Ubuntu version on your Windows 10 devices. In the past few days and weeks Microsoft now announced that you can now download and install SUSE Enterprise Server, openSUSE Leap and Ubuntu (my guess there will be more to come) from the Windows Store. All you need today is the latest Windows Insider Build 16237 (it also works with a couple of older insider builds), and you will be able to install these versions. For the mainstream, this will be available in the Windows 10 Fall Creators Update arriving in the Fall of 2017. The Windows Subsystem for Linux will also be part in the next Windows Server RS3 release.

Ubuntu Windows 10 Store

If you want to know more about how it works check out Scott Hanselman blog about Ubuntu now in the Windows Store: Updates to Linux on Windows 10 and Important Tips

One great thing, Scott describes in his blog, if you want to configure the different Windows Subsystems for Linux and for example configure the default one, you can use the command line with the wslconfig utility.

WSLConfig on Windows 10

 



Azure Stack Administration and Operation

Interview: Microsoft Azure Stack – An Introduction

Back at Experts Live Australia 2017 I had the chance to talk to Veeam’s Senior Technical Evangelist Clint Wyckoff about the upcoming Microsoft Azure Stack Solution.

Veeam’s Senior Technical Evangelist Clint Wyckoff and Thomas Maurer, Cloud Architect at itnetX and Microsoft Cloud & Datacenter MVP discuss the upcoming Microsoft Azure Stack Solution.

If you want to know more about Azure Stack: Check out my blog post: Microsoft Azure Stack – Azure Extension in your Datacenter



Microsoft Certified Trainer MCT

MCT Microsoft Certified Trainer

I am proud to announce that I am now a Microsoft Certified Trainer. I got the official certification a couple of months ago, but I didn’t have time to share it yet. A Microsoft Certified Trainer (MCT) is a professional trainer, who has been certified by Microsoft as an expert in terms of professional knowledge and with the ability to properly impart this knowledge to others. MCTs are considered as the premier instructional and technical experts in all Microsoft technologies and they have the sole authority to deliver training for other Microsoft Certifications. It is great to be finally part of this community and I am looking forward to meet other MCTs.

 



Thomas Maurer Speaking

Speaking at Experts Live Europe 2017 in Berlin

I am proud to announce that I will speak at Experts Live Europe 2017 Conference at August 23-25 in Berlin. Experts Live, formerly known System Center Universe, is one of Europe’s largest community conferences with a focus on Microsoft cloud, datacenter and workplace management. Top experts from around the world present discussion panels, ask-the-experts sessions and breakout sessions and cover the latest products, technologies and solutions. It’s the time of the year to learn, network, share and make valuable connections. Experts Live presents top content with top presenters around Microsoft Windows Server, System Center, Microsoft Azure, Office 365, Intune and much more.

ExpertsLive Europe

After speaking at different System Center Universe and different Experts Live events in the past years around the world, such as Bern, Basel, Kuala Lumpur, Ede, Melbourne and many more, I am really happy to speak this year again at one of the greatest community conferences in Europe.

If you want to know more about the events from the past check out my blog posts:

This year I have the chance to speak in a couple of different sessions, about some really cool stuff focusing on Azure Stack, Windows Server vNext and Azure, Docker and Containers.

Azure Stack - Everything you need to know!

Microsoft released Azure Stack as a Azure appliance for your datacenter. Learn how you deploy, manage and operate a Azure Stack in your datacenter. Learn about the features and options you will get by offering Azure Stack to your customers.

Getting started with Windows Containers, Docker and Azure

In Windows Server 2016 you Microsoft released their first version of Windows and Hyper-V Containers. In this session you will get an overview about how containers work and how you can use them for your deployments and you will learn how you can get started with Containers and Docker on Windows 10, Windows Server or on Microsoft Azure.

Windows Server - What is next in Redstone 3

A little less than one year ago Microsoft released Windows Server 2016. This Fall Microsoft will update Windows Server to the next Current Branch for Business release with new features and improvements together with the Windows 10 Client release. Windows Server will also join the Windows Insider Program and we will see the first innovation coming this summer. Join this session for the best of Windows Server. You will get an overview about the new, exciting improvements that are in Windows Server and how they will improve your day-to-day job.

In this presentation Thomas Maurer (Microsoft MVP) will guide you through the highly anticipated innovations including:

Windows Server Containers, Hyper-V features, Nano Server, Storage, Networking, Security, Windows Server Containers and more!

enjoy summer and hopefully see you in Berlin!

 



Windows Server Semi-annual Channel Overview

What is next for Windows Server and System Center with a faster release cadence

A couple of weeks ago at the Microsoft Build Conference, Microsoft released some new information about what is coming in the next version of Windows Server like Linux support on Hyper-V Container and much more. Today Microsoft just announced some new details about the next Windows Server releases and how they will work. The biggest change of todays announcement that Windows Server and System Center will also move to the Semi-annual Channel, just like Windows Client and Office moved to the Semi-annual Channel release cycle. The other large announcement is that Microsoft focuses Nano Server on Container and will remove support Nano on Hosts and Virtual Machines. This means you can run Nano Server only as a Windows or Hyper-V Container.

Nano Server is only supported as a Container Image

Microsoft is removing support for the Nano Server operating system running on physical hardware or inside Virtual Machines. Nano Server will be only supported as a Container Image. Windows Server Core will be the preferred installation option for your infrastructure servers like Hyper-V or Storage Spaces Direct.

This next release will focus on making Nano Server the very best container image possible. From these changes, customers will now see the Nano Server images shrink in size by more than 50 percent, further decreasing startup times and improving container density. As part of this effort to focus on containers, we will be removing the functionality for infrastructure-related roles. Instead of using Nano Server for these scenarios, we recommend deploying the Server Core installation option, which includes all the roles and features you would need.

Windows Server Servicing Channel

As mentioned Microsoft will offer Windows Server updates in the Semi-annual Channel as well as in the Long Term Servicing Channel for Nano Server Container Images as well as Windows Server Core.

There will be two primary release channels available to Windows Server customers, the Long-term Servicing Channel, and the new Semi-annual Channel.

Long-term Servicing Channel

The Long-term Servicing Channel is the release model you’re already familiar with (currently called the “Long-term Servicing Branch”) where a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support, 5 years of extended support, and optionally 6 more years with Premium Assurance. This channel is appropriate for systems that require a longer servicing option and functional stability. Deployments of Windows Server 2016 and earlier versions of Windows Server will not be affected by the new Semi-annual Channel releases. The Long-term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.

Semi-annual Channel

The Semi-annual Channel releases will deliver new functionality for customers who are moving at a “cloud cadence,” such as those on rapid development cycles or hosters keeping up with the latest Hyper-V investments. Windows Server products in the Semi-annual Channel will have new releases available twice a year, in spring and fall. Each release in this channel will be supported for 18 months from the initial release.

Most of the features introduced in the Semi-annual Channel will be rolled up into the next Long-term Servicing Channel release of Windows Server. The editions, functionality, and supporting content might vary from release to release depending on customer feedback.

The Semi-annual Channel will be available to volume-licensed customers with Software Assurance, as well as via the Azure Marketplace or other cloud/hosting service providers and loyalty programs such as MSDN.

Windows Insider Program

At Microsoft Build, Microsoft also announced that Windows Server will be part of the Windows Insider Program, and you will see the first preview builds this summer.

System Center

in the first Semi-annual Channel release from System Center, the team will focus on System Center Operations Manager, Virtual Machine Manager, and Data Protection Manager. The key areas of investment will include support for Windows Server and Linux, enhanced performance, usability and reliability, and extensibility with Azure-based security and management services. Which will bring features like Nested Virtualization support, software load balancing, Storage QoS Self-Service and management support for heterogeneous environments with improved Linux monitoring using a FluentD agent as well as VMware backup. System Center Configuration Manager will continue to offer three releases a year to give you the latest updates for managing servers, PCs, and mobile devices.

Conclusion

This changes will improve the release cadence of datacenter and cloud innovation dramatically. Customers like service providers will have the chance to update their offerings much more often which allows them to add new features and functionality. But there is choice for customers who need a stable and not fast moving environment they can deploy builds from the Long-term servicing channel, which will have long term support. With that you should be able to choose the best solution for your environment and workload.