Deploy Windows Server 2025 on Raff: Image Choice, VM Creation, and First Boot

In short

To deploy a Windows Server 2025 VPS on Raff, open the Windows VM creation flow, choose the us-east region, select a VM size that fits the workload, choose Windows Server 2025, set a strong Administrator password, and create the VM. For production, use Raff-provided Windows Server licensing under SPLA or eligible customer BYOL rights. When the VM reaches Running, connect over RDP and verify the operating system before installing the workload.

This guide covers provisioning, not post-deployment configuration

Raff already has separate Windows Hub pages for choosing a Windows Server version, connecting over Remote Desktop Protocol (RDP), licensing, and configuring a new server after first login.

This page owns one specific job:

Choose Windows Server 2025
→ choose VM size
→ confirm production 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 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 a strong default 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 support runway makes Server 2025 a practical 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;
• ERP software;
• legacy Microsoft Access applications;
• older 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:

1. region;
2. VM size;
3. Windows Server image;
4. production licensing path;
5. 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:

Do not choose a larger VM simply because it runs Windows Server 2025. Choose it because the workload needs the capacity.

For reference, current Windows totals start at $28.99/month for 1 vCPU / 2 GB / 50 GB when the $15/month Windows Server Standard SPLA licence is included. 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 Windows Server 2025 and confirm the production licensing path

Choose Windows Server 2025 from the Windows image selector.

For a production Raff Windows VM, use one of these supported licensing paths:

• Raff-provided Windows Server licensing under SPLA when Raff supplies the hosted Windows Server licence;
• eligible customer BYOL when the customer has qualifying Microsoft rights and the deployment fits Microsoft's applicable outsourcing or Flexible Virtualization rules.

Raff currently charges $15/month per Windows Server Standard instance when Raff supplies the operating-system licence through its hosted SPLA model.

Do not treat a temporary evaluation installation as the production licensing plan. If you are validating software compatibility or migration behavior, keep that activity separate from the production deployment decision.

For BYOL eligibility, CALs, RDS licensing, and the distinction between Windows Server outsourcing rights and License Mobility, use Windows Server Licensing on Raff.

Verification: Before creating the VM, confirm that the selected image says Windows Server 2025 and that the production licensing path is understood.

Step 4 — Set the Administrator password and save it immediately

During VM creation, set a strong password for the Windows Administrator account.

Use a password manager and generate a long, unique password. Do not reuse a password from another server, Microsoft account, email account, or customer environment.

The current Raff Windows workflow expects you to set this password during creation. Save it before you leave the creation flow.

Your first-login credentials will normally be:

Username: Administrator
Password: the password you set during VM creation

If you later lose the password, the VM details page provides a password-reset action. The detailed recovery workflow is covered in How to Connect to a Windows VPS via RDP.

Do not put the password in:

• a server name;
• a ticket subject;
• a shared spreadsheet;
• an ordinary chat message;
• a screenshot for documentation.

Verification: Confirm the password is saved in an approved password manager before clicking the final create/deploy action.

Step 5 — Create the VM and wait for Running

Submit the VM creation request.

The VM will need time to provision the virtual hardware, Windows image, networking, and initial operating-system state. Do not start troubleshooting RDP while the VM is still being created.

After creation:

1. open Compute → All Virtual Machines;
2. select the new Windows VM;
3. wait until its status is Running;
4. open the VM details page;
5. copy its Public IPv4 address.

Keep the VM name and public IP together in your server inventory so you know which environment you are connecting to later.

Verification: The VM should show Running and have a public IPv4 address before you attempt the first RDP connection.

Step 6 — Make the first RDP connection

Once the VM is Running, connect to the Windows desktop with RDP.

Use:

Computer / PC name: <your-public-ip>
Username: Administrator
Password: <the-password-saved-during-creation>

On Windows, you can use the built-in Remote Desktop Connection client. On macOS and mobile platforms, Microsoft provides Windows App. Linux users can use an RDP client such as Remmina or FreeRDP.

This article intentionally does not repeat the complete client setup or troubleshooting flow. Follow How to Connect to a Windows VPS via RDP if you need platform-specific instructions, certificate-warning guidance, password reset, or fixes for port 3389 and credential errors.

