To set up a small office network with Windows Server Essentials, give the server a static IP, install Active Directory Domain Services and DNS, promote it to a domain controller for a new forest, create users and security groups, share folders with NTFS permissions, join Windows 11 Pro PCs to the domain, apply Group Policy and schedule backups.
Written by the Softkeyworld technical team · Updated October 2026
Most offices with five to twenty-five people reach a point where a shared drive on someone's PC and a router doing everything stops working. Passwords are reused, nobody knows who has access to the accounts folder, a leaver still has files on a laptop, and backups are "someone copies things to a USB drive on Fridays". A single Windows Server running Essentials edition fixes most of that: one sign-in per person, central file storage with proper permissions, policies pushed to every PC, and one place to back up.
This guide covers building that network from scratch. The steps apply to Windows Server 2019, 2022 and 2025 Essentials, and equally to Standard edition if you outgrow Essentials. If the server is not installed yet, follow our Windows Server 2022 Essentials download, install and activation guide first.
Key takeaways
- Essentials is limited to 25 user accounts and 50 devices on a single-processor server, and needs no CALs within those limits.
- Since Windows Server 2019, Essentials no longer has the old dashboard wizard; you configure standard roles yourself.
- Every PC must point to the server for DNS, or domain sign-in will fail.
- Windows 11 Home cannot join a domain. You need Pro, Enterprise or Education.
- A domain controller without backups is a single point of failure. Plan backup on day one.
Is Essentials the right edition?
Essentials is the same Windows Server operating system as Standard, with licensing limits that suit small businesses. Microsoft's Windows Server 2025 licensing guidance describes it as ideal for up to 25 users and 50 devices, on single-socket servers with up to 10 cores.
| Aspect | Essentials | Standard |
|---|---|---|
| User and device limit | 25 users, 50 devices | No fixed limit (licensed by CALs) |
| Client access licences | Not required | Required per user or device |
| Processor | Single socket | Licensed per core, multi-socket |
| Virtualisation | Physical or one VM (limited) | Two VMs per fully licensed host |
| Multi-user Remote Desktop Services | Not intended for this | Yes, with RDS CALs |
| Typical use | Domain, files, printing, small apps | Growing businesses, virtualised hosts, RDS |
If you expect to pass 25 staff within a couple of years, or want staff to work on a shared remote desktop, go straight to Standard. Our guides to Windows Server CALs and setting up Remote Desktop Services cover that route.
On versions: Windows Server 2022 left mainstream support in October 2026 but, per the Windows Server 2022 lifecycle page, continues to receive security updates under extended support until October 2031. That is a long runway for a small office server; our article on Server 2022 mainstream support ending explains what changes and what does not.
Step 1: Plan the network
Ten minutes of planning saves hours later. Decide these before you touch the server:
| Item | Example | Notes |
|---|---|---|
| Router / gateway | 192.168.10.1 | Your internet router or firewall |
| Server IP | 192.168.10.10 | Static, outside the DHCP range |
| Server name | DC01 | Set before promotion; renaming a DC later is awkward |
| AD domain name | ad.yourcompany.co.uk | Subdomain of a domain you own; avoid .local |
| NetBIOS name | YOURCO | Short, 15 characters or fewer |
| DHCP | Server, range .100–.200 | Or keep it on the router, but hand out the server as DNS |
The hardware does not need to be exotic. A tower server with a single modern CPU, 32 GB of RAM, mirrored SSDs for the OS and mirrored larger drives for data, plus a UPS, handles a typical 20-person office comfortably. The UPS is not optional: unexpected power loss is a common cause of directory and file corruption.
Step 2: Prepare the server
- Activate Windows and install all updates via Settings > Windows Update.
- Rename the server:
Rename-Computer -NewName DC01 -Restart. - Set a static IP in Control Panel > Network and Sharing Center > Change adapter settings > IPv4 properties. Set the preferred DNS server to the server's own IP (or 127.0.0.1 after promotion), not your router.
- Check the time zone and clock. Active Directory authentication (Kerberos) fails if clocks drift more than five minutes apart.
Step 3: Install Active Directory and promote the domain controller
- In Server Manager choose Manage > Add Roles and Features, select Role-based or feature-based installation, and tick Active Directory Domain Services. Accept the additional management tools.
- When installation completes, click the yellow notification flag and choose Promote this server to a domain controller.
- Select Add a new forest and enter your root domain name, for example
ad.yourcompany.co.uk. - Leave Domain Name System (DNS) server and Global Catalog ticked, and set a strong Directory Services Restore Mode (DSRM) password. Store it in your password manager.
- Ignore the DNS delegation warning (expected for a new forest), review the options and click Install. The server restarts as a domain controller.
The PowerShell equivalent is Install-WindowsFeature AD-Domain-Services -IncludeManagementTools followed by Install-ADDSForest -DomainName ad.yourcompany.co.uk -DomainNetbiosName YOURCO -InstallDns.
After the restart, open DNS Manager, right-click the server, choose Properties > Forwarders and add your ISP's or a public resolver's addresses so the server can resolve internet names for clients.
Step 4: Configure DHCP
You have two options. Moving DHCP to the server gives you better integration (clients register in DNS automatically). Keeping it on the router is fine, provided you change the router's DHCP DNS setting to hand out the server's IP. Never leave both running on the same subnet.
To use the server: add the DHCP Server role, click Complete DHCP configuration in Server Manager to authorise it in AD, then in the DHCP console create a new IPv4 scope with your range, router (option 003), DNS server (option 006, the server IP) and DNS domain name (option 015). Disable DHCP on the router once the scope is active.
Step 5: Create users, groups and file shares
In Active Directory Users and Computers (dsa.msc), create an organisational unit for your company with sub-OUs for Users, Computers and Groups. Group Policy cannot be linked to the default Users and Computers containers, so this structure matters. Create one account per person (never shared logons) and a security group per team, such as GRP-Finance and GRP-Sales.
For file shares, create a folder structure on the data volume, for example D:\Shares\Finance. Then:
- Share the top-level folder with Authenticated Users: Full Control at share level.
- Control actual access with NTFS permissions on the Security tab: disable inheritance on each department folder and grant the matching group Modify.
- Turn on access-based enumeration in the share's properties (File and Storage Services > Shares) so people only see folders they can open.
- Enable Shadow Copies on the data volume so users can restore previous versions themselves.
Always assign permissions to groups, not individuals. When someone changes role, you move them between groups instead of hunting through folder permissions.
Step 6: Join the PCs to the domain
Only Windows 11 Pro, Enterprise and Education can join an Active Directory domain. If some PCs came with Home, a Windows 11 Home to Pro upgrade key converts them in place without reinstalling.
- Confirm the PC receives the server as its DNS server:
ipconfig /all. - Open Settings > System > About > Domain or workgroup, click Change, select Domain and enter the domain name.
- Enter domain admin credentials when prompted and restart. Or use PowerShell:
Add-Computer -DomainName ad.yourcompany.co.uk -Restart. - Move the computer object into your Computers OU so policies apply.
- Copy any local user files into the new domain profile, or use OneDrive to carry them across.
Step 7: Apply Group Policy basics
Open Group Policy Management (gpmc.msc). A handful of policies deliver most of the value in a small office:
- Password and lockout policy in the Default Domain Policy: long passphrases and account lockout after repeated failures.
- Mapped drives via Group Policy Preferences, targeted by security group, so Finance automatically gets the F: drive.
- Screen lock after a period of inactivity.
- Windows Update settings so PCs install updates within a defined window rather than deferring indefinitely.
- Folder redirection of Documents and Desktop to the server, if you want user files centrally backed up.
Run gpupdate /force on a client and gpresult /r to confirm the policies applied.
Step 8: Printing, backup and remote management
Printing: install the Print and Document Services role, add printers in Print Management, and deploy them to PCs via Group Policy. One driver install on the server beats twenty on the desks.
Backup: add the Windows Server Backup feature and schedule a daily backup of the full server, including system state, to a dedicated external or network target. Follow the 3-2-1 rule: three copies, two media, one off-site. Test a file restore every quarter; a backup you have never restored is a hope, not a plan.
Management: install Windows Admin Center on an admin PC for a browser-based view of the server's health, updates, storage and event logs.
Basic security hardening
A domain controller holds the keys to every account in the business, so treat it accordingly:
- Use a separate admin account for server work and a normal account for email and browsing. Never browse the web on the server.
- Keep Microsoft Defender Antivirus enabled on the server and every PC, and install monthly updates promptly.
- Do not expose Remote Desktop on the server to the internet. Use a VPN on your firewall for remote administration.
- Disable accounts for leavers on their last day, and review group membership every few months.
Common problems after setup
Almost every small-office domain problem we are asked about comes back to DNS. Check these first:
| Problem | Usual cause | Fix |
|---|---|---|
| "An Active Directory Domain Controller for the domain could not be contacted" when joining | PC is using the router or a public resolver for DNS | Point the PC's DNS at the server, then retry |
| Slow sign-in or slow mapped drives | Clients have a secondary public DNS server configured | Remove external DNS from clients; use forwarders on the server instead |
| Users see folders they cannot open | Access-based enumeration not enabled | Enable it on the share |
| Group Policy not applying | Computer or user object still in the default container | Move it into the OU where the policy is linked |
| Time or Kerberos errors in the event log | Clock drift between PC and server | Ensure the DC syncs to a reliable time source and clients sync to the domain |
Frequently asked questions
Do I need CALs with Windows Server Essentials?
No. Essentials includes access for up to 25 users and 50 devices without separate CALs. Above those limits, you need Standard edition with CALs.
Where did the Essentials dashboard go?
The Essentials Experience role, with its dashboard and client connector, was removed starting with Windows Server 2019. You now use standard tools like Server Manager and Windows Admin Center.
Can Windows 11 Home PCs use the server?
They can access shared folders with a username and password, but cannot join the domain, receive Group Policy or use domain sign-in.
Should I use .local for my domain name?
We advise against it. A subdomain of a domain you own avoids conflicts with multicast DNS and makes certificates and cloud integration simpler.
Is one domain controller enough?
For a small office it is common, but only with reliable, tested backups that include system state. A second DC adds resilience if you have the licensing and hardware.
Our recommendation
For an office under 25 people that wants central sign-in, controlled file sharing and simple management without per-user licensing, Windows Server Essentials remains a cost-effective foundation. Get DNS right, use groups for permissions, standardise PCs on Windows 11 Pro, and test your backups. If your headcount is close to the limit, choose Standard now rather than migrating in a year.
Get Windows Server 2022 Essentials
Related reading
| Resource | Why read it |
|---|---|
| Server 2022 Essentials install guide | Install and activate the server first |
| Windows Server CALs explained | Understand licensing if you move to Standard |
| Server 2022 mainstream support ends | Plan your server lifecycle |