I have seen a lot of sysadmins using Remote desktop to manage their servers, I was even one of them, but with Nano Server you can’t just RDP into it. In this guide I will show you three methods of managing Nano Server. One will be via Powershell, second will be Powershell Direct, and the third will be via Server Manager.
When you first boot up your Nano Server it is not a member of a Domain. Because of this we have to establish a WinRM session to a workgroup computer. To do this, you may need to allow WinRM on the nano server via the Recovery Console. This is only needed if you did not use the -EnableRemoteManagementPort switch when creating your Nano Server. The second Part of allowing the Winrm session is to add the Nano Server to the trusted Hosts List on the server you want to use to manage.
|
1 2 |
# Change IP address to your Nano Servers IP Set-Item wsman:localhost\Client\TrustedHosts -value 192.168.2.17 |
Manage Nano Server via PowerShell.
|
1 2 |
#Change Administrator if needed. Enter-PSSession –ComputerName 192.168.2.17 -Credential Administrator |
From here you can do what you need via Powershell.
Manage Nano Server Via PowerShellDirect
For this method you need to do this from the Hyper-V server that hosts the Nano VM. You also do not need to add the server to the Trusted Hosts List.
|
1 2 |
#Change VMName to your Nano Servers name Enter-PSSession –VMName "PIXEL-NANO01" -Credential Administrator |
From here you can do what you need via Powershell.
Manage Nano Server via Server Manager
Sometimes you just want a GUI. You can easily add your Nano Server to Server Manager you just need to provide the appropriate credentials.
Open Server Manager and add your Nano Server.
Click OK. The refresh will fail. This is to be expected.
Right Click your Nano Server and click Manage As …
Enter your Nano Server’s credentials.
You are now able to use server manager to manage your Nano Server.
Note: You can also use the Azure Server Management Tools to manage your Nano Server. You can just adapt this guide to do that.
[AdSense-A]
0 Comments