To deploy a Windows Server 2025 VPS on Raff, open the Windows VM creation flow, choose the us-east region and a VM size for your workload, select Windows Server 2025, choose the appropriate licensing path, set and save a strong Administrator password, and create the VM. When its status becomes Running, copy the public IPv4 address, connect over RDP, and verify the operating system and network state before installing anything.
This guide stops at first boot. For updates, hostname changes, firewall review, Defender, administrator accounts, storage checks, and recovery setup, continue with the Windows Server Initial Setup Checklist.
This guide covers provisioning, not post-deployment configuration
Raff Technologies already has separate Windows Hub pages for choosing a Windows Server version, connecting over Remote Desktop Protocol (RDP), and configuring a new server after the first login.
This page owns one specific job:
Choose image → choose VM size → choose licensing path → create Windows VM → wait for Running → get public IP → make first RDP connection → verify Windows Server 2025 booted correctly
It does not duplicate:
- Windows Server 2019 vs 2022 vs 2025 for operating-system selection;
- How to Connect to a Windows VPS via RDP for client-by-client RDP instructions and troubleshooting;
- Windows Server Initial Setup Checklist for the first 30 minutes after deployment;
- Windows Server Licensing on Raff for detailed Evaluation, SPLA, and BYOL licensing guidance.
If you have already created the VM and can see the Windows desktop, skip directly to the initial setup checklist.
Windows Server 2025 is the right image for new validated workloads
Windows Server 2025 is a Long-Term Servicing Channel release. Microsoft lists mainstream support through November 13, 2029 and extended support through November 14, 2034.
That long support runway makes Server 2025 a sensible default for a new environment when the software you plan to run supports it.
Before deploying, check the application vendor if the server will run:
- accounting or tax software;
- enterprise resource planning (ERP) software;
- legacy Microsoft Access applications;
- older Open Database Connectivity (ODBC) drivers;
- specialized printer or scanner drivers;
- older SQL Server versions;
- endpoint security or remote monitoring agents;
- software with strict Windows Server certification requirements.
If the vendor only supports Server 2022, use Server 2022 rather than creating a Server 2025 VM and discovering the compatibility issue after migration.
For the detailed decision, use Windows Server 2019 vs 2022 vs 2025.
Step 1 — Open the Raff Windows VM creation flow
Sign in to the Raff dashboard and open the Windows VM creation page.
Direct dashboard path:
/home/create-product/vms/windows
You can also start from the Raff Windows VM product page and continue to deployment.
The creation screen is where you define the VM before Raff provisions the operating system.
You will need to make five decisions:
- region;
- VM size;
- Windows Server image;
- licensing path;
- Administrator password.
Verification: Do not continue until the creation page is specifically configured for a Windows VM rather than a Linux VM.
Step 2 — Choose us-east and size the VM for the workload
Choose the Raff us-east region for the deployment.
Then select a VM size based on what the server will actually run. Windows Server itself is only the baseline. IIS, SQL Server, Remote Desktop Services (RDS), business applications, antivirus, background services, and concurrent users all consume additional CPU and memory.
A useful decision pattern is:
| Workload | Sizing approach |
|---|---|
| Lab, testing, or light administration | Start with a smaller Windows VM and scale if needed |
| IIS or a light internal application | Size for application CPU, memory, and expected traffic |
| SQL Server | Prioritize memory, storage behavior, database size, and query load |
| RDP/RDS users | Size for concurrent sessions and applications, not total employee count |
| ERP or accounting software | Follow the software vendor's supported requirements first |
| Mixed app + database workload | Leave headroom or consider separating roles as usage grows |
Do not choose a larger VM simply because it runs Windows Server 2025. Choose it because the workload needs the capacity.
Review current options on Raff Windows VM and Raff pricing before creating a production server.
Verification: Confirm the selected VM size has enough CPU, memory, and storage for the first workload you plan to install.
Step 3 — Select the Windows Server 2025 image and licensing path
Choose Windows Server 2025 from the Windows image selector.
Raff's Windows flow supports different licensing scenarios. The important distinction at creation time is whether this is a production deployment or a temporary evaluation/testing environment.
Use a licensed Windows Server 2025 image for production
Use the licensed path when the VM is intended to become a normal production Windows Server and you want Windows licensing provided through the hosted service.
This is the cleaner path for:
- production business applications;
- long-running RDP or RDS environments;
- IIS workloads;
- SQL Server hosts;
- file servers;
- MSP client environments;
- persistent internal infrastructure.
Raff is a Microsoft Service Provider License Agreement (SPLA) partner, so hosted Microsoft licensing can be provided through the applicable Raff Windows licensing workflow.
Use the Evaluation image for testing
Microsoft's Windows Server 2025 Evaluation edition expires after 180 days. Microsoft also states that Evaluation installations need internet activation during the initial evaluation period to avoid automatic shutdown behavior.
Use Evaluation when you are:
- checking application compatibility;
- building a temporary lab;
- testing a migration;
- validating Server 2025 before committing to a production build.
Do not treat Evaluation as a permanent production licensing model.
For the licensing details and BYOL considerations, use Windows Server Licensing on Raff.
Verification: Before creating the VM, confirm that the selected image says Windows Server 2025 and that the licensing option matches the intended use.
