Last updated by at .

  • Hyper-V 2016
    What's new in Hyper-V 2016
  • Microsoft Azure
    Microsoft Azure

Tag: Windows

Bash on Windows 10

How to Install Linux Bash on Windows 10

With the Windows 10 Anniversary Update, which was released by Microsoft in Summer 2016, Microsoft included a Windows Subsystem for Linux in Windows 10. This allows you to enable Bash on Windows 10. In this blog post I quickly want to show how you can enable the Windows Subsystem for Linux on Windows 10. This is great if you want to use some Linux tools on your Windows 10 machine. I use it for example to use SSH to connect to Linux Virtual Machines on Azure.

First you have the following requirements:

  • Windows 10 Anniversary Update – Windows 10 Build 14393 and higher
  • 64-bit versions of Windows 10
  • Internet Connection to download the Windows Subsystem for Linux in Windows
  • Active Developer Mode in Windows 10

First enable Developer Mode There are two option you can do this

Open the Settings App, go to Update & Security, go to For developers and enable Developer mode:

Windows 10 - Developer Mode

You can also use the following PowerShell command to enable Developer Mode:

After this you can enable the Windows Subsystem for Linux as a Windows Feature in the Control Panel or PowerShell

Windows 10 - Windows Subsystem for Linux

Run the following PowerShell command to enable the Windows Subsystem for Linux:

Enable Windows Subsystem for Linux using PowerShell

After that you will need to restart your computer.

Now you can open up PowerShell or the command prompt and start using bash. (You can also start Bash directly from the Start Menu)

Bash on Windows 10

Hope this helps you to get started.

 



Microsoft Technical Summit

Speaking at Microsoft Technical Summit 2016 in Darmstadt Germany

After some great events like ITDEV Connections in Las Vegas, E2EVC in Rome and ExpertsLive in Amsterdam, I will also speak at the Microsoft Technical Summit 2016 in Darmstadt, Germany. The Microsoft Technical Summit will be the Microsoft IT event in 2016. This time it will be in Darmstadt from December 6-8. In my session I will speak about the new Nano Server deployment option in Windows Server 2016.

Nano Server - The Future of Windows Server

Nano Server is the future of Windows Server. With Nano Server Microsoft created the foundation for Windows Server for the next years. In this session you will get an overview about Nano Server and see some great live demos how you can deploy, manage and operate Nano Server as well as creating applications for it. Get a better understanding of Nano Server and see how you deploy, manage and operate it.

This will be more the last conference I will be speaking in 2016. I am really looking forward and hopefully see you there.



Hyper-V Nano Server Console

How to deploy Nano Server

Two weeks Microsoft released Windows Server 2016 and with that the first version of Nano Server. Now in this blog post I want to quickly show you how you can deploy Nano Server in Virtual Machines or on Physical Servers. Nano Server is following the zero-footprint model, so know roles and features as well as no drivers are included by default. With this you always have to create a new Nano Server Image and include the physical drivers or the virtual machine drivers and of course the roles and features.

To create new Nano Server Images you have basically two options, you can choose between the Nano Server Image Generator PowerShell module or the Nano Server Image Builder UI tool. With both you can create VHD, VHDX and WIM files which can be used to deploy Nano Server.

Create a Nano Server Image using the Nano Server Image Generator PowerShell module

New-NanoServerImage

This is the built in PowerShell module which can be found on the Windows Server 2016 media in the Nano Server folder.

  • MediaPath – The location with the Windows Server 2016 files
  • BasePath – Temporary folder to mount the WIM file
  • TargetPath – Where the new Image file gets stored. You can create a .wim, .vhd or .vhdx file
    • .vhd creates a Image for a Generation 1 VM (BIOS boot)
    • .vhdx create a Image for a Generation 2 VM (UEFI boot)
  • DeploymentType allows you to choose between Guest and Host
    • Guest creates a Virtual Machine
    • Host creates a Physical Image
  • Edition can be Standard or Datacenter
  • ComputerName adds the server name of the Nano Server
  • MaxSize changes the Partition size, if you are not using this parameter it will create a default partition of 4GB

If you want to know more about the option to Create a Nano Server Image using PowerShell blog post

Create a Nano Server Image using the Nano Server Image Builder

Nano Server Image Builder

The Nano Server Image Builder can help you with the following tasks:

  • Graphical UI to create Nano Server Images
  • Adding drivers
  • Choose Windows Server Edition
  • Adding roles and features
  • Adding drivers
  • Adding updates
  • Configuration of Network Settings
  • Configuration of Domain settings
  • Set Remoting Options
  • Create an ISO file to boot from DVD or BMC (remote connection like HP ILO)

First download and install the Windows Assessment and Deployment Kit (ADK) and the Nano Server Image Builder.

Set more options, choose packages (roles and feature), drivers and more.

Nano Server Packages and Drivers

If you want to know more about this deployment option check out my blog post about How to create a Nano Server Image using the Nano Server Image Builder.



Installation Windows Server 2016 VPN

How to Install VPN on Windows Server 2016

This post shows you how you can install a VPN Server on Windows Server 2016 Step-by-Step. It shows you how you can easily setup a VPN server for a small environment or for a hosted server scenario.

This is definitely not a guide for an enterprise deployment, if you are thinking about a enterprise deployment you should definitely have a look at Direct Access.

I already did similar blog posts for Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.

