Windows Server 2016 Nano Server – Installation and Management
Posted by Mikhail Rodionov on
February 7, 2017
Time to continue our conversation about that “scaled down even further” Server 2016 installation option. In my previous article, I covered general concepts around Nano Server, now I want to switch gears and talk about more practical aspects: installation and management. At the end of the day, you would agree that the best way to learn new technology it is trying to use it – this way you will be exposed to its strengths and weaknesses directly, and can get the real understanding of whether it works for you or not. Though at this point even Microsoft admits that despite all its greatness, at the moment, Nano Server has quite limited utility as it supports only a small subset of roles and features out of those which you can find in full GUI version of Windows Server.
Nano Server Image Builder tool
Posted by Romain Serre on
November 15, 2016
Nano Server is a new way to deploy Windows Server in your datacenter or in the Cloud. Nano Server is a low footprint operating system which handles what you need and no more. When you create the Nano Server, you choose the role that you want to add to the image (Hyper-V, Storage, containers and so on). Nano Server doesn’t contain Windows Logon, 32-bit legacy or cannot be managed by GPO.
Currently, I don’t really like Nano Server for some jobs as Hyper-V or storage. Nano Server comes with the Current Branch for Business servicing model. So, to be fully supported, your Nano Server has to be upgraded two or three times in a year. You can imagine what happens with hundreds of Hyper-V/Storage nodes? Anyway, Nano Server can run other jobs as IIS and Containers, and in these cases, it could be fine.
In this topic, I’ll show you how to prepare a Nano Server image which will be deployed in a virtual machine. The operating system will be configured to run containers. To create the Nano Server image, I’ll use the Nano Server Image Builder tool which is a graphical interface to prepare the image in VHD, VHDX or WIM file format.
Shared virtual hard disks in Hyper-V 2016
Posted by Oksana Zybinskaya on
August 9, 2016
A new feature called VHD Set for Hyper-V in Windows Server 2016 has been introduced by Microsoft. It allows sharing virtual hard disks between several servers in order to implement guest cluster easily without using complex technologies such as NPIV, virtual HBA, or virtual SAN.
As VHD Set, Shared VHDX enables sharing a virtual hard disk between multiple virtual machines. This feature is useful for implementing a guest cluster where shared disks are required (e.g., SQL Server AlwaysOn/FCI or File Servers).
Deploy an Azure VM from a generalized image in Azure RM portal
Posted by Romain Serre on
August 2, 2016
Microsoft Azure provides a way to deploy Azure VM from the Marketplace or from a generalized image. When you deploy the Azure VM from the Marketplace, no customization is deployed. You have to configure the operating system as your master. When you have several Azure VMs to deploy, the customization of each system can be time consuming. A lot of companies have a master or a baseline image in a VMDK for VMWare, in a VHD(X) for Hyper-V or in a WIM image. In this topic we will see how to create a generalized image from a single Azure VM and how to deploy Azure VM from this generalized image.
In the old portal (https://manage.windowsazure.com), all steps can be done from the GUI but also by using PowerShell. In the new portal (https://portal.azure.com), you have to use PowerShell because it is not yet integrated to the portal. In this topic, I will work from the new portal (AzureRM).