Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows Server 2016 / Remote Management in Windows Nano Server 2016

November 10, 2017 Windows Server 2016

Remote Management in Windows Nano Server 2016

Unlike common Windows Server 2016 edition, Nano Server hasn’t got any graphical interface or an opportunity to log on locally or  through Remote Desktop (RDP). So by 99.9% Windows Nano Server 2016 is managed remotely using PowerShell or WMI. In this article, we’ll dwell on the most common methods of Nano Server remote management.

Nano Server provides the following management capabilities:

Contents:
  • Nano Server Recovery Console
  • PowerShell Direct
  • PowerShell Remoting
  • Server Manager Console and MMC Snap-Ins
  • Azure Server Management Tools

Nano Server Recovery Console

Nano Server Recovery Console (or Emergency Management Console) is the only way to manage Nano Server from the local console. However, it offers a very limited functionality necessary to configure network parameters or remote connectivity options. In Nano Server Recovery Console you can view or edit IP address settings, routing tables, firewall rules, WinRM. Also, you can restart or turn off your server using this console.

Nano Server Recovery Console

PowerShell Direct

If Nano Server is a virtual machine running on a Hyper-V server, you can use PowerShell Direct to directly connect to the VM via the VMbus from the Hyper-V host server. For example, you can start a PoSh session to Nano Server as follows:

Enter-PSSession -VMName "ws2016nano" -Credential (Get-Credential)

At the same time, the VM running Nano may be located in an isolated network or have no network adapter at all.

PowerShell Remoting

PowerShell Remoting is the main tool to configure and manage Nano Server. It is accessed via WinRM (Windows Remote Management) services running on Nano Server.

To connect to Nano Server, enable WinRM on the side of a local computer:
net start WinRM

Then add the IP address or the name of your Nano Server to the list of trusted WinRM hosts. (You will have to do it, if your Nano Server and the client are not in the same Active Directory domain):

Set-Item WSMan:\localhost\Client\TrustedHosts -Value "192.168.2.17" –Concatenate

Set-Item WSMan:\localhost\Client\TrustedHosts

Note. If you have to allow the remote WinRM connection to any server:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*"

Now you can start a remote session to Nano Server using Enter-PSSession cmdlet. You can specify the name of the user to authenticate on Nano Server directly or via PSCredential object:

Enter-PSSession -ComputerName 192.168.2.17 -Credential Administrator

or

Enter-PSSession -ComputerName 192.168.2.17 -Credential (Get-Credential)

Enter-PSSession

After the session is established, you can run the necessary PowerShell cmdlets to be executed on the remote Nano Server. Please, note that not all cmdlets available in the full edition of Windows Server 2016 are supported in Nano Server environment. Using this command you can view the full list of available commands supported in Nano Server:

Get-Command –CommandType cmdlet

To exit the remote PowerShell session, run:
Exit-PSSession

Server Manager Console and MMC Snap-Ins

Nano Server supports remote management using graphic consoles. These are Server Manager and other specialized MMC consoles that can be used to connect to Nano Server if it has the corresponding role. For example, these are DNS, Cluster Failover Manager, Hyper-V Manager, DHCP, and other consoles.

To do it, it is enough to add Nano Server to Server Manager (All Servers ->Add Server) and provide the credentials.

Available MMC snap-ins to manage roles can be run directly from Server Manager. For example, DNS console.

remote-consoles

Or directly from the necessary snap-in, like classic Computer Management.

Computer-Management-snapin

Azure Server Management Tools

Nano Server supports connection and management directly through the Azure Web Services using Server Management Tools (SMT). This feature is available for most Azure subscriptions and doesn’t need to be paid separately. To manage Nano Server from Azure cloud, you have to deploy a separate on-premises gateway.

Finally, let’s list a few less popular remote server management options. These include: Windows Management Instrumentation (WMI), Virtual Machine Manager (VMM) and System Center Operations Manager (SCOM).

0 comment
1
Facebook Twitter Google + Pinterest
previous post
Getting AD Accounts Created in the Last 24 Hours
next post
The Requested Resource Is in Use: Cluster Disk Error in Windows Server 2012 R2

Related Reading

How to Sign a PowerShell Script (PS1) with...

February 25, 2021

How to Shadow (Remote Control) a User’s RDP...

February 22, 2021

Configuring PowerShell Script Execution Policy

February 18, 2021

Configuring Proxy Settings on Windows Using Group Policy...

February 17, 2021

Updating Group Policy Settings on Windows Domain Computers

February 16, 2021

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • SMB 1.0 Support in Windows Server 2012 R2 / Windows Server 2016
  • User Profile Disks on Windows Server 2012 R2 / 2016 RDS
  • “Downloading updates 0%” Issue on Windows Server 2016 and Windows 10
  • Configure Storage Spaces Direct (S2D) on Windows Server 2016
  • Windows XP Can’t RDP to Windows 10 / Server 2012R2/2016 RDS
  • Create a Bootable USB Flash Drive for Installation Windows Server 2016
  • Activating Windows Server 2016 with KMS Server
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top