8–Windows Server 2016
Nano Server
Nano Server
Introduction
Windows Server 2016 offers Nano Server as a new installation option. Nano
Server is a remotely administered server operating system optimized for private clouds and data centers. It is similar to Windows Server in Server Core mode, but significantly smaller, has no local logon capability, and only supports 64-bit applications, tools, and agents. The Nano Server takes less disk space, sets up faster, and requires fewer updates and restarts than Windows Server. When it does restart, it restarts much faster.
Table 8-1 shows the roles and features that are available in this release of Nano
Server, along with the Windows PowerShell options that will install the packages for them. Some packages are installed directly with their own Windows
PowerShell options (such as -Compute). Others are installed as extensions to the -Packages option, which you can combine in a comma-separated list.
Table 8-1. Roles and Features of Nano Server
Role or Feature Options
Hyper-V role
Failover Clustering
Hyper-V guest drivers for hosting
Nano Server as a virtual machine
Basic drivers for a variety of network adapters and storage controllers. This is the same set of drivers included in a Server Core installation of Windows Server
2016 Technical Preview.
-Compute
-Clustering
-GuestDrivers
-OEMDrivers
File Server role and other storage components
Windows Defender Antimalware, including a default signature file
Reverse forwarders for application compatibility, for example common application frameworks such as Ruby, Node.js, etc.
-ReverseForwarders
DNS Server Role
Desired State Configuration
(DSC)
Internet Information Server (IIS)
-Storage
-Defender
-Packages Microsoft-NanoServer-DNS-Package
-Packages Microsoft-NanoServer-DSC-Package
-Packages Microsoft-NanoServer-IIS-Package
108 BC0154501-00 F
8–Windows Server 2016
Nano Server
Table 8-1. Roles and Features of Nano Server (Continued)
Role or Feature
Host Support for Windows Containers
System Center Virtual Machine
Manager Agent
-Containers
Options
-Packages Microsoft-Windows-Server-SCVMM-
Package
-Packages Microsoft-Windows-Server-SCVMM-
Compute-Package
Note: Use this package only if you are monitoring Hyper-V. If you install this package, do not use the -Compute option for the Hyper-V role; instead use the -Packages option to install -Packages Microsoft-NanoServer-
Compute-Package, Microsoft-Windows-Server-
SCVMM-Compute-Package.
-Packages Microsoft-NanoServer-NPDS-Package
Network Performance Diagnostics Service (NPDS)
Data Center Bridging
-Packages Microsoft-NanoServer-DCB-Package
The next sections will describe how to configure a Nano Server image with the packages you will need, and how to add additional device drivers specific to
QLogic devices. It will also explain how to use Nano Server Recovery Console, how to manage Nano Server remotely, and how to run Ntttcp traffic from Nano
Server.
Deploying Nano Server on a Physical Server
Use the following procedure to create a Nano Server virtual hard disk (VHD) that will run on a physical server using the pre-installed device drivers:
1.
Download Windows Server 2016 OS image.
2.
Mount the ISO.
3.
Copy the following files from the NanoServer folder to a folder on your hard drive:
NanoServerImageGenerator.psm1
Convert-WindowsImage.ps1
4.
Start Windows PowerShell as an administrator.
5.
Change directory to the folder where you pasted the files from Step 3.
109 BC0154501-00 F
8–Windows Server 2016
Nano Server
6.
Import the NanoServerImageGenerator script by entering the following command:
Import-Module .\NanoServerImageGenerator.psm1 -Verbose
7.
Enter the following power shell command to create a VHD that sets a computer name and includes the OEM drivers and Hyper-V:
NOTE
This command will prompt you for an administrator password for the new VHD.
New-NanoServerImage –DeploymentType Host –Edition
<Standard/Datacenter> -MediaPath <path to root of media> -BasePath
.\Base -TargetPath .\NanoServerPhysical\NanoServer.vhd -ComputerName
<computer name> –Compute -Storage -Cluster -OEMDrivers –Compute
-DriversPath “<Path to Qlogic Driver sets>”
For Example:
New-NanoServerImage –DeploymentType Host –Edition Datacenter
-MediaPath C:\tmp\TP4_iso\Bld_10586_iso
-BasePath ".\Base" -TargetPath
"C:\Nano\PhysicalSystem\Nano_phy_vhd.vhd" -ComputerName
"Nano-server1" –Compute -Storage -Cluster -OEMDrivers -DriversPath
“C:\Nano\Drivers"
In the example above, C:\Nano\Drivers is the path for QLogic drivers.
This command takes about 10-15 minutes to create a VHD file. A sample output for this command is displayed below:
Windows(R) Image to Virtual Hard Disk Converter for Windows(R) 10
Copyright (C) Microsoft Corporation. All rights reserved.
Version 10.0.14300.1000.amd64fre.rs1_release_svc.160324-1723
INFO : Looking for the requested Windows image in the WIM file
INFO : Image 1 selected (ServerDatacenterNano)...
INFO : Creating sparse disk...
INFO : Mounting VHD...
INFO : Initializing disk...
INFO : Creating single partition...
INFO : Formatting windows volume...
INFO : Windows path (I:) has been assigned.
INFO : System volume location: I:
INFO : Applying image to VHD. This could take a while...
110 BC0154501-00 F
8–Windows Server 2016
Nano Server
INFO : Image was applied successfully.
INFO : Making image bootable...
INFO : Fixing the Device ID in the BCD store on VHD...
INFO : Drive is bootable. Cleaning up...
INFO : Dismounting VHD...
INFO : Closing Windows image...
INFO : Done.
Done. The log is at:
C:\Users\ADMINI~1\AppData\Local\Temp\2\NanoServerImageGenerator.log
8.
Login as an administrator on the physical server where you want to run the
Nano Server VHD.
9.
Complete the following procedure to copy the VHD to the physical server and configure it to boot from the new VHD: i.
j.
Go to Computer Management > Storage > Disk Management.
Right-click on Disk Management and select Attach VHD.
k.
Provide the VHD file path.
l.
Click OK.
m.
Run bcdboot d:\windows.
NOTE
In this example, the VHD is attached under D:\.
n.
Right-click on Disk Management and select Detach VHD.
10. Reboot the physical server into the Nano Server VHD.
11.
Login to the Recovery Console using the administrator and password you supplied while running the script in Step 7.
12. Obtain the IP address of the Nano Server computer.
13. Use Windows PowerShell remoting (or other remote management) tool to connect and remotely manage the server.
111 BC0154501-00 F
8–Windows Server 2016
Nano Server
Deploying Nano Server in a Virtual Machine
Use the following procedure to create a Nano Server virtual hard drive (VHD) that will run in a virtual machine:
1.
Download the Windows Server 2016 OS image.
2.
Go to the NanoServer folder from the downloaded file from Step 1.
3.
Copy the following files from the NanoServer folder to a folder on your hard drive:
NanoServerImageGenerator.psm1
Convert-WindowsImage.ps1
4.
Start Windows PowerShell as an administrator.
5.
Change directory to the folder where you pasted the files from Step 3.
6.
Import the NanoServerImageGenerator script by entering the following command:
Import-Module .\NanoServerImageGenerator.psm1 -Verbose
7.
Enter the following power shell command to create a VHD that sets a computer name and includes the Hyper-V guest drivers:
NOTE
This command will prompt you for an administrator password for the new VHD.
New-NanoServerImage –DeploymentType Guest –Edition
<Standard/Datacenter> -MediaPath <path to root of media> -BasePath
.\Base -TargetPath .\NanoServerPhysical\NanoServer.vhd -ComputerName
<computer name> –GuestDrivers
For Example:
New-NanoServerImage –DeploymentType Guest –Edition Datacenter
-MediaPath C:\tmp\TP4_iso\Bld_10586_iso
-BasePath .\Base -TargetPath .\Nano1\VM_NanoServer.vhd -ComputerName
Nano-VM1 –GuestDrivers
This command takes about 10-15 minutes to create a VHD file. A sample output for this command is displayed below:
PS C:\Nano> New-NanoServerImage –DeploymentType Guest –Edition
Datacenter -MediaPath
C:\tmp\TP4_iso\Bld_10586_iso -BasePath .\Base -TargetPath
.\Nano1\VM_NanoServer.vhd -ComputerName Nano-VM1 –GuestDrivers cmdlet New-NanoServerImage at command pipeline position 1
112 BC0154501-00 F
8–Windows Server 2016
Nano Server
Supply values for the following parameters:
Windows(R) Image to Virtual Hard Disk Converter for Windows(R) 10
Copyright (C) Microsoft Corporation. All rights reserved.
Version 10.0.14300. 1000.amd64fre.rs1_release_svc.160324-1723
INFO : Looking for the requested Windows image in the WIM file
INFO : Image 1 selected (ServerTuva)...
INFO : Creating sparse disk...
INFO : Attaching VHD...
INFO : Initializing disk...
INFO : Creating single partition...
INFO : Formatting windows volume...
INFO : Windows path (G:) has been assigned.
INFO : System volume location: G:
INFO : Applying image to VHD. This could take a while...
INFO : Image was applied successfully.
INFO : Making image bootable...
INFO : Fixing the Device ID in the BCD store on VHD...
INFO : Drive is bootable. Cleaning up...
INFO : Closing VHD...
INFO : Deleting pre-existing VHD : Base.vhd...
INFO : Closing Windows image...
INFO : Done.
Done. The log is at:
C:\Users\ADMINI~1\AppData\Local\Temp\2\NanoServerImageGenerator.log
8.
Create a new virtual machine in Hyper-V Manager, and use the VHD created in Step 7.
9.
Boot the virtual machine.
10. Connect to the virtual machine in Hyper-V Manager.
11.
Login to the Recovery Console using the administrator and password you supplied while running the script in Step 7.
12. Obtain the IP address of the Nano Server computer.
13. Use Windows PowerShell remoting (or other remote management) tool to connect and remotely manage the server.
113 BC0154501-00 F
8–Windows Server 2016
Nano Server
Managing Nano Server Remotely
There are a variety of options for managing Nano Server remotely, including
Windows PowerShell, Windows Management Instrumentation (WMI), Windows
Remote Management, and Emergency Management Services (EMS). This section will discuss how to access Nano Server using Windows PowerShell remoting.
Managing Nano Server with Windows PowerShell Remoting
Use the following procedure to manage Nano Server with Windows PowerShell remoting:
1.
Add the IP address of the Nano Server to your management computer’s list of trusted hosts.
NOTE
Use the recovery console to find the server IP address.
2.
Add the account you are using to the Nano Server’s administrators.
3.
Enable CredSSP if applicable. (optional)
Adding the Nano Server to List of Trusted Hosts
Enter the following command at an elevated Windows PowerShell prompt to add the Nano Server to the list of trusted hosts:
Set-Item WSMan:\localhost\Client\TrustedHosts "<IP
address of Nano Server>"
The following are examples:
Example 1:
Set-Item WSMan:\localhost\Client\TrustedHosts "172.28.41.152"
Example 2:
Set-Item WSMan:\localhost\Client\TrustedHosts "*"
NOTE
This command sets all host server as a trusted host.
114 BC0154501-00 F
8–Windows Server 2016
Nano Server
Starting the Remote Windows PowerShell Session
Enter the following commands at an elevated local Windows PowerShell session to start the remote Windows PowerShell session:
$ip = “<IP address of Nano Server>”
$user = “$ip\Administrator”
Enter-PSSession -ComputerName $ip -Credential $user
You can now run Windows PowerShell commands on the Nano Server as normal.
However, not all Windows PowerShell commands are available in this release of
Nano Server. To see which are available, run Get-Command -CommandType
Cmdlet. To stop the remote session with the command Exit-PSSession.
For more details on Nano Server refer to: https://technet.microsoft.com/en-us/library/mt126167.aspx
Managing QLogic Adapters on Windows Nano Server
To manage QLogic adapters in a Nano Server environments, refer to the Windows
QCC GUI / Windows QCS CLI Management Tools and associated documentation on driverdownloads.qlogic.com
.
RoCE Configuration
In this example, the Nano Server is managed through PowerShell Remoting feature.
1.
Connect to the Nano Server through PowerShell Remoting from another machine as shown below.
PS C:\Windows\system32> $1p=”172.28.41.152”
PS C:\Windows\system32> $user=”172.28.41.152\Administrator”
PS C:\Windows\system32> Enter-PSSession -ComputerName $ip
-Credential $user
NOTE
The IP of the Nano Server is 172.28.41.152 in this example.
Administrator is the User Name.
115 BC0154501-00 F
8–Windows Server 2016
Nano Server
You will get the following if the Nano Server connects successfully:
[172.28.41.152]: PS C:\Users\Administrator\Documents>
2.
Enter the following PowerShell command to check if the drivers are installed and the link is up:
[172.28.41.152]: PS C:\Users\Administrator\Documents>
Get-NetAdapter
3.
Enter the following PowerShell command to check if RDMA is enabled on the adapter:
[172.28.41.152]: PS C:\Users\Administrator\Documents>
Get-NetAdapterRdma
4.
Enter the following PowerShell command to assign IP address and VLAN ID to all the interfaces of adapter:
[172.28.41.152]: PS C:\> Set-NetAdapterAdvancedProperty
-InterfaceAlias “slot 1 port 1” -RegistryKeyword vlanid
-RegistryValue 5
[172.28.41.152]: PS C:\> netsh interface ip set address name=”SLOT 1 Port 1” static 192.168.10.10 255.255.255.0
5.
Enter the following PowerShell command to create SMBShare on the Nano
Server:
[172.28.41.152]: PS C:\Users\Administrator\Documents>
New-Item -Path c:\ -Type Directory -Name smbshare -Verbose
116 BC0154501-00 F
8–Windows Server 2016
Nano Server
[172.28.41.152]: PS C:\> New-SMBShare -Name “smbshare” -Path c:\smbshare -FullAccess Everyone
6.
Enter the following PowerShell command to map the SMBShare as Network
Drive in Client Machine:
NOTE
The IP address of an interface on the Nano Server is 192.168.10.10.
PS C:\Windows\system32> net use z: \\192.168.10.10\smbshare
7.
Enter the following PowerShell command to perform Read/Write on
SMBShare, and check RDMA statistics on Nano Sever:
[172.28.41.152]: PS C:\>
(Get-NetAdapterStatistics).RdmaStatistics
117 BC0154501-00 F
9
Troubleshooting
This chapter provides information about the following topics:
Troubleshooting Checklist
Verifying that Current Drivers are Loaded
Testing Network Connectivity
Microsoft Virtualization with Hyper-V
Linux
Miscellaneous
118 BC0154501-00 F
