Tag: Nano Server

Nested Virtualized Windows Server 2016 Hyper-V Cluster LAB – Scenario 2

This Scenario will be lot quicker and we will be using PowerShell since Nano Server is without GUI and it will definitely reflect on footprint and size of cluster.

I recommend you read Nano Server – Deployment since I will be using that procedure for creating script that will automate creation of Nano Servers.

In this scenario we will have 3 VMs and first one same as in Scenario 1 will be VM with our Domain Controler, DHCP, DNS and we will need to setup all those services on that VM(detailed info on this procedure). This time we will also need to install Failover Cluster Manager so we can manage Nano servers since they don’t have any GUI. Second and Third will be our Nano Servers that we will create with script below but before we do it we need to mount Windows Server 2016 ISO  and copy NanoServer folder to our C: drive.

Add Nano Server to Domain

This is procedure how to add Nano Server to domain. Basic idea behind this is to do offline join to domain. Before you venture to adding Nano Server to domain you must set network address and adequate DNS record on your DNS server.

Nano server is a headless server which you cant RDP or not a command prompt. For Nano Server management we have to use PowerShell or RSAT tools. So as a first step is to login to other server which stays in the same network and run the PowerShell and execute the following commands.

First add the server to TrustedHost List

Set-Item WSMan:\localhost\Client\TrustedHosts "192.168.2.95" -Concatenate

Nano Server – Deployment

So, if you are an IT Pro you probably know that with Microsoft Server 2016 comes with something called Nano Server.

In my opinion it is the best of new thing that Server 2016 have. To see what is new in Windows Server 2016 check out this link on TechNet and if you have more time available there are a series of really good Microsoft Virtual Academy resources here.

Over the last few years the Microsoft tried to downsize their Windows Server product and answer on many issues that users had.

The first attempt to resolve these issues was in Server Core released as an installation option in Windows Server 2008. A command line only version of the Server OS that can be managed remotely and to a limited degree from a direct console This ‘server core’ did away with a lot of extraneous ‘stuff’ and meant fewer updates, smaller images and smaller, quicker installations.

But this was not enough and so the Server Product team in Microsoft went back to the drawing board and produced a deployment option now known as Nano server. This cannot be installed from the DVD or ISO, it has to be installed using PowerShell and each individual image built up to only contain the roles and services that are required for that particular server.

Powered by WordPress & Theme by Anders Norén