Stay on Windows Server if
- You need on-premises Exchange or a Microsoft Enterprise CA
- You run several sites that need read-only domain controllers
- A line-of-business program only runs on a Windows server
Samba can act as an Active Directory domain controller that Windows PCs join. It is not a full copy of Windows Server. Here is what it does, what Samba's own documentation says is missing, and how a NetYard plan works around each gap.
| Gap | What NetYard does |
|---|---|
| On-premises Exchange | Email stays in Google Workspace or Microsoft 365 |
| Microsoft Enterprise CA | Not planned. We raise it on the call if a program needs one |
| Read-only domain controllers | Not planned for a single small office |
| Sysvol replication between DCs | Raised on the call if you need a second domain controller |
| Network browsing | Shares are mapped by group, so nobody has to browse for them |
| Windows-only server programs | Listed on the free call, before anything is bought |
NetYard writes the plan for free: addressing, a Samba Active Directory on Debian that Windows PCs join, shared drives by team, guest Wi-Fi on its own network, a WireGuard VPN stub, a shopping list, install scripts, a user CSV, and a runbook. If you would rather not run it yourself, First Deploy AI builds it from that same written plan for $1,750 setup ($875 to start), then $250/mo. Hardware is bought separately.
The Samba wiki FAQ says Samba AD is stable for production environments, with AD DC support since version 4.0 in December 2012. Checked October 19, 2026.
NetYard does not plan on-premises Exchange, a Microsoft Enterprise CA, or read-only domain controllers on Samba. Samba's docs also list Sysvol replication and network browsing as unimplemented. Email stays in Google Workspace or Microsoft 365.
Yes. Windows PCs joined to a Samba domain receive Group Policy, and you edit policies from a Windows PC with Microsoft's free RSAT tools.
Plain-text sources, no outbound links. Each was read on the date shown. Prices change, so check before you buy.