How to Run Accounting Software on a Windows RDP Server for Your Team

To run desktop accounting software for several users or branches, install the program and its database on one Windows server and let each user connect to it over RDP. Everyone works on the same live database, nothing syncs between offices, and the data stays on the server instead of on office PCs. To do it properly you need the right licences (Windows Server remote desktop licences plus a multi-user licence from your software vendor), a server sized for your concurrent users, and database backups that leave the server every day.

Why companies move accounting software to a server

The pattern is familiar in Egyptian companies. The accounting program runs on one PC in the head office. A second branch opens, or the accountant needs to work from home, and copies of the database start travelling by flash drive and email. Within weeks there are two versions of the truth. A server fixes this:

• One database: the Cairo office, the Alexandria branch and the accountant at home all post to the same books.

• Work from anywhere: a laptop, a home PC or even a tablet becomes a window onto the server.

• Less office risk: a dead hard drive, a stolen PC or an office internet outage no longer stops the books.

• Central control: you add or remove a user in one place, and a departing employee loses access in minutes.

For more ways businesses use a Windows server, see Windows VPS uses for business and remote work.

How it works: RDP sessions vs a network database

There are two ways to put an accounting program "on a server", and they behave very differently over the internet:

• Full RDP session (recommended): the program and the database both run on the server. Users only send keystrokes and receive screen updates. A modest connection is enough, and the database never travels over the internet.

• Program on each PC, database on the server: every screen and report pulls data across the network. This works inside an office LAN but is slow over the internet, and file-based databases can be damaged when a connection drops mid-write.

A third option, RemoteApp, shows only the accounting program window instead of a full desktop. It needs the Remote Desktop Services role and its licensing, which is covered below. If your users have never used RDP, our guide on connecting to RDP from Windows, Mac and phones walks them through it.

Sizing the server: rules of thumb per concurrent user

Count concurrent users, not total employees. Ten staff who log in at different times may only need capacity for four or five. Then start from these rules of thumb and check your vendor's stated requirements:

• Baseline: Windows Server plus the database engine need around 4 GB RAM and 2 vCPU before any user logs in.

• Per user: add roughly 0.5 to 1 GB RAM for each concurrent user of a typical desktop accounting program, and more if they also open Excel or a browser in the session.

• CPU: plan about one vCPU for every three to five light users. Month-end reports and inventory recalculation are the peaks to size for.

• Disk: NVMe storage helps the database most. Leave space for at least a week of local backups.

Worked examples: 5 concurrent users fit in about 4 vCPU and 8 GB RAM; 10 to 15 users in about 6 to 8 vCPU and 16 GB; beyond 25 users, consider 32 GB or more, or a separate database server. IM HOST Windows VPS plans run in 13 tiers from 4 GB to 256 GB RAM with isolated resources, so you can start at the size your user count needs and move up as you add branches.

Licensing: the part people skip

Technically, RDP will let several people connect. Legally, three separate licences are usually involved, and you must confirm each one before going live:

1. Windows Server and its client access licences. Out of the box, Windows Server allows two simultaneous sessions for administration. Regular staff working through RDP need the Remote Desktop Services role with RDS CALs, licensed per user or per device, in addition to Windows Server CALs.

2. The accounting software itself. Many desktop licences are per PC and do not allow use on a terminal server. Vendors often sell a network or multi-user edition, sometimes priced per concurrent user. Ask specifically whether running on a remote desktop server is permitted.

3. The database engine and Office. If the program uses Microsoft SQL Server, check which edition you are allowed to use; the free Express edition is limited in size and resources. If users export to Excel inside the session, Office needs licensing for that server use too.

Licensing rules change and depend on your agreement. Confirm with Microsoft or an authorised Microsoft licensing partner, and with your accounting software vendor, before you move real users onto the server.

Database backups you can trust

Accounting data is the one dataset a company cannot recreate. A sensible schedule:

• A nightly database backup, plus an extra one before every month-end and year-end close.

• Copies moved off the server daily, to cloud storage or a second location.

• Retention of about 30 daily and 12 monthly copies as a rule of thumb.

• A restore test on a copy of the database every month. Open it in the program and compare a trial balance.

If your program uses its own built-in backup tool, use it and follow the vendor's guidance on closing the program first. If it runs on SQL Server Express, which has no SQL Agent scheduler, you can run a PowerShell script from Windows Task Scheduler:

$d = Get-Date -Format yyyy-MM-dd
sqlcmd -S .\SQLEXPRESS -E -Q "BACKUP DATABASE [AccountsDB] TO DISK = N'C:\Backups\AccountsDB-$d.bak' WITH CHECKSUM"
sqlcmd -S .\SQLEXPRESS -E -Q "RESTORE VERIFYONLY FROM DISK = N'C:\Backups\AccountsDB-$d.bak'"

Replace AccountsDB and the folder with your own database name and path, and create the folder first. The second line checks that the backup file is readable.

Security for a server that holds your books

• One Windows user per person. Never share the Administrator account, and keep only one or two people in the Administrators group.

• Permissions inside the program. Separate roles for accountants, cashiers and managers, so a cashier cannot edit closed periods.

• Restrict RDP. Allow it only from your branches' fixed IPs where possible, and enable account lockout after repeated failed logins.

• MFA where possible. An MFA solution for Windows logon or a Remote Desktop Gateway adds a second factor in front of RDP.

• Idle sessions. Set session time limits by Group Policy so forgotten sessions sign out at night.

• No browsing on the server. Email and web browsing in the same session are the most common way malware reaches business data.

Printing and local files

RDP redirects local printers through Remote Desktop Easy Print, so most office printers appear inside the session without installing drivers on the server. Thermal receipt printers and some label printers are the exception and may need the manufacturer's driver installed on the server; test them before cut-over. When printing is unreliable, exporting invoices to PDF and printing locally is a dependable fallback. For importing bank statements or price lists, enable drive redirection so users can reach files on their own PC.

Where to place the server

RDP is sensitive to delay because every keystroke travels to the server and back. Host it close to your branches. IM HOST has data centers in Cairo, London, Berlin, Warsaw and New York; services are available across our locations subject to stock, and we confirm your location before activation. If you are weighing a hosted desktop program against moving to a web-based system, our CRM vs ERP hosting guide compares the hosting needs.

A safe migration order

1. Record the program version and licence details.

2. Take a full backup on the current PC.

3. Install the same version on the server and restore the backup.

4. Test with one user: posting, reports, printing.

5. Create user accounts and permissions.

6. Switch after a closing day, then keep the old copy read-only for reference.

Frequently asked questions

Can I run my accounting program on an RDP server?

Technically most Windows desktop accounting programs run fine in an RDP session. Whether your licence allows it is a separate question; confirm with the vendor.

How many users can work on one server?

It depends on RAM and CPU. As a rule of thumb, 8 GB covers about five concurrent users and 16 GB about ten to fifteen, provided you have the RDS licences for them.

Is accounting software slow over RDP?

Usually it feels faster than a shared network database, because only the screen travels. Slowness normally means the server is undersized or far from the users.

Do I still need backups if the server is in a data center?

Yes. A data center protects against power and hardware problems, not against a wrong deletion, ransomware or a bad update. Keep your own copies off the server.

If you are ready to move your books to one place, start with a Windows VPS with full Administrator and RDP access sized for your concurrent users. Our engineers are available 24/7 to help you plan the setup.