locked
Unable to LogOn to Nano Server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I created a nano Server VHD and i am unable to logon to the server. Stuck on please wait when i enter the user name and password.

    I have gone through the steps 5 times, same outcome, nothing on the blogs or forums have helped. 

    Created VHD from Image 10514.0.150808-1529.TH2_RELEASE_SERVER_OEMRET_X64FRE_EN-US downloaded directly from the Microsoft TechNet Evaluation Center 

    Ran command below to create VHD:

    New-NanoServerImage -MediaPath E:\ -BasePath D:\NanoServer\ -TargetPath D:\NanoServerVHD\ -Compute -OEMDrivers -Clustering -ComputerName 1stNano -AdministratorPassword ("P@ssw0rd" | ConvertTo-SecureString -AsPlainText -Force)

    Screenshoot:

    Also Ran command without the password switch;

    New-NanoServerImage -MediaPath E:\ -BasePath D:\NanoServer\ -TargetPath D:\NanoServerVHD\ -Compute -OEMDrivers -Clustering -ComputerName 1stNano

    Screenshot:

    Am I missing something? Any help will be greatly appreciated.

    Wednesday, November 4, 2015 9:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Did you try to enter the computername (1stNano) in the "domain" field?

    To check the keyboard layout, you can also type the password in the username or domain name field just to see if it's correct.

    Thursday, November 5, 2015 8:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    None of the above made a difference.

    Thursday, November 5, 2015 7:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Set the domain name to 'localhost' and see if you can log in?  I can't ever remember the machine name when I'm dual-booting into NanoServer, so I just use 'localhost' and it seems to work.
    Friday, November 6, 2015 9:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Is your VHD on the network? Can you use PowerShell Remoting to connect? There is an issue in Technical Preview 3 (10514) where if there is no networking you can't use the Recovery Console to log on locally. This is fixed in Technical Preview 4 (10586). You can either make sure networking is functional or try building an image using Technical Preview 4.

    Hope that helps,

    Andrew

    Wednesday, November 25, 2015 3:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    This happened to me once.

    I notice you used OEM drivers (designed for host installs)

    I had created the VHD for use as a VM and used OEM drivers instead of guest drivers.

    I couldn't replicate it but when I built the VHD with Guest drivers it always logged in immediately.

    Try that.

    Yours

    Ed

    Please mark this as an answer if you find it useful

    Monday, January 4, 2016 11:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I encountered a seemingly similar problem today.

    Difference is I am doing a Bare Metal install intended as a Hyper-V Host. When I boot, I get presented with

    Domain
    Username
    Password

    But I don't know whether it's because there's no wireless keyboard support, but I can't enter the damn administrator password to get into the recovery console :D

    I checked I was using USB2 not USB3. I have -OEMDrivers in my image. Wonder if anyone else has come across this?

    Next, I'm going to convert the WIM file to VHD and set it up as a VM Guest, just to check the image is sound.

    Sunday, September 18, 2016 10:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It should work with:

    Domain = <computerName>

    Username = Administrator

    Password = <whatever entered>

    In Hannel's case it should be:

    Domain = NanoServerVHD

    Username = Administrator

    Password <whatever entered>

    Sunday, February 26, 2017 3:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Had issues logging into a nano server via console when its IP was wrong when joined to a domain. Noticed if I logged in between about 30-60 seconds it worked. Other than that connecting via PowerShell and correcting the IP setting and rebooting did work. Just my experience with nano.
    Monday, February 27, 2017 10:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    thank you very much!!!
    Thursday, May 23, 2019 3:47 AM