A ten-person firm with a Windows Server under the desk has a familiar problem when half the staff work from home: the domain controller that holds their logins and group policies, and the shared applications that only run on Windows, are reachable only from the office. The usual fix is to move both to hosted Windows Servers. This guide walks through the design for 5 to 25 users: why the domain controller and the Remote Desktop session host should be two servers, how to size them from Microsoft's own sizing guidance, which licences are involved and which are rented monthly, and the handful of hardening rules that make a hosted domain controller safe.
Why move the domain controller at all
Active Directory Domain Services is still the identity layer for most small Windows networks: it holds the user accounts, applies Group Policy to the machines, and authenticates everything from file shares to the accounting package. Microsoft Entra ID (the former Azure AD) covers Microsoft 365 sign-in, but Windows applications that expect a domain, line-of-business software with Windows authentication, printers and file servers with NTFS permissions, and Remote Desktop Services all still want a domain controller. A hybrid setup with Entra Connect synchronising the on-premises domain to Entra ID is the normal pattern, and it needs the domain controller to be reachable and backed up, which a server in a cupboard with a consumer broadband line is not.
Hosting the domain controller in a data centre gives it a static IP address, a 10 Gbps port, a cluster that restarts it on another node if the hardware fails, and daily backups, without buying hardware. It also puts it next to the session host, so the logon traffic between them never crosses the internet.
One server or two
Two. The temptation at ten users is to run Active Directory, the file shares and Remote Desktop Services on one Windows Server and save a licence. Resist it for three reasons.
- Security. Microsoft's guidance on securing domain controllers is that they should be secured separately and more stringently than the general infrastructure, that no web browser should be used on them, and that RDP to them should be allowed only from authorised users and jump servers. A session host is the opposite: a machine where every user signs in, opens a browser and runs whatever the business runs. Putting both on one server means every user has an interactive session on the box that holds every password hash in the company.
- Remote Desktop Services does not want to be on a domain controller. Installing the Remote Desktop Session Host role on a domain controller is technically possible but changes the local security policy in ways that give ordinary users log-on rights to the DC, and the Remote Desktop Connection Broker role will not install on a domain controller at all. Microsoft's RDS documentation assumes member servers.
- Operations. A session host gets rebooted for application installs, driver updates and the occasional hung session. A domain controller should reboot only for Windows Update. Separate servers mean separate maintenance windows and a smaller blast radius.
The design for 5 to 25 users is therefore one small domain controller and one session host sized to the user count, both in the same city at MassiveGRID so authentication stays on the local network, with the file shares on the session host or on the domain controller's data disk (acceptable at this scale, though a third file server is cleaner once you pass about 25 users). A second, read-only or full domain controller in another city is the step after that, when the business cannot afford to lose logons during a server restore.
Sizing for 5, 10 and 25 users
The domain controller is light. For a single domain with a few dozen objects, 2 vCPUs, 4 GB of RAM and 64 GB of NVMe is comfortable; the AD database for a small firm is tens of megabytes and the server idles. On the Windows VPS that is $22.20 a month on shared cores with the licence ($2.87 per vCPU and $6.31 per vCPU for Windows Server, plus $0.80 per GB of RAM and $0.01 per GB of NVMe). A domain controller does not need reserved cores.
The session host is where the sizing matters. Microsoft's session host sizing guidelines (Microsoft Learn, updated July 2025, read on 8 November 2026) give these figures for multi-session hosts: light workloads such as data entry support up to 6 users per vCPU, medium workloads (Office, static web pages) 4 users per vCPU, heavy workloads (Outlook, PowerPoint, dynamic web pages, development) 2 users per vCPU, and the recommended minimum configuration for a multi-session host is 8 vCPUs and 16 GB of RAM, with 4 vCPUs the smallest Microsoft considers stable for several concurrent users. The same page notes that a VM costs 15 to 20 percent of capacity against bare metal and that memory is often the limit at small sizes. In practice, budget 1 GB of RAM per light user, 2 GB per office user with Outlook and a browser, and 4 GB for the operating system, as a planning figure to be checked against your own usage.
| Users (medium office workload) | Session host | Reserved cores? | Monthly server cost at MassiveGRID |
|---|---|---|---|
| 5 | 4 vCPU, 12 GB, 128 GB NVMe | Shared cores are usually fine | Windows VPS with licence: $47.60 |
| 10 | 4 vCPU, 24 GB, 192 GB NVMe | Reserved cores recommended | Windows Dedicated VPS with licence: $92.36 |
| 25 | 8 vCPU, 56 GB, 256 GB NVMe | Reserved cores | Windows Dedicated VPS with licence: $193.68 |
The Dedicated VPS rates are $5.74 per vCPU, $1.60 per GB of RAM and $0.03 per GB of NVMe, plus the $6.31 Windows licence per vCPU. Reserved cores matter on a session host because twenty people typing at once produce exactly the kind of sustained, bursty CPU demand that shared cores schedule badly; see the Remote Desktop VPS page for the two tiers side by side. Above 25 users Microsoft's advice is to add a second host and load balance rather than keep growing one; two 8 vCPU hosts behave better than one 16 vCPU host. If you would rather have the operating system patched and backed up for you, the same roles run on the managed Windows Server hosting tiers at $24.75 per vCore.
The licences involved
Four licences are in play, and only two of them come from the hosting provider.
- Windows Server. Rented monthly under Microsoft's Services Provider License Agreement (SPLA) at $6.31 per vCPU on each server, billed with the server and cancelled with it. There is nothing to activate or report on your side. Each server starts on Microsoft's 180-day evaluation if you prefer, and is converted in place when the licence is added.
- RDS client access licences. Every user or device that connects to a session host needs an RDS CAL, and a Remote Desktop Licensing server to issue them; Microsoft allows a 120-day grace period before the licensing server must be in place. MassiveGRID rents per-user RDS licences at $8.90 per user per month, so ten staff on the session host add $89.00 a month. Two administrative sessions are included on every Windows Server for administration without CALs; they are not for users. The RDS CALs guide covers per-user versus per-device and the version rules.
- Microsoft Office. Office on a session host is licensed through Microsoft 365, not through the host. At the time of writing, Microsoft 365 Apps for enterprise (and the E3 and E5 suites and Business Premium that include it) support shared computer activation on Remote Desktop Session Hosts, while the Apps for business edition in Business Basic and Business Standard does not; confirm the current rule for your plan on Microsoft Learn before buying, because a session host full of Office installs that will not activate is a common and expensive surprise.
- Line-of-business applications. Sage, QuickBooks Desktop, legal or practice-management software and similar are licensed by their vendors, usually per user or per installation, and several require you to tell the vendor the software is on a terminal server. Check before you move them.
Windows Server and RDS CALs are the parts a hosting provider can supply under SPLA. See the SPLA hosting page for what else can be rented monthly and what must be brought.
Hardening a hosted domain controller
A domain controller with a public IP address is a target the moment it exists. The rules below follow Microsoft's securing domain controllers guidance and the practice we see hold up.
- No RDP to the domain controller from the internet. Allow 3389 on the DC only from the session host's internal address and from a VPN or jump host. On MassiveGRID servers the Windows firewall and the per-server firewall both let you scope the rule to a source address. Users never log on to the DC; administrators do so from a management session, not from their daily account.
- Publish the session host through a gateway or a VPN, not bare 3389. Remote Desktop Gateway wraps RDP in HTTPS on port 443 and authenticates against the domain before a session is opened; alternatively a WireGuard or IPsec VPN to the hosted network. Either way the session host's 3389 is closed to the internet. Our RDP hardening guide has the step-by-step for network level authentication, account lockout and port rules.
- Multi-factor authentication on the gateway. Entra ID multifactor authentication through the NPS extension, or a third-party RADIUS provider, on the RD Gateway. Passwords alone on a public endpoint are not acceptable in 2026.
- Keep internal traffic internal. Put the two servers on a private network so LDAP, Kerberos, SMB and DNS between them never traverse a public address; expose only the gateway port.
- No browsing on the DC, Server Core if you can. Microsoft's guidance is blunt: no web browser should be used on domain controllers. Install Server Core, manage with Windows Admin Center or RSAT from the session host, and block outbound internet from the DC except Windows Update and the Entra Connect endpoints.
- Tiered administration. Separate domain admin accounts from the accounts people use on the session host, and never sign in to the session host with a domain admin account; a credential-stealing tool on a session host should not be able to harvest the keys to the forest.
- Back up the DC as a DC. Daily VM backups with snapshots are included on the managed tier and configurable on the VPS, but a domain controller restore needs system-state awareness; take a Windows Server Backup system state regularly to the data disk or a second location, and test an authoritative restore once, on a test VM, before you need it.
A worked example for twelve users
A twelve-person accountancy practice in Manchester, with staff split between the office and home, moves its office server to two Windows Servers in MassiveGRID's London data centre.
- Domain controller: Windows VPS, 2 vCPU, 4 GB, 64 GB NVMe, Windows Server 2025 Server Core, licensed: $22.20 a month. Roles: AD DS, DNS, Entra Connect for Microsoft 365 sign-in, Remote Desktop Licensing.
- Session host: Windows Dedicated VPS, 4 vCPU reserved, 28 GB, 256 GB NVMe, Windows Server 2025 with Desktop Experience, licensed: $100.68 a month. Roles: Remote Desktop Session Host, RD Gateway, file shares for the practice documents, the tax software and Microsoft 365 Apps for enterprise under shared computer activation.
- RDS user licences for twelve users: $106.80 a month.
- Total: $229.68 a month for the two servers and the RDS licences, before Microsoft 365 and the tax software's own licences, with both servers on the HA cluster, daily backups and 100% uptime SLA.
Office staff and home workers connect through the RD Gateway on 443 with Entra MFA, get the same desktop and applications on any device, and the practice owns a domain that no longer depends on a box in the back room. When the firm grows past 25 users, the second session host and the second domain controller are configurator orders, not a hardware purchase.
Frequently Asked Questions
Can I run Active Directory and Remote Desktop Services on the same hosted server?
You can install both, but you should not. Microsoft's guidance is to secure domain controllers more stringently than other servers, with no user sign-ins, no browsing and RDP only from administrators, while a session host is where every user signs in and runs applications. The Remote Desktop Connection Broker role will not install on a domain controller at all. Run a small domain controller and a separately sized session host, in the same city so authentication stays on the private network.
How big does the session host need to be for ten users?
For ten office users running Outlook, a browser and a line-of-business application, plan on 4 vCPUs with reserved cores, about 24 GB of RAM and 192 GB of NVMe, which is $92.36 a month on a MassiveGRID Windows Dedicated VPS with the Windows licence. Microsoft's sizing guidance puts a medium workload at four users per vCPU and treats 4 vCPUs as the smallest stable multi-session host; memory is usually the limit at this size, so budget around 2 GB per office user plus 4 GB for Windows.
What licences do I need for staff to log on to the session host?
Each user needs an RDS client access licence, issued by a Remote Desktop Licensing server after Microsoft's 120-day grace period; MassiveGRID rents per-user RDS licences at $8.90 per user per month alongside the Windows Server licence at $6.31 per vCPU. Office needs a Microsoft 365 plan that supports shared computer activation, such as Microsoft 365 Apps for enterprise or Business Premium at the time of writing, and line-of-business applications keep their vendors' own licences.
Is a domain controller with a public IP address safe?
Only if it is locked down. Allow RDP to it solely from the session host and a VPN or jump host, expose nothing else, keep LDAP, Kerberos, SMB and DNS on a private network between the servers, run Server Core with no browser and no general outbound internet, use separate domain admin accounts that are never used on the session host, and publish the session host through Remote Desktop Gateway or a VPN with multi-factor authentication rather than open port 3389.
What happens to logons if the domain controller is restored from backup?
A single domain controller restored from a VM backup comes back with the directory as of the backup, and anything changed since (new users, password changes) is lost; Active Directory also needs the restore to be handled as a system state restore to avoid replication problems once a second DC exists. Keep regular Windows Server Backup system state copies and, when the business depends on uninterrupted logons, add a second domain controller in another MassiveGRID city so one can be restored while the other keeps authenticating.
Windows Servers for the domain and the desktops
MassiveGRID runs Windows Server 2016 to 2025 on a Proxmox HA cluster in New York, London, Frankfurt or Singapore: a Windows VPS from $3.99 a month for the domain controller, a Windows Dedicated VPS with reserved cores from $18.84 for the session host, the Windows licence at $6.31 per vCPU and RDS user licences at $8.90 per user, all rented monthly under SPLA and billed with the servers. Managed tiers with the operating system patched and backed up for you are available on every size.
See Windows Server hostingFurther Reading
- Microsoft Learn: Session host virtual machine sizing guidelines (users per vCPU by workload)
- Microsoft Learn: License Remote Desktop Services with client access licenses (120-day grace period, CAL types)
- Microsoft Learn: Securing domain controllers against attack
- Microsoft Learn: Overview of shared computer activation for Microsoft 365 Apps
- Microsoft Learn: Remote Desktop Gateway role