Guide to installing NGINX + PHP-FPM + MariaDB on Debian 7 & 8

This tutorial will guide you through the steps to get nginx, php5-fpm and MariaDB working on your server with Debian 7 or 8 installed. This will run just fine on a 128MB OpenVZ VPS.

Let’s get started by installing nginx. First you’ll need to add the nginx repo to get the latest stable release installed on your server. Follow the simple steps below.

Installing Nginx and adding repository

Login to your server using either PuTTy or your favourite SSH client and use the following commands.

Make sure to get the right keys added or else the install will fail with a key error;

wget http://nginx.org/keys/nginx_signing.key
apt-key add nginx_signing.key

Add the NGINX repository to your sources.list, for debian 7 (Wheezy) change jessie to wheezy;

echo 'deb http://nginx.org/packages/debian/ jessie nginx' /etc/apt/sources.list

Now perform an update and upgrade and install the latest stable version of nginx;

apt-get update apt-get upgrade
apt-get install nginx

Now let’s configure our first website. Go to /etc/nginx/conf.d, remove the default.conf and example_ssl.conf and create a new your-website.conf file using nano (apt-get install nano).

cd /etc/nginx/conf.d
rm default.conf example_ssl.conf
nano your-website.conf

Copy and paste the following configuration file into your-website.conf, make sure to change the your-website.tld to your own domain name you’d like to use. Use CTRL + C to save the file once you’re done in nano;

server {
    listen 80;
    root /var/www/your-website;
    index index.php index.html;
    server_name your-website.tld www.your-website.tld;
    location / {
            try_files $uri $uri/ /index.php;
    }
    location ~ \.php$ {
            try_files $uri =404;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            include fastcgi_params;
            fastcgi_pass unix:/var/run/php5-fpm.sock;
    }
}

If you’d like to have SSL enabled on your website then please use the following configuration file, this will also redirect all non HTTPS/SSL request to HTTPS/SSL. Make sure to have a valid .pem and a .key file in your /etc/ssl directory.

server {
    listen 80;
    root /var/www/your-website;
    index index.php index.html;
    server_name your-website.tld www.your-website.tld;
  return 301 https://$host$request_uri;
    location / {
            try_files $uri $uri/ /index.php;
    }
    location ~ \.php$ {
            try_files $uri =404;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            include fastcgi_params;
            fastcgi_pass unix:/var/lib/php5/php5-fcgi.sock;
    }
}
server {
    listen   443;
    ssl    on;
    ssl_certificate    /etc/ssl/your-website.pem;
    ssl_certificate_key    /etc/ssl/your-website.key;
    root /var/www/your-website;
    index index.php index.html;
    server_name your-website.tld www.your-website.tld;    
    location / {
            try_files $uri $uri/ /index.php;
    }
    location ~ \.php$ {
            try_files $uri =404;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            include fastcgi_params;
            fastcgi_pass unix:/var/lib/php5/php5-fcgi.sock;
    }
}

Now let’s create the /var/www directory and give nginx permissions to the /var/www folder.

chown -R nginx:nginx /var/www

Installing PHP5-FPM

Now, let’s go and install PHP5-FPM and some of the extra PHP5 modules.

apt-get install php5-fpm php5-common php5-sqlite php5-gd php5-mysqld php-pear php5-imap php5-mcrypt php5-curl

Now we’re going to make a few modifications to the php.ini file located at /etc/php5/fpm/php.ini and we’re going to replace the php.ini file with a file optimized for wordpress by me (this will make wordpress load faster).

cd /etc/php5/fpm
rm php.ini
wget --no-check-certificate https://raw.githubusercontent.com/joodle/Hiawatha-MariaDB-PHP5-FPM-SQLBuddy/master/php.ini

Now we’ll need to make a few small changes to our php-fpm.conf configuration file so that nginx will be able to load PHP files. I already have a almost pre-configured php-fpm.conf on github, which will make things a bit easier.

cd /etc/php5/fpm
rm php-fpm.conf
wget --no-check-certificate https://raw.githubusercontent.com/joodle/Hiawatha-MariaDB-PHP5-FPM-SQLBuddy/master/php-fpm.conf

