Workloads & Use Cases
Workloads & Use Casesbeginner17 min read·Updated Nov 17, 2026

Windows VPS for MSPs: SPLA Handled, RDS, Backups & Security

A Windows VPS guide for MSPs: Raff handles SPLA for Windows Server and Remote Desktop users, plus client separation, RDS, backups, security, migration, and a 3-client QuickBooks and Sage month.

Give your team Windows desktops on one server, $8.00 per person a month.

Windows Server with the licence included, and a Remote Desktop licence from Raff for each person who signs in. No CALs to buy, and you raise or lower the count any month. One person from $42.99 a month.

In short

A Windows VPS can be a strong infrastructure layer for an MSP when a client needs Windows-only business software, Remote Desktop access, a replacement for an aging office server, shared files, SQL-backed applications, or a centralized Windows environment for multiple locations.

Raff Technologies provides Windows Server VMs that MSPs can use as the infrastructure underneath their own managed service, with the Microsoft licensing handled: Raff holds the SPLA, licenses Windows Server at $6 per vCPU a month (2 vCPU minimum) and Remote Desktop users at $8 per person a month, and files the monthly report, so the MSP files nothing with Microsoft. The MSP still owns the client design: user access, application support, backups, monitoring, documentation, security policy, and day-to-day client support.

For an MSP, the goal should not be to sell “a VPS.” The goal is to create a repeatable Windows service that can be deployed, supported, backed up, migrated, and eventually offboarded without reinventing the process for every client.

Quick verdict: when Windows VPS fits an MSP client

Client situationWindows VPS fitMSP planning requirement
Client needs one Windows-only business appStrong fitConfirm vendor support, sizing, backups, and user access.
3-10 users need a shared Windows environmentGood fit with RDS planningPlan Session Host, RDS CALs, profiles, printers, and concurrency.
Client is replacing an aging office serverStrong fitInventory hidden services, files, apps, jobs, and rollback requirements.
Multiple offices need the same app or dataStrong fitTest latency and access from every location.
Client uses QuickBooks, Sage, ERP, tax, Access, or legacy softwareGood fit after testingVerify vendor licensing and deployment support.
Client needs a cloud file serverGood fit with secure access designPlan SMB, permissions, mapped drives, backups, and remote access.
Client requires a fully managed desktop platformNot a one-VM decisionDesign RDS/VDI architecture and management responsibilities first.
Client requires high availabilityNot a single-VPS solutionDesign redundancy, recovery, and database/application failover.

The best MSP use case is a well-defined Windows workload with a known support owner, backup policy, access model, and recovery target.

Use Raff Windows VM as the infrastructure layer for client Windows workloads, remote access, business apps, and migrations.

MSP clients buy an outcome, not a server

Most SMB clients never ask an MSP for a “Windows VPS.” They ask for a business problem to be solved.

Typical requests sound like:

  • “Our accounting software needs to work from home.”
  • “The office server is old and we do not want to buy another one.”
  • “Both branches need the same inventory system.”
  • “We need several users in the same Windows application.”
  • “Our Access database only works properly in the office.”
  • “We need a Windows server for a legacy app.”
  • “Can you move this SQL-backed app out of the server closet?”

The MSP translates that request into an architecture. A Windows VPS can be the right foundation, but the service still needs migration, configuration, access, backup, monitoring, security, and user support around it.

That is the difference between reselling infrastructure and delivering a managed Windows service.

Why MSPs standardize client Windows environments

Standardization lowers support cost and reduces mistakes.

Architecture diagram showing MSP client Windows VPS environments with remote users, business apps, backups, and security controls

An MSP can define a small number of repeatable patterns instead of building every Windows server differently.

StandardWhat the MSP defines
OS baselineSupported Windows Server versions and patch policy
Access modelAdmin RDP, RDS, RD Gateway, VPN/private access, or app-only access
User modelNamed accounts, groups, admin separation, offboarding
Backup modelFrequency, retention, off-server copy, restore ownership
MonitoringCPU, RAM, disk, backup success, services, logins, event logs
SecurityFirewall, least privilege, patching, Defender/security tooling, logging
DocumentationVM spec, apps, users, licensing, backups, change history, runbook
MigrationDiscovery, test build, pilot, cutover, rollback
EscalationWhat the MSP owns versus what the infrastructure or app vendor owns

The technical value is not only consistency. The commercial value is that a technician can support the next client using a familiar process instead of learning a completely different environment.

Keep client environments separate by default

For most MSP workloads, one client should have its own Windows VPS rather than sharing a server with unrelated customers.

