Tax Software Hosting on Windows VPS: Remote Access Guide (2026)

In short

Tax software hosting on a Windows VPS can work well when the tax application's vendor supports Windows Server or hosted Remote Desktop deployments. The important part is compatibility: do not assume that software which runs on a Windows 11 workstation is automatically supported on Windows Server, RDS, or a third-party cloud VM.

Raff Technologies provides Windows VMs that can host supported Windows workloads for tax firms, accountants, and MSP-managed practices. Before production, confirm the exact tax year and software version, supported Windows Server release, multi-user model, RDS requirements, data paths, printers and scanners, backup method, and vendor support policy.

The vendor differences are meaningful in 2026. Drake Tax currently lists Windows Server 2019, 2022, and 2025 as supported operating systems and supports dedicated-server network configurations. Lacerte currently documents Windows Server 2016, 2019, and 2022 as file-server operating systems and lists Windows Remote Desktop Services or Citrix as hosted-environment options. TaxAct Professional's current public system requirements list Windows 11, not Windows Server, so a generic Windows Server VPS should not be presented as supported without direct confirmation from TaxAct for the exact deployment.

Is a Windows VPS a good fit for your tax software?

Use this decision table before selecting infrastructure.

A Windows VPS is the infrastructure layer. It does not override the tax software vendor's licensing, operating-system support, or deployment rules.

Tax software hosting is a seasonal infrastructure problem

Tax practices often have a sharp difference between off-season and filing-season demand. A server that feels comfortable in summer can become constrained when more preparers connect, more PDF documents are open, and more client data is processed during peak filing periods.

Plan for the busiest realistic period, not average annual use.

If the tax platform is business-critical, treat the Windows VM as production infrastructure from day one.

Vendor compatibility comes before VM sizing

The correct order is:

1. Confirm the exact software and tax-year version.
2. Confirm the vendor-supported operating system.
3. Confirm whether server, network, RDS, Citrix, or hosted deployment is supported.
4. Confirm application and user licensing.
5. Then size the VM and design remote access.

A technically successful installation is not the same as a vendor-supported deployment.

Drake Tax on Windows Server

Drake's current system-requirements documentation, updated in April 2026, lists these supported operating systems for the desktop version:

• Windows 11
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Drake also states that its software can be networked with a dedicated server, which it recommends, or with a peer-to-peer network. Its current documentation says Windows Server 2016 is no longer supported after Drake Tax 2025.

That makes Drake a clearer candidate for a Windows Server VM than software whose vendor only lists a desktop operating system. Still verify the exact tax-year release, licensing, integrations, scanners, and multi-user workflow before migration.

Lacerte on Windows Server and RDS

Lacerte's current public requirements are more specific. Intuit currently lists Windows Server 2016, 2019, and 2022 as supported file-server operating systems and lists Windows Remote Desktop Service or Citrix as supported hosted-environment patterns. The same requirements specify at least 2 GB RAM per user for the hosted environment.

That is useful evidence for firms researching how multiple preparers can access the same Lacerte environment, but it also creates an important limitation: the current public requirements do not list Windows Server 2025 as a supported Lacerte file-server OS. Do not choose Server 2025 for Lacerte only because it is Microsoft's newest LTSC release. Follow Intuit's current compatibility list for the exact Lacerte release.

Lacerte also states that file-share and sync services such as Dropbox, Google Drive, and OneDrive are not supported for its data storage, backup, or sharing purposes. Use the vendor's supported data architecture instead of placing the live tax database in a generic sync folder.

TaxAct Professional on a Windows VPS

TaxAct needs a different answer. Its current 2026 public Professional system-requirements page lists Windows 11 as the supported operating system and does not list Windows Server in that requirements table. TaxAct also provides its own local-network and cloud-networking options for Professional editions.

Therefore, do not market a standard Windows Server VPS as automatically supported for TaxAct Professional. If your firm specifically wants TaxAct on Raff, confirm the intended deployment directly with TaxAct and document the supported architecture before production.

This distinction matters because users already search for phrases such as "TaxAct VPS." The safe answer is compatibility first, not "Windows software means it will work on Windows Server."