We’re going to change some permission settings in the php-fpm.conf file. Nginx will otherwise complain about not being able to access the php5-fcgi.sock file which is needed to execute php files on the server end.

Open php-fpm.conf in the nano text editor and search for the following;

[www]
user = www-data
group = www-data

And replace it with;

[www]
user = nginx
group = nginx

Save the file using CTRL + C and press Y.

Create a php information file at the /var/www/your-website directory;

echo /var/www/your-website/phpinfo.phpsite/phpinfo.php

Now restart php-fpm and nginx;

systemctl restart php5-fpm.service
systemctl restart nginx.service

Or when you’re using Debian 7;

service php5-fpm restart
service nnginx restart

Navigate to http://your-website.tld/phpinfo.php and if everything went alright you should see a page containing some information about the php version you’ve installed on your server.

Installing MariaDB MySQL Server

First we’ll have to add the MariaDB official repository plus keys.

apt-get install software-properties-common
apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 0xcbcb082a1bb943db
add-apt-repository 'deb http://mirror.i3d.net/pub/mariadb/repo/10.1/debian jessie main'
apt-get update

Let’s install MariaDB;

apt-get install mariadb-server

Make sure to have a strong password for the MariaDB (MySQL) root user. You can generate strong passwords on random.org (https://www.random.org/passwords/).

You can add/create databases using the following commands;

<strong>Login to MySQL</strong>: mysql -u root -p
<strong>Add user</strong>: CREATE USER 'YOUR-OWN-USERNAME'@'localhost' IDENTIFIED BY 'YOUR-OWN-PASSWORD';
<strong>Add database</strong>: CREATE DATABASE DATABASENAME;
<strong>Assign user to database</strong>: GRANT ALL PRIVILEGES ON DATABASENAME . * TO 'YOUR-OWN-USERNAME'@'localhost';
<strong>Delete database</strong>: DROP DATABASE DATABASENAME;
<strong>Delete user</strong>: DROP USER 'YOUR-OWN-USERNAME'@'localhost';
<strong>Flush all privileges</strong>: FLUSH PRIVILEGES;

That’s it! Now you have a server with Nginx + PHP5-FPM + MariaDB installed!

How to install Windows Server 2016 On OVH, Kimsufi or SoYouStart servers

Are you looking to install Windows Server 2016 on your server, and are you renting your server at OVH? That’s awesome! You can install Windows on your server free of charge besides license costs, but that is up to you, we only provide the template.

Please do note: this template might work on other servers at other providers as well (Online.net and Hetzner for example).

This is a 180 days Evaluation template, but you can still use your own license (if you have one).

Follow the steps to install Windows on your server just one simple command.

1. Boot your server in rescue mode.
2. Login with the SSH credentials which should have been sent to your email address (if on OVH).
3. Copy the command in the box below and paste it in the terminal, press enter and wait till it’s fully downloaded and unzipped.

wget -O- 'https://mirror.joodle.nl/WindowsServer2016Evaluation-Template.gz' | gunzip | dd of=/dev/sda

Once fully downloaded and unzipped set your server to boot from the HDD again and wait till the Remote Desktop is accessible.

You can login using these credentials:

Username: Administrator
Password: Password147

Microsoft Windows on DigitalOcean!

You can now run Microsoft Windows on your DigitalOcean Droplet!

I am pleased to share we have completed our initial beta template build for Microsoft Windows Server 2012 R2 Standard Evaluation and confirmed the template is fully operational on DigitialOcean’s 512MB RAM droplet!

We will be building additional templates over the next several days and plan to include Microsoft Windows Server 2012 R2, Microsoft Windows Server 2016 and Microsoft Windows 10.

You may locate all of the beta builds on our DC2 mirror – http://onlinenet-dc2.mirror.whatuptime.com/

More to come!

Installing Microsoft Windows onto DigitalOcean Droplet

Installing Microsoft Windows Operating System to DigitalOcean’s Droplet is impossible using conventional methods due to the inability to mount an installation ISO and lack of a KVM providing a virtual keyboard (ie. Send Ctrl + Alt + Del, etc.).

We, the volunteers here at WhatUpTime, have built special templates allowing Windows to be installed via DigitalOcean’s Recovery ISO; their Recovery ISO is available with all of their droplets, however you need to request it to be mounted via support ticket.

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.

Tools You Need



The Guide


  1. Log In – Log into your DigitalOceans Control Panel.

  2. Create Droplet – Once you have logged in, you will need to choose “Create Droplet”.
  3. Choose an Image – Ubuntu 16 is recommended, however any Operating System may be chosen.
  4. Choose a Size – The template will successfully install to all size Droplets, however depending on your workload you may need a larger size due to CPU & RAM needs.
  5. Choose a Datacenter Region – You may choose any location you desire to have your Droplet located.
  6. Choose a Hostname – Here you will choose the name for your Droplet.
  7. Create – Once you have selected the operating system, size and location for your Droplet you will need to choose “Create” at the bottom of the page.

    As you may have noticed there were additional options on the Droplet creation page, please ensure to do NOT choose “Backups” or “User Data” as they may interfere with the installation of Microsoft Windows and cause the installation to fail.

    You can certainly enable “IPv6” and “Private Networking”, both should work without issue once Microsoft Windows has been installed.

  8. Recovery ISO & Support Ticket – Once your Droplet has been successfully created a support ticket will need to be created to request DigitialOcean’s Recovery ISO be mounted to your Droplet.
    a. Locate Support Ticket Creation Page – Choose “Support” at the top of DigitalOcean’s control panel webpage.
    b. Support Tickets – Once you are inside DigitalOcean’s “Support Center” you need to choose “Support Tickets” at the top right of the page.


    c. Create Ticket – Depending on the age of your account you may need to choose “Create Ticket” (Blue Button) at the top right of the control panel web page.

    d. Create New Support Ticket – Once you have arrived on the “New Support Ticket” page inside DigitialOcean’s control panel you will need to fill in the page similar to the following screenshot.


    e. Submit Ticket – Once you have completed filling in the Support Ticket Request to be similar to the above screenshot you will need to choose “Submit Ticket” (Blue Button) at the bottom right of the page.

    Depending on the time of day it may take several hours for DigitalOcean’s Support Team to respond to your Support Ticket.

     f. Ticket Response – DigitalOcean’s Support Team will eventually respond to your ticket noting the Recovery ISO has been mounted to your Droplet.

  9. Power Off & Power On Your Droplet – Once the recovery ISO has been mounted for you by DigitalOcean’s Support Team you will need to power your Droplet off and then power it back on all via their web control panel.a. Choose “Switch Off”

    b. Choose “Turn Off” – When you have chosen “Off / Switch Off” you will be presented with an warning message providing some good information. I would recommend reading the message thoroughly so you are well informed for the future.

    When you have read the entire message continue by choosing “Turn Off”.

    It will take a few moments for your Droplet to completely power off.

    c. Choose “Switch On”

    As with powering off, it will take a few moments for your Droplet to power on.

  10. Accessing Your Droplet’s Console – DigitalOcean provides console access for all of their Droplets (It provides similar access to have a monitor, keyboard and mouse attached) which will be used to install Microsoft Windows onto your Droplet.a. Opening the Console – Choose “Console” at the top, right side of DigitalOcean’s web control panel for your Droplet.


    b. A New Browser Windows Opens – Once you have chosen “Console” as detailed above a new browser window will open presenting you with your Droplet’s console.

    In the event your console windows doesn’t look nearly identical to the above you will want to respond to your Support Ticket requesting assistance from DigitalOcean’s Support Team in regards to booting your Droplet into the recovery ISO.

  11. Access Interactive Shell – Your recovery environment now has network access allowing us to continue with the downloading and installation of Microsoft Windows to your Droplet.Choose “6” on your keyboard to choose option #6 (“Interactive Shell [/bin/bash]”) and then choose “Enter” on your keyboard to run the command.


  12. Installing Microsoft Windows – To begin the Windows installation you will need to input the following command into your Droplet’s console. Please ensure the command matches perfectly otherwise your installation will likely fail.# Microsoft Windows Server 2012 R2 Standard Evaluation 64-bit
    wget -O- http://mirror.whatuptime.com/cer5w2631/betas/2012.R2.STD.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda

    # Microsoft Windows Server 2012 R2 Datacenter Evaluation 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/betas/2012.R2.DC.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda

    # Microsoft Windows Server 2016 Standard Evaluation 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/betas/2016.STD.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda

    # Microsoft Windows Server 2012 R2 Datacenter Evaluation 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/betas/2016.DC.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda

    # Microsoft Windows 10 Enterprise Evaluation 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/betas/10.ENT.x64.EVAL.US-English.gz | gunzip | dd of=/dev/vda

    Username:  Administrator / WhatUpTime.com
    Password: P@ssword64

    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.


    You may need to re-open your Droplet’s console via DigitalOcean’s web control panel as the console automatically disconnects from the Droplet after a period of time when there is no mouse or keyboard input.

    # Installation Complete – The installation of Microsoft Windows onto your Droplet will be complete when your Droplet’s console resembles the below screenshot.
    The important portion of the screenshot to review is the blinking cursor to the right of the “bash-4.2#” prompt which denotes the command you ran to install the template has completed.

    # Powering Off Your Droplet – Once you have confirmed the installation of the Microsoft Windows template has completed using the information above you will need to power off your Droplet via DigitalOcean’s web control panel.


    #Respond To Your Recovery ISO Support Ticket – When you Droplet has completed powering off you need to respond to your previous recovery ISO ticket requesting DigitalOcean Support Team remove the recovery ISO.


    Depending on the time of day it may take several hours for DigitalOcean’s Support Team to respond to your Support Ticket.

    #Recovery ISO Removed – Once DigitalOcean’s Support Team has removed the recovery ISO from your Droplet you will be ready to proceed to the next step.


    # Power On (Switch On) Your Droplet – Choose “Switch On” for your Droplet allowing your Droplet to begin starting up and booting into Microsoft Windows.


    It will take a few minutes for your Droplet to begin booting into Microsoft Windows. Once it begins booting into Microsoft Windows it will take several more minutes before Microsoft Windows is fully booted and you are able to login.

    # Open your Droplets Console – As done in Step #10 you will need to open the console for your Droplet as the next actions you will need to take will be performed via your Droplet’s console.


    #Confirm Microsoft Windows is Running – Once you have launched your Droplet’s console you should be presented with either Microsoft Windows booted or Microsoft Windows login screen (It will depend on how long it took Microsoft Windows to fully boot).

    Depending on the version of Microsoft Windows you chose to install to your Droplet your console may not match the following screenshot perfectly, however it should closely resemble it.

    # Logging into Microsoft Windows – Once you have confirmed your Droplet has completed booting into Microsoft Windows you will be ready to proceed logging into Microsoft Windows using the username & password.

Depending on the version of Microsoft Windows installed onto your Droplet you may find the login form is hidden when you first open your Droplet’s console.
 
In order to reveal the login form you will need to perform the following.
 
– Click inside your Droplet’s console window
– Click & hold the left mouse button on your mouse
– Swipe toward the top of your console window revealing the login fields

# Successfully Logged Into Microsoft Windows – Once you have entered the username, password and chosen “Enter” on your keyboard you should be successfully logged into Microsoft Windows on your Droplet.

# Manually Configure Your Droplet’s IP Address – Unfortunately due to the nature of DigitalOcean’s network configuration you will need to manually configure your assigned IP address(es) inside Microsoft Windows in order for your Droplet to access the internet.

Microsoft’s Guide – https://msdn.microsoft.com/en-us/library/dd163570.aspx

You may locate your Droplet’s Public IP Address, Subnet Mask & Gateway at the very bottom of your Droplet’s console window.
 
In addition to configuring the Public IP Address, Subnet Mask & Gateway you will also need to configure DNS servers. We have provided the following DNS server IP addresses for your convenience, however you may use any DNS servers you desire.
 
Preferred DNS Server: 208.67.220.220
Alternate DNS Server: 8.8.8.8

#Microsoft Windows Remote Desktop – Once you have completed manually configuring the IP Address(es) for your Droplet you will be able to log into your Droplet directly using Microsoft Remote Desktop.

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.

# Congratulations! You have successfully installed Microsoft Windows to your DigitalOcean’s Droplet and accessed it via Microsoft Windows Remote Desktop!

You should consider completing the follow to avoid potential issues in the future.

  1. Change the password for the “Administrator” account, a guide on how to change a password in Microsoft Windows Server 2016 Datacenter Evaluation x64 can be found here.

  2. Install all of the latest updates for Microsoft Windows

  3. Activate Microsoft Windows with your valid, legitimate license key

  4. Expand your C:\ Partition – When you install our Microsoft Windows template it will by default only use ~15GB of your hard drive. Using “Disk Management” inside Microsoft Windows you can expand your C:\ partition to include your entire drive.

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

 

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

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.

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.

  4. Choose “Rescue”

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

  6. Choose “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.

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

    – Start Putty- Input your server’s IP address

    – Choose “Open” at the bottom.

    – 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.


    – 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.


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

  10. At the prompt you will need to enter the following command:
    sudo -i

    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.

  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.
    Microsoft Windows 10 Enterprise Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_10_Enterprise_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows 10 Enterprise LTSB (Long Term Service Branch) Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_10_Enterprise_LTSB_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2012 R2 Standard Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2012_R2_Standard_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2012 R2 Datacenter Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2012_R2_Datacenter_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2016 Standard Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2016_Standard_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2016 Datacenter Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2016_Datacenter_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Username:  Administrator or WhatUpTime.com
    Password: P@ssword64

    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

  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).

  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.

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

    – Install all of the latest updates for Microsoft Windows.

     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.

    – 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!

