Windows VPS and dedicated servers are managed via Remote Desktop (RDP), the same protocol Windows uses for remote desktop sessions everywhere. This article covers how to connect from any client OS, plus the basic security practices we recommend right after first login.

What you need: the server's public IP address, the Administrator password, and an RDP client. The IP and password are in the welcome email we send when your Windows server is provisioned. If you can't find that email, open a support ticket with your domain and we'll resend it.

Connect from Windows

Windows ships with the Remote Desktop Connection client built in.

  1. Press Win+R, type mstsc, and press Enter. (Or search the Start menu for "Remote Desktop Connection".)
  2. In the Computer field, type your server's IP address and click Connect.
  3. When prompted, enter the username Administrator and the password from your welcome email.
  4. The first connection will warn that the certificate isn't from a trusted authority — that's normal for a fresh server. Click Yes to continue.

Once connected you'll see the Windows Server desktop in a window on your local machine. You can now use it like any other Windows PC.

Connect from macOS

Microsoft publishes a free official client called Windows App (formerly Microsoft Remote Desktop):

  1. Install Windows App from the Mac App Store.
  2. Open it and click the + button at the top → Add PC.
  3. Set PC name to your server's IP. Click Add.
  4. Double-click the new entry to connect. Enter Administrator and the password when prompted.

Connect from Linux

Use one of these clients (most distributions have all three packaged):

  • Remmina — GUI, full-featured, the standard Linux choice.
  • FreeRDP (xfreerdp) — command line, scriptable, what Remmina uses underneath.
  • GNOME Connections or KRDC — desktop-environment specific, simpler UI.

Quick FreeRDP one-liner:

xfreerdp /v:YOUR.SERVER.IP /u:Administrator /p:'YourPassword' /size:1920x1080 /cert:ignore

Connect from iPad / iPhone / Android

Microsoft's Windows App is also available on iOS and Android. Configure the same way as the Mac version: add a PC, enter IP, save credentials.

First-login security checklist

Once you're in, run through these immediately:

  1. Change the Administrator password. The one in our welcome email is auto-generated and was sent over email — rotate it to something only you know. Press Ctrl+Alt+End (the RDP equivalent of Ctrl+Alt+Del) → Change a password.
  2. Run Windows Update. Server Manager → Local Server → Last installed updates / Windows Update settings. Install everything pending.
  3. Lock down RDP at the firewall. Windows Server's default firewall allows RDP from anywhere. If you have a fixed office or home IP, restrict the inbound RDP rule (TCP 3389) to that IP only. Windows Firewall with Advanced Security → Inbound Rules → Remote Desktop rules → Properties → Scope tab → Remote IP address.
  4. Create a non-administrator user for daily use, if you'll be doing routine work on the server. Use Administrator only when necessary.
  5. Configure off-server backups for anything you care about. Windows Server has its own backup feature, or you can use third-party tools.
RDP exposed to the open internet is a brute-force target. Restricting the firewall rule to specific IPs is the single biggest thing you can do. If you can't (because you connect from many places), at minimum use a strong unique Administrator password and rotate it regularly.

Common issues

  • "Cannot connect" / timeout: confirm the server is up via the OVH manager (or open a ticket). RDP listens on TCP 3389; some networks (corporate, school, public WiFi) block this port. Try from a different network.
  • "Authentication error": usually wrong username (it's Administrator, not your name) or wrong password. Copy / paste the password from the welcome email to rule out typos.
  • "Identity of the remote computer cannot be verified": the certificate warning. Normal for a fresh server. Click through to connect; you can install a real SSL cert on the RDP listener later if you want to remove the warning permanently.
  • Black screen after login: usually a graphics driver hiccup. Disconnect and reconnect — it almost always clears. If it persists, reboot the server.
  • Server unreachable after a Windows Update reboot: give it 5-10 minutes — some updates take a while to apply on first boot. If still unreachable, open a ticket and we can request a console.

Managing your Windows server day to day

Windows VPS and dedicated servers are fully self-managed — we provide the infrastructure, OVH-level DDoS protection, and network uptime, but software installation, patching, security configuration, and application setup are your responsibility. We can help with infrastructure issues (network, hardware, OS-level reboots) via support tickets, but we don't administer Windows servers for clients.

Related articles

Still stuck? Open a support ticket

Cette réponse était-elle pertinente? 0 Utilisateurs l'ont trouvée utile (0 Votes)

Les plus consultés

Getting started with your VPS or dedicated server

Welcome! This article is a quick orientation for new VPS and dedicated server clients - what you...
Logging in to WHM on your VPS or dedicated server

WHM (WebHost Manager) is the server-wide control panel for your VPS or dedicated server. It's...
Creating a cPanel account on your VPS or dedicated server

Each website you host on your server needs its own cPanel account. This article walks through...
Accessing your VPS or dedicated server via SSH

SSH (Secure Shell) gives you command-line access to your server as the root user - useful for...
Requesting a reboot or reporting an issue with your server

If your server is unresponsive, running slowly, or you need it rebooted for any reason - don't...