Visual showing separate Windows VPS environments for different MSP clients with isolated backups, users, and access policies

Client separation simplifies:

AreaWhy separate client VMs help
SecurityOne client's users and data are not mixed with another client's environment.
BackupsRestore points map cleanly to one client.
BillingInfrastructure cost can be assigned to that customer.
PerformanceOne client's workload is less likely to interfere with another's.
Change managementApp updates affect only the intended client.
TroubleshootingLogs, services, users, and applications are easier to isolate.
OffboardingA departing client can be transferred or retired without touching others.
DocumentationThe VM, users, apps, backups, and support history stay in one record set.

A shared MSP management server can still make sense for internal tooling, monitoring, automation, or jump-host functions. Client business applications and data should normally stay isolated unless there is a deliberate architecture for multi-tenancy.

Windows VPS vs managed Windows VPS for MSP clients

The phrase “managed Windows VPS” can mean very different things. MSPs should define the boundary instead of assuming the hosting provider manages the same things they do.

LayerTypical infrastructure provider roleTypical MSP role
Physical/cloud infrastructureProvider—
VM provisioningProviderMSP selects and configures
Windows Server OSProvider makes image availableMSP patches and administers unless contract says otherwise
RDP accessProvider enables VM accessMSP controls who can connect
Business application—MSP/client/app vendor
RDS deployment—MSP designs and configures
Remote Desktop usersSome providers license and report them (Raff: $8 per person a month)MSP keeps the user count equal to the people who sign in
File permissions—MSP
App-specific backups—MSP/client/app vendor
MonitoringInfrastructure and/or platform-specificMSP monitors client workload according to contract
User supportPlatform support for provider serviceMSP supports end users and client workflow

For Raff specifically, the current Windows offering provides Windows Server 2019, 2022, and 2025 options, full administrator access through RDP, Windows Server and Remote Desktop users licensed and reported by Raff under its SPLA, 24/7 infrastructure support, and migration assistance. The MSP should still treat client application management, RDS design, backups, users, and operating procedures as part of its own managed-service scope.

This separation is useful commercially because it lets the MSP keep ownership of the client relationship while using Raff as the Windows infrastructure layer.

SPLA handled: who reports what for MSP clients

On Raff, SPLA is handled for the MSP. Raff holds the Microsoft SPLA agreement, licenses Windows Server in every Windows server at $6 per vCPU a month (2 vCPU minimum) and Remote Desktop users at $8 per person a month, and files the monthly usage report for both. An MSP hosting its clients on Raff files nothing with Microsoft for them.

Hosts use the word "SPLA" for three different offers, and the difference decides how much paperwork stays with the MSP:

What the host offersWho holds the licenceWho reports to Microsoft
Windows availableYou bring it (your own SPLA, or an eligible licence under the Flexible Virtualization Benefit)You
SPLA licences availableThe host, for Windows Server; Remote Desktop users, SQL Server or Office may still be yoursSplit: check the host's written scope
SPLA handledThe host, for Windows Server and Remote Desktop users, with what is left to you written downThe host

Raff is the third kind. The reporting is the part MSPs feel: 45% of SPLA providers in SAMexpert's 2026 survey had a Microsoft compliance audit in the previous 12 months, and 51% had no purpose-built reporting tool.

Here is the shape it takes on Raff. On 2026-11-17, one MSP ran 13 Windows servers for 5 clients, one project per client, all in US East. Each client has a small 2 vCPU server and one or two 8 vCPU servers with 16 or 32 GB of memory.

"SPLA handled" never means every licence on the server is handled. This is Raff's written scope:

ItemRaffThe MSP and its client
Windows Server licenceIn every Windows server at $6 per vCPU a month, 2 vCPU minimum. Raff holds the SPLA and files the monthly report.Nothing to file.
Remote Desktop users$8 per person a month, reported to Microsoft by Raff.Add each server's users in the dashboard, and lower the count any time.
QuickBooks Desktop or EnterpriseRuns on the server. Raff is not in Intuit's authorized hosting program.The client's own QuickBooks licence; Intuit supports the software under it.
Sage 50, 100 or 300Runs on the server.The client's own Sage licence.
Microsoft Office on the serverNot part of Raff's licence.A Microsoft 365 plan with shared computer activation, one licence per user.
SQL ServerExpress and Developer are free; Web, Standard and Enterprise come from Raff.Or the client's own SQL Server licence where its agreement allows it.
Client accessA project per client, with project-only access for each client's own people.Who gets access, and when it ends.
Support24/7 human support for servers, network and billing, included free.First-line support for the client's staff.