Installing Microsoft Windows onto Kimsufi Dedicated Servers

Installing Microsoft Windows to Kimsufi (www.kimsufi.com) Dedicated Servers,  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 Kimsufi’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.

Tools You Need


The Guide


  1. Log into your Kimsufi Control Panel

  2. Once you have logged in, you will need to navigate to your server list (At the top left of the screen)

  3. Choose “Manage” to the right of your dedicated server in the list.
  4. Choose “Netboot”
  5. Choose “Rescue” and select “rescue64-pro” from the drop down menu and click “Next”.
  6. Choose “Restart” then click “Confirm”.
  7. Your server is now being restarted and will shortly boot into Kimsufi’s rescue mode. Please allow up to 10 minutes for your server to restart and boot into the rescue mode.
  8. Once the server has been rebooted you will receive your SSH login details via email for the rescue system. 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.
    – Start Putty
    – Input your server’s IP address

    – Choose “Open” at the bottom

    – 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.– Once you have entered your username and password you will be successfully logged into the system rescue for your server.
  9. At the prompt you will need to enter the following command:

    sudo -i
  10. 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.
    – Microsoft Windows 10 Enterprise Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_10_Enterprise_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows 10 Enterprise LTSB (Long Term Service Branch) Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_10_Enterprise_LTSB_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2012 R2 Standard Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2012_R2_Standard_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2012 R2 Datacenter Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2012_R2_Datacenter_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2016 Standard Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2016_Standard_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Microsoft Windows Server 2016 Datacenter Evaluation, 64-bit

    wget -O- http://mirror.whatuptime.com/cer5w2631/releases/Microsoft_Windows_Server_2016_Datacenter_Evaluation_64-bit_US_English.gz | gunzip | dd of=/dev/sda
    

    Username:  Administrator or WhatUpTime.com
    Password: P@ssword64

    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.

  11. Navigate back to the Kimsufi control panel web page and select “Netboot” then select “Hard disk” and click “Next”

    Once you have chosen “Hard disk” You will need to choose “Restart” to restart your server. once restarted it will 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).

  12. 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.

  13. 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.
    – Change the password for the “Administrator / WhatUpTime.com” account; a guide on how to change a password can be found here.
    – Install all of the latest updates for Microsoft Windows.
    – 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.
    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!