Lacerte Remote Access: A CPA’s Practical Setup Guide

Your staff accountant is working from home. Your client just uploaded the last K-1. Tax season doesn’t pause, but your office server is locked behind a VPN that drops every 45 minutes. If that scenario sounds familiar, you already know why Lacerte remote access matters—and why getting it wrong costs you billable hours.

This guide covers the three main paths to remote Lacerte access, the exact steps to configure each, and the specific failure points that catch firms off guard.

The Three Paths to Remote Lacerte Access

Before touching any settings, understand what you’re actually choosing between.

Option 1 — Intuit’s own hosted environment (via Rightworks) Intuit partners with Rightworks to deliver cloud-hosted Lacerte. You log in through a remote desktop session; the software and client files live on Rightworks infrastructure. According to Rightworks, Lacerte hosted this way can be accessed from anywhere on any device. Intuit’s own product page confirms it provides remote access, real-time collaboration, and security on any device.

Option 2 — Third-party managed cloud hosting Providers like Sagenext host Lacerte on their own managed infrastructure and deliver it via a remote desktop session. You get multi-user access, managed backups, and software updates handled for you—without depending on a single vendor relationship.

Option 3 — Generic RDP or Citrix into your own server You maintain an office terminal server and connect to it remotely. An Intuit community response confirms that Intuit does not support generic remote access unless you’re using Lacerte’s remote host, but also notes that Lacerte should work as if you’re at the office when accessed through Citrix or similar RDP tools. Translation: it can work, but you own the support burden entirely.

Setting Up Intuit’s Hosted Environment: Step by Step

If you go the Rightworks/Intuit route, here is what the onboarding actually looks like.

Step 1 — Run the setup wizard on each workstation Intuit’s onboarding guide instructs users to download and run RightworksSetupWizard.exe, then select “Just set up your computer” to configure that machine for hosted access. Do this on every device that needs access—not just one.

Step 2 — Understand the one-session-at-a-time rule This trips up firms constantly. Intuit’s hosting onboarding guide is explicit: only one computer can access the hosted environment at the same time with the same login. If a second device signs in with the same credentials, the first session gets kicked off. For a firm with two staff sharing one Lacerte license, this means scheduling who accesses what and when—or buying separate logins.

Step 3 — Register each client file before processing If you use Lacerte’s Remote Entry Processing (REP), each client file must be registered with Lacerte through a short transmission before a return can be processed or printed. You can start this from the Clients tab, by pressing F5, or from Forms by selecting R.E.P. Access and then choosing either Transmit Now or Transmit Later. Skipping this registration is one of the most common reasons a return won’t print in a remote session.

Step 4 — Coordinate software updates carefully This is non-negotiable on terminal server setups: Intuit’s terminal server guidance states that all users must be out of Lacerte to perform an update. Schedule updates during off-hours and communicate the window to your team. One person staying logged in while another pushes an update will corrupt the session for everyone.

Step 5 — Know where to call when something breaks Intuit’s Lacerte Hosting FAQ says users can reach a Lacerte Hosting expert by calling 800-933-9999 and saying “Hosted.” Support hours are generally weekdays from 8 a.m. to 8 p.m. CST, with variation throughout the year. Keep that number somewhere your staff can find it at 7:45 p.m. on April 14th Intuit.

Running Lacerte on Your Own Terminal Server

If you already have a terminal server and want to keep it, here’s the lean version of what matters.

• Use Citrix or a standard RDP client. Lacerte behaves as if local when the terminal server is configured correctly.
• Store the Lacerte data folder on a mapped network drive that every user session can reach consistently.
• Lock down who can push updates. One admin account, update window set, everyone else read-only on the installer directory.
• Test the REP transmission process from a remote session before tax season, not during it.

The downside: when the server has a hardware problem at 10 p.m. in February, that’s your problem. No managed backup kicks in automatically. No one patches the OS for you.

How Sagenext Helps

For a 10-person firm, managing your own terminal server for Lacerte means someone on your team is also functioning as an IT admin—patching Windows Server, monitoring disk space, and scheduling backups. That’s not why you hired them.

Sagenext hosts Lacerte on fully managed infrastructure and delivers it as a remote desktop session your staff can reach from any device. Provisioning, data backups, security, and software updates are all handled on your behalf. Multi-user access is built in, so you’re not engineering around single-session login conflicts yourself.

You can start with a free trial—no credit card required—to verify that Lacerte runs the way you need it to before committing.

Lacerte Remote Access Compared at a Glance

Common Mistakes That Cost Time

Sharing one login across two users. The session-kick behavior is not a bug—it’s by design. If two people need simultaneous access, they need separate credentials.

Skipping REP registration. A return that won’t print remotely is almost always a registration step that got skipped. Transmit the file first, every time.

Running updates mid-session. One user who ignores the “please log out” message can break a multi-user update and force everyone to close work they haven’t saved.

Not testing remote access before busy season. The setup wizard, the REP process, and update coordination should all be validated in October or November—not April 13th.

For a deeper look at how multi-user Lacerte setups behave on shared infrastructure, see our related guide on How Lacerte Tax Software Hosting Benefits Tax Preparers.

Key Takeaways

• Run RightworksSetupWizard.exe on every workstation that needs hosted Lacerte access, not just one machine.
• One login supports one active session at a time; a second device signing in kicks the first session off—plan user credentials accordingly.
• Register every client file via REP transmission before attempting to process or print a return remotely.
• All users must be out of Lacerte before any software update runs in a terminal server or hosted environment.
• Generic RDP into your own server works but puts the full support and maintenance burden on your firm.
• Managed cloud hosting removes the server administration overhead so your staff can focus on returns, not infrastructure.

Frequently Asked Questions

Can two staff members access hosted Lacerte at the same time?

Yes, but not with the same login. Intuit’s hosted environment allows only one active session per login credential. If a second device authenticates with the same username, the first session is terminated immediately. Each concurrent user needs a separate login. For firms with multiple preparers working simultaneously, plan your license count around that requirement before tax season starts.

What is Remote Entry Processing in Lacerte and why does it matter for remote access?

REP is Lacerte’s mechanism for registering a client file with Intuit’s servers before you can process or print a return. You initiate it from the Clients tab, the F5 key, or from Forms via R.E.P. Access. In a remote session, this step is easy to overlook—and when it’s skipped, the return simply won’t print. Transmitting the file first takes under a minute and prevents a frustrating dead-end later.

Does Intuit support using Lacerte through a generic RDP or Citrix connection?

Intuit does not provide support for generic remote access setups. However, Intuit’s community documentation acknowledges that Lacerte should function as if you’re at the office when accessed through Citrix or a standard RDP connection to a properly configured terminal server. You won’t get Intuit’s help desk support for that configuration, so your firm owns any troubleshooting.

When can I call Intuit for Lacerte hosting support?

Lacerte Hosting support is available by calling 800-933-9999 and saying “Hosted” when prompted. Support hours are generally weekdays from 8 a.m. to 8 p.m. CST, though hours vary at different points in the year. During peak tax season, expect wait times—calling early in the day or early in the support window tends to reach someone faster.

What’s the difference between Intuit-hosted Lacerte and a third-party host like Sagenext?

Both deliver Lacerte via a remote desktop session. The primary differences are in infrastructure ownership, support relationships, and flexibility. Intuit’s hosted option runs on Rightworks infrastructure with Intuit as the coordination point. Third-party hosts like Sagenext manage their own infrastructure and can host multiple accounting applications—QuickBooks, Sage, ProSeries, Drake—alongside Lacerte in the same environment, which simplifies access for firms using more than one platform.