Updating server 2016 core
As you probably know by now, in Windows Server 2008, the Server Core installation provides a minimal environment for running specific server roles, which reduces the maintenance and management requirements and the attack surface for those server roles (read more about Server Core on my “Understanding Windows Server 2008 Server Core” and “Installing Windows Server 2008 Core” articles).
One of the challenges of using Server Core is the management aspect.
This means the storage pool can survive the outage of a disk and also survive the outage of a server in the storage pool.
This technology is not likely to knock the SAN off of its perch at the pinnacle of our storage hierarchy, but it could be a very useful option for some environments where the cost of continuously adding storage to the SAN is becoming a management and cost nightmare.
This opens up an enormous library of enhancements that can easily be taken advantage of directly from Power Shell.
From a programmability standpoint, classes can now be developed directly in Power Shell much like other object-oriented languages.
It does have an Emergency Management Console from which you can change the IP address of the machine, shutdown, restart and configure Windows Firewall settings.
Hyper-V Containers run in a minimalistic virtual machine to provide even greater levels of isolation, albeit with more resource consumption.
Microsoft has been working with Docker to bring the container management and libraries found in Linux over to Windows.
We have to go all the way back to Windows NT 4.0 to find a Windows Server operating system that used less hardware than Nano.
Last year at Ignite, I saw a demonstration of Nano server running on a stack of tiny devices, each about the size of a deck of cards.