Back to site

First RDP connection

Connect to a Windows VPS for the first time via Remote Desktop, credentials, and troubleshooting.

First RDP connection

After your HolyCloud Windows VPS is delivered, the first step is to open a Remote Desktop (RDP) session with the credentials received by email or in the client area. This guide covers Windows, macOS, and Linux.

Prerequisites

  • Active Windows Server VPS (status Online in the client area)
  • VPS public IP address and RDP port (3389 by default, unless stated otherwise)
  • Administrator account (or provided account) and initial password
  • Client machine with an RDP client installed

Save a copy of the credentials in a password manager before your first connection.

Retrieve information from the client area

  1. Log in to holycloud.frClient area.
  2. Open VPS → your Windows server.
  3. Note:

- Public IP

- RDP port (often 3389)

- Username and password (“Show” button or reset if needed)

If the password was regenerated, wait 1 to 2 minutes before trying again.

Connect from Windows

  1. Press Win + R, type mstsc, Enter.
  2. Computer: PUBLIC_IP or PUBLIC_IP:PORT if the port is not 3389.
  3. Click Connect.
  4. User: Administrator (or the account indicated).
  5. Password: the one from the client area.
  6. On the certificate warning: Yes (normal on first connection).

Command-line shortcut:

mstsc /v:203.0.113.10

With a custom port:

mstsc /v:203.0.113.10:3390

Connect from macOS

  1. Install Microsoft Remote Desktop from the App Store.
  2. Add PC → PC name: 203.0.113.10.
  3. User account: Add User Account → username and password.
  4. Double-click the entry to connect.

Connect from Linux

Install an RDP client, for example Remmina or xfreerdp:

sudo apt update && sudo apt install -y remmina remmina-plugin-rdp

Command line with xfreerdp:

xfreerdp /v:203.0.113.10 /u:Administrator /p:'VotreMotDePasse' /cert:ignore

Once connected:

  1. Change the password: Ctrl + Alt + End (RDP equivalent of Ctrl+Alt+Del) → Change a password.
  2. Time zone: Settings → Time & language → (UTC+01:00) Paris zone.
  3. Windows Update: Settings → Windows Update → check for updates (schedule a maintenance window).

PowerShell (administrator) — check the version:

Get-ComputerInfo | Select-Object WindowsProductName, OsVersion, CsName

HolyCloud and Windows firewall

  • The Windows firewall allows RDP by default on standard images.
  • If you have a network firewall in the HolyCloud client area, open the TCP port in use (3389 or other) toward the VPS IP.

Test from your machine (PowerShell):

Test-NetConnection -ComputerName 203.0.113.10 -Port 3389

TcpTestSucceeded : True means the port is reachable.

Security from the first session

  • Do not share credentials over unencrypted email.
  • Create a dedicated administrator account, then consider renaming/disabling Administrator (see the “Secure Remote Desktop” doc).
  • Enable NLA if not already enabled (recommended in production).

Troubleshooting

| Symptom | Likely cause | Action |

|----------|----------------|--------|

| Timeout then failure | Closed port or wrong IP | Check IP/port in client area; Test-NetConnection |

| « Credentials did not work » | Incorrect password | Reset VPS password in the panel |

| « Remote desktop can't connect » | RDP service stopped | KVM/IPMI console or support ticket |

| Black screen after login | Session in progress | Disconnect the other session or restart via the panel |

| Certificate refused | Strict client policy | Accept once or use /cert:ignore (xfreerdp) |

Restart the RDP service (if you already have an admin session):

Restart-Service TermService -Force
Get-Service TermService

Need help?

Open a HolyCloud ticket with the VPS IP, RDP port, and time of the attempt. Support does not send passwords in plain text via chat — use secure reset in the client area.