Remote Desktop Server Hosting for Business: Setup, Costs & RDS

In short

A remote desktop server gives employees a shared Windows environment for business apps, files, and remote work. On Raff, the infrastructure is a Windows VM; daily multi-user desktops should use Remote Desktop Services rather than administrative RDP. Current hosted pricing starts with the VM, $15/month Windows Server Standard SPLA, and, when RDS is used through Raff's hosted licensing model, $8/month per RDS User SAL.

A remote desktop server centralizes Windows apps and user sessions

A remote desktop server is a Windows Server environment that users reach over Remote Desktop Protocol instead of running every application and data file on their local PCs.

For a business, that can centralize:

• accounting and tax software;
• ERP and inventory applications;
• Microsoft Access and other legacy Windows apps;
• shared files and reports;
• RemoteApp programs;
• support tools used by an MSP or internal IT team;
• a consistent Windows workspace for remote or branch-office users.

Microsoft continues to include Remote Desktop Services (RDS) in Windows Server 2025. RDS supports session-based desktops, RemoteApp, RD Gateway, RD Licensing, Connection Broker, and other roles used to deliver Windows applications and desktops to users.

The important distinction is that a Windows VPS is the infrastructure. A production remote desktop environment is what you design on top of that infrastructure: access, user licensing, security, sizing, application support, profiles, backups, and recovery.

Remote desktop hosting fits businesses with centralized Windows workloads

A hosted remote desktop server is a strong fit when several people need the same Windows applications or data from different locations.

The buying question is therefore not simply “Do I need an RDP server?” It is: Do my users need a centralized Windows Server workspace that I can secure, license, back up, and support?

RDP, RDS, RD Gateway, and Windows VPS solve different problems

Buyers often use “RDP server” as a catch-all term. The underlying components are different.

For a first administrative login to a Raff Windows VM, use the Windows VPS RDP connection guide. For staff using desktop sessions every day, plan RDS instead of stretching administrative RDP into a user platform.

Administrative RDP is not a substitute for employee RDS sessions

Windows Server administrative Remote Desktop access exists for managing the server. It should not be treated as a way to avoid licensing a real multi-user desktop deployment.

Use administrative RDP for:

• server setup;
• Windows Update and patching;
• application installation;
• troubleshooting;
• emergency maintenance.

Use RDS Session Host when users need their own regular Windows sessions or RemoteApp access for daily work.

Microsoft's current RDS licensing guidance states that users or devices connecting to an RD Session Host need appropriate RDS access licensing. Microsoft separately documents per-user SALs for service providers, hosters, MSPs, and ISVs as the hosted-service licensing path.

For the architectural split, use Multi-User RDP vs RDS Session Host.

Raff hosted RDS uses User SALs rather than ordinary customer CAL pricing

The licensing model depends on how Windows Server and RDS rights are supplied.

Raff-hosted SPLA model

For a Raff-hosted Windows Server deployment using Raff's SPLA licensing:

• Windows Server Standard license: $15/month per instance;
• RDS User SAL: $8/month per user when users need hosted RDS sessions;
• the VM compute plan is billed separately;
• application licenses such as Microsoft 365 Apps, QuickBooks, SQL Server, ERP, or tax software remain separate from Windows/RDS unless explicitly included by that vendor or agreement.

A User SAL is assigned per user in the hosted service model. It is not the same commercial model as buying perpetual RDS CALs for an on-premises server.

Customer-owned Microsoft licensing

A customer with eligible Microsoft licensing can have a different path, but hosted deployment rights must be validated before production. Do not assume that an existing on-premises Windows Server or RDS CAL purchase automatically transfers unchanged to a hosted environment.

The detailed licensing decision is covered in Windows Server Licensing: SPLA, BYOL, CALs & RDS and the RDS CAL Licensing Guide.

Remote desktop server cost is VM + Windows + users + the application stack

Hosted remote desktop pricing should be calculated from the actual workload, not from one advertised VPS number.

The base formula is:

Monthly remote desktop infrastructure cost =
Windows VM compute
+ Windows Server license
+ RDS user licensing when RDS is used
+ storage / backup additions
+ application or database licensing

Current Raff Windows Server Standard SPLA pricing is $15/month per instance. In the Raff-hosted RDS model, RDS User SAL is $8/month per user.

Illustrative examples using current Raff VM configurations:

*Examples are infrastructure/licensing illustrations, not workload guarantees. They exclude application licenses, additional volumes, backup retention, snapshots, migration work, and other software costs.

Raff VM traffic is 3 Gbps unmetered with no VM egress fees, so the main remote-desktop sizing variables are usually CPU, RAM, storage, user concurrency, application behavior, and latency rather than transfer overage.

For the full pricing model, use Windows VPS Pricing Explained.

Concurrent users and workload type determine the VM size

Remote desktop servers should be sized for peak concurrent users, not employee headcount.

Ten employees with three simultaneous sessions are a different workload from ten people working in Windows all day.

Use these current Raff configurations as planning anchors:

These are starting points, not guarantees. User behavior can change requirements dramatically.

A user running one line-of-business app is different from a user running Outlook, multiple browser tabs, Excel, PDF tools, reporting software, and a locally hosted database at the same time.

Use Windows VPS Sizing for Remote Users for the deeper 1-, 3-, 5-, and 10-user model.

RD Gateway is usually a better team access layer than broadly exposed RDP

Direct RDP to a public IP is simple for initial administration, but a production team environment should minimize unnecessary exposure.

Microsoft documents RD Gateway as an RDS role that provides encrypted remote access over HTTPS and can avoid exposing internal RDP directly to external users.

For a business deployment, consider:

