Introducing the Nano Server Recovery Console


The Recovery Console is a diagnostic shell which runs locally on Nano Server to help you re-establish connectivity to your remote management tools.  By connecting to Nano Server via your KVM solution, you have the ability to view/edit network configuration details, enable/disable network cards and shutdown/reboot the machine to name a few.

Login Screen

image

 

Home Page

image

  • You can view the following details:
    • Computer Name
    • Workgroup / Domain
    • OS version
    • Local machine date/time
    • Time Zone the machine is configured for
    • List of installed network cards
  • Actions you can take:
    • Enter Networking menu
    • Enter Firewall menu
    • Shutdown  the machine
    • Restart the machine

 

Network Settings

image

  • You can view the following details:
    • IPv4 & IPv6 details
    • DNS servers
    • Default gateway
    • Network driver details
    • Routing table details
  • Actions you can take:
    • Enable/Disable the interface
    • Edit the IPv4 & IPv6 details
    • Add network route
    • Switch from DHCP to Static IP

 

Firewall Settings

image

  • You can view the following details:
    • Rules that are configured
  • Actions you can take:
    • Turn a rule on / off

 

What’s Next?

We want to hear from you.   What do you think of the Recovery Console so far? While we are actively adding additional features / functionality to cover those scenarios in which you may need to have local access to Nano server to troubleshoot and re-establish connectivity to your remote management tools, your opinions and ideas influence what we deliver in our next release.

Please take a moment to post a comment and let us know what we should be building next.

Comments (12)

  1. Ken says:

    It would be good to be able to test basic connectivity using ping, and being able to check your DNS settings by doing a test name resolution. Perhaps traceroute as well?
    Something like telnet/netcat so you can test connectivity to a specific TCP port would be nice, but probably overkill for this.

  2. Thank you for taking the time to post your comment. Testing via basic network troubleshooting tools is something we have discussed adding to a future release. Your feedback helps influence when we are able to get that done. Thanks again for letting us
    know what capabilities you would like to see added.

  3. Arie says:

    I noticed the Recovery Console gets locked and only shows a black screen when there is a Direct PSSession to the nano server. If this is by design, then I think it would be helpful if the Recovery Console could show some information about current PSSessions
    to the server when the Recovery Console is in a “locked” state.

    In general I think it would be useful when we could see an overview of all PSSessions to the server and from where those sessions are initiated, being able to close those sessions would be useful to.

    Same goes for processes running on the server. When a process is using up all or most of the resources of the server then most of the time it’s impossible to remotely connect to the server and you have to revert to the console to investigate and kill the problematic
    process(es), in situations like this it would be very helpful if we could get a list of all running processes, showing at least CPU and MEM usage, and have the ability to kill processes.

    On the subject of processes going rogue, would it be useful (or possible even) to have the Recovery Console run with the highest priority (CPU and MEM wise) and always have a certain amount of resources reserved for the Recovery Console so we can still manage
    certain portions of the server when things really get out of control and the server crawls to a halt?

    I also noticed the information shown in the Recovery Console is static and only updates when you to switch from one page to another, making the shown information dynamic would be nice or at least have the ability to refresh the page you’re currently on.

    I really like the idea of nano server and so far it looks promising, but I wonder how to do certain critical tasks when the server is not running in a Hyper-V environment (physical server or if possible other type of hypervisor) and a PSSession for whatever
    reason is not working and a Direct PSSession to the server is not available (correct me if I’m wrong about not being able to use Direct PSSession when nano server is not running in a Hyper-V environment).

    I’m looking forward to future updates to the Recovery Console and nano server in general.

  4. Fabien Dibot says:

    Hello

    It’d be very usefull if we could change the keyboard layout as well as timezone which already exists. NTP configuration (setting/viewing) can be a very good idea too.

    Thanks for this stuff it’s really great so far

  5. Chris J Warwick says:

    Agree with @Fabien’s keyboard language suggestion – especially as passwords include special characters (or should!) which may not be available on the US layout (or in the wrong places – very confusing…)

  6. BladeFireLight says:

    I like the keyboard layout and basic networking tests. Just don’t over complicated the console. Most should be done via a PS Session.

  7. Thanks so much for the great feedback thus far. While I can’t give a specific timeline, I have taken note of the suggestions made so far and will review them with the Nano Server engineering team.

  8. John Riley says:

    How about a domain join command to add or rejoin the machine to Active Directory?

  9. Brian says:

    I don’t see a way to set the DNS in recovery console only edit IP, Sub, Gateway

  10. Joe Coutcher says:

    How about…you know…adding a local PowerShell console? I’m running this on an Intel Compute Stick, and because the wifi drivers aren’t included, the only thing I can do is reboot! How can I add drivers if i can’t get to a prompt?! Although…this is nothing new…Windows IoT has the same issue…no local PowerShell console…ugh…

  11. what is username y pass de nano server del vhd que descarga ?? please help me

  12. Mark says:

    Other than what has already been suggested below Under Networking > NIC > VLAN ID, NIC team/vSwitch/SET management, DNS and domain name Computer name, Date/Time, and possibly Windows Updates

Skip to main content