Windows Server

What we configure on Windows Server

On Windows Server we build the Active Directory domains that manage users, computers and network permissions across your business, with one or more domain controllers to keep the domain running even if one machine goes offline. We pair this with file servers that use granular per folder permissions, disk quotas and the recycle bin, so a file deleted by mistake does not require a full restore from backup. Where email needs to stay in house we also configure on premises Exchange Server, with its mailboxes and transport rules.

We do not install these roles on undersized hardware. We assess whether the domain controller, file server and any Exchange role should run on separate physical machines or on virtual machines, often on Proxmox, the virtualisation platform we use for most of the projects we handle. This lets us consolidate several Windows Server roles on less physical hardware, with snapshots and backups managed at the infrastructure level, not just on the individual server.

• Active Directory and domain controllers
• File servers with permissions and quotas
• On premises Exchange Server
• Role virtualisation on Proxmox

Typical scenarios and when it is not the right fit

Windows Server remains the right choice for businesses running Windows native management software that needs a local domain, technical firms with shared CAD files on network folders with complex permissions, or businesses that still keep Exchange on premises for regulatory or legacy integration reasons. It is also the typical backbone for networks with multiple sites that need to share the same user identities across a single domain.

It is not the right fit when your business has no applications tied to a local domain and only needs email, files and collaboration: in that case Microsoft 365 avoids maintaining hardware, CAL licences and security updates on a physical server in the office. We assess this case by case: sometimes the sensible answer is hybrid, with a smaller local Active Directory domain and email moved to Exchange Online.

How we work: from project to maintenance

We start by reviewing the number of users, the applications tied to the domain and the layout of your sites before sizing the project. We design the Active Directory structure, organisational units, groups and group policies, then install and configure the domain controllers and file servers in our Melzo lab, where we test the environment before moving it into production at the client site.

After testing, we keep supporting the infrastructure with ongoing maintenance: planned security updates, domain controller monitoring and independent backups that we verify periodically, not just configured once and left alone. We handle both in warranty and out of warranty support on the physical hardware Windows Server runs on, with HP, Dell or Lenovo hardware also available on operational rental for the periodic refresh of your servers, without tying up capital in a direct purchase.

Security, backup and end of life

Backup of an Active Directory domain and a Windows file server needs to be independent from the server itself: if the domain controller fails, the backup must allow a restore onto different hardware, not just a rollback of the same disk. We plan regular copies with periodic restore tests, because a backup that has never been tested is often useless exactly when you need it most.

We also track the end of life of Windows Server versions: when a version leaves Microsoft support, we plan the upgrade before the lack of security patches becomes a real risk for the domain. We support clients who need to comply with the NIS2 directive with access controls, patch management and domain monitoring in line with the required obligations.