• RD Gateway for controlled external RDS access;
• a VPN/private-access layer where appropriate;
• Network Level Authentication;
• source-IP restrictions for administrative RDP;
• named accounts instead of shared Administrator credentials;
• MFA at the appropriate access layer;
• logging and failed-sign-in monitoring.

Compare the models in RD Gateway vs Direct RDP.

Business application support must be checked before migration

A technically working RDS session does not mean the software vendor supports the deployment.

Before moving a production app, verify:

This matters especially for accounting, tax, ERP, inventory, healthcare, legal, and legacy line-of-business software.

User profiles and storage can become the hidden bottleneck

Remote desktop workloads create more storage pressure than the operating-system installer suggests.

Plan capacity for:

• user profiles;
• browser caches;
• Outlook data where supported;
• downloads and documents;
• app data and logs;
• temporary files;
• print spools;
• shared folders;
• database files;
• Windows Update growth;
• backup staging if used.

Raff volumes are currently $0.08/GB/month when additional block storage is needed. Snapshots/backups are $0.06/GB/month according to the current Raff product pricing model.

Do not size a five- or ten-user RDS server for the amount of free disk space available immediately after Windows installation.

Backups need to protect both the VM and the business data

A remote desktop server can become the working environment for an entire business. Recovery therefore needs more than a single snapshot.

Plan for:

• VM-level recovery;
• file-level backup where needed;
• application-aware database backups;
• restore testing;
• retention that matches business requirements;
• an off-server recovery copy where appropriate;
• a rollback point before risky updates or migrations.

A snapshot is useful before change. It is not automatically a complete backup strategy for SQL Server, QuickBooks, ERP data, shared files, or user profiles.

Use Windows VPS Backup Strategy for Small Businesses before users begin storing production data.

Remote desktop performance depends on both the VM and the user path

When users say “the remote desktop server is slow,” the bottleneck can be anywhere in the path:

If the server is already deployed, use RDP Performance Tuning and Windows Server Performance Monitoring before resizing blindly.

A remote desktop server should be hardened before staff depend on it

Minimum production controls include:

1. Use named user accounts.
2. Separate administrator accounts from daily user accounts.
3. Keep Network Level Authentication enabled.
4. Restrict administrative RDP exposure.
5. Prefer RD Gateway or another controlled access layer for teams.
6. Keep Windows and business applications patched.
7. Review local and domain Group Policy.
8. Apply least-privilege file and application permissions.
9. Monitor failed logins and unusual account activity.
10. Configure backups and prove that restore works.

For the broader baseline, use the Windows Server Hardening Checklist and Configure Windows Firewall.

A safe office-server migration separates build, test, and cutover

Many hosted remote desktop projects begin as replacements for an office PC or local Windows Server.

Use this migration sequence:

1. Inventory users, applications, files, databases, printers, and dependencies.
2. Confirm software-vendor support for Windows Server and RDS.
3. Decide which Microsoft licensing model will be used.
4. Size the Raff Windows VM for peak concurrent users.
5. Build the new Windows environment.
6. Configure access, firewall, RDS, and RD Gateway/VPN if needed.
7. Install the applications and dependencies.
8. Copy non-production data first.
9. Test real users from real locations.
10. Configure backups and complete at least one restore test.
11. Schedule final data cutover.
12. Keep the old environment available as a rollback path until the new system is stable.

A remote desktop migration is successful when users can complete their normal business workflow reliably, not merely when an RDP window opens.

Raff provides the Windows VM foundation, not a fully managed virtual desktop service

Raff is a strong fit when a business, MSP, or IT operator wants to build a Windows Server remote desktop environment with:

• administrator-controlled Windows VMs;
• Windows Server 2022/2025 workloads;
• hourly PAYG compute;
• NVMe storage;
• 3 Gbps unmetered VM traffic with no VM egress fees;
• additional volumes;
• snapshots and backups;
• RDS User SAL availability in the Raff-hosted licensing model;
• direct access to a real support team when infrastructure help is needed.

Raff supplies and supports the cloud infrastructure layer. The customer or MSP still owns application support, user design, RDS architecture, profile strategy, domain/GPO design, application licensing, and day-to-day Windows administration unless a separate service agreement says otherwise.

If the requirement is a fully provider-managed enterprise virtual desktop platform with profile management, identity orchestration, multi-region failover, and managed user support included, a single self-managed Windows VM is not the same product.

The production checklist should be complete before the first workday

Validation scope

This is a commercial planning and architecture guide, not a claim that Raff performed a fresh multi-user RDS deployment test for this September 2026 revision. Current Raff VM pricing, Windows Server licensing, RDS User SAL pricing, storage pricing, and network terms were revalidated against Raff's current product source of truth. Microsoft RDS roles and CAL/SAL guidance were revalidated against current Microsoft documentation. Application compatibility must still be checked with each software vendor.

What's next

• Remote Desktop VPS — compare and deploy the Windows infrastructure.
• Windows VPS Pricing Explained — calculate compute, Windows licensing, storage, and hosted user costs.
• Windows Server Licensing — understand SPLA, BYOL, CALs, and hosted RDS licensing.
• Windows VPS Sizing for Remote Users — size 1, 3, 5, or 10 concurrent users.
• Multi-User RDP vs RDS Session Host — choose the correct user-session model.
• RD Gateway vs Direct RDP — design external access.
• RDS CAL Licensing Guide — understand customer CALs and RDS licensing mechanics.
• Windows VPS Backup Strategy — design recovery before production.

Sources

• Microsoft Learn — Remote Desktop Services overview in Windows Server
• Microsoft Learn — License Remote Desktop Services with Client Access Licenses
• Microsoft Learn — Remote Desktop Services: choose how you pay
• Microsoft Learn — Install Remote Desktop Services client access licenses
• Raff — Windows VM
• Raff — Pricing
• Sources revalidated: 2026-09-09