Trouble starting Win 10 Virtual Machine with Bastion for first time

JP Win VM 101 Reputation points
2020-06-20T04:32:46.917+00:00

I was able to add the subnet and create the Bastion. When I login to Azure Virtual Machine using Bastion with 10365-oobesttings.jpgUser name and password it times out "OOBESETTINGS" I found a page saying this can be normal the first time. How do I find what I need to update. I still have not been able to access V.M. Windows 10 that was set up. Thx for the help

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,160 questions
Azure Bastion
Azure Bastion
An Azure service that provides private and fully managed Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines.
242 questions
0 comments
Accepted answer
  1. JP Win VM 101 Reputation points
    2020-06-20T17:08:48.4+00:00

    RDP does not connect either. I created a new VM to see if basic settings would get me to connect via RDP and no luck. I guess I am done with this BS.

    Too bad, Microsoft really sells this stuff hard but it is not functional unless you hire an expert to set it up. A real shame since I was able to get AWS Amazon Lightsail up and running in 3hrs. The reason I tried Azure is because my boss has a big issue trusting AWS which is just his politics but is the reason I came here to see IF Azure was a better option.

    Thanks for the help @pituach and @ManuPhilip but unfortunately Azure VM is a bust.

    1 person found this answer helpful.

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. KarishmaTiwari-MSFT 18,527 Reputation points Microsoft Employee
    2020-06-23T05:45:01.47+00:00

    @JPWinVM-9200
    From the discussion above, it looks like you want to connect to Azure Windows VM using Azure Bastion.
    If I am not understanding it correctly, please let us know the end goal and we would work with you to achieve it.

    Please complete the two steps below by following these documents:

    Step 1: Create an Azure windows VM from Azure Portal and try RDP to it : https://learn.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-portal
    Follow this document until Connect to a VM step only.
    Please let me know if you are not able to RDP into the VM as per this step.

    Once you are done with Step 1,
    Step 2: Connect to a Windows virtual machine using Azure Bastion : https://learn.microsoft.com/en-us/azure/bastion/bastion-connect-vm-rdp

    Please let me know if you are stuck at any of the steps above.

    1 person found this answer helpful.
    0 comments
  2. Manu Philip 16,986 Reputation points MVP
    2020-06-20T04:38:00.313+00:00

    Hello,

    As per Microsoft documentation, the error can be resolved by any one of the method as below

    1. Try again
    2. Turn off and turn on again. Power off the VM from azure portal and turn on again

    https://support.microsoft.com/en-us/help/4020048/windows-oobe-fails-when-you-start-a-new-windows-based-computer-for-the

    Please mark as "Accept the answer" if the above steps helps you. Others with similar issues can also follow the solution as per your suggestion

    Regards,

    Manu

  3. Manu Philip 16,986 Reputation points MVP
    2020-06-20T05:13:47.873+00:00

    Hello,

    I have some other way of fixing it as below:

    1. While on the screen where you see OOBESETTINGS error , press Shift+F10 to bring up the command prompt.
    2. Type CD C:\windows\system32\oobe
    3. Type msoobe and hit Enter. You may then be prompted to create an account name and password, and set the time and date. Click Finish when done.
    4. The installation process should then complete and allow the computer to boot into Windows.

    Please mark as "Accept the answer" if the above steps helps you. Others with similar issues can also follow the solution as per your suggestion

    Regards,

    Manu

  4. Ronen Ariely 15,096 Reputation points
    2020-06-20T07:05:00.66+00:00

    Good day @JPWinVM-9200,

    Option 1: You said that this is a new VM which you never connected. The time that you spend to solve the issue is 10 times more then starting from scratch and create new VM. This would probably be my first attempt. You can do it on the same time we try try to solve the issue with the current VM.

    Option 2: Configure RDP temporarily until you connect first time to the machine, and install updates. This simply done by opening the right port in the portal and assuming you have public IP then you can connect from home, otherwise connect from another machine in the same vNet.

    Option 3: Open the Portal -> navigate to the Virtual Machine -> On the left menu you have option "run commend"

    10410-f2.png

    At this interface you can execute some build-in command or any powershell command.

    I am not windows expert and personally pretty much hate win 10, but this way you can bypass the "press Shift+F10 to bring up the command prompt" which @ManuPhilip recommended and you can go straight to execute any command which you need in order to fix the issue

    I hope this solve your needs :-)

    And welcome to the QnA forums