Two lines cause most of the trouble:

  • Remote Desktop users are counted per person. Microsoft requires a Subscriber Access License for each unique person who uses Remote Desktop, so a client with 5 staff who all sign in during the month needs 5 users even if only 3 are connected at once, and a shared login used by 3 people still counts as 3. The two connections Windows Server includes are for administering the server, not staff desktops.
  • Office needs its own licence. To run Microsoft 365 Apps on a Remote Desktop server, Microsoft requires shared computer activation and a plan that supports it, with a licence for every user. Microsoft 365 Business Premium is the only business plan that supports it; Business Standard does not. Setup: shared computer activation for Microsoft 365 Apps on RDS.

For what SPLA itself is, bring-your-own licences and evaluation media, read Microsoft SPLA licensing explained.

What three QuickBooks and Sage clients cost a month on Raff

Prices from Raff's live pricing on 2026-11-17: US East, Business plans (3x data replication with high availability). Sizes follow our QuickBooks and Sage pages.

ClientServerServerWindows licenceRemote Desktop usersMonth
A: accounting firm, QuickBooks Desktop Enterprise, 5 people8 vCPU / 16 GB$76.99$48.005 x $8.00 = $40.00$164.99
B: dental office, Sage 50, 2 people8 vCPU / 16 GB$76.99$48.002 x $8.00 = $16.00$140.99
C: distributor, QuickBooks Desktop Enterprise, 10 people8 vCPU / 32 GB$137.99$48.0010 x $8.00 = $80.00$265.99
Three clients$571.97

Raff files the SPLA report behind the $144.00 of Windows licences and the $136.00 of Remote Desktop users. Not on this bill: the clients' QuickBooks and Sage licences (paid to Intuit and Sage), their Microsoft 365 plans, and the MSP's own fee. Each client sits in its own project, so servers, backups and access stay apart.

Remote Desktop design should be standardized before onboarding clients

“RDP” is often used as shorthand for several different remote-access patterns. MSPs should distinguish them.

Access patternBest fit
Restricted admin RDPMSP technicians or one administrative user
RDS Session HostMultiple client users need Windows desktop or RemoteApp sessions
RD GatewayControlled remote access for RDS users across external networks
VPN/private accessInternal services, file shares, or management paths
Web applicationClient users only need browser access

Microsoft describes Remote Desktop Services as the Windows Server platform for delivering managed desktops and applications to users across offices, homes, branches, and partner locations.

If ordinary staff use an RD Session Host, every person who signs in needs a Remote Desktop licence, so the user count belongs in the quote and the onboarding. On Raff that licence is a Subscriber Access License at $8 per person a month, licensed and reported by Raff; the MSP's job is to keep the count equal to the people who sign in.

Read RDS CAL Licensing on Windows Server and Remote Desktop Gateway vs Direct RDP before standardizing client remote-access packages.

Build service tiers around workload, not employee count

A 20-person company might have only two people using the Windows server. A 6-person accounting office might keep five concurrent RDS sessions open all day. Employee count is not enough for sizing.

Start with concurrent users + application load + database load + storage growth + backup window.

Client workloadStarting planning rangeWatch for
1-2 administrative users2 vCPU / 4 GB RAMBackground tools, antivirus, app services
3 light remote users4 vCPU / 8 GB RAMBrowsers, PDFs, Office workloads
3 business-app users8 vCPU / 16 GB RAMAccounting, tax, Access, legacy apps
About 5 active users8 vCPU / 16 GB RAMPersistent sessions and reporting
About 10 active users8 vCPU / 32 GB RAMShared desktop workload throughout the day
Heavy ERP/SQL workload8-16 vCPU / 32 GB RAMDatabase and RDS session contention; beyond 32 GB, give the database its own server

These are starting points, not guarantees. The application vendor's requirements and real client behavior should override a generic sizing table.

A useful MSP pattern is to define three or four internal service profiles such as light app, standard business app, multi-user RDS, and heavy database/app. Then monitor real usage and resize only when the workload shows the need.

Use Windows VPS sizing for remote users for the detailed sizing process.

Compare Raff Windows VM plans after estimating concurrent users, application load, memory, storage, and recovery requirements.

Backups must be part of the MSP contract

Backups are not an optional infrastructure checkbox once a client depends on the server.

Define the recovery service in business terms:

