Applies to: Windows Server 2016 Technical Preview 3
Legacy guide: This article was originally published in 2015 when Windows Server 2016 Technical Preview 3 introduced an early public look at Windows Server Containers and continued the development of Nano Server. The final Windows Server 2016 release later shipped with Windows container support, while Nano Server evolved significantly in later Windows Server releases.
1. Windows Server Containers
One of the major additions in Windows Server 2016 Technical Preview 3 was Windows Server Containers. Containers provide process and namespace isolation so applications can run in separate environments while sharing the host operating system kernel.
At the time, Microsoft was also working with Docker so Windows containers could be created and managed with familiar Docker tooling. Windows Server Containers were Microsoft Windows technology rather than a Linux-based Docker feature.
Hyper-V Containers were still under development in Technical Preview 3. The technology later shipped in Windows Server 2016 and is now generally described as Hyper-V isolation, where each container runs inside a lightweight virtual machine for stronger isolation.
2. Nano Server
Technical Preview 3 also continued the development of Nano Server, a very small, remotely managed Windows Server deployment option designed to reduce footprint, servicing requirements and attack surface.
Nano Server changed considerably after Windows Server 2016. In current Windows container scenarios, Nano Server is primarily used as a lightweight container base image for modern applications rather than as the general-purpose server installation model described in early Windows Server 2016 previews.
What Happened After Technical Preview 3?
Windows Server Containers and Hyper-V isolation became part of the final Windows Server 2016 container platform. Windows containers continue to be supported in later Windows Server releases, including Windows Server 2019, Windows Server 2022 and Windows Server 2025.
For current information, see the Microsoft documentation:
This article is retained as a historical reference for the Windows Server 2016 Technical Preview 3 period.
Cloud and infrastructure professional with nearly two decades of experience in enterprise IT environments, spanning public cloud, private cloud, and hybrid architectures.