Estate271
Servers: physical, on-premises and Azure.
Employees in the business5,000+
Across Australia and New Zealand.
Operating rhythmChange. Recover. Learn.
- CAB-reviewed changes
- 100+ changes raised and run through CAB
- DR test every six months, none failed
- Written incident reviews
Capacity decision4 → 2 vCPUs
Right-sized three batch-processing VMs in Azure from 4 to 2 vCPUs when the workload dropped, which cut the cost.
Next improvementsLess routine upkeep
Moving a 3 TB file and print server used by 150 to 200 admin staff to Azure, with DFS namespaces to bring file sharing up to standard, and rebuilding the production information server for a paper mill on Windows Server 2025. Exploring Server Core and modern app delivery.
HardeningHarden by default.
Switched off SMBv1 and IE11, retired TLS 1.0 and 1.1 with TLS 1.3 as the standard, and turned on LSA protection, all through Group Policy.
ProductionA platform a mill runs on.
I own patching for the 18 production servers behind a paper mill, from the vendor’s approved update list and a patch calendar agreed with the site before each shutdown. In 2026 I built new terminal and web servers and moved the session broker off the database server before the June shutdown.
Delivery at scale12 sites, about 35 cutovers.
A server refresh across 12 sites in Australia and New Zealand, then about 35 cutovers consolidating site file servers into central and Azure storage.