A first-time certificate warning is expected when connecting directly to a new server by IP with the default RDP certificate. Confirm that you are using the correct VM IP before accepting it.

Verification: You should reach the Windows Server desktop and be able to open an elevated PowerShell window.

Step 7 — Verify that Windows Server 2025 booted correctly

Before installing IIS, SQL Server, RDS roles, business software, agents, or other workloads, verify the operating system.

Open PowerShell as Administrator and run:

Get-ComputerInfo |
Select-Object CsName, WindowsProductName, WindowsVersion, OsBuildNumber, OsArchitecture

Confirm that the output identifies Windows Server 2025.

Then check the network state:

Get-NetIPConfiguration

Record:

• computer name;
• Windows product name;
• OS build number;
• public IP from the Raff dashboard;
• current network adapter configuration.

You can also confirm that the Remote Desktop Services service is running:

Get-Service TermService

Expected status:

Running

Do not manually replace the guest network configuration with a static IP, gateway, or DNS server just because this is a cloud VM. An incorrect guest-level network change can break RDP access. Follow the provider networking model and only change guest networking when the workload requires it and you have a recovery path.

Verification: The Windows product and build are correct, PowerShell opens normally, and networking is present. At that point, provisioning is complete.

Provisioning ends here; initial server setup starts next

A VM reaching the Windows desktop does not mean it is production-ready.

The next phase should cover:

• Windows Update;
• hostname and time zone;
• a named administrator account;
• Windows Firewall;
• Microsoft Defender;
• storage and free-space checks;
• snapshot or backup planning;
• a baseline record before workload installation.

Those actions belong in the Windows Server Initial Setup Checklist.

Keeping the handoff explicit prevents two common problems: installing production software before the base OS is ready, and mixing infrastructure provisioning with application troubleshooting.

Common Windows Server 2025 deployment mistakes

Choosing Server 2025 before checking software support

Server 2025 has a long Microsoft support runway, but an application vendor may still certify only Server 2022.

Check the complete software stack before production deployment.

Treating evaluation as the production licensing plan

Testing and production are different decisions. For production on Raff, use the hosted SPLA path or eligible customer BYOL rights and document which licensing model applies before users depend on the server.

Losing the Administrator password

The first password is operationally important. Save it during creation rather than assuming the dashboard will show it later.

Connecting before the VM reaches Running

An RDP timeout during provisioning does not necessarily mean Windows or the firewall is broken. Wait until the dashboard reports the VM as Running and shows its public IP.

Installing the workload immediately after first login

Patch and baseline the server first. A clean initial state makes later troubleshooting much easier.

Changing the Windows network adapter without a reason

A bad static IP, gateway, or DNS change can remove remote access. Confirm the provider networking model before altering the guest configuration.

Treating administrative RDP as a multi-user desktop service

Windows Server administrative access and a real RDS Session Host deployment are different. If several employees will use the server every day, review Multi-User RDP: 2 Admin Sessions vs RDS Session Host and the RDS CAL licensing guide.

Deployment checklist

If all checks pass, the Windows Server 2025 VPS has been provisioned correctly and is ready for post-deployment setup.

What's next

• Windows Server Initial Setup Checklist — complete the first 30 minutes of server configuration.
• How to Connect to a Windows VPS via RDP — detailed Windows, macOS, Linux, and mobile connection instructions.
• Windows Server 2019 vs 2022 vs 2025 — confirm the operating-system choice before production.
• Windows Server Licensing on Raff — understand SPLA and eligible BYOL paths.
• Raff Windows VM — review the Windows VM product.
• Raff pricing — review current VM pricing before deployment.

Sources

• Microsoft Lifecycle — Windows Server 2025: https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2025
• Microsoft Learn — Windows Server release information: https://learn.microsoft.com/en-us/windows/release-health/windows-server-release-info
• Microsoft Licensing — Windows Server licensing guidance and Product Terms
• Raff Windows VM: https://rafftechnologies.com/products/windows-vm
• Raff Windows Server Hub: https://rafftechnologies.com/windows-server
• Sources revalidated: 2026-09-17