Backup decisionWhat the MSP should define
RPOHow much recent data the client can lose
RTOHow long the workload can be unavailable
VM backupWhether the full Windows environment is recoverable
File-level backupWhether individual documents and folders can be restored
App-aware backupSQL Server, accounting, ERP, or other stateful app protection
RetentionHow many restore points and how long they are kept
Off-server copyWhere recovery data exists outside the VM
Restore ownerWho performs the recovery
Test cadenceHow often a real restore is validated

The client should understand what “backup included” actually means. A restore after accidental deletion is different from full VM recovery, database point-in-time recovery, or ransomware recovery.

A good MSP agreement says what is protected, what is not protected, how often backups run, how long data is kept, and what recovery time is realistic.

Use Windows VPS Backup Strategy for Small Businesses when defining the client policy.

Define backup frequency, retention, off-server recovery, and restore testing before the client environment goes live.

Migration is where an MSP can add the most value

A client moving from an office server rarely needs only a VM. They need discovery and risk reduction.

A repeatable MSP migration process can be:

  1. Inventory the source server, users, apps, files, databases, jobs, printers, and integrations.
  2. Identify which workloads move, rebuild, retire, or remain local.
  3. Confirm application vendor support and licensing.
  4. Define user access and RDS requirements.
  5. Build the destination Windows VPS.
  6. Apply the MSP security and monitoring baseline.
  7. Configure backups before production data is moved.
  8. Migrate non-production data or restore a test copy.
  9. Test with real client users.
  10. Validate printing, file paths, reports, exports, and scheduled jobs.
  11. Schedule the final cutover.
  12. Keep the source environment available for rollback until the new system is proven.
  13. Record final configuration and hand the environment into normal support operations.

The value of the MSP is visible here: a hosting provider can supply a Windows VM, but the MSP understands the customer's applications, deadlines, users, and operational risk.

If the client is replacing local infrastructure, read Local Office Server to Cloud Windows VPS Migration, File Server Migration to Windows VPS, and SQL Server Migration to Windows VPS.

Security should be a repeatable baseline

Do not configure every client server from memory.

A minimum MSP Windows baseline should cover:

AreaBaseline question
Admin identitiesAre technicians using named admin accounts?
Client identitiesAre users separated from administrators?
RDP exposureIs direct public access minimized and restricted?
FirewallAre inbound rules documented and limited?
Patch policyIs there a maintenance window and restart process?
Endpoint/security toolingIs the chosen Windows security stack configured and monitored?
LoggingAre failed logins and critical events reviewed?
BackupsCan ordinary users or compromised credentials delete recovery data?
Vendor accessIs temporary third-party access controlled and removed afterward?
OffboardingCan one user be removed without disrupting the whole environment?

Microsoft publishes Windows security baselines and the Security Compliance Toolkit for recommended configuration guidance. These are useful starting points, but an MSP should not present a generic baseline as proof of compliance with a client's industry requirements.

Monitoring must map to an action

A dashboard alone is not a managed service. Each alert needs an owner and response expectation.

Useful Windows VPS monitoring for MSP clients includes:

SignalWhy it matters
CPUDetect sustained workload pressure
RAMCatch memory exhaustion before sessions fail
Disk free spacePrevent profile, database, backup, and export failures
Backup statusDetect failed recovery jobs
Windows servicesConfirm business-critical services remain running
RDS session countUnderstand real concurrency
Failed loginsSurface suspicious or broken access
Event logsTroubleshoot repeated OS or application failures
Application logsIdentify problems before the client reports them
Patch/restart statusKeep maintenance visible and controlled

For every signal, decide whether it creates a ticket, sends an alert, pages an engineer, or is only reviewed during scheduled maintenance.

Documentation is what makes the service transferable

The environment should not depend on the technician who built it.

Each client record should contain:

DocumentMinimum contents
Client workload summaryWhat the VM does and who depends on it
VM specificationvCPU, RAM, storage, Windows version, region
User/access modelAdmins, users, RDS, RD Gateway, VPN/private access
Licensing notesWindows, RDS, SQL, and application licensing responsibilities
Application inventoryInstalled software, versions, vendor contacts, dependencies
Backup policyFrequency, retention, restore owner, last restore test
Monitoring policySignals, thresholds, response owner
Change logUpgrades, incidents, migrations, major changes
Recovery runbookSteps to restore service
Offboarding planData export, credential removal, retention, server retirement

Store the recovery instructions somewhere accessible even when the client VM is unavailable.

Checklist visual for MSPs managing Windows VPS client environments including sizing, access, backups, monitoring, security, and documentation

Choose the infrastructure provider around MSP operations

MSPs should compare Windows providers on operational fit rather than only the lowest VM price.

