Getting Started with Nano Server 2016
Microsoft has hit it again with windows server 2016, In their new server operating system, Microsoft has felt it has to move to a platform where the cloud will play a big role in the future enterprise software, and introduced Nano Server a new small-footprint option for installing Windows Server 2016. Nano Server pushes the concept of a minimal install that Microsoft has offered in previous versions of Windows Server in the form of Server Core. Unlike Server Core, Nano Server is intended to be a completely headless installation (no local UI and no local console). Also, where the Windows UI can be installed on top of Server Core, Nano Server has no such capability.
- 93 percent lower VHD size
- 92 percent fewer critical bulletins
- 80 percent fewer reboots
To achieve these benefits,We removed the GUI stack, 32 bit support (WOW64), MSI and a number of default Server Core components. There is no local logon or Remote Desktop support. All management is performed remotely via WMI and Power Shell. We are also adding Windows Server Roles and Features using Features on Demand and DISM. We are improving remote manageability via PowerShell with Desired State Configuration as well as remote file transfer, remote script authoring and remote debugging. We are working on a set of new Web-based management tools to replace local inbox management tools. That’s according to Jeffrey Snover, Distinguished Engineer and Lead Architect.
Nano Server supports the DNS Server and IIS server roles, as well as MPIO, VMM, SCOM, DSC push mode, DCB, Windows Server Installer, and the WMI provider for Windows Update. Its Recovery Console supports editing and repairing the network configuration. A Windows Power Shell module is now available to simplify building Nano Server images.
The big news in regards to Nano Server is on the management front. Clearly, as a completely headless version of Windows Server, all management of Nano Server is accomplished remotely. A variety of Microsoft management tools are available to use, including MMC (Microsoft Management Console) Snap-Ins like Hyper-V Manager or Services, Windows PowerShell, Desired State Configuration (DSC), Server Manager, and Microsoft System Center. Microsoft also states that third party management tools, such as Puppet and Chef, will be supported and they are working with chef no ensure that Nano Server works seamlessly in a DevOps continuous deployment and management workflow.
At minimum, Nano Server offers an additional set of tools for IT Pros looking for options when it comes to scalability. We’d really like to see capabilities added to Nano Server, particularly the ability to run core infrastructure roles like DHCP, DNS, and Active Directory. It’s going to be fun to see how Microsoft builds out Nano Server leading up to the Windows Server 2016 release. you can get
You can read more of our blog from here