How to set up Windows Server 2012 R2 on your VPS

This guide takes a VPS with Windows Server 2012 R2 from a fresh install to a working Remote Desktop connection. The same steps apply to Windows Server 2019, 2022 and 2025.

Choosing a version: Windows Server 2012 R2 no longer gets security updates from Microsoft. Use it only if your software needs it; otherwise pick Windows Server 2019, 2022 or 2025 when you install. Windows needs a plan with enough memory, so it is shown as unavailable on the smallest plans.

1. Install Windows

Choose Windows Server when you order the VPS, or reinstall an existing one from the panel: open your VPS, choose Reinstall and pick the Windows version. A reinstall erases everything on the server. The installation takes several minutes and the server restarts a few times.

2. Open the console and set the password

1. Open your VPS in the panel and click Open console to see the server's screen in your browser.
2. On first start Windows may ask you to set the Administrator password. Choose a strong one: at least 12 characters with upper and lower case letters, numbers and symbols. Remote Desktop is attacked constantly, so a weak password gets found.
3. To send Ctrl+Alt+Del for the login screen, use the button in the console toolbar.

3. Check the internet connection

Open a web browser or run ping 1.1.1.1 in Command Prompt. If it answers, the network is already set up and you can skip to step 5.

4. Set the IP address by hand (only if there is no connection)

Find your server's IP address on the Network tab of your VPS in the panel. You will need:

• IP address: your server's IP, for example 102.220.163.121
• Subnet mask: 255.255.255.0
• Default gateway: your IP with the last number replaced by 1, for example 102.220.163.1
• DNS servers: 1.1.1.1 and 1.0.0.1

Then:

1. Press Windows+R, type ncpa.cpl and press Enter. The network connections open.
2. Right-click the Ethernet adapter (for example Ethernet Instance 0) and choose Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Choose Use the following IP address and enter the IP address, subnet mask and default gateway.
5. Choose Use the following DNS server addresses and enter 1.1.1.1 and 1.0.0.1.
6. Click OK, then Close. Test again with ping 1.1.1.1.

If your panel shows a different gateway or mask for your IP, use those. If it still does not connect, open a ticket and tell us your server's IP.

5. Turn on Remote Desktop

1. Open Server Manager and click Local Server.
2. Click the value next to Remote Desktop (it says Disabled), choose Allow remote connections to this computer and click OK.

Windows opens the firewall for Remote Desktop automatically.

6. Connect from your computer

• Windows: open Remote Desktop Connection (mstsc), enter your server's IP and log in as Administrator.
• macOS: install Windows App (formerly Microsoft Remote Desktop) from the App Store.
• Linux: use Remmina or xfreerdp.

From now on you can work over Remote Desktop and only need the console if the connection breaks.

7. Secure the server

• Install updates: Settings or Control Panel, Windows Update, then restart.
• Limit who can connect:
• Consider changing the RDP port from 3389 to reduce automated login attempts, and keep a strong password.

Good to know

• Memory shows close to 100% in the panel. That is normal for Windows on KVM: Windows claims all its memory for its own cache, so the panel sees it as used. Check the real usage in Task Manager inside Windows.
• Locked out (wrong password, network or firewall change)? The console always works, even without network.