Ask:

Provider questionWhy it matters to an MSP
Which Windows Server versions are available?Client app support may depend on the OS version.
Is Windows licensing clear?Licensing confusion creates quoting and compliance risk.
Do you get full administrator access?MSPs need control of the client server.
How is Remote Desktop access delivered?Initial deployment and troubleshooting depend on it.
Are backups/snapshots available?Recovery should not require building everything from scratch.
Can the VM be resized?Client workloads change over time.
Is migration assistance available?Office-server replacement is often the actual project.
Is infrastructure support available 24/7?MSP escalation paths matter during incidents.
Is pricing understandable month to month?MSPs need predictable client margins.
Can each client environment remain isolated?Security, billing, and offboarding are cleaner.

For four Windows hosts MSPs use, compared on these questions from each host's own pages, read Windows hosting for MSPs: Raff vs HVENS vs OVHcloud vs Leaseweb.

How Raff fits MSP client hosting

Raff fits MSPs that want a Windows infrastructure provider underneath their own managed-service offer.

The current Raff Windows VM service supports Windows Server 2019, 2022, and 2025, provides full administrator access through RDP, licenses Windows Server ($6 per vCPU a month, 2 vCPU minimum) and Remote Desktop users ($8 per person a month) under its SPLA and files the report, and offers 24/7 infrastructure support. Raff also provides migration assistance for teams moving Windows workloads from another provider or local infrastructure.

That means the MSP can focus on the client layer: applications, users, RDS, security policy, backups, monitoring, documentation, and support—while using Raff for the cloud Windows VM foundation.

Raff should not be described as the MSP for the client. The cleaner model is:

Text
Raff = Windows infrastructure layer MSP = managed service, client operations, applications, users, backups, monitoring, and support

That boundary makes it easier to package a repeatable client service and keep the end-customer relationship with the MSP.

Give your team Windows desktops on one server, $8.00 per person a month.

See Remote Desktop hosting

MSP client environment checklist

Before production, confirm:

CheckDone
Client workload and business owner documented[ ]
Application vendor support checked[ ]
Concurrent user count estimated[ ]
Windows Server version selected[ ]
VM size selected from workload, not company headcount[ ]
Admin access method documented[ ]
Staff RDS requirements reviewed[ ]
Remote Desktop user count matches the people who sign in[ ]
Client environment isolated from unrelated customers[ ]
Firewall/security baseline applied[ ]
Backup frequency and retention defined[ ]
Restore owner and RPO/RTO defined[ ]
Restore test completed or scheduled[ ]
Monitoring signals and escalation path documented[ ]
Patch window agreed with client[ ]
Migration rollback plan written[ ]
App support boundary documented[ ]
Offboarding/export process documented[ ]

If those items are repeatable, the MSP has a service model. If every answer is different for every client, the next step is standardization before scaling sales.

What's next

Sources

Was this article helpful?

Frequently asked questions

Should each MSP client get its own VPS?
Yes, in most cases: one environment per client gives isolation, clean per-client billing, simpler documentation, and painless offboarding. Shared servers save little and complicate everything the day a client leaves or has an incident.
How do MSPs standardize client environments?
With a template: the same base build, access model, backup policy, monitoring, and documentation applied per client. Repeatability is what makes ten client servers manageable by a small team.
How does billing work for MSP-hosted clients?
Each client environment is a predictable monthly cost that resizes with that client's growth, which maps cleanly onto per-client pricing. No shared-hardware cost allocation debates.
What should be documented per client environment?
Access model and who holds admin, backup schedule and restore test date, firewall rules, licensing (Windows, RDS, applications), and the rollback plan. If the engineer who built it leaves, the document is the environment.
Does an MSP need its own SPLA agreement to host clients on Raff?
No. Raff is the SPLA licensee for Windows Server and Remote Desktop users on its servers and files the monthly report, so an MSP using Raff's licences files nothing for them.
Does an included Windows licence cover Remote Desktop users and SQL Server?
No. On Raff the Windows licence ($6 per vCPU a month, 2 vCPU minimum) covers Windows Server only. Remote Desktop users are $8 per person a month, and SQL Server is a separate licence available from Raff.

Published July 3, 2026 · Updated November 17, 2026

Back to hub

Give your team Windows desktops on one server, $8.00 per person a month.

Windows Server with the licence included, and a Remote Desktop licence from Raff for each person who signs in. No CALs to buy, and you raise or lower the count any month. One person from $42.99 a month.

14-day money-back guarantee

Related articles