Save 10%Pay yearly on any plan. 6% half-yearly, 3% quarterly. Help centreWhatsAppTelegram TeamsOpen a ticket

How to Set Up a Secure Private RDP for Your Business

A plan for a team that shares a remote Windows server: one account per person, least privilege, access through a VPN, sign-in protection and backups.

4 min readBy Swati

Reviewed by the AmazingRDP technical team

Setting up a secure private RDP for a business

A private Windows server for your team, with full administrator access. See Windows VPS from $8.99

A private RDP server gives a small business a shared Windows machine that staff reach from anywhere: the accounting program lives there, the files are in one place, and nobody needs a powerful laptop. Because it holds the company's data and faces the internet, it has to be set up as a company system, not as one person's remote PC. This is a plan in the order to carry it out. The technical settings for a single server are in securing RDP on your server; here the subject is people and process as well.

1. Start with the right kind of server

A business needs a private server, where it controls accounts and settings: see what a private RDP is. A shared remote desktop has no administrator rights and is not meant for company data.

TeamStarting size
2 to 3 people, office programs4 cores, 8 GB of memory
5 to 10 people8 cores, 16 to 32 GB; consider a dedicated server

Count about 2 GB for Windows and 1 to 2 GB for each person working at once, more with heavy programs.

2. Know the licensing rule

Windows Server lets two administrators connect at once for administration. More people working on the desktop at the same time requires the Remote Desktop Services role and a client access licence for each user or device. Plan for this before five people try to log in on Monday morning; ask support what applies to your plan.

3. One account per person

  • Never share a login. With one account for everyone, nobody can say who did what, and a departing colleague takes the password along.
  • Staff get standard user accounts. Only one or two people hold administrator accounts, and they use those only for administration.
  • Rename or disable the built-in Administrator once your own administrator account works.
  • Put people in groups ("Accounts", "Sales") and give rights to groups, not to individuals.
New-LocalUser -Name "anna" -FullName "Anna Example" -Password (Read-Host -AsSecureString)
Add-LocalGroupMember -Group "Remote Desktop Users" -Member "anna"

4. Do not expose Remote Desktop to the whole internet

A Remote Desktop port open to everyone receives password guesses within hours. In rising order of protection:

MeasureEffect
Lockout policy and long passwordsMakes guessing impractical. The minimum
A different portCuts the noise from automated scans, nothing more: see RDP on a different port
Firewall rule limited to your office's fixed addressStrong and simple, if staff work from fixed places
A VPN in frontRemote Desktop is reachable only for devices connected to your VPN. The usual answer for teams that travel: see understanding VPNs
Remote Desktop GatewayMicrosoft's own front door over HTTPS, with policies per user

5. Protect the sign-in

  • Network Level Authentication on. It is the default; leave it.
  • Account lockout: for example 5 wrong attempts, 15 minutes.
  • Passwords of 14 characters or more, from a password manager.
  • A second factor for at least the administrators. On the VPN, or with a multi-factor product for Windows logon.

6. Limit what a session can carry out of the building

Drive and clipboard redirection let files move between the server and whatever PC a person connects from, including an infected home computer. Decide deliberately. In the Group Policy editor (gpedit.msc), under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Device and Resource Redirection, you can switch off drive redirection and, if needed, the clipboard. In the same area, under Session Time Limits, end sessions that have been disconnected for hours.

7. Give each person only the folders they need

  • A folder per department, with rights for that department's group.
  • Personal folders for personal work.
  • Nothing important on the desktop of a shared account.

8. Updates and protection

  • Windows updates every month, with the restart planned outside working hours.
  • Microsoft Defender on, including its ransomware protection for the data folders.
  • Remove software nobody uses.

9. Backups that are not on the server

The 3-2-1 rule: three copies, on two kinds of storage, one of them somewhere else. A backup on the same server is lost with it, and ransomware encrypts it along with the rest. Test a restore twice a year; an untested backup is a hope.

10. Watch the logs

Event (Security log)Means
4624, logon type 10A successful Remote Desktop login
4625A failed login. Hundreds per hour mean someone is guessing
4720, 4732An account was created; someone was added to a group

Look once a week. A login at three in the morning from an account whose owner was asleep is the kind of thing you want to notice yourself.

11. Joiners and leavers

  • New colleague: a personal account, the right groups, a short briefing on safe habits for RDP users.
  • Leaving colleague: disable the account the same day, end its sessions, change any shared secrets that person knew, then archive and remove the account later.

12. Write it down

One page: who the administrators are, where the backups go and how to restore, the provider's contact and control panel (what its buttons do), and what to do if a break-in is suspected: disconnect the server from the network, do not delete anything, change passwords from a clean device, and get help.

A note on personal data

If the server holds customers' or employees' personal data, data protection law applies to it, including where the server stands and who can reach it. That is a legal question for your own adviser; technically, the steps above are what such rules expect.

Private Windows servers for a team start with our Windows VPS plans; for larger teams see dedicated servers.

Questions

How do I secure RDP for a business?

Give each person an own standard account, keep Remote Desktop behind a VPN or a restricted firewall rule, enforce lockout and long passwords, and back up off the server.

Can several employees use one RDP server at once?

Yes, on Windows Server with the Remote Desktop Services role and a client access licence per user or device. Without it, two administrative sessions are allowed.

Should employees share one RDP login?

No. Shared logins make it impossible to tell who did what, and cannot be withdrawn from one person.

Is changing the RDP port enough?

No. It reduces automated noise but does not protect a weak password. Use a VPN or firewall restriction.