Base de conocimientos | VPSGrid
BetaEspañol
EnglishBeta EspañolPortuguês (Brasil)Coming soonFrançaisComing soonDeutschComing soonBeta translation — some areas may still appear in English.
Área de cliente

Getting Started with a Windows VPS

KB-065, Windows VPS, VPSGrid, unmanaged 0 found helpful

Getting Started with a Windows VPS

Short answer

After provisioning, collect your primary IP and Administrator password, connect with Remote Desktop, install updates, confirm Windows Firewall still allows RDP, then install only the software you need. VPSGrid Windows VPS plans are unmanaged.

Overview

This is your first-day checklist for a new VPSGrid Windows VPS. Detailed RDP client steps for every device are covered in a dedicated article — this guide focuses on the full getting-started path.

1) Confirm your VPS is ready

  • Log in to the VPSGrid client area
  • Open Services → My Services and select your Windows VPS
  • Confirm status is active/online and note the primary IP
  • Use the welcome / “VPS Ready” email for the initial Administrator password (change it after first login)

2) Connect with Remote Desktop (RDP)

From a Windows PC: open Remote Desktop Connection (mstsc), enter your primary IP, and sign in as Administrator.

For macOS, Linux, iOS, and Android steps, see How to Connect to a Windows VPS Using Remote Desktop (RDP).

Locked out?

Use the noVNC/console from the product details page in the client area to regain access without RDP.

3) First login hardening checklist

  1. Change the Administrator password to a long, unique password and store it securely.
  2. Open Settings → Windows Update and install pending updates (reboot if required).
  3. Confirm Remote Desktop is still enabled after updates.
  4. Review Windows Defender Firewall — keep RDP allowed; only open extra ports you need.
  5. Create a non-administrator user later for daily work if your workflow allows (optional but recommended).

4) Firewall and ports (quick view)

  • Keep TCP 3389 allowed for RDP (or your custom RDP port if you changed it)
  • Open 80/443 only if you will host websites
  • Do not expose database ports (for example SQL 1433) to the public internet unless required and secured

GUI guide: Windows Firewall Basics. PowerShell rules: Windows Firewall — PowerShell Rules.

5) What to install next (common paths)

Important notes

  • VPSGrid Windows VPS is unmanaged — OS updates, firewall, backups inside the VM, and applications are your responsibility.
  • Licensing for Windows Server is provided according to your plan terms; do not assume extra CAL/RDS licensing is included unless stated at checkout.
  • Current plans and specs are listed on vpsgrid.net — this article does not publish fixed pricing.

VPSGrid context

VPSGrid provides the KVM virtual machine, primary IP, power controls, and billing. You administer Windows Server inside the guest: users, firewall, updates, IIS/apps, and data.

Frequently Asked Questions

Where are my IP and password?

Check the VPS Ready email and Services → My Services → product details in the client area.

Can VPSGrid configure Windows for me?

Not on standard unmanaged plans. Support helps with platform, networking to the primary IP, and billing — not day-to-day Windows administration unless a managed product applies.

RDP will not connect. What should I try first?

Confirm the VPS is online, verify the IP and password, try noVNC/console, then review firewall and RDP settings. See the RDP connection and RDP troubleshooting articles.

Related Articles

Need More Help?

Open a ticket at billing.vpsgrid.net with your service ID, primary IP, and steps already tried.

¿Le ha resultado útil esta respuesta?

Artículos relacionados