Nano Server 2018 Update



AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at (hosted at Please bear with us while we are still under construction!

We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either as you do today, or at our new site Please feel free to update your bookmarks accordingly!

Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.

If you have never visited the TechCommunity site, it can be found at On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.

NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at!

As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!


Hello again! Allen Sudbring here, PFE in the central region, bringing you some news on Nano server and an update to the blog post I did back in the Windows Server Technical Preview time frame on configuring and deploying Nano Server, located here (link: This massive blog post covered everything from management to deployment as both a virtual machine on Hyper-V and VMWare and on bare metal hardware.

A lot has changed since my initial post. Windows Server 2016 went GA and we announced a new Semi-Annual Channel branch to Windows Server that saw the first release named Windows Server 1709. With this new version, also comes a major change to Nano Server. Nano Server going forward will no longer be a host operating system available in a virtual machine or on physical hardware.

Nano server will be a container image only for use with Windows Containers and Docker. Containers are a new technology, similar to Virtualization, that containerizes an application for portability and resilience.

We originally announced these changes in a blog post in June, 2017, and have formally announced these changes at the following links:

Changes to Nano Server in Windows Server Semi-Annual Channel

From <>

More info on Windows Containers and Docker:

Windows Containers

From <>

As a result of Nano being optimized for containers, the image that is used is much smaller than the version that shipped with Windows Server 2016, as you can see from the screenshot below:

The 2016 version (Tagged latest) is over 1GB, the 1709 version is 312MB.

I encourage everyone to check out Windows Containers as well as our new guidance on the Semi-Annual Channel for Windows and how this affects Nano Server:

Windows Server Semi-Annual Channel overview

From <>