You can simply follow this step by step guide:

First install the “Remote Access” via Server Manager or Windows PowerShell.

Install Remote Access Role VPN

Select the “DirectAccess and VPN (RAS)” role services and click next.

DirectAccess and VPN (RAS)



diskpart-usb-drive

Create a USB Stick for Windows Server 2016 Installation

If you have download the latest version of Windows Server 2016 you can create a USB stick to install it on a physical server.

For UEFI Systems:

  • The at least a 8GB USB drive has to be formatted in FAT32
  • The USB needs to be GPT and not MBR
  • Copy all files from the ISO to the USB drive

diskpart-usb-drive

This is it, and here is how you do it:

First plugin your USB drive to your computer. The USB drive should be bigger than 6GB.

Open a CMD prompt or PowerShell using the Run as Administrator option and open diskpart. Now you can do list all this by using

Select the USB disk, in my case this was disk 1

Clean the disk. Be careful this will remove all files and partitions on the USB media.

Now convert it to GPT

Create a new primary partition. But make sure the partition is not greater than 16GB otherwise it can be formatted with FAT32.

Format the partition with FAT32

Assign a drive letter to the volume

now you can exit the diskpart and copy all files from the Windows or Windows Server to the USB drive and boot it. This works with Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2012 R2 and Windows Server 2016 or even Hyper-V Server in the same editions.

For MBR systems:

  • The at least a 8GB USB drive has to be formatted in FAT32
  • The USB needs to be MBR
  • Partition need so be set active
  • Copy all files from the ISO to the USB drive

diskpart-usb-drive-mbr

 

This is it, and here is how you do it:

First plugin your USB drive to your computer. The USB drive should be bigger than 6GB.

Open a CMD prompt or PowerShell using the Run as Administrator option and open diskpart. Now you can do list all this by using

Select the USB disk, in my case this was disk 1

Clean the disk. Be careful this will remove all files and partitions on the USB media.

Create a new primary partition. But make sure the partition is not greater than 16GB otherwise it can be formatted with FAT32.

Format the partition with FAT32

Set Active

Assign a drive letter to the volume

now you can exit the diskpart and copy all files from the Windows or Windows Server to the USB drive and boot it. This works with Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2012 R2 and Windows Server 2016 or even Hyper-V Server in the same editions.

 

Important:

If Install.wim is larger than 4GB, you cannot copy the file to the drive, because of theFAT32 based partition limitation. The solutions for this is to split the wim file into smaller files.

split wim file using dism (you may have to change the drive letters):

 



Windows Server 2016 Whats new in Hyper-V

My Hardware Recommendations for Windows Server 2016

Many people are right now asking me about what they have to look out for, if they are going to buy hardware for there next Windows Server 2016 deployment using Hyper-V, Storage nodes or just physical servers. Of course you should normally not just buy hardware and design the solution after that, you should create an architecture for your datacenter first and than buy hardware for your needs. But still there are several things to look out for, this is probably not easy to say right now but here are several thing I would recommend to you.

My recommendations

  • Windows Server Logo: Make really sure that hardware is certified for Windows Server and Windows Server 2016 when the certification is available
  • Network Adapters:
  • Processor / CPU
    • A 64-bit processor with second-level address translation (SLAT).
    • Of course recommend you do get the latest server grade CPUs from Intel or AMD to get the latest CPU functionalities
    • Think about the new licensing for Windows Server 2016 which will be core based
  • TPM Trusted Platform Module v2.0 – especially for the Hyper-V feature Shielded Virtual Machines or/and BitLocker support.
  • Storage
    • If you are going to deploy new Storage in your Datacenter, make sure you have a look at Storage Spaces and SMB Direct (Hyper-V over SMB) and especially the new Storage Spaces Direct feature, which I will write a bit about later this month. This also allows you to do Hyper-Converged scenarios running Storage and Hyper-V on the same physical hardware.

This are just some recommendations if I would buy new hardware I would also look at these features. Of course you don’t need all these features in every scenario, but if you want to make the most out of it, you should definitely look at them. Here are some feature related requirements:

Discrete device assignment

  • The processor must have either Intel’s Extended Page Table (EPT) or AMD’s Nested Page Table (NPT).
  • The chipset must have:
    • Interrupt remapping — Intel’s VT-d with the Interrupt Remapping capability (VT-d2) or any version of AMD I/O Memory Management Unit (I/O MMU).
    • DMA remapping — Intel’s VT-d with Queued Invalidations or any AMD I/O MMU.
    • Access control services (ACS) on PCI Express root ports.
  • The firmware tables must expose the I/O MMU to the Windows hypervisor. Note that this feature might be turned off in the UEFI or BIOS. For instructions, see the hardware documentation or contact your hardware manufacturer.

Shielded Virtual Machines

  • UEFI 2.3.1c — supports secure, measured boot
  • The following two are optional for virtualization-based security in general, but required for the host if you want the protection these features provide:
  • TPM v2.0 — protects platform security assets
  • IOMMU (Intel VT-D) — so the hypervisor can provide direct memory access (DMA) protection

for more detailed specification check out Microsoft TechNet: System requirements for Hyper-V on Windows Server 2016



PowerShell get Drvier Version

Get Installed Driver Version using PowerShell

If you are using Windows Server Core or you just want to check the driver version using PowerShell you can using the following command:

You can also filter a specific driver name using the following command: