Microsoft announced the next version of windows server with new features called Nano Server. Windows Nano Server has provided many benefits i.e Windows Server deployments, it has to run multiple instances on a single host. Windows Server should be totally reworked to smaller, faster, and more secure. Jeffery Snover is a engineer and lead architect for Microsoft Windows server and he stated that Nano Server is a game changer for windows server. The Nano Server is similar to the Windows Server Core mode, but the configuration size of the OS should be smaller and there is no GUI layer, local logon and RDP (Remote Desktop Support). The only way to manage the Nano Server by PowerShell Remoting and WMI, also we can add Windows Server Roles and Features using Features on Demand and DISM (Deployment Image Servicing and Management).
The deployment is different in Nano Server, We need to decide the purpose of Server before we deploy the Nano Server. In Windows Server 2012 R2, the deployment can be done and we need to select the roles and features that are required, but on Nano Server this is not the case. At the time of image creation, the user can select the roles that need to be included in the image. For example, If Hyper-V Deployment, the features of Hyper-V Role and Failover Clustering is selected. Nano Server has provided some benefits in Hyper-V environment.
Nano Server Features are:
Cost Effective:
The resource needed to run the Nano Server VMs on a Hyper-V host should be very small. It will reduce the cost and improve the IT environment. The recommendation of Microsoft, Nano Server can perform 1000 of VMs in 1TB of RAM. Nano Server predicts the dollar spent on hardware, so reason to use the Nano Server in companies is to increase the business continuity.
VHD Size is Small:
Nano Server requires just 400MB to install i.e. It reduces 90 percentage lower VHD Size. The traditional version requires minimum, 6GB of disk space. Also, no need to worry about the application because there is no access of GUI APIs. Storage of Nano Server VMs on a SAN or Hyper-V in local storage should be less amount and mass deployment of VMs compress the install and configuration time. The disk space, considered for the operating system and application is very less amount in Nano Server.
Fewer reboots required:
The Windows Server should be rebooted for the patch and update components, this should be more complex for IT admin. In Nano Server the patches are moved out and it perform 80 percent of fewer reboots. The delays can be possible because of reboots. In Hyper-V hosts there is less interruptions on VMs. The environment should perform with less delay.
Interested in trying Vembu VMBackup? Click here to download:https://www.bdrsuite.com/vembu-bdr-suite-download/
Go questions? Email us at: vembu-support@vembu.com for answers.
Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.
