Installing Microsoft Windows to Online.net’s (www.online.net) Personal Range, specifically XC 2016 and SC 2016, of dedicated server’s is impossible using conventional methods due to the lack of a KVM console with video output, however Windows can still be installed!

We, the volunteers here at WhatUpTime, has built special templates allowing Windows to be installed via Online.net’s rescue system; their rescue system is included with all of their servers.

The guide below will walk you through the entire process, from beginning to end. Once you have reached the end of the guide your server will be successfully running Microsoft Windows Operating System.

Additional assistance is available via our community forums.


Tools You Need



The Guide


  1. Log into your Online.net Control Panel

  2. Once you have logged in, you will need to navigate to your server list (Login –> Server –> Server List)

  3. Choose “Manage” to the right of your dedicated server in the list.



    online-net-manage-page


  4. Choose “Rescue”

    online-net-manage-page-rescue


  5. Choose “Ubuntu 14.04 amd64” from the drop down menu.

    online-net-rescue-page


  6. Choose “Click Here to Launch Rescue System”.

    online-net-click-here-to-launch-rescue-system


  7. Your server is now being restarted and will shortly boot into Online.net’s rescue mode.

    Please allow up to 10 minutes for your server to restart and boot into the rescue mode. In the event you are unable to access your server using SSH (Point #8 below), please open a support request with Online.net via their website to request assistance.


  8. Once you have chosen “Click Here to Launch the Rescue System” Online.net’s control panel will load a new web page which includes all the access information for rescue mode. You will access rescue mode for your server via SSH (Putty is an excellent SSH client); the guide will detail how to connect in the steps below.

    online-net-rescue-information


  9. Now that your server has booted into rescue mode we can connect via SSH using the following steps.

    1. Start Putty

    2. Input your server’s IP address

      putty-input-ip-address


    3. Choose “Open” at the bottom.

      putty-input-choose-open


    4. Once you chose “Open” Putty will transform into a new, all black Window. At the very top left of the window you will find the prompt “Login as:”; here you will need to input the username provided on the system rescue page (See point #8 above) and hit “Enter” on your keyboard.

      putty-black-window


    5. Once you have entered the username you will be prompted for a password, here again you will need to navigate to your system rescue page (See point #8 above) and grab the password provided. You will then need to enter the password at the prompt and choose “Enter” on your keyboard.

      putty-password-1


    6. Once you have entered your username and password you will be successfully logged into the system rescue for your server.

      putty-rescue


  10. At the prompt you will need to enter the following command:
    [simterm]sudo -i[/simterm]
    Once you have typed in the command, choose “Enter” on your keyboard.


  11. You will now be prompted for a password, here again you will need to navigate to your system rescue page (See point #8 above) and grab the password provided. You will then need to enter the password at the prompt and choose “Enter” on your keyboard.

    putty-sudo


  12. You have now successfully connected to the rescue mode for your server and used “sudo” to gain root access allowing for Windows to be installed.

  13. To begin the Windows installation you will need to input the following command into your SSH client. Please ensure the command matches perfectly otherwise your installation will likely fail.

    [donationlocker]

    The Windows template will be downloaded from a WhatUpTime content mirror and installed automatically to your Droplet. The installation may take several hours depending on your Droplet’s connection to the content mirror.


    21-digitalocean-input-wget-windows-installation


  14. Navigate back to the Online.net control panel web page where you located your rescue access information (See point #8 above) and choose “Boot in Normal Mode”.

    Once you have chosen “Boot in Normal Mode” your server will be rebooted and removed from the rescue system. Your server will now begin booting Windows for the first time; please be patient at the initial boot can take quite a lot of time to complete (10+ minutes depending on the CPU of your server).



    online-net-rescue-information-boot-normal


  15. You may now log into your server using Remote Desktop (RDP) using the credentials listed above in step #13.

    In the event you unfamiliar with Windows Remote Desktop it is recommended you review Microsoft’s article here on how to use the remote desktop client built into Windows.

    Alternatively you may wish to use Windows Remote Desktop Connection Manager, you can download it for free here.


  16. Once you have logged into your server via Remote Desktop there are two additional steps you should take immediately to ensure your server is secure.

    1. Change the password for the “Administrator / WhatUpTime.com” account; a guide on how to change a password can be found here.

    2. Install all of the latest updates for Microsoft Windows.

    3. Activate Windows with your license key.

      In the event you do not already own a legitimate Microsoft Windows license key you can purchase a legitimate key from members on Reddit, please visit here.


    4. Installing missing Microsoft Windows drivers using SDI, you can download it for free here.

Congratulations! You have reached the end of the guide and your server is now running Microsoft Windows!

[/donationlocker]

Installing Microsoft Windows onto Online.net Personal Range (XC 2016 & SC 2016)

26 thoughts on “Installing Microsoft Windows onto Online.net Personal Range (XC 2016 & SC 2016)”

  • October 20, 2016 at 7:28 pm
    Permalink

    Credentials don’t work Dedibox XC 2016 – 1TB SATA Amsterdam

    Reply
    • October 20, 2016 at 7:54 pm
      Permalink

      The credentials above are indeed correct, which template did you install specifically from the mirror links above?

      Reply
    • October 21, 2016 at 2:03 am
      Permalink

      Tampoco me funcionaba y cambie el “Administrador” por “Administrator” y funciono perfecto, espero te sirva, saludos!

      Reply
  • October 22, 2016 at 8:22 am
    Permalink

    Excellent How-To.
    My two XC 2016 were ready really fast !
    Thanks thousand million times !!

    Reply
  • October 24, 2016 at 6:03 pm
    Permalink

    Thanks for the great work
    Can you create a 2008 version as well please
    Thanks

    Reply
  • November 3, 2016 at 9:50 am
    Permalink

    Hi,

    any chance you’d be willing to share your unattend.xml file for Win10 ltsb ?

    Reply
    • November 3, 2016 at 11:47 am
      Permalink

      Hello!

      Presently there isn’t one, the templates are created on an alternative system and then setup to copied onto the end user’s server.

      Reply
  • November 3, 2016 at 12:01 pm
    Permalink

    Thanks for your work!

    Reply
  • November 29, 2016 at 10:27 pm
    Permalink

    “Activate Windows with your license key (Server Manager –> Local Server –> Product ID/Not Activated). ”

    I entered the key and it shows “This edition cannot be upgraded”

    Reply
    • November 30, 2017 at 7:12 pm
      Permalink

      In order to convert from Evaluation Mode to Normal, you should use this command line :
      Dism /online /Set-Edition:ServerStandard /AcceptEula /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

      Replace “ServerStandard” by “ServerDatacenter” if you have a datacenter version.

      Reply
  • December 29, 2016 at 4:23 am
    Permalink

    Thank you very much, it helps me a lot!
    By the way what should I do for reinstalling the windows? Just repeat this process?

    Reply
    • December 29, 2016 at 10:14 am
      Permalink

      You’re welcome!

      Correct, to re-install Windows you simply perform the exact same steps.

      Reply
  • December 31, 2016 at 12:45 am
    Permalink

    Can we create a backup and restore it on a different server afterwards? If yes how?

    Thank so much for the Tutorial, it helped out alot.

    Reply
    • December 31, 2016 at 12:53 am
      Permalink

      Yes, in theory it would be possible with a bit knowledge and work.

      Please create a thread in our community forums.

      Reply
  • February 10, 2017 at 12:27 pm
    Permalink

    Hey there,

    please can you make this also for server 2008 r2?

    Would be nice 🙂

    Reply
    • February 10, 2017 at 12:28 pm
      Permalink

      Please create a thread in our community forums requesting it to be added.

      Reply
  • February 15, 2017 at 2:11 pm
    Permalink

    Hi,

    The links for the templates are broken.

    Will you be updating these?

    Thank you

    Reply
    • February 15, 2017 at 2:17 pm
      Permalink

      Yes!

      Please accept my apologies for the inconvenience, we are presently undergoing a small transition which rendered our older mirror links inoperable. You can read more about the transition here.

      Reply
  • March 9, 2017 at 6:45 pm
    Permalink

    Can you be compatible with packet and internap? I found here in packet and internap’s bare metal can not be used normally.

    Reply
    • March 9, 2017 at 6:46 pm
      Permalink

      Unfortunately I cannot say as I do not have access to either provider at this time.

      Please create a thread in the community forums providing as much details as possible and I will see what we can do to expand compatibility.

      Reply
  • November 30, 2017 at 7:17 pm
    Permalink

    30 november 2017 : for everyone, I’ve just used WhatUpTime solution to successfully install a Windows Server 2016 Standard on a Online Dedibox XC SATA 2016.
    No problem with the DHCP, I get directly the access through RDP to my server. Just be carefull, the firewall is set on “enable” so you CAN’T ping the server itself. Just have to try to connect RDP from time to time after reboot. Thank you ihadp \o/

    Reply
  • December 1, 2017 at 8:58 pm
    Permalink

    Just done the same on a Windows Server 2016 Standard on a Online Dedibox XC SSD 2016 (AMS1) with no problem 🙂 Thank anoter time to ihadp for the gain of time.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.