Netherlands: Software

Introductie Windows Server 2016

Issue link: http://hub-nl.insight.com/i/692748

Contents of this Issue

Navigation

Page 134 of 173

125 C H A P T E R 6 | App Plat Specializing Nano Server Just like Server Core, you can use a subset of what is available via Unattend to specialize a Nano Server image. In an effort to further reduce the deployment time beyond just the smaller footprint, a couple of commonly used unattend settings are available to set offline: Computer name Domain join using Djoin.exe More info For information on how to perform offline domain join using Djoin.exe, see https://technet.microsoft.com/library/offline-domain-join-djoin-step-by-step(v=ws.10).aspx. When you deploy a Nano Server image with these settings configured in the offline section of the unattend file, Nano Server is specialized on first startup. This eliminates the second startup that occurs with Server Core during specialization, further reducing deployment time. Remotely managing Nano Server Nano Server is truly headless—there is no way to sign in locally or to use Remote Desktop to connect remotely. Both of these have dependencies that would require including frequently serviced features, so they are not available in Nano Server. As a result, you must perform all Nano Server management remotely, either via Windows PowerShell, Windows Management Instrumentation (WMI), Windows Remote Shell (WinRS), Emergency Management Services (EMS), or remote GUI tools. Note The options discussed in this section to remotely manage Nano Server are the same mechanisms that you can use to remotely manage Server Core. The only difference in managing Nano Server is that you must do it all remotely. Windows PowerShell Nano Server includes a refactored subset of Windows PowerShell called Core PowerShell, which is based on the CoreCLR. Core PowerShell provides the following: Full Windows PowerShell language compatibility Full Windows PowerShell remoting Most core engine features Support for all cmdlet types, including C#, Windows PowerShell, and CIM Because Nano Server includes Core PowerShell, it is possible to use PowerShell Remoting to manage Nano Server. To do so, you need to be an administrator on the Nano Server machine and add its IP address to the management machine's trusted hosts. To do that, from an elevated Windows PowerShell prompt, run the following command (which, for this example, assumes the Nano Server machine's IP address is 192.168.1.10): PS C:\> Set-Item WSMan:\localhost\Client\TrustedHosts "192.168.1.10" Next, you need to make yourself an administrator on the Nano Server machine by using the following WinRS command (chcp is used to set the code page) from an elevated command prompt: C:\> chcp 65001 C:\> Winrs –r:192.168.1.10 –u:192.168.1.10\Administrator –p:NanoServer net localgroup Administrators /add domain\username

Articles in this issue

Links on this page

Archives of this issue

view archives of Netherlands: Software - Introductie Windows Server 2016