Windows Server version choice is application-specific

Windows Server 2025 is the current Microsoft LTSC release, but tax software vendors can certify operating systems on a different schedule.

Vendor requirements change. Recheck them before each major tax-year upgrade instead of treating this table as permanent compatibility certification.

Use Windows Server Version Comparison after the tax vendor has established which Server versions are acceptable.

Remote access: administrative RDP is not the same as employee RDS

A common small-business mistake is deploying one Windows Server and treating unrestricted administrator RDP as the multi-user workplace.

Use the access model that matches the job:

Microsoft states that a user or device connecting to an RD Session Host running Windows Server requires the applicable RDS access licence. In a customer-owned Microsoft licensing model, this generally means RDS User or Device CALs. In a Raff-hosted SPLA deployment, hosted RDS access follows the applicable service-provider licensing model, including RDS User SALs.

The licensing path and the technical RDS configuration should be decided before staff begin using the server.

Read RDS CAL Licensing Guide for the distinction and Remote Desktop Gateway vs Direct RDP before publishing Remote Desktop access to the internet.

Security is part of the tax-software architecture

Tax practices store taxpayer information that is valuable to attackers. In June 2026, the IRS again reminded tax professionals that a Written Information Security Plan, or WISP, is required and should be tailored to the firm's size, scope, complexity, and sensitivity of customer data.

The IRS Security Summit checklist also recommends core controls including antivirus protection, a firewall, multifactor authentication where offered, backup software or services, drive encryption, and secure VPN use.

For a hosted Windows Server, translate that into concrete infrastructure controls:

• give every preparer a named account;
• separate administrator accounts from daily user accounts;
• restrict inbound access instead of exposing RDP broadly;
• use MFA-capable access layers where the architecture supports them;
• keep Windows and the tax application patched;
• protect and monitor backup credentials separately from normal user access;
• encrypt appropriate data at rest and in transit;
• review failed logons and security events;
• limit file permissions to the users who need the client data;
• document offboarding for seasonal staff;
• keep the security and recovery plan outside the server itself.

Use the Windows Server Hardening Checklist as the technical baseline. This article is infrastructure guidance, not legal or regulatory advice; firms should apply their own compliance and professional-adviser requirements.

Size for peak concurrent preparers, not employee count

The old approach of saying "five tax users need exactly X vCPU and Y GB RAM" is too rigid. Tax applications have different vendor requirements, and the same number of users can generate very different load depending on PDFs, browser sessions, document management, scanners, SQL components, and other applications running in the same RDS session.

Collect these inputs first:

• peak concurrent preparers;
• vendor minimum and recommended memory;
• vendor-specific per-user RDS memory guidance;
• CPU utilization during return calculation and reporting;
• PDF/document workload;
• user-profile size;
• current and prior-year client-data size;
• backup and snapshot storage;
• other applications that run in the same sessions;
• peak-season growth margin.

For Lacerte specifically, Intuit's current hosted-environment requirements call for at least 2 GB RAM per user in supported RDS or Citrix environments. That is a vendor minimum for Lacerte, not a complete VM sizing formula. Windows, security software, profiles, browser/PDF tools, and other applications also need memory.

Use Windows VPS Sizing for Remote Users to map the measured workload to current Raff VM tiers instead of relying on stale hard-coded plan sizes.

Storage planning must include the whole client workflow

The tax application installer is usually a small part of the storage footprint.

Plan capacity for:

Do not place live application data in OneDrive, Dropbox, or another sync folder unless the tax-software vendor explicitly supports that architecture. Both Lacerte and TaxAct publish restrictions around file-sync services for application data workflows.

Backup design: snapshots help, but they are not the backup strategy

Use several recovery layers where the workload requires them:

Define the business targets before choosing frequency:

• RPO: how much recent tax-work data can the firm afford to lose?
• RTO: how long can preparers be unable to work?

A backup job showing "successful" does not prove that the tax application and client data can be restored. Test representative recovery before peak season.

Use Windows VPS Backup Strategy for Small Businesses for the broader recovery design.

Printers, scanners, PDF tools, and portals need real-user testing

Tax workflows often combine the tax application with hardware and browser-based services. Test from the same endpoints and networks staff will use in production.

For Lacerte, Intuit specifically documents printer and scanner requirements and notes that DMS requires a TWAIN-compliant driver. Drake also lists TWAIN-compliant scanners for relevant document workflows.

Do not discover these limitations during a filing deadline.

Plan updates around filing deadlines

Windows and tax-software updates are both necessary, but production changes should have a maintenance process.

A practical sequence is:

1. Confirm the latest good backup.
2. Check vendor release notes or support notices.
3. Apply the change during a low-impact window.
4. Reboot if required.
5. Confirm Windows services and RDS availability.
6. Launch the tax application with a normal user account.
7. Open representative client data.
8. Test PDF, printing, scanning, and e-file related workflow where applicable.
9. Confirm the next backup completes.

A snapshot can provide a convenient short rollback point before an update, but it should not replace application-aware backup and restore testing.

Migration to a Windows VPS before tax season

Avoid changing the production platform close to a major filing deadline unless the current environment has a more serious failure risk.

Use a side-by-side migration when practical:

Existing tax environment stays available
-> Build the Windows VM
-> Confirm OS and vendor compatibility
-> Configure RDS and secure access
-> Install the exact tax application version
-> Copy non-production/test data
-> Validate preparer workflows
-> Configure and test backups
-> Schedule final data synchronization
-> Cut users over
-> Keep controlled rollback available

For firms moving from an office server, use Server Migration to Cloud: Local Windows Server Guide for the cutover and rollback framework.

Windows VPS vs vendor-hosted tax software

A self-managed Windows VPS is not always the best answer.

For example, Intuit also sells a hosted Lacerte option. A firm that only needs Lacerte and wants the vendor-aligned hosted experience should compare that with managing its own supported RDS environment. A firm or MSP that needs multiple supported Windows applications, custom access controls, or its own server administration may prefer a Windows VM.

The right answer is based on workload ownership, not simply which option is called "cloud."

How Raff fits tax software hosting

Raff is a fit when the vendor-supported architecture requires a Windows Server VM and the firm or its MSP wants control of the server environment.

A Raff Windows VM can provide the infrastructure for supported workloads including:

• Windows Server application hosting;
• Remote Desktop/RDS environments;
• centralized application and client-data workflows;
• private networking;
• NVMe-backed VM storage;
• snapshots and backup options;
• seasonal VM resizing when the workload needs more resources.

Raff does not certify tax applications on behalf of Drake, Intuit, TaxAct, or another vendor. Vendor compatibility, tax-software licensing, client-data controls, RDS design, Windows administration, and compliance remain part of the deployment plan.

For Microsoft licensing, Raff can provide Windows Server through SPLA, while eligible customer BYOL depends on the customer's Microsoft agreement and applicable rights. Review Windows Server Licensing on Raff before production.

Pre-deployment checklist for tax firms

• Exact tax product and tax-year version documented
• Vendor-supported Windows version confirmed
• Server/RDS/hosted deployment support confirmed
• Application licence and concurrent-user model confirmed
• Windows Server SPLA or eligible BYOL path selected
• RDS licensing path selected if staff use Session Host
• Peak concurrent preparers estimated
• Vendor memory guidance recorded
• Client-data and PDF storage growth estimated
• Printers and scanners tested
• File paths and application-data locations documented
• Named user and administrator accounts separated
• Remote access restricted and hardened
• Backup layers configured
• Representative restore tested
• WISP/security controls mapped to the hosted environment
• Update and reboot window defined
• Production migration and rollback runbook written
• Real preparers completed acceptance testing

If vendor support is unclear, resolve that before buying or migrating production infrastructure.

Frequently asked questions

Can I host tax software on a Windows VPS?

Yes, when the tax-software vendor supports the exact Windows Server, network, RDS, or hosted architecture you plan to use. Compatibility varies by vendor and tax-year release, so a successful installation alone is not enough evidence for production support.

Does Drake Tax support Windows Server 2025?

Drake's current public system requirements list Windows Server 2019, 2022, and 2025 for the desktop version. Confirm the exact Drake Tax release and your network, licensing, scanner, and multi-user requirements before deployment.

Can multiple preparers use Lacerte through Remote Desktop Services?

Intuit's current Lacerte requirements list Windows Remote Desktop Service or Citrix as hosted-environment options on supported file-server operating systems and specify at least 2 GB RAM per user. The current page lists Windows Server 2016, 2019, and 2022, not Windows Server 2025.

Can I run TaxAct Professional on a Windows Server VPS?

Do not assume it. TaxAct Professional's current public system requirements list Windows 11 and do not list Windows Server in the operating-system requirements. TaxAct also provides its own network options. Confirm your intended hosted/server architecture directly with TaxAct before production.

Do remote tax preparers need RDS licensing?

When employees use RD Session Host on Windows Server, the deployment needs the applicable Microsoft RDS licensing. Customer-owned licensing generally uses RDS User or Device CALs. Raff-hosted SPLA environments follow the applicable service-provider licensing model, including RDS User SALs.

Is a VM snapshot enough to protect client tax data?

No. A snapshot is useful for short-term rollback, but production recovery should also include the application/vendor-supported backup method, appropriate file or VM backups, an off-server recovery path, and tested restores.

Does moving tax software to a cloud VM satisfy IRS security requirements?

No. Hosting location alone does not satisfy a tax firm's security obligations. The IRS states that tax professionals need an information security plan and recommends safeguards such as antivirus, firewalls, multifactor authentication where available, backups, encryption, and secure remote-access practices.

Validation scope

This article was revalidated on September 11, 2026 against current public documentation from Drake Software, Intuit Lacerte, TaxAct Professional, Microsoft Remote Desktop Services, and the IRS.

No "Tested on Raff" claim is made for Drake, Lacerte, or TaxAct because this refresh does not have a current named-engineer compatibility test and screenshot for those applications. Vendor requirements remain the source of truth for supported software versions and deployment models.

What's next

• Raff Windows VM - review the Windows infrastructure platform.
• Raff Pricing - check current VM, storage, backup, and licensing pricing.
• Windows Server Licensing - review SPLA, eligible BYOL, CAL, and RDS licensing.
• RDS CAL Licensing Guide - understand multi-user Session Host licensing.
• Windows VPS Sizing for Remote Users - size for peak concurrent users and actual workload.
• Remote Desktop Gateway vs Direct RDP - choose a safer remote-access model.
• Windows Server Hardening Checklist - secure the production server.
• Windows VPS Backup Strategy for Small Businesses - design recovery before filing season.
• Server Migration to Cloud - plan migration and rollback from an office server.
• Windows VPS for MSP Client Environments - standardize tax-firm environments managed by an MSP.

Sources

• IRS - Written Information Security Plans are essential for tax pros: https://www.irs.gov/newsroom/written-information-security-plans-are-essential-for-tax-pros
• IRS - Tax Security 2.0: Taxes-Security-Together Checklist: https://www.irs.gov/tax-professionals/tax-security-2-point-0-the-taxes-security-together-checklist
• IRS - Protect Your Clients; Protect Yourself: https://www.irs.gov/tax-professionals/protect-your-clients-protect-yourself
• Drake Software - Drake Tax System Requirements: https://kb.drakesoftware.com/KB/Drake-Tax/11776.htm
• Drake Software - Network Setup: https://kb.drakesoftware.com/kb/Drake-Tax/11851.htm
• Intuit Accountants - Lacerte system requirements: https://accountants.intuit.com/support/en-us/help-article/product-system-requirements/lacerte-system-requirements/L4QtkL7WO_US_en_US
• TaxAct Professional - System Requirements: https://www.taxact.com/professional/system-requirements
• TaxAct Professional - Tax Year 2026 setup resources: https://www.taxact.com/professional/resources/setupguide
• Microsoft Learn - RDS Client Access Licenses: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license
• Microsoft Learn - Install RDS CALs: https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-install-cals
• Sources revalidated